Forum Replies Created
-
Posts
-
Looks like we got another one of these. Should be Amy the Doll, but store link is for Annesca from the same author.
https://www.renderhub.com/dreamlight/amy-the-doll-genesis-8-9-female
Man, I completely forgot I posted this thread.
Thanks for the answer Jaba (and for the necro Krasser -- guess we wouldn't have gotten the answer without it!)
I'm seeing something similar -- can't bid on requests. Renewing membership didn't change anything (not surprised since my membership should be good for a couple more months...)
I'm guessing it's just bugs due to the site being revamped.
Got a request pointed at the wrong product:
Link goes to Annesca for Genesis 8 Female, should go to Amy The Doll - Genesis 8 + 9 Female
https://www.renderhub.com/dreamlight/amy-the-doll-genesis-8-9-femaleImporting that many separate materials is expected, but less than ideal, especially if you're concerned with Unreal's performance (like if you actually want to use the imported model in a real-time context, like in your own game or something -- or if you're using limited hardware).
Frank's suggestion to combine models can work, but can run into issues if a single model needs to point to different texture sets (like how a Genesis 8 body has separate UV sets for the legs, arms, torso, head, and each needs to point at its own textures). Only having one material on those meshes will prevent you from assigning the correct textures to each body region.
Ideally, you set up a single master material with the textures parameterized, like in this tutorial: https://www.artstation.com/blogs/qdwach/eN1V/tutorial-intro-to-unreal-engine-master-materials
Then, for anything that has multiple materials per object, you use a material instance of the master material, with the texture fields on the instance pointing to whatever other textures those materials need. Material instances with their own textures tied to a single master material will be significantly more performant than completely new standalone materials on everything.
Of course that's a lot of manual setup, but generally expected for this kind of thing. Unfortunately I don't know of a way to do this automatically.
Could be. The name "Resistance 3D" has a defiant ring to it, seems like he may be trying to circumvent the ban.
Wow @trader2h, that is a hell of a find. Thank you!
While I obviously can't speak to the backend, I did notice the request search URL is just a modification of the regular search URL. Compare:
https://zonegfx.com/?s=genesis+8+female https://zonegfx.com/?s=genesis+8+female&wpessid=2030603First one searches for "genesis 8 female" in blog posts, second searches the same term in the request section.
Seems like it would be easy to have a "suggestion link," maybe at the end of a set of blog search results, that's just the same search link but with the last bit appended to direct the user to the requests section. Something simple like that could increase request visibility.
Right now I'm watching that bridal set. it's the second time it's been requested and even though it's over 30K points, there's no share in site. I doubt it ever will show up here.
Last year I watched a large architecture piece go unfilled for months even though it was heavily discounted at some point.Had a thought about this... it looks like the request section can be sorted by bump date, creation date, or product name, but not by points accumulated. Being able to sort the whole request list from highest points to lowest might help with this. If someone was looking to get points for money by purchasing to fill a request, they could quickly look over all the requests with the highest point totals and see which ones seem worth filling.
@warrant63 It's the opposite of the problem you're describing -- the posts are SFW content, but using the default NSFW image instead of uploading a valid picture of the product. Basically all of the recent uploads by this user are a good example: https://zonegfx.com/author/nguyenduc7980/
I reported a number of these, but stopped just because of the absolute slew of them. At a certain point it's the user and not the posts that need to be dealt with.
