Forum Moderators: Staff
Poser Technical F.A.Q (Last Updated: 2024 Nov 02 8:21 pm)
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.
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.
This isn't so much a question as an observation. I finally (yes, believe it or not, it works!) figured out the obj/cr2/external geometry/runtimes dance. No one tutorial or book was step by step accurate for my install. I had to 'Frankenstein' a workflow from LittleFox's clothing tut (Part 3-Poser 1, page 39) and this guys blog ( http://brian-the-techie.blogspot.ca/2013/03/how-to-rig-poser-prop.html ). I got a cr2 that points to a new obj and it loads reliably but I also get an xmp file(?) I know that these files are a metadata container started by Adobe. I opened it in Notepad++ and saw the sort of informational gibberish one would expect.
After reading all the books (yes I bought them) and going through the many online tutorials I'm convinced that every version of Poser works a bit different due to undocumented changes. I have the latest PPro 2014 SR3 (and yes, I paid for it too) and I occassionally run into things that aren't exactly like the official Poser manual or recent tutorials.
Littlefox also instructs one to delete the new resultant obj and place ones original obj in that directory. When loading the model Poser will ask where the obj is. You 'tell' it by using the pop-up box; it loads the new obj and all is fine....maybe? I'm going to play around and see if this sort of foolishness is still necassary.