Posts by Alexander Devaykin
sure you can disable it - see attached settings screenshot. You've probably enabled it once, because this feature is disabled by default.
Issues with rendering big screenshots on RTX is a mixture of GPU memory amount needed and how memory is managed when RTX is enabled. We are aware of this and work on a solution (or at least significant improvement) for 2.7.
Demian Gutberlet I think the black/colored noise on the textures is the problem.
gusta it should be enough if you send those problematic textures for us to take a look. PM me.
Maybe tuning fog to 100% will do what you want?
Yes, AMD Radeon RX 570 Series. Seems there is no workaround which is annoying. Is there something AMD can update from their side?
I'm assuming this causes the same issue in Rhino 6 with clipping plane which does not display correctly.
We've seen it on multiple AMD GPUs, both pro and consumer devices. We've also tried to workaround it with no luck. This is unfortanutely the result of how AMD drivers or hardware work. Not sure if Rhino section plane issue is caused by this particular defect, but AMD GPUs sometime show quiet some unexpected behavior.
Are you using an AMD GPU?
Hello Michael Ruehr
The BIM mode will enable BIM data display in Enscape and some interaction with it. This feature is on the early stage at the moment. You can enable it by pressing "B" in Enscape:
Just downloaded latest preview version and was eager to test the new orthographic projection mode but the Projection pulldown menu seems to be disabled in SketchUp version?
It should be available everywhere. Try to close Enscape window and start again without closing SketchUp, there seems to be a bug which leads to hidden projection type selection UI on first run in some cases.
We have reproduced the problem and opened a bug report. Thank you for reporting!
Better texture scale handling is work in progress - hold on Specially for such cases.
Thank you very much for the deep investigation of the issue. The best way for us to find out what's up would be to have the sketchup scene to reproduce the bug. Maybe this grid alone lets Enscape crash even if there is no other geometry in the scene? In this case it would be enough to have the grid to debug.
If you cannot send the sketchup file, you still could try to create a standalone exe with this scene on an older machine, try to run it on RTX laptop and send us the standalone if it will crash with RTX.
In any case, you may also send us the logs and crash dumps via feedback button (see my post signature). It is also the best way to get in contact with the support to send the scene file if you can. Thank you in advance!
Let me know if there is a time-line to when this issue might get resolved
There are a few bugfixes to the RTX implementation pending to be released. The major issue was, however, memory consumption which was reduced. There is no particular hotfix release date at the moment, but it should happen very soon.
Sad to read that. Sounds like a good candidate for the hotfix release. But we need some more information to tackle it down. Could you give more precise step-by-step instructions? If I got it right:
1. Open CAD (Sketchup?) with a project
2. Change some Enscape settings
3. Start Enscape
4. Change some Enscape settings
5. Save settings to project
6. Close Enscape window
Currently there are no outlines for the transparent/semitransparent geometry. We have planed this functionality already. Not sure if 2.7 will have it, however.
Safe frame preview keeps rendering in the window resolution minus areas behind the frame. You are always welcome to send the feedback with logs so we could have a look. Even better if you attach the steps to reproduce the crash
This functionality is actually work in progress for the future releases. No guarantee that 2.7 will have it, but we are working on it
Thanks for report bsfranza
Which version do you use? I cannot reproduce with 2.6.1. This is what I have tried:
1. Enable "Safe frame"
2. Click Screenshot button, see Safe Frame
3. Change capture resolution
4. Change window size (rendering resolution)
With all my respect to all the Enscape personel, I know they are working hard, and they are so nice. But I wonder did not nobody try to get a 4k render before the release of "major" RTX support of Enscape?
Crash possiblity depends on the current OS environment, other running applications and GPU usage, project contents, uptime and lots of other factors very much. Chances to get out of VRAM have grown with the introduction of RTX, but it does not mean it will crash directly. If it would crash directly by the first attempt to do a 4k screenshot on a typical scene, we would catch it immediately
Guys really? Lets decide it honestly, RTX is a good thing or a bad thing for Enscape?!
RTX gives Enscape ability to render better reflections, among other phenomena, compared to non-RTX. There is also enough space for further improvements in e.g. shadows quality. So visual quality is better with RTX, and will get better with the time when we will adopt more rendering passes to use RTX where possible. From this point of view, RTX is a good thing for Enscape.
But there are issues of course, which is expected given how young this technology is. Current major issue is that you may get out of VRAM easily when you render big screenshots (>= 4k). This is of course not a good thing. Fixing or at least mitigating this particular problem is work in progress for the possible 2.6 bugfix or 2.7 release.
Our first priority for the RTX implementation now is to make Enscape with RTX work more stable and fix known issues. Further visual improvements are also planned. So the bad thing can go soon and RTX users will end up with the good tool in hands.
I think it's up to you to decide if it worth it right now. RTX is the cutting edge tech with all the pros and cons for those who want to use cutting endge features. There are comparisons of Enscape with and without RTX in the showcase section to help you make a decision.
The minimap is not supposed to work in web standalone. There is also no way to turn it on or off in web, except for exporting for web while having minimap active on the desktop. Which is a bug which I've recorded thanks to your report!
We have minimap for web on our agenda, but there is no exact ETA yet.