degenerated/inefficient RT hierarchy??
mambanegra
Posts: 586
Bought a product tonight and I can't render it using GPU because of this error. Is there any way that I can fix this? I submitted a ticket, but I was really excited to use it. It renders fine on my Mac via GPU but it won't even start to render on my windows machine with a GTX 980. Here is the actual error from the log. This was one of the items from the 65% discount, so it is weeks old at least, since it wasn't too new to be discounted...so, you would think other folks would have run into the problem by now. I'm still clinging to the non-beta version (4.8.0.59 or something)
WARNING: dzneuraymgr.cpp(261): Iray WARNING - module:category(IRAY:RENDER): 1.4 IRAY rend warn : RTKernel: please check the input geometry (degenerated/inefficient RT hierarchy)
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
What is the actual product?
It's the productivity area. I tried the full scene as well as just loading the complete set. Both crash DS when it tries to render the very first pass: (removed silly link choice...see khory for correct link)
Your link takes us to our own product lists. Is this the product? http://www.daz3d.com/i13-productivity-area-and-poses Is it the ready to render scene or an individual prop that is giving you the error?
Ooops, I thought that link looked weird. Khory, The product you linked to is the right one. I first tried one of the completed scenes, which includes environment settings and everything (replacing your entire scene). The full scene crashed DS. I tried it several times using different cameras and it always crashed when trying to render the very first pass. Next, I tried using the full set (it included all cameras, but didn't replace my default scene). That too crashed. I didn't try to identify which individual prop was causing the problem. I just called it a night and went to bed.
That may include one of the problem settings/items that will crash in 4.8 but is fixed in 4.9...
DAZ really shouldn't be selling stuff that won't work on the non-beta version of their software. That's just crazy. If I were using an older version than the official, that would be a different story.
Most of the problem is Iray related...certain settings/items cause the problem, but not on all machines and sometimes it is only when a full scene is loaded from a preset. And to compound the issue, it isn't a problem on the 3Delight side of things...
So it is not really that they are selling things that don't work in the current version...it's more like they may not work for everyone, in the current version, but should work for everyone after the updated Iray version is included (it's in the beta, now, hence, 'they work in 4.9).
And most all the items with this problem...it doesn't show up until AFTER it is being sold and in wide use (mostly because it isn't a universal problem...it's not like put a red color on 36 poly cube and it will crash...it's more like do this, with this setting and have it set to x subdivison and rotate 39.6deg...and maybe 30% of the people doing this will have it crash).
Ugh, apparently DAZ has totally washed their hands of 4.8 and this crash even though they are very well aware of it. I got confirmation that some products simply aren't compatible with 4.8 and windows 8/10 and that the only way to use those is to install the beta. So, now I have to decide whether I want to install a potentially buggy beta or ask for a refund...
4.9 is going to be out in the near future...at this point, I'd just wait.
My guess, before March 1st.
I'm not sure what you mean by "washed thier hands" the only way to fix an old version is with a new version. Which 4.9 is.
No, they could patch 4.8 with the necessary fix to prevent this crash, which they obviously know how to fix. My version is 4.8.0.59 or something like that. They could bump that up to 60 with a fix for this problem. There is a reason that 4.9 isn't out of beta, and it isn't because it doesn't crash on certain scenes for folks using newer versions of windows.
BTW, after I was a bit grouchy to the tech support person, she responded that there was a fix, and it works! It probably slows overall rendering down, since you are no longer going to be using the CPU and GPU, but at least the renders can complete in reasonable time. I'm copying from her email, which hopefully won't upset her for my lack of permission:
The scene is at 87% after about 4 minutes, so I'm inclined to believe the workaround does just fine. Before unchecking the CPU options there, I couldn't even get to 1%.
Daz has never done patches. They do new versions. If they did not have a new version so far along in beta they might do a smaller version but at this point they have put so many months into it that they might as well just finish up and get it out there. There is at least one important update to Iray that needs to be implemented as soon as possible as well so there are a variety of reasons for the new version.
It isn't Daz that is fixing the problem...it is Nvidia and the only fix Nvidia is offering is the next version of Iray. That said, putting the new version of Iray into 4.8 would take as much effort as the already being worked on next version...and slow down/stop work on the next version.
Good point mjc.