the proposed method is very crappy, so I won't see the render progression or the tonemapping options, etc.
Hi kino_unico and everyone else experiencing this issue. Here is the status update:
So far we've had about 5 users with this issue. In most cases it consists of the two following symptoms: 1) Rendering randomly freezing at various stages (it can be denoising, parsing, or other) unless the VFB or other part of 3ds Max UI is moved by the user with the mouse cursor.
2) Appearing sometimes, randomly, if the VFB is disabled in Render Setup > Common: "Internal error: device or resource busy" error message.
Conditions: 1) Using a remote desktop software such as Team Viewer or Chrome Remote Desktop.
2) Using 3ds Max 2022.
Possible solutions:1) Fully uninstall the remote desktop software that you are using and clean up any leftovers from it, then restart your computer. For example, if you are using Team Viewer, you should uninstall it from Windows and then remove all registry entries as explained here under "advanced":
https://community.teamviewer.com/English/kb/articles/16835-uninstall-teamviewer-on-windows 2) Use Max 2023 instead. We haven't had any report of this in Max 2023 and the affected users confirmed it is not happening for them in Max 2023.
Disabling the VFB is just a workaround. It may work, it may not, it may cause some other issues (like the "internal error").
What to do if you are experiencing this and cannot apply the above solutions:Capture a minidump file from 3dsmax.exe when it is frozen.
A minidump file does not have to be generated during crashes. You can simply download Process Explorer and capture a minidump from 3dsmax.exe at any point.
Here are the instructions how to do it:
https://support.chaos.com/hc/en-us/articles/4649117083409#h_01FDY55JCQMR188S36A1F0SS1T Then, send the minidump to us along with the description of the problem:
https://support.chaos.com/hc/en-us/requests/new What happens next:We will investigate the minidump file and we should be able to tell what exactly is causing the freeze in your case.
We also have some special internal daily builds which are created for mitigating this issue. Once you contact us, we can send you those special builds so that you can check if they work. We would like to include a fix for this in Corona 9.