Annoying pokethrough problem..
HamEinar
Posts: 117
I'm a bit stumped here, so if someone with know-how can take a look at the attached picture and perhaps provide some reason as to why this happens, I'd deeply appreciate it.
As you can see, everything is fine until I hit render? I've tried upping smoothing and collision iterations and increased the subD of the dress - no luck..
pokemum.jpg
1700 x 900 - 385K
Daz 3D is part of 
Connect
DAZ Productions, Inc.
7533 S Center View Ct #4664
West Jordan, UT 84084
Licensing Agreement | Terms of Service | Privacy Policy | EULA
© 2025 Daz Productions Inc. All Rights Reserved.
Comments
I had this same problem last night, exactly the same.
It was the first time I was really working with G3F and creating a custom character. I was using the Allure Lingerie:
http://www.daz3d.com/allure-lingerie-for-genesis-3-female-s
-Patrick
Damn I sure hope this is not a "thing" with G3 and custom characters..
...but still, why is the viewport Iray rendering different from the final render?
maybe displacement on the shader?
No displacement on either the G3 or the dress..
Looks a lot like the Smoothing modifier is not done calculating before getting rendered.
yes, maybe try interactive update on? I can only guess
I would try a push modifier though if its not displacement on the material
Try turning Interactive Update off...
In the Parameters tab, for the dress, find Mesh Smoothing and under its options, turn off Interactive Update, if it is on. Also make sure that the collision item is G3F.
To add a Push modifier, Edit > Figure >Geometry>Add Push Modifier. You will need to turn down the push amount as it will probably load at 1. That would be a 'scale' value of 1 cm in Studio...so you would want to drop it to 0.1 or less (1 mm). I find values of 0.01 to 0.05 about 'right' for this kind of thing. The Push modifier's parameters will be right next to the Smoothing, after it's added.
Dead on, IMO. This has happened to me so many times it's not funny. Hit that render button too soon, and the smoothing-in-progress geometry is what will get sent to Iray.
Sadly not the case this time; I ended up having to create a couple of morphs.
Depending on how many iterations (collision and smoothing) and mesh resolutions (both the clothing item and figure) it could take several minutes from the last move of the mesh to finish calculating.
There is something going on here.
It does indeed look as though it is unsmoothed, however:
Why is the progress bar in the lower right corner of the UI not showing (The one that shows when it's processing smoothing or collisions)?
I loaded the scene, let it sit for a good 30 minutes, untouched, before hitting Render.
Why does both the Smooth Shaded preview and the Iray preview show the mesh fine, but the final Render looks unsmoothed?
My machine is new, Core i7 6-core, 32GB RAM, GeForce GTX980 and Titan-X. My system should not be slow by any means.
I've not had any problems with pokethru, honestly, since Daz Studio 4.0 was released.
-Patrick
Patrick, your settings, and the fact that you have Interactive Update off, strongly suggest it's not a smoothing delay issue. Still, the smoothing update is something to be watchful for. It's a real bummer to start a render, only to come back half an hour later to see that Victoria is showing more private bits than you had anticipated.
If you have something like Fit Control, and this is Genesis 1 or 2, you can try a slight expansion to pull the clothing geometry slightly away from the main figure. On your example, there appears to be some kind of displacement stuff going on, which could influence the render. Your plain mesh doesn't show the texture in preview mode that you get when rendered, and if you have a strong displacement map in that part of the garment -- which looks likely in your case -- it might deform the geometry enough for a poke-thru. You will only see this in the render.
And remember...in Iray, displacement is NOT the same as it is with 3DL. If there isn't sufficient geometry and/or subdivisions, then larger areas of the geometry are going to be moved by the displacement...instead of tiny pixel or smaller areas being displaced, it's possible that whole polygons will be moved.
Thanks for the input. The thought had occured to me that it seemed like a displacement issue, but I didn't think much about it because the figure is Gen3Female and the clothing is the Allure Lingerie for G3F from OOT here in the DAZ store:
http://www.daz3d.com/allure-lingerie-for-genesis-3-female-s
No special morphs done and I'm using one of the default Iray materials that comes with the set, so I assumed that things like that were checked before it went up for sale in the store and I dismissed that as the cause of the problem.
Well, it's no big deal as I am able to adjust for things like this, I just thought I'd agree with the OP that I, too, noticed this issue seemingly for the first time last night.
Thanks again for the suggestions!
-Patrick
Your model looks more built than the ones in the promos. We also don't know what shape morphs the PA used for his model that could have deviated the geometry in a way that the problem doesn't show up -- if it's even a displacement problem at all. It could be something else.
It would be useful if you let everyone know the fix, when you've discovered it.
Remember displacement on either the figure or the clothes can be the source...
If the pokethrough doesn't show in the viewport, but does in the render...it is usually displacement or smoothing not finishing...or both.
Well, I just ended up using some of the adjustment morphs included with the Allure Lingerie. I imagine it was the fact that I had the "Breast Cleavage" morph dialed in about 5%. It wasn't much, but enough to press the breasts together enough to overstep the displacement map and AutoFollow doesn't take displacement into consideration, so, no big deal.
-Patrick
UPDATE!
..and definitely not the kind one wants to hear... I loaded the scene again today to dig deeper and experiment with every conceivable setting - and started with a "0" render (i.e. just rendered straight after loading the scene, no modifications), which rendered PERFECTLY; no pokethrough whatsoever.
:-/ so I guess the problem fixed itself - which in my world is the worst fix; no way of knowing if I did something wrong, what causes the issue and if it's a matter of being lucky upon loading the scene..
The issue can be that Collision is not being applied in a render. I've had this problem with many peices of clothing as well as dynamics. I don't ever see it when using the Iray viewport, but in some random renders there's poke through.
While not always a solution I think you can also try turning off the visibility of the body parts that are poking through the clothes. This may also help speed up rendering times a bit.
Well, it is now May 13th, 2017 and this very same problem still exists.. I cannot understand why the iRay preview window shows a perfect image and the final render just seems to ignore the mesh smoothing. Is this a bug or has someone found the solution for it?
Hope someone can help me. :)
Create a Geometry shell of G3F and make it a little larger than original G3F fit clothes to Geometry shell but go to shader tab and make shell invisable this should work.
These seems to be happening more and more. Maybe with the update? The collision detection and smoothing is not being applied within the Iray render. Thoughts?
It's January 20th, 2019 and this problem still exists. Frustrating.
Try switching off/down SubD of the suit in render.