Ravyns opened this issue on Oct 10, 2012 · 8 posts
bagginsbill posted Wed, 10 October 2012 at 1:39 PM
You have to apply logic here which includes rejecting all assumptions.
If things are inconsistent, then you have to question the belief that they should be consistent.
First assumption that I've seen people make so many times. They assume the document they saved from the modeler (Wings, Max, whatever) is the document they are loading into Poser.
I just had this happen the other day with my partner, Tom. He kept showing me a material in Max, and then showed me the polygons were not assigned the same when loaded into Poser.
Turns out, he had the obj in the geometries folder and the character folder. Poser was loading one he had saved several days ago. He incorrectly assumed he was loading the one he was saving.
A two line python script showed him that the obj he loaded was not what he was assuming he had loaded. Perhaps you would find it useful?
Save the following to a .py file and run it (make sure you have an actor selected that has geometry)
import poser
print 'Current Actor Geometry is from', poser.Scene().CurrentActor().GeomFileName()
Renderosity forum reply notifications are wonky. If I read a follow-up in a thread, but I don't myself reply, then notifications no longer happen AT ALL on that thread. So if I seem to be ignoring a question, that's why. (Updated September 23, 2019)