Boundaries are broken.
How do I fix this?
"geo-craft" is the problem.
Moderator: BK
Forum rules
Please keep character renders sensibly modest, please do not post sexually explicit scenes of characters.
Please keep character renders sensibly modest, please do not post sexually explicit scenes of characters.
- withgoodman
- Posts: 19
- Joined: Tue May 21, 2013 2:10 am
3dmania wrote:Hi,
have you tried to subD the area of effect?
Of course, same results.
Look at the attached picture on the right things.
The default renderer is fine.
to me this much looks like faulty geometry; studio's internal rendering smoothing defaults to 89.9 degrees where octane uses a much lower overall angle.
what might help is to apply a smoothing modifier and set it to ~5 iterations.
ps: to investigate this further i'd need the scene & graft to reproduce it...
what might help is to apply a smoothing modifier and set it to ~5 iterations.
ps: to investigate this further i'd need the scene & graft to reproduce it...
„The obvious is that which is never seen until someone expresses it simply ‟
1x i7 2600K @5.0 (Asrock Z77), 16GB, 2x Asus GTX Titan 6GB @1200/3100/6200
2x i7 2600K @4.5 (P8Z68 -V P), 12GB, 1x EVGA GTX 580 3GB @0900/2200/4400
1x i7 2600K @5.0 (Asrock Z77), 16GB, 2x Asus GTX Titan 6GB @1200/3100/6200
2x i7 2600K @4.5 (P8Z68 -V P), 12GB, 1x EVGA GTX 580 3GB @0900/2200/4400
I've narrowed down the situation that the problem seems to happen most for me. It occurs on geografted objects that have custom morphs. Specifically morphs that change the location of polygon edges on the geografted model that are supposed to be aligned to polygon edges on the main figure for geografting.
Here is how I reproduce the problem.
I open a fresh scene.
I load a figure.
I load a geografted item onto the figure
I apply a custom morph on the geograft item that has polygon edges that are misaligned to the corresponding edges on the main figure for geografting
I open the Octane render plugin panel
I open the viewport
When I the viewport in the Daz Octane plugin it will render perfectly fine with no problems in geometry.
At this point, if I hit reload on the Octane viewport window, the geometry shows signs of breaking from the smooth surface that existed before. The result looks similar to the image on the first post. Upon closer inspection though, it looks as if the geometry was loaded correctly with the geografting working correctly, but another instance of the geografted item gets placed on top of the figure with offsets in xyz translation.
At any point in the process, if a custom morph exists and the Octane animation feature is started, the geometry problems start immediately. They are not as noticeable without any morphs applied.
It seems to me that the problem seems to be associated with the functions behind the reload button on the Octane viewport.
The button works for normal geometry just fine, but this special case of geografted geometry causes errors.
The plugin works perfectly except for this one little snag. I would hope it gets addressed soon in an update. I have enjoyed using the Daz Octane plugin and have really gotten some amazing results. The UI is intuitive and after playing with the plugin, i've found that it really lets Daz users implement some of the best parts of Octane in a workflow that is reasonable considering how different Daz and Octane are in their control schemes.
I would really appreciate some assistance on this matter if anyone could provide any.
Here is how I reproduce the problem.
I open a fresh scene.
I load a figure.
I load a geografted item onto the figure
I apply a custom morph on the geograft item that has polygon edges that are misaligned to the corresponding edges on the main figure for geografting
I open the Octane render plugin panel
I open the viewport
When I the viewport in the Daz Octane plugin it will render perfectly fine with no problems in geometry.
At this point, if I hit reload on the Octane viewport window, the geometry shows signs of breaking from the smooth surface that existed before. The result looks similar to the image on the first post. Upon closer inspection though, it looks as if the geometry was loaded correctly with the geografting working correctly, but another instance of the geografted item gets placed on top of the figure with offsets in xyz translation.
At any point in the process, if a custom morph exists and the Octane animation feature is started, the geometry problems start immediately. They are not as noticeable without any morphs applied.
It seems to me that the problem seems to be associated with the functions behind the reload button on the Octane viewport.
The button works for normal geometry just fine, but this special case of geografted geometry causes errors.
The plugin works perfectly except for this one little snag. I would hope it gets addressed soon in an update. I have enjoyed using the Daz Octane plugin and have really gotten some amazing results. The UI is intuitive and after playing with the plugin, i've found that it really lets Daz users implement some of the best parts of Octane in a workflow that is reasonable considering how different Daz and Octane are in their control schemes.
I would really appreciate some assistance on this matter if anyone could provide any.
thanks for the detailed report jth0087!
this is really helpful to dig into that issue. the way how studio manages grafts was already a little hard to get by when implementing it, since every graft means the geometry actually exits twice - in its unaltered form, and in the grafted from. the plugin now tries to find out where grafts do exists, and then skip the original geometry in favor of the grafted one.
thus your explanation makes perfect sense, as it seems that this fails under certain circumstances - what would help to investigate this, is to have a prepared scene with this issue, where i can trace the way how the geometry is updated (and when)...
this is really helpful to dig into that issue. the way how studio manages grafts was already a little hard to get by when implementing it, since every graft means the geometry actually exits twice - in its unaltered form, and in the grafted from. the plugin now tries to find out where grafts do exists, and then skip the original geometry in favor of the grafted one.
thus your explanation makes perfect sense, as it seems that this fails under certain circumstances - what would help to investigate this, is to have a prepared scene with this issue, where i can trace the way how the geometry is updated (and when)...
„The obvious is that which is never seen until someone expresses it simply ‟
1x i7 2600K @5.0 (Asrock Z77), 16GB, 2x Asus GTX Titan 6GB @1200/3100/6200
2x i7 2600K @4.5 (P8Z68 -V P), 12GB, 1x EVGA GTX 580 3GB @0900/2200/4400
1x i7 2600K @5.0 (Asrock Z77), 16GB, 2x Asus GTX Titan 6GB @1200/3100/6200
2x i7 2600K @4.5 (P8Z68 -V P), 12GB, 1x EVGA GTX 580 3GB @0900/2200/4400
I have a quick geograft where the left arm has been replaced by a duplicate left arm that has been geografted onto the genesis figure. It should be saved with a morph that enlarges the end of the geograft arm. Please let me know if if does not load correctly for you.
- Attachments
-
- Test Scene for Octane t_3.zip
- Test Scene
- (180.18 KiB) Downloaded 236 times
I don't have this particular item, but I have always had problems with other geografts. The way I solve it is to press final render twice (I think caus that reloads the geometry).
DAZ Store: http://www.daz3d.com/elele
Renderosity Store: https://www.renderosity.com/mod/bcs/vendor/elele
Deviant Art Page: http://eleleoke.deviantart.com
Renderosity Store: https://www.renderosity.com/mod/bcs/vendor/elele
Deviant Art Page: http://eleleoke.deviantart.com