I had to rig a character quick today and I noticed that a newly-rigged TSM character now gets "Error loading string xxxx" at the end of its relationship names. Since the character still seems to otherwise work ok and this didn't happen before, I'm guessing that A:M has changed some detail about how it reads these names in from the model file. Perhaps some termination character is not being recognized anymore or something like that.

Has anyone pawed thru this situation with a text editor and found out what the cause is?

It is not just TSM rigs...all relationships display like this.

I made a report of it, but like you said, everything works fine.

Just a HUGE thank you for letting me know that TSM2 still works with v14.
I had given up on it ever working again when it stopped in 13q(?)

I installed it with my v14 install this morning and everything works! It's like christmas came a little early this year

You mean even if someone installs a squetch rig the relationship names get that error?

I checked v14 last night when I saw that comment...I didn't see it when using the Squetch Rig installation. Maybe I'm not understanding the steps to make this happen.

I was using V13, I really think this is an A:M/TSM thing. I hadn't noticed a constraint haveing any problem in other situations.

All newly created (ie not copied, pasted or imported, such as during a squetch rig install) relationships, whether tsm or not, give string errors.

Imported actors with relationships built under previous versions do not display the error.

To test this, create a new relationship, any relationship, on a model. It will display the string error text.
Very minor.

(These facts are true in v14c, I don't use 13 anymore.)

Thanks for the information, Jesse. I'll have to try that tonight...I've been doing a lot of work in older versions to get the Squetch Rig update released.

I tested v14 by creating new relationships on a very simple model that I made in that version...I didn't get the string error. I tried "orient like", "aim at" and "translate to" constraints without anything unusual turning up. Then, I opened Squetchy Sam in v14 and started adding new Poses...I didn't get the string error.

Does TSM put anything in one of the AM folders? Like an HXT file in the HXT folder? If so, have you tried testing for this problem without those files installed, Jesse? I don't have TSM, so it's not something I would be able to try.

I tried making some new relationships in V13 and didnt' get the error either.

So far it's only happened with TSM.

That's weird. It doesn't give me an error today at all.
*shrugs*
doesn't matter either way, can still read relationship names thru the error when it happens

Has anyone tried TSM2 in V15 yet?

According to this it won't work in V14 and later...

That was a temporary glitch. My TSM works still in v15. As long as the SDK stuff it uses remains relatively unchanged, TSM should continue to work. Good thing, too, it saves me ages of time. (even if it is not always the best rig, it is usually adequate, once customized)

Great! Do the relationship folders still get the weird "Error loading String" tag on the end of their names?


I tried looking at the strings in a hex editor and I coudln't see any difference between the ones that were ok and the ones that weren't.

Does anyone have the download location for TSM2? I have found my licence key but can't find the installer.

Cheers

im in the same boat as you mate...

Cant find the installer for it but i do own a license and have my key...

The last link from the last tsm2 update still works, forum post here
http://www.hash.com/forums/index.php?s=&am...st&p=157478

Happy rigging.

Oh, & Rob, the Error Reading String error seems to be gone.

Thank you!

The setup machine works directly from model made in V15?
or brought in from ver 12?

It works on A:M 14 models so I'm pretty sure that it is still working with A:M 15 models.