This is the error I receive on the initial crash (line 606) and indicates an -assertion- failed
Steps to recreate. Restart Windows. Run Chief. Start a new plan. Draw a basic 4 wall closed structure accepting all defaults, and put in two windows and a door. Place a full camera and change from standard view to PBR.
C:\p4sync\ryan3070\dev\Astral\Releases\1.2\Astral\AstralEngine\Astral.cpp(606): Error #272032746
"An internal rendering error has occurred (assertion failure): !"Astral::update caught Exception""
11/4/2022 12:54:32 PM
Build: 23.4.1.8x64
Thereafter, after the initial crash, and clicking away to close the 3d window gives this.. (exception now)
C:\p4sync\ryan3070\dev\Astral\Releases\1.2\Astral\AstralEngine\Astral.cpp(609): Error #272032746
"An internal rendering error has occurred (assertion failure): !"Unknown exception caught in Astral::update""
11/4/2022 12:55:03 PM
Build: 23.4.1.8x64
This happens with the latest Studio & Game Ready Drivers from Nvidia. Game Ready Driver version 526.47
Running Chief 23.4.1.8x64, on a laptop with an RTX 2080 (8 G of Graphics Memory), 16 GB RAM (14 GB usable) feature set 6.5 supporting Chief Minimum requirements (displayed in the program as well) Windows 11 Pro 21H2, build 22000.978 with Feature Experience pack 1000.22000.978.0, Intel(R) Core(TM) i7-8750H CPU @ 2.20GHz 2.21 GHz
I have tried the program with all defaults, turning OFF Windows Hardware based GPU Scheduling and variable frame rates , removing any NVIDIA components in the system tray, and turning OFF any video game based overlays.
I also experimented with the lighting settings in the CAD, and Lighting Menus (using a sun angle, using a generic sun, using backdrop image, rendering with the default light set, or a custom light set).
These do not seem to affect the error I am getting. CPU ray tracing works but it really slows down my workflow.
@Kbird1Thank you for the suggestion. I rolled back to 522.25 , getting the exact same problem. Will investigate to see if messing with any Windows or Chief options changes things (or gives me a different error ) in this configuration. Will revert once tested.