Although this isn't exactly what you are looking for, note that clearance items are marked in your wishlist with a red circle with a C in it. So you can drag your scroll bar down at high speed while looking at that column for the red dot and find any on the page in a second or two, although you'll have to repeat for each page of your wishlist since it only shows you 50 at a time.

Although that prime price listed in the wishlist doesn't match the prime price when you click on it though, something's still off somewhere.

I now see the prime price in the wishlist, thanks! The wishlist sorting (sort by: lowest price to highest price) does not actually sort by it yet though.

There's no specific product in question, you can see it with a wide range of products in the store, just select "sort: low to high" then take a look at the results. For example here's a fragment out of the middle of today's prime flash. sorted low to high, you can see $8.27, then down to $5.85, then down again to $3.88, then down again to $3.50, then up to $9.95, then back down to $4.18, etc.

Ok, thanks for the info.

Yes, I think? they're poseable, so I assume that they're rigged, unless I'm misunderstanding something. I'm unfamiliar with weight mapping and content design though, so I'm not sure how to know what kind of weight mapping they might use. They come with V4 poses as well as the pearl poses, which might be a clue to vaguely when they were created. I do see the base requirement was Poser 8. Weight mapping is one of the many things I need to read up on and learn about someday.

Actually there are a bunch of things that do not autofit correctly from generation 4 to genesis1. Shoes get crinkly, dresses are damaged along the centerline, etc. Some items work, some items can be used if steps are taken to hide/disguise the flawed areas, some things don't work. I was hoping somebody who owned the product and is familiar with the common autofit issues could identify if this one converted without issues, or if there were problems, what they were.

Thanks, and congrats to the others as well.

It would be helpful if the "Sort By: low to high" by price worked. Currently it does not. Example screenshot. I wonder if possibly it sorts by what the price would have been had it not been on sale? (Not counting the top row of items that are actually sponsored ads always pinned to the top out of sort order of course).

Quote - By default Genesis uses V4 UV mapping.  In Studio it is easy to change the UV mapping, you will have to ask how to do it in Poser.

To change the UV mapping in DAZ Studio, look in the Surfaces (color) tab for the parameter labeled "UV Set".  For all materials, that dropdown value needs to be changed from the (potentially) incorrect value to the correct value that matches what you have.  Except, that isn't working for me right now, although I've gotten it working in the past; there must be a second step I'm overlooking.

You can free up some space by deleting things you don't need.  For example, if you imported a human figure into the scene you may be able to delete body parts hidden underneath clothing or on the side of the figure facing away from the camera, teeth if the mouth is closed, etc.

In addition to resizing images smaller like TheBryster said, you may also be able to delete some images entirely and just use basic materials instead.  No point in having a 2000x2000 pixel image texture for something 10 pixels wide in the background.

You may also want to use Large Address Aware if appropriate, that might give you a tiny bit of extra available memory under certain circumstances.

I haven't taken the time to see how much memory it might free up, but if you use instances instead of copies for identical objects, that should help some.

  Concerning individual books vs. a group, you could do both.  I have a lot of products that have content thumbnails for each individual element in the scene, plus another one that is a "preset" scene with all the elements arranged into a scene that's ready to use, and that works well for me.

  Personally I like the ability to break a scene down into it's individual components (ie, a single book) because that allows me to arrange the scene however I want; maybe I don't want a line of books on a shelf and I want a single book, or I want a pile of books on the floor, or I want a staggered stack of books, etc.  But it certainly would also be helpful to have an entire row of them if I did want to stock a library or something.

  If you decide to use the .duf DAZ Studio format, it should be very easy to do.  Just import your object, get the materials working the way you want, then File > "Save As" > "Scene Subset".

  (If you save as "scene subset", that creates a file that will be added to an existing scene when you load it.  If you save as "scene", that creates a file that will REPLACE the existing scene, which you probably don't want.)

  If you wanted to create a single book and a row of books, you could just put the single book into one file like Book.duf, then make the row of books and save that into a second file like BookRow.duf.

  As a DS user, while I do sometimes use products distributed in .obj format, it generally scares me off because in the past too often something was wrong or materials are missing when I import it, so I've mostly stopped trying.  I'm probably missing lots of good things because of this.  Unless I'm the only one like that, you may find additional customers simply by offering it in a different format.

  Although it appears you got everything working already, I want to add that some downloads (from various sites, including but not limited to Renderosity) are zipped into differring folder structures that may need to be rearranged before the products can be used. 

  Sometimes they unzip directly into a runtime folder, sometimes they create a subfolder within that folder and you have to move the contents up a level or two, and sometimes they won't even have a runtime folder structure (even though they may still require it) and you'll have to create those folders manually (or if you use a single runtime, move the files into the correct places within it.)  I have also seen a product with two zip files where one file unzipped one level deeper than the other file for the same product, so you had to unzip half the product, move it, then unzip the other half to get them together.

  It may seem confusing at first, but once you do it a bit, you'll get the hang of it.  When I think something should have installed but it didn't, I might compare it to a known working product's runtime and then my incorrect unzip location jumps out and I can correct it.

  If you have a ground plane, that would explain why the sky went black (it's blocking the sky from view and not lit by the default light from above).

  This also ?can?will? cause distortion of the horizon line.  See attached screenshots of a cube and a ground plane.  The top screenshot shows the normal view from above, the bottom screenshot shows the view with the camera moved below the horizon (see dark black sky in upper left thumbnail render, also curved horizon line.)

Quote - ... Lately, I've been thinking of wiping everything and starting over, using multiple runtimes to help keep things organized. ...

What are the advantages and disadvantages?

...

Can I still use the Custom categories feature in DS 4.6 Pro?

How many runtimes can I use?

  Some answers and info:

  I don't know if there is any upper limit on runtimes (I don't THINK there is, but don't quote me on that).  I haven't counted but would guess I have in the hundreds, as I'm mostly using one per product.

  I'm not sure exactly what you mean by "custom categories"; I can create my own categories and organize content within them as I wish in the Content Library tab.  You do have to map each of the runtimes so DS knows where to look for content (the same way you mapped your current runtime, if you aren't just using default locations), but other than that you don't have to do anything different to set up multiple runtimes.

  The advantage I get out of it (with one product per runtime) is that if files get messed up, I can just delete the entire folder and reinstall to clean it up without worrying about other products.

  There are several disadvantages I have found.  One is that at least some things don't work; there was a plugin for DS long ago (Finder, I think) that couldn't handle more than a small number of runtimes.  There may be other things I don't know about that I'm breaking by doing this.  I have also found products that needed to be installed together in the same folder (the installers required this, however I think with the advent of the DIM zips in place of the executables and the latest version of DS, possibly that restriction may not be there anymore, but I haven't verified this.)  And of course you have to map each runtime, plus back up/restore those mappings, which can be really tedius.   This may also negate some of the benefits of using DIM (DAZ Install Manager) which allows you to easily mass install/uninstall into a location.