Problem with Faery Flyer

ruekakaruekaka Posts: 346
edited December 1969 in The Commons

Hi everybody,

I bought the Faery Flyer (http://www.daz3d.com/faery-flyer) but it does not work properly in DS (4.6.2.118, WinXP, 32Bit).

After reparing the path names to the image "chrome_2Refl.jpg" it could be placed into the scene without any warning, but as soon as I start moving or rotating the wagon DS freezes. Sometimes DS comes back after a while, sometimes I have to kill it. The memory usage of DS at that time is not more than 300MB (and it's enough memory left)

I tried the same object in Poser 2012 (same PC) and here it works without this problem.

1) Does anybody else have the same problem?
2) Does anybody have an idea how to solve it?

Any hint is welcome.
Thanks in advance.

Comments

  • icprncssicprncss Posts: 3,694
    edited December 1969

    One, be aware that this product was created before DS even existed. IIRC, it comes from the P4/PPP days.

    Did you install this through the DIM or did you manually install this? If you used the DIM, uninstall all files from it. Manually download it and manually install it to wherever you install your content.

    It will install to the runtime folder that resides inside the content folder of your DS content.

    If it works without an issue in Poser but is causing issue in DS, it could be a number of things. There could be an internal naming convention issue (which I doubt knowing the vendor and his products as I do) or some hier issue. Poser can be much more forgiving of these things than DS.

    Here's a simple thing to try: Manually download the file. Install it to your Poser runtime. Since it's designed for Poser, there should be no problem there. Make certain you have deleted all other installions of this product and their files from you DS libraries. Map your DS directory to your Poser runtime if you haven't already done it. Try opening the file in DS from the Poser runtime.

    Since this is an old product, do not move files about. This is a file that requires the various parts to remain in the old rigid Poser runtime file conventions.

    If this doesn't solve the problem, contact the vendor.

  • ruekakaruekaka Posts: 346
    edited December 1969

    Thanks for your reply.
    That's what I did already (I do not use DIM at all).
    The only fix I did so far was the change of the image file names in the *.cr2 files.
    You mentioned that a possible problem could be a wrong naming. Do you have anything specific in mind?
    (I was just hoping I can do something by myself).
    Nevertheless I will try to contact the vendor.

    Again, Thanks for your help.

  • icprncssicprncss Posts: 3,694
    edited December 1969

    Here's another simple thing to try. Load the figure into Poser. Make sure you have save external binary morph targets unchecked in your general prefs for this. Save it back to the Poser library. Close Poser and open DS. Load the figure into DS. Sometimes resaving will work out the kinks.

    Legacy Poser rigs have very strict naming conventions. Slight deviations are forgiven by Poser or automatically correct when it's loaded into Poser but DS doesn't do this.

    One example is an old BSG Viper model I have. I can load it into Poser without issue. However when I load it into DS, only the canopy loads. It took a while but when I really took a look at the cr2 text, I found the rigger labelled the main part of the model Body. I had to go back and hand edit the cr2.

    Try the above suggestion first. If you still have issues, contact the vendor. If you are still within the 30 day return time and you don't want it because of the issues, return it.

    I wish I could offer you a clear solution but this isn't a product I own. Sorry.

  • ruekakaruekaka Posts: 346
    edited December 1969

    O.K., that's what I get so far.
    Whatever I tried (Saving from Poser, Saving from Hexagon, using the repair options of PoserEdit, ...) it does not work properly on my 32 bit XP PC, but it works without problems on my 64 bit Win7 PC (Same DS version, just 64 bit).
    So maybe it's not a problem with the product (at least not with the product alone).
    I will stop my investigations here.

Sign In or Register to comment.