Choosing a Stationary Character (Mesh vs. BIN w/Examples) - by Derspegn
PinkDot on 29/1/2019 at 15:48
@Derspegn -
If you want to go through this as a learning experience, that's fine.
But if you just want to have this done, I can trim the motion as needed and send you new .mi and .mc files. No need to mess around with flags, in case flags are the culprit.
Quote:
The Motions and MSchema folders should be in your Thief2 folder. IIRC you said this was a test installation so anything you do won't affect your main play installation.
I wouldn't say they 'should' - they can, but working outside is safer and cleaner. Even the author of the tool recommends to keep it outside the Thief folder. It's already messy enough, as it is...
Derspegn on 30/1/2019 at 06:11
Quote Posted by PinkDot
@Derspegn -
I can trim the motion as needed and send you new .mi and .mc files. No need to mess around with flags, in case flags are the culprit.
Please, by all means, trim the motion (I was just about to ask for this). I usually start the motion at about frame 89 (1/3 or so into the motion). In MotEdit I've noticed that if the AI tends to rotate more to the right the further you go into the motion (last 1/3 section). That would be much appreciated! :D
Derspegn on 30/1/2019 at 06:28
About 2 years ago I was having problems getting a sitting AI attached to an AIWatchObj link to play a motion. I started editing in T2 v1.18 and later updated to NewDark. I found that this AI would not play the motion if the motiondb.bin was from 2015 (reload_schemas utilized, FM optimized), later than the 2004 version that <strike>(I think) came with v1.18.</strike>
EDIT: The 2004 motiondb.bin was likely used when I started using v1.21.
Yesterday when I first updated my own motiondb.bin, I had the same problem. I reverted to the old (2004) motiondb.bin, reload_schemas, then typed in show_phys_models twice (X2), and motion (Conv 96) would play again. I typed show_phys models twice with the newer motiondb.bin, but nothing happened for the sitting AI. I looked through my files trying to find if something was missing, thinking a new motiondb.bin would not support Conv 96.
Here are 3 screenshots of the 3 AI I have linked to AIWatchObj links, showing how they are set up. These are characters the player will have no physical contact with, and will simply play one motion continuously each. The blacksmith (thanks Digital Nightfall!) continues to move his arms with an updated motiondb.bin, the lute player is a work in progress, and the ghost freezes when motiondb.bin is updated:
Inline Image:
https://i.imgur.com/0tOPf0U.pngInline Image:
https://i.imgur.com/1SNz3j7.pngInline Image:
https://i.imgur.com/y7o0ItK.png
john9818a on 30/1/2019 at 07:31
I guess everyone can choose where to put them but I like to keep all of my mission and resource building and testing together. :) I have more folders outside of Thief than in.
Yandros on 30/1/2019 at 13:45
I don't know much about motions so can't speak to most of what you posted, but a few things you said confuse me.
You speak of upgrading from v1.24 to NewDark, but NewDark is everything beginning with v1.19.
The reload_schemas command only reloads sound schemas, and has nothing to do with motion schemas. Those are compiled into the motion_db.bin file when you build it (from a DOS command line outside of Dromed, not using reload_schemas).
I don't think any updated motion databases have ever been included with NewDark. If you had a later one from 2015 which didn't work the same as the 2004 version, you must have gotten it somewhere else, which means it is entirely possible that whoever compiled it left out some motions that are in the 2004 version (which I would assume is Shadowspawn's original extended motion DB).
Derspegn on 31/1/2019 at 06:11
Quote Posted by Yandros
You speak of upgrading from v1.24 to NewDark, but NewDark is everything beginning with v1.19.
My bad, that should be v1.18.
Derspegn on 3/2/2019 at 10:11
Quote Posted by Yandros
I don't think any updated motion databases have ever been included with NewDark. If you had a later one from 2015 which didn't work the same as the 2004 version, you must have gotten it somewhere else, which means it is entirely possible that whoever compiled it left out some motions that are in the 2004 version (which I would assume is Shadowspawn's original extended motion DB).
I messaged PinkDot, and the 2004 motiondb is likely Shadowspawn's extended motion database. I probably used that file after upgrading from v1.18 to v1.21.