R Soul on 2/2/2014 at 19:02
The TimeScale value in the .mos file can be used. It's like the Time Warp property in Dromed, but for specific motions. It might look odd when the idling part of the motion speeds up. If it does, let me know how long each part should be and I'll modify them in Blender.
nightshifter on 14/1/2017 at 00:50
ressurecting this thread because I can't get the motions to work.
problem is that I can't recreate the motiondatabase. When I use Makdb, the Nmotiondb proves to be corrupted.
all AI stand with their arms spread and my playarm-motions won't work too.
any one who has a working motiondb with the GMDB( from the demo) and this new motions?
Yandros on 14/1/2017 at 10:31
The motionDb I'm using in DCE has both GMDB and these motions in it. I'll email it to you, Ger.
R Soul on 14/1/2017 at 16:38
It should work the same for everyone. The apparent corruption was probably caused by missing files when the db tool was run. You should also make sure you're not running it from Program Files, because Windows doesn't like files being written in there.
nightshifter on 15/1/2017 at 00:09
thanks Russ,
the motions are working great with your file!!
redleaf on 17/1/2017 at 15:30
Thank you from me, too, since this is one of my earliest missions that I am trying to finally get released. :)
Yandros on 17/1/2017 at 15:59
\O/
vfig on 13/2/2022 at 18:28
not sure where to put this, since there doesnt seem to be a dedicated thread for makmdb and its motion schemas. so im putting it here!
What the mystical numbers in the motion schemas mean:For a tag in tags.moc:
Code:
motionTag <Tag> <mandatory> <weight>
A mandatory tag (1) means queries including that tag will only return schemas that have that tag. Non-mandatory tags (0) give "best match" results, that may not have all the tags in the query.
The weights of tags in the query and in all the matches for the tags are added together. When multiple schemas are found for a query, the schema with the highest sum of weights will be chosen.
For a motion in *.mos:
Code:
motion <Name> <flags> <blend_time>
Flags can be a combination of:
1 - neck is fixed (some hack for bad mocap data handling)
2 - is turning motion
4 - ignore root translation in this motion
8 - is locomotion (not sure if this actually gets used)
Blend time is in ms. Shorter blend times will transition into the new motion more quickly, but less smoothly. A blend time of 0 would make the AI 'snap' into the new motion.
Additional comments:When should you make a tag mandatory? For example, a new tag "Swimming" for making swimming ais should be mandatory, since you would never want a ground-based motion to be used, if a query couldnt find a suitable swimming motion. However, a new tag "Hopping" for making Benny hop around on one leg should not be mandatory, since it would generally be reasonable for him to fall back to a two-legged motion for actions where a one-legged version couldn't be found.
PinkDot on 14/2/2022 at 10:31
Quote:
A mandatory tag (1) means queries including that tag will only return schemas that have that tag. Non-mandatory tags (0) give "best match" results, that may not have all the tags in the query.
The weights of tags in the query and in all the matches for the tags are added together. When multiple schemas are found for a query, the schema with the highest sum of weights will be chosen.
Nice find! I didn't know the meaning of the motionTag parameters.
