Forum Moderators: Staff
Poser Technical F.A.Q (Last Updated: 2024 Nov 13 12:50 am)
Welcome to the Poser Technical Forum.
Where computer nerds can Pull out their slide rules and not get laughed at. Pocket protectors are not required. ;-)
This is the place you come to ask questions and share new ideas about using the internal file structure of Poser to push the program past it's normal limits.
New users are encouraged to read the FAQ sections here and on the Poser forum before asking questions.
No ideas?
C makes it easy to shoot yourself in the
foot. C++ makes it harder, but when you do, you blow your whole leg
off.
-- Bjarne
Stroustrup
Contact Me | Kuroyume's DevelopmentZone
Well, I still don't have any clue on how Poser detemines the export scale factor, but it is definitely a factor applied to the offsets and translations. I might need to check to see if the same factor is applied across all joints or differently thereby.
C makes it easy to shoot yourself in the
foot. C++ makes it harder, but when you do, you blow your whole leg
off.
-- Bjarne
Stroustrup
Contact Me | Kuroyume's DevelopmentZone
This site uses cookies to deliver the best experience. Our own cookies make user accounts and other features possible. Third-party cookies are used to display relevant ads and to analyze how Renderosity is used. By using our site, you acknowledge that you have read and understood our Terms of Service, including our Cookie Policy and our Privacy Policy.
Anyone know how Poser scales when exporting BVH motion?
I ask because I can handle direct Poser values with "don't do any scaling". But if "Scale Automatically" is used, positions and offsets are based on this scaling factor (geeze, thanks for putting the value into the BVH file guys!).
Obviously, the scale factor is determined algorithmically when both importing and exporting with the scale option - but for some reason I have no idea what it involves - hmmm. One possible way to determine this might be to compare some non-zero origin against its corresponding offset. But since the offset is relative to the parent whereas the origin is relative to the world system, some tracking would need to done (summing parent offset vectors to arrive at the world equivalent).
I've never liked the "Scaled" BVH - it not only sets arbitrary values which makes import into other applications require some trial-and-error every time but it also doesn't include the BODY (which receives translation, say, for walk paths).
Any information would be greatly appreciated!
Thank you,
Robert
C makes it easy to shoot yourself in the foot. C++ makes it harder, but when you do, you blow your whole leg off.
-- Bjarne Stroustrup
Contact Me | Kuroyume's DevelopmentZone