robcat2075

A:M is all-spline modeling. The ways of polygon modeling are the worst way to use A:M. If you don't want to do the things that work best in A:M there isn't much i can do for you.

If you're trying to make models in A:M by putting primitives together... you're doing it wrong. Insisting on doing it the wrong way won't make the wrong way work. The giraffe tut in TaoA:M teaches essential techniques in modeling character bodies.

Here is a WIP thread in which i show many stages of building a simple-spline head from scratch... https://forums.animationmaster.com/topic/48269-paint-fall-image-contest-wips/#findComment-414056 Have you downloaded the "extended data set"? That has many sample characters in it. After you become familiar with how spline modeling works it is very instructive to examine other modelers' splining to learn how common objects are put together.

Follow your nose and bring your A:M questions to Live Answer Time at Noon CST, February 7, 2026! Walt Disney's "Pinocchio" premiered on this day in 1940 . Original trailer... Milt Kahl's Pinocchio...

As far as modeling... Have you done the exercises in "The Art of Animation:Master"? nos. 8, 9, 10 and 11 are fundamental to understanding how to model with splines. 11.5 is about making a face but I don't like that one since it is over complicated for new users and IMO uses too many splines for the shape it is making.

Not possible. Every window remembers its own setting and i believe the initial default is wireframe

Hi Lucas, You can select the various real-time display modes with the number keys at the top of the keyboard 0 Shaded wireframe 9 Shaded 8 wireframe 7 "default" (objects take on the "Object Render mode" chosen for them in the Project Work Space)

Which of those are the unwanted keyframes? Possible work-around, when just pressing the Delete Keyframe button doesn't work... click to a keyframe you want to delete draw a selection lasso around the keyed CPs, nudge them 1 pixel left and right with the cursor keys press the Delete Keyframe button It may take a few iterations of that to find and select all the CPS that are in a key in a complex mesh.

In my brief test I notice that I can click through and delete key frames in the expected fashion in v18, but not in v19.5 i will look at this some more.

Here is a simple Gerstner wave implemented in just one direction with muscle poses, then one more pose slowly displaces the CPs horizontally so that the wave is not one straight line. SimpleWaves.mp4 Waves015e simple.prj

Kevin brought in a great demonstration of the Gerstner Wave 00:00 Opening chit chat 02:13 Kevin's Gerstner Wave 29:08 Discussion of additive waves with muscle motion instead of bones 36:59 Implementing Gerstner motion with muscle mode pose sliders 53:22 Tiling possibilities 58:05 Cartoon: The Catanooga Cats sing "Birthday Suit" January 3, 2026

Yes, back to v15 IF... the problem was the video driver, then it would seem that something happened that damaged compatibility for OpenGL/OpenGL3 which is all A:M v19 has now. OR... maybe 15 was simpler and easier-to-emulate code, without all the processor-specific optimizations that Steffen has done in the last 15 years. OR... maybe just going back to 32-bit code had better compatibility. We didn't get around to trying 32-bit v19, i was just glad to see A:M working again. All-in-all I didn't know A:M would work at all on ARM so finding out that it was working fine until a week ago makes it extra mysterious.

Good news... A:M v15 will run in "Windows on ARM" with no compatibility settings needed. It appeared to be completely functional with proper GUI, graphics and even shaded wireframe mode. v15 still has Direct3D as a graphics driver option. i suspect that is the essential element.

Here are a few more options that only show up on an ARM computer. We got it so that A:M would load a PRJ without crashing but it didn't run well after that.

I have to think you are doing something other than what is described. I am able to delete keys in a smartskin, both whole and partial.

One of our users has a laptop running "Windows on ARM". Until a few days ago he was able to run A:M and it worked fine but now it crashes upon loading a PRJ. Steffen says this is due to the "OpenCL™, OpenGL® and Vulkan® Compatibility Pack" In Windows Settings one can choose to "uninstall" that pack but it reappears upon reboot. Does anyone know a solution?

Welcome back Edward! AFAIK CP movement in a smartskin is not displayable in graph form. However, when you have a smartskin window open, and are in muscle mode, you can use the Previous and Next keyframes buttons to jump through all the smartskin keys. When you find one you don't like you can press the Delete Keyframe button to vanquish that key or... draw a selection around specific CPs you don't want, then press Delete Keyframe to remove the keys on just those CPS.

Hi Mark, welcome back to A:M! I've sent you a PM with Filip's email

It wouldn't work very much. Jason maintains the website and the store. Steffen does the programming and all of that is communicated and logged via AMReports

Hi Jack, One may make feature suggestions at reports.animationmaster.com That site does not know your forum password so you will need to make an account there. Choose V19.5 at the upper right for current issues Use the same form that "issues" are reported with. For "Severity" choose "feature" I will caution you that most programming now is on fixing bugs as they are discovered, you will notice many suggested features that are not yet implemented, but... you can ask!

Here is a 3D render of my 3D model of my 3D Stereo Realist camera

That's really @Rodney's PRJ. If you right above the PRJ in his post there is a PNG there you can download.

At Live Answer Time we investigated making a sphere of randomly arranged stars entirely within A:M with no coding. Using expressions to randomly vary the X and Y rotation of a Bone with a star on the end of it got us the random placement of a star on the sphere. However, randomly varying the the X and Y Scale of the bone did not get us uniformly scaled stars.... the Random function was computed separately for each, creating fat and skinny stars A work-around I have found is to make a Pose that uniformly scales the Star, then use a random function to control that Pose slider value.

Non-embedded files get resaved with whatever state they are in in your current PRJ, even if you changed nothing about them when you do a PRJ save. If you don't want to overwrite your original starsphere, resave it under a new name after you first load it and use the resaved version.

I've never had a 3D TV to try such a thing with. Creating a 3D Blu-ray is probably what it would take, but 3D TVs and 3D blu-ray players are scarce now.