Renderotica

I had not tried with the V6 New Gens but I've just run two renders with V7 HD and Bethany 7HD and, oddly, V7 looked ok but Bethany has the ridge. This is with SubD at +1 and Render SubD at +3.

Yes, you are right...

I tried to find out the problem but that's temporary above my head : (
I'm very sorry...

Hi everyone, this is KTdid.

I noticed that there is some what might be some miscommunication among users and 3feetwolf.

The settings in DAZStudio that changes "base" to "High Resolution" is only one step of sub division. This is done in 'Resolution Level' in the 'Mesh Resolution' part of Parameters Tab.
(yeah, I know you know but for those who don't and just reading, just want to keep it clear for those peeps)

In that same 'Mesh Resolution' part, there are further sub-division levels (that's what subD is btw). The first set is to actually show the subD on screen only. If you have a powerful enough computer to do Iray in the Viewport and you have 'View SubD Level' at say 1 or even 0 to make it render faster, the ridge everyone is saying that shows up, may show up in your ViewPort.

There is another SubD choice, which is the next one, and that's the subD for renders. I don't own non-V7 based figures but the only time I can even see a hint of a ridge is when I set the render subD to 1 or 0 and I do have quite a few of the 'HD' versions.

I believe it would help 3feetwolf diagnose these ridge problems more quickly if those who are having the problems state how they are seeing it (Viewport or Render), what subD level they have it on (Viewport or Render) and also if they are doing a render, the subD of the Render.

So, to help him out, state something like this:

Figure: G3F based Ronya HD
SubD Viewport @ 1 (that's the default btw)
SubD Render @ 2 (again the default)

For what it's worth, you may want to try a render at subD 6 (don't change the view subD, just the render subD), just to see. You don't have to do some huge size render but something like 300 x 300. If the ridge shows, post it and tell 3feetwolf the settings you used for the render.

More data is a good thing but organized data is even better.

And a message to those who jumped on the 4.9.2 wagon (I did too). You may want to 'unlock' the beta testing version in your DAZ3DIM application. That way you can make sure things work before you upgrade. To get betas, launch DAZ3DIM and click on the gears icon in the top right corner. Click the download tab and scroll down to the bottom and make sure all the 'builds' are checked. When you go back to the main screen, you'll see all the other things you can test out, like ZBrush plugins (beta). Now all of you talk, so everyone doesn't start to download betas from DAZ at the same time (that was my lame attempt at a joke). Anyway, you will also notice that they slowed down DAZ3DIM so that you would use Studio to buy stuff and download so they have their DRM.

So here are two more screen shots of IRay renders. Both are G3F Bethany 7 with Ronya skin. As you can see from the parameters on the right, one has a Render SubD level of 1 and the other is level 2.

Level 1 has no ridge, Level 2 does have the ridge.

Edited by user Friday, May 27, 2016 3:22:46 PM(UTC)  | Reason: Not specified

Sorry - my reply tone might have seemed like I was all fired up but I wasn't. I was just pointing out that I had already done as you asked.

It seems to me from 3feetwolf's replies that he has been able to reproduce the problem, unless I'm misunderstanding. I can confirm it is not PC related because it happens on both my new Windows 10 PC and my iMac. Nor is it related to the Ronya character - it happens with a standard Bethany 7. I did notice that it was not so obvious with V7 as with Bethany, however. I don't have any of the other DAZ V7 based figures like Josie or Mei Lin.

Nevertheless, I can reproduce it at will and if 3feetwolf would like me to try anything or provide any more details, I'm only too happy to do so. I can render without HD/SubD but would rather have it all working if possible.

Hi

I ran into this problem someone else listed about 10 pages back: WARNING: TypeError: Result of expression 'oCTRLGensC' [null] is not an object.

Turns out I installed older updates over more recent updates (alphabetically) because I bought them all together recently. Folks who have had the product for a long time are probably installing the updates in the correct order, so they don't run into the same problem. I discovered it by comparing the script files between the different updates and noticed more recent figures are not listed in the older scripts.

@3FW, of you don't want to update the older scripts every time a new figure is added, you may want to add a comment in the readme telling users what order to install the updates in.

Thanks

Rune 7 has released! *cracking whip sounds* :-P

I'm also having issues with ridges in renders. I'm using Teen Josie 7 (stock) with poses from Nasty Apartment.
http://www.renderotica.c...Nasty-Apartment-For-G3FM

Pose 6 should be easy... But I get a ridge all around the New Gens. The figure is set for High Resolution, Sub D 1, and Render 2. I'm using Octane, but what I'm seeing in the view port is what I'm rendering.

I tested with the Stock V7, and stock gens and I get some ridging as well. Me thinks I have to many morphs running around.

Any chance of support for the Base Male UV set? (from here: http://www.daz3d.com/gen...wap-male-and-female-base)

Thank you for reminding, I will check this out.