Could whoever posted the support ticket with a fake use name and fake email try again. Maybe with a real email address? I need to get a scene that demonstrates the problem. Can't do that with a fake user.

Yes I'm a bad nerd.I should have already done that tutorial.

If you rotate 2 axis to 90deg the third will appear to quit working. This is a "singularity" and it's a limitation of the Euler rotation system in Poser. Some people call this effect "gimbal lock"

If you use Posers direct Manipulation tool it can rotate through the singularity in most cases.

When working with mechanical object like this you'll probably want to disable bending of the mesh. It's on the Properties page for each body part. Useful for any mechanical rig. Wheels on cars, doors, chains any things that shouldn't bend when moved.

Open a support ticket at https://support.posersoftware.com/ we'll make sure it gets to the right desk.

It's believed this is caused by Windows "Background Activity Monitor" It's supposed to prioritize network traffic on the computer. Library loads work through the network even if the library is local. (The library window is really just a stripped down Chrome web browser.)

The "BAM" seems to incorrectly force all the library processes into a background thread. If you're brave (or crazy) the relevant registry key is here:

Computer\HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\bam\State\UserSettings\

Cleaning out all references for Poser in that key seems to rectify this condition. And, don't even try it unless you know what a registry key is and why messing with the wrong one will crash your computer.

Many years ago I found a Python called "WalkThisWay" it used a different approach. It didn't use walk designer at all. The way it functioned was to load a simple walking pose and then loop it. The script actually calculated the walk travel based on the movement of the feet.

I thought this was one of Ockham's but I can't find it on his site. I doubt it would even run in a current environment but it might be a starting point if anybody remembers who created that.

Is this what you're looking for? https://www.renderosity.com/premium-tutorials?section_id=1

Right ...

... There

Be careful deleting a split morph. There's a bug if you delete a morph that's been split Poser may crash. That bug was in there for a long time. Should be fixed in 13.1. Just save the scene and reload to be safe.

OK ..., before you start this have the Tylenol handy and have the straight jacket ready in case your mind just snaps.

There's a shopping list of pit-falls and traps in here. I can't cover them all off the top of my head.

First thing you need is to know a little tiny number. It's going to be the scalar for each of the rotations. We'll use Y and Z rotations in the example since that's probably what you're using here.

The scale for each individual rotation is 1 divided by the target rotation for the JCM. For example if the arms are rotated 75deg up the scale of the Z rot is 0.013333.

Figure out the rotation scale for Y and Z and write it down. Pay careful attention to positive and negative numbers. Polarity matters.

Before you start bake the morphs to be pre-Rotation.

1. Rotate all involved body parts to the target rotation on both axis

2. On a body part (Shoulder) select the context of the morph and choose the option to "Convert to pre-Transform morph". Don't do this on the BODY of the figure. It must be on the individual morphs on each body part.

If the option is grayed out that means it's already a pre-transform and you don't need to convert it.

OK it's finally time to make the dependencies. Don't use the "Start Teaching" thing. It can't create an interlocked dependency.

1. Select the master parameter for the JCM morph (Probably in the BODY, We'll assume it's called "JCMrArmFwdUp" in this example.

2. From the JCM's master dial click the context menu and choose edit dependencies.

3. On the Dependency Editor go to the Value Operator tab.

4. [Create New Value Op] > Delta Add

5. Choose the master actor (rShldr)

6. Choose the master parameter (y rotate)

7. In the scale factor type in the number you figured out for the Y rotation above (0.01333, it's always going to be a tiny number)

8. Did you get the +/- right. (I always mess this up at least once.)

Now we add the Multiply controller for the second rotation ...

9. [Create New Value Op] > Multiply

10. Choose the Actor and Parameter for the multiply operator

11. Type in the scale factor for the Z rotation

Close the DE and test the JCM performance.

Further brain droppings ...

Make sure you have limits set and enforced on the JCM 0 to 1. This prevents the JCM from running backwards.

You have to create the dependencies in the right order. The order of operations is critical. The multiply MUST be at the bottom.

If you don't value your sanity and really need it, a JCM can use all 3 axis of the joint to control it. Just add another multiply for the 3rd axis.

What's going on in Poser's brain for this is the rotation of the first (Y) is added to the JCM morph then the value of the JCM is multiplied by the second (Z). That's why the order is so important Add 1 then multiply by 0 it results in 0. But if you Multiply by 0 and then add 1 you get 1. And that's not correct. For JCM the multiply will always be last.

If you need a JCM can have multiple body parts as controllers. Add each additional body part and parameter as a multiply. An example would be a JCM thats active only when the shoulder and collar are both dialed. (This is not recommended for real production. It's just too complicated)

You should probably switch to Ray traced shadows. That looks like the kind of artifacts depth mapped shadows will produce.

Make sure to enable raytracing in the render settings and set bounces to at least 2.

Download Manager doesn't work any more. It was A Smith Micro program and wasn't included when Bandware bought Poser. The latest release of Poser 11 is on the downloads page at posersoftware.com. Look at the bottom of the page for the old versions of Poser.

https://www.posersoftware.com/downloads

Try this. in File Explorer type this in the address:

%appdata%\Poser Pro\11

In the Poser Pro 11 folder delete these two files (or move them to a safe place while testing to see if this works):

Poser UI Prefs (the numbers will vary depending on the screen resolution)

Poser.ini

FYI the file LibraryPrefs.xml is where the linked runtime are stored. If you need to reinstall saving that file can save you needing to re-link a bunch of runtimes.

You can exit Poser and the queue will continue to process any jobs enqued. When you delete a completed job from the queue all temp files for that job are removed.

I rigged the figures for RWBY the faces were fully sculpted and use morphs for expression the way LaFemme or any other Poser figure does. Those would be the absolute deep end of Poser rigging. In season 2, episode 7 there a dance scene where all the figures are dancing. The character Pyrrha wears a long dress. That's rigged using a hybrid of bullet physics and proxy objects. Those dresses are not dynamic cloth. It's all rigged. Most important it wasn't conformed clothing. Each costume was a discrete figure. That's to save the sanity of the animators. The rigs did contain pose dial presets for common expressions and hand poses. That's also to save on animator sanity.

Now for getting started in animation and making your own figures for Poser. If your eventual goal is animation and you have a set of specific characters you'll probably want to build in the clothes. It's just easier in the long run.

To get your feet wet start off with the mannequin Andy. He's got a mostly blank face but there are a couple of morphs that five him a sort of face. You can use Poser's built in Morph Brush Tool to create expressions for the faces of Andy.The morphs in Poser don't change the UV map of a figure. They change the shape of the actual geometry. Think like your working with clay. Doing that will give you a feel for manipulating an existing mesh in Poser. No matter what, the place to start will be modifying existing figures to get the hang of how they work.