Using 3.2 at the moment. This crash appears to be only isolated to this SketchUp model or the file. Based on the crash the error is due to memory limits on Ray Traced Shadows, It is odd as this is a small file and my PC reports look fine.
Any thoughts or ideas to this crash? Has anyone run into this?
I had one model that wouldn’t render specific views but would render others.
What I determined what that the problem views had a lot more proxy’s in them (flowers in my case) than the others. These were proxys of my own making via Transmutr with quite dense geometry.
I found in testing that I could render if I either deleted some proxys or turned the camera slightly so that less were in the view.
As a test will it render if you point the camera somewhere less complex such as the sky?
Okay - think you are onto something. So I remove my "Skatter" of Enscape Trees and now the project file appears to be running smoothly. So this raises the big question - Does the latest version of Enscape have a limit? Is this due to the number of objects within a scene? Is this a known issue?
I'll test an older project render with 2.9 and see if this is really the cause.
Edit:
review a few projects developed using 2.9 with a great deal of "skatter" objects. These are projects that performed flawlessly in 2.9. So is the issue with the number of objects being calculated with the Raytrace sun or something new with 3.2? I do notice a massive jump with VRam now.
Edit:
So RayTraced shadows add twice the amount of weight to GPU. If enable it maxes out my GPU and can't render. Did a render with RXT off and YIKES this is bad. Very glitchy and noisy.
I have an 8gb 2070 , I have all the RTX stuff turned off or I’ll crash 99% of the time with them on.
Couple of questions:
I have an 8gb 2070 , I have all the RTX stuff turned off or I’ll crash 99% of the time with them on.
Couple of questions:
- Will it render with the RTX stuff off?
- Are all the Enscape trees placed recently or were they placed in an earlier version of Enscape? I ask as some trees were deleted from the library and if the proxy’s are still used it could be a cause.
- Instead of deleting stuff will it render if the camera points at the floor or sky?, ie, very little geometry in the view.
So testing now turning of RTX Sun Shadows.
Project files that are being tested are files that were developed with 2.9
Just test a very heavy skatter file and in the viewport works but can export a render.
I use Skatter to place a very dense curtain of trees around my houses. I’d say at least 400 Enscape trees would be a safe bet and that’s on top of all the interior furniture so I doubt it’s an object limit.
This model has 1000’s of scattered trees, bushes, plants and renders ok.
Video wasn’t a problem either
But as I mentioned above I have all the RTX stuff off.
yeah, the project in question has roughly 5500 component instances with RTX Sun Shadows on the setting completely nerfs my 3090.
Here is a comparison with the GPU loads with RTX sun on and off.
So I think moving forward I'll opt out of RTX sun on large projects. Maybe the dev team and produce an algorithm that can apply RTX Sun to objects within a set distance. Objects in the distance have little benefit.
Oh man, a 3090. Just out of interest is there any particular time of the day that’s left unattended…. Asking for a friend 😈
That must be some model to have burned through 24gb, textures will fill the memory damn quickly, do you have many large textures such as 4k grass maps?
There is a SketchUp plugin that will list all the jpg’s used and their size. I found one of my biggest offenders was a texture used on a wicker basket I’d downloaded from the warehouse, it was stupidly large and I knocked it down to meer kb’s.
Oh man, a 3090. Just out of interest is there any particular time of the day that’s left unattended…. Asking for a friend 😈
That must be some model to have burned through 24gb, textures will fill the memory damn quickly, do you have many large textures such as 4k grass maps?
There is a SketchUp plugin that will list all the jpg’s used and their size. I found one of my biggest offenders was a texture used on a wicker basket I’d downloaded from the warehouse, it was stupidly large and I knocked it down to meer kb’s.
The time of day was noon. I didn't try changing the time as I really don't believe it would change the impact on the GPU as the path data will still be calculated.
General I use or general custom map with a max resolution of 2K or lower Maps. No need to go higher at least in my situations.
This model itself is nothing out of the ordinary - 45MB. However, with 5500+ objects. I suppose I will need to be more aware of the number of objects and their placement if I want to use RTX Sun. This is where statistical data from Enscape would be amazing. At the moment my setup will crash at or around 5500+ objects with RTX Sun on. I'll try some new testing and see how the results vary.
Been looking potentially at upgrading to a 3080 and have been set on the 12GB variant. But damn, if this crashes a 3090 with 24GB....damn.
Been looking potentially at upgrading to a 3080 and have been set on the 12GB variant. But damn, if this crashes a 3090 with 24GB....damn.
I still believe the 3090 is the best card to have. The 3080 will most certainly get the job done. This is the first time that I have maxed out the 3090. Enscape integration of path tracing "sun shadow" is a major step in the right direction. However, the impact on skatter elements calls for more creative workflows. I have some workaround ideas, but I would love to see a hybrid solution that integrates 2.9 and 3.3. Such as turning off RTX sun support but keeping RTX reflections.
Great examples:
This is a project I did last summer with 2.9 using a 3090. A rough estimate was maybe just under 14GB of VRAM. The entire project was contained in one model making rendering simpler. I believe this is where Enscape shines the brightest. With the latest build, I can not run this model with RTX enabled.
Here is another project built with 2.9 where the size and scope are twice that of the video above. Again, a well-optimized model in one project file 14GB of VRAM. You can see the density of this project within the marketing renders shown on the website. Again with 3.3, I can't enable RTX without a crash.
(Our scope was only exterior so interior content shown was a different firm.)
https://uptown.azurewebsites.net/about-uptown/#location
I have several other projects that are similar, and built with 2.9 that could be viewed with RTX however, the new Sun support nerfs the card causing me to disable it.
So the project that started this thread turned out stellar even with RTX disabled. Reflection quality took a hit, but still the team was happy with the result. The dev team could probably better explain or share more details about what the RTX settings are doing. Sure would love to see some option settings if possible. =D
Phew! With that kind of vegetation, I'd be looking more closely at TwinMotion vs SU/Skatter. Their landscape vegetation tools are next-level compared to Skatter/SketchUp. IMO, I reach the end of SketchUp's capabilities long before Enscape's. So, while I'd love to have a 3090 with 24 GB at my disposal, I have 11GB now with my 1080ti and stay pretty clear from that with my use case. Understanding now that RTX features in Enscape might be a RAM hog though- thats something to consider in the future for my upgrade. SketchUp drags its knuckles enough as it is when my larger models, and I'm nowhere near the RAM limitation my system provides.
Undervolt that 3090 btw.
