Consider adding a TdrDelay of 15, 30 or 60 and see if the error gets resolved. Export times might be longer than expected but will avoid the crashing issues.
Check to make sure you have the proper dedicated GPU for Twinmotion if you have several GPU. https://twinmotionhelp.epicgames.com/s/article/Use-your-dedicated-GPU-with-Twinmotion-on-a-Windows-computer
When considering if a GPU crash is related to a specific driver. You may also want to check with the manufacturer also for known issues this driver may cause.
When considering if a GPU crash is related to the operating system, all of the above information applies. Also, for Windows, we strongly recommend using version 20H2. You can find out which version of Windows you are using by pressing the Windows key and typing in winver.
I have the same exact issues! Please Vincent could you explain or tells us about a solution on the way? I have deadlines for my project and the Path Tracer is driving me crazy on the new 2023 version. In my case I'm trying to open a 2022.3 project with the conversion tool, and 2 out of 3 times when it does open correctly and I try to use the PT it goes black and crashes after a few seconds. I'm using a new computer with RTX 4090 and also 64 GB RAM so I'm sure the GPU is not the problem. Thank you in advance.
For anyone using AMD graphics card, go into AMD Software and under graphics disable everything that you see there, including all the things under advanced, this should make Twinmotion more stable
Thank you for posting in the community and sorry to hear about this crash. This is a common GPU crash and hard to diagnose but we are investigating those crashes further with the manufacturer.
Check to make sure you have the latest Windows OS and builds, and latest Drivers. Make sure you have installed the DirectX as well.
For future crashes and bugs you can directly contact us by using the [ contact us ] button from the home page or this link:
Try opening Twinmotion 2023.1 then changing the quality setting to low and then open the file and export the renderings to see if the issue is still happening. I imagine it's happening in larger scenes and not an empty or simple file?
If the issue is still happening you can contact us directly by using this link: