Hi. Just some feedback in case they read here. When I export video with path tracing, my computer bluescreens around 1 min into the render.
Windows 11
32gig ram
RTX 3080 12gig vram
Core i7 11700k
Nothing is over clocked or anything.
I am keeping a close eye on things, temps are ok, GPU is at 100% load as I would expect but running at 60oC
CPU are around 50% ram at around 50%
I think its just something in the programming. I am running the latest 23 beta. Sadly I have not done a terrific amount of video export so don't know if it relates just to this build.
Well what ever it is, its fundamental. I reinstalled it, and it crashes the computer every time on an export with path tracing. Also tried it in a new user account, same result.
Thanks but thats from over 2 years ago and I would imagine does not relate to this issue. I have never had to touch registry before an I have been using twinmotion since its first beta
It would be a real shame if they had not fixed it in all this time. This being said it got so bad I reverted to the last release of 2022 and its behaving perfectly. I'll skip this beta until the next one.
With Twinmotion 2023.1, we've transitioned from utilizing Unreal Engine 4.27 to Unreal Engine 5.0.3. In this version of Unreal Engine, support for DirectX Raytracing (DXR), which is the DX12 feature that enables Path Tracer, was removed for Nvidia's GTX 10 series cards, due to stability issues identified by Nvidia and the UE developers. As such, Twinmotion inherited this, and as of 2023.1 Preview 1 any GTX 10 series card won't support Path Tracer.
You can still utilize Path Tracer on the 2022 versions of Twinmotion, but you will need an Nvidia RTX series card or an AMD Radeon RX 6000 series or newer for Twinmotion 2023 going forward.
Hello, I also have a lot of problems with Pathtracer or general with program, when it starts to render on screen whole computer is not usable, even changing menus in TM takes minutes. also a lot of crashes ( did find out that I had to turn off Steam becasue it uses some part of graphic that TM wants to use and then the TM crashes)
By way of an update. It was something to do with my rig and I dont know what, I pulled the graphics card and reinserted and now all is fine. Dont you just love computers!
I do not get BSOD as you, but sometimes my computer freezes so even the mose is not moving and computer is stuck. I have to hard restart it with button on pc.
In that case, since your GPU is supported, have you tried updating your GPU drivers recently? Faulty drivers are known to cause BSODs, so an update to a recently released faulty driver might cause the issue, requiring a rollback, or if you haven't updated in a while, the old driver might be faulty and requires an update.
It would also be helpful if you could submit a bug report here and attach copies of your Twinmotion.log files from when the BSODs occurred so we can investigate these issues in more detail and try to get them fixed by the next update.
If your computer is freezing while running Twinmotion, it could indicate that your computer is running out of resources while operating; either CPU, VRAM, or RAM usage is being maxed out. Usually, it is due to running out of RAM or VRAM. In these cases, you would either need to reduce the complexity of your scene by lowering quality settings or removing/hiding content, or install more powerful components, like a stronger GPU or additional RAM.
If hardware utilization doesn't seem to be the cause, please submit a bug report here and share your Twinmotion.log files (Where to find Twinmotion .log file) so we can investigate the cause in more detail.
Running the version prior to this has been flawless
Running this initial beta of 2023 its been fine then it started going wrong, then it fell off a cliff.
Something is amiss with the programme, I don't think my computer is running out of resources. I can monitor everything in real time, everything is 50% apart from the GPU which is maxxed out I would expect this.
Apologies for the confusion Irwin . this response was directed to @matuso ff regarding their issue. You can ignore that since it does not apply to you. My response to you is located in a thread further up this page.