Adorable, Mary.  Thanks so much!

Check the specularity settings on the corneas. That's usually the culprit when you get "white eye". Glossiness should be in the 90% range, with the color set to black.

For which app are you targeting your prop? Most generally, one doesn't load .obj files in D|S or Poser. They're loaded using library files (e.g. .pp2 for props). These apply the texture files when loading the figure. If you're targeting only D|S, you can apply the textures to the .obj and use File>Save As to save the textured prop as a scene, which will also load the textured figure.

I've got a Compaq R3000 with 512GB memory and an Athlon 2.8GB processor. It does fine for running graphics, but I don't use it for any heavy renders. I got it for the same reasons you're contemplating--I wanted to be able to take my Poser projects with me. Gaming, at least the online, graphics heavy kind, is going to be much more demanding than your average Poser/Painter/etc. session, unless you're trying to do a full-blown render of a large scene.

This is so totally incredible!!! Joe, you're my hero. :)

Thanks ever so much, Joe. Can't wait to try this out. :)

Absolutely awesome! :)

Joe, GMTA. :) I came looking for just that thing, cuz I'm tired of saving all those morphs individually. ;)

Absolutely not giving up, just really disappointed. Having the ability to select how parameters are read and written would have eliminated the extra step of "prepping" the .obj file so that it will export with proper node groupings (e.g. for use in creating morphs with D-formers). I'm SO glad I haven't had other problems that some folks have posted about. The "doubling morphs" bug is also a PITA, especially since I was working on superconformers at the time, and really don't want to have to reinstall an older version to eliminate the problem.

I don't know what they were thinking, either. The import/export function doesn't do half the stuff you're supposed to be able to do, including maintaining object grouping. I was really looking forward to integrating this into my content development workflow, and I'm back to square one.

I'd highly recommend just using the Surfaces tab and changing each material to reference your new files. Once that's done, you can save as a scene (.daz), so you can load the book with the textures already applied.

The nice thing is that the Parameter organizer plugin appeared in my Available Downloads without me resetting it, so apparently DAZ has been able to automate that. :)

I've not had any crashes with the new version, but I have had to deal with the "doubling morphs" bug. I've seen enough to know that they're moving in the right direction, especially with the object export (oh yeah, and then there's the bug I reported on that because it doesn't maintain node groups when you import an object then export it).

I suppose it's worth exactly what you've paid for it. :) I'm sure that someone did test it, but technically we're all testing it in return for getting it FREE.

Edited to add: Oh, BTW, most long-time D|S users will warn you to ALWAYS keep the previous install file until you're sure that you don't need it (this would now include all the matching plugin installs as well). Saves a lot of headbanging, fist slamming and other comparable troll like behavior.

Message edited on: 01/18/2006 18:47

When you do a new install of D|S, you don't have to reinstall all of your content. Just run the D|S installer. It will uninstall the previous D|S version, and once installed will ask if you want to use your previous content settings. SAY YES. At this point, you do have to download and install updated versions of any plug-ins (Power Pose, D-Formers, etc.), but we've been promised this won't be necessary, once the SDK is finalized. I've not noticed the problem with poses and morphs, although I suppose it's probably related to certain characters and packages.

Message edited on: 01/17/2006 06:17

Missed that one altogether! Don't have any way to check the C5 issues, as I don't use it. Could it be related to the alpha channel? I don't know that previous versions of D|S used it, and my graphics program doesn't use it either, so I wouldn't have noticed that.