Items marked for Poser don't work properly in Poser

I bought some flower and tree props by Andrey Pestryakov because they were marked working in Poser (not dson), and while they work fine in Studio they don't work properly in Poser at all.  Once moved away from 0,0,0 where they load rotating them makes them rotate wildly in space, the further away from 0,0,0 the bigger the orbit. Moreover, their x, y and z axes are all off so that moving them with the ztrans dial for example causes them to move diagonally instead of in and out from the main camera's point of view. So they are practically unusable. I'd like to use them as they are very nice. Is there any way to fix this? Using Poser Pro 2014.

Comments

  • LeanaLeana Posts: 11,737

    Are you sure they're not parented to something?

  • RandomRandom Posts: 205

    Absolutely. Tried it in an empty scene.

  • Richard HaseltineRichard Haseltine Posts: 101,010

    Are they figures or props? it sounds as if they may be figures and you are using a mix of the root node and the figure when transforming.

  • RandomRandom Posts: 205
    edited March 2016

    They are props, no parts, only material zones. They unzip into the props section of the library.

    Post edited by Random on
  • SimonJMSimonJM Posts: 5,983

    Some DS items act the same way - their 'centre' is set to scene zero so rotate about that. In DS I can use the joint editor tool to chnage that, but not a clue in Poser, sorry.

  • Richard HaseltineRichard Haseltine Posts: 101,010

    There are (hidden by default, as I recall) offset paarmeters that can be used to change the centre-point for Poser props.

  • ChoholeChohole Posts: 33,604

    I tend to cahnge parent and then parent them to Universe, if they are smart propped to a certain area in the scene.

  • RandomRandom Posts: 205
    edited March 2016

    I'll have to check out the offset parameters. I doubt if they're smart propped as they load as individuals, but I'll look at that too. Over at Renderosity there was a solution suggested which was to export and reimport as objs. That worked but it's a tremendous amount to do that for the many props all having many variations.

    Post edited by Random on
  • RandomRandom Posts: 205
    edited March 2016

    Richard, thanks!! The hidden parameters were all out of wack. When I zeroed eveything, all was well!

    Post edited by Random on
  • Great tip, guys! I'll check that the next time I have that issue again.

    BTW: The last time I encountered this issue, I placed the object in a new Group (and only that object -- there was nothing else in the group), and then manipulated the group xyz settings. It worked like a charm on an object that wasn't parented to something else.

  • RandomRandom Posts: 205

    Zeroing the hidden parameters doesn't work completely on further experience, so I'm one-by-one going through and using the export-import obj method. The trees and flowers are so nicely and artistically done it's worth the effort.

  • RandomRandom Posts: 205

    Best solution yet, make a self group out of the item and manipulate the group.

  • Random:just a couple dumb questions

    1. which sets are causing the problem?

    2. why are you using the export import method? didn't the items come with obj files or did they only have dsf and py files(dson importer)?

Sign In or Register to comment.