A:M12.0v+ and TSM2

[Paul Forwood]

I have been getting an unhandled exception #001, during the final rigging stage with TSM2, which shuts down A:M 12.0v+. TSM2 Builder and Flipper seemed to work flawlessly but the Rigger fails at the last stage. To start with Rigger goes to work with the rigging, control bones appear as geometry bones are hidden, it gets to the last limb, (Left leg), and then before it completes the left leg the exception occurs. I have checked the geometry rig and can't find a fault with anything.

 

Has anyone else been experiencing this? I just can't see what might be causing it. The rig is just a standard biped rig, same as I usually do. Any thoughts?

 

-----------------------------------------------------

Edit:

I just thought that I would try the rigging in A:M11.1i but running TSM2's Rigger plugin produced the error:

 

"Error:No systems found"

 

-----------------------------------------------------

 

Back in A:M 12.0v+, I re-rigged my character but this time I left out any intermediate bones, only TSM2 bones used, and I received the same error when running the final Rigger. I think this must be an A:M problem rather than TSM2 so I will post this to A:M Reports.

[Gene]

Hi Paul,

 

I reported this to Anzovin last week and Morgan is working on it. At first I sent it to Hash, only because I wasn't sure, but it appears to be an issue they are investigating.

 

You can always drop Morgan a line and just let him know...might bump it up the priority list.

 

Cheers,

 

E

[luckbat]

In the meantime, you can always run TSM2 from within v11.1i. Works like a charm.

[Paul Forwood]

Gene, thank you for the feedback! It is good to know what others are experiencing so that I can start elliminating possible causes.

 

STRANGE!

 

TSM2 has always worked beautifully with A:M 11.1 but it won't work at all now! I booted A:M11.1i, imported my model, copied the geometry to a new model to start afresh and then ran TSM Builder. Nothing happened! I tried it over and over without success. I then suspected that it might relate to attempting to rig an A:M 12 character in A:M 11.1 so I built a new A:M11 proxy model and ran TSM Builder again. Still nothing!

 

Luckbat, I'm guessing here but I will assume that you have checked that TSM2 is still working with A:M11.1i and that you have not ever installed A:M13 beta? Can you confirm that for me, please?

 

I have a feeling that this has something to do with A:M12 or 13 making a global change which is affecting all versions of A:M on my machine.

 

The only other alteration that my PC has had recently is the, less than happy, update from QuickTime 7.0 to 7.1 which prevents me from viewing the new H.264 movies.

[luckbat]

Luckbat, I'm guessing here but I will assume that you have checked that TSM2 is still working with A:M11.1i and that you have not ever installed A:M13 beta? Can you confirm that for me, please?

Yeah, I use TSM2 more or less weekly--whenever I make changes to my character. It runs perfectly in both v11.1 and v12. Frankly, I don't believe that v13 is capable of making changes to an existing installation of v11. Are you running the latest version of TSM?

[Paul Forwood]

Hmmm!

I checked the hxt folder for A:M11.1i and for some strange reason the TSM2 folder was empty. I guess when TSM2 uninstalled, before installing the new version, it left this folder empty. I guess I installed into version 12 or 13 and forgot to check 11.1.

 

Thanks for the replies, Luckbat.

 

Time to test...

--------------------------------

Ha, ha! I am soooo stupid!

 

Note to anyone running more than one version of A:M:

When updating TSM make sure that you check the TSM folder in the hxt folder of all of your A:M installations.

 

I'm on the road again...

 

--------------------------------

Please note that the unhandled exception problem is a seperate issue and still persists in A:M 12.0v+.

This just gets A:M 11.1i working again.

[Morgan]

You should install TSM 2.07 -- and make sure it installs to 12, not 11.1. And that you close A:M before you run the installer.

 

That's the current version, not a fix, by the way... but I'm pretty sure the reason I can't duplicate the problem is because it doesn't exist in 2.07. Please let me know if I'm wrong about that, though.

[Paul Forwood]

Thank you very much, Morgan!

TSM 2.07 did the trick!