3ds max is crashing when accessing textures on ASUSTOR NAS

[wmiler]

Hey guys,
I am facing the following problem.
I have an ASUSTOR NAS AS6404T, with 4 HD in raid1, so 2 volume.
I've had it for about 2 years, so far no problems.

But since Saturday, I'm having problems with the max.
Only max is unable to access the textures that are stored on this NAS.
Windows explorer, photoshop, premiere, etc... everything is normal.
But if I open a scene in 3dsmax that has a texture that is on the NAS it crashes.
Even starting a scene from scratch, and putting a simple texture on a material, it freezes.
I've tried everything, changing cables, resetting, formatting the PC, reinstalling the max, changing the version of the max.

But without success.

Does anyone have any tips?

[wmiler]

I'm doing tests, and the problem only happens with Corona, with Vray it's normal.
It simply freezes when using a texture that is on the NAS.
If the texture is on a local HD, I have no problems.

[wmiler]

It seems that the NAS created a certain blockage for the 3dsmax+Corona, as the problem occurs on all my PCs, not just 1.

[Avi]

What version of 3ds Max you are using?

Can try the following troubleshooting steps?

1. Check if your NAS is using a compatible SMB protocol version with your PC (preferably SMB 2 or 3).
2. Make sure the NAS permissions are correctly set, allowing full read/write access to the folders where the textures are stored.
3. Use UNC paths (e.g., \\NAS\Textures\) in 3ds Max instead of mapped drives.

https://www.autodesk.com/support/technical/article/caas/sfdcarticles/sfdcarticles/Working-with-multiple-copies-of-3ds-Max-across-a-network-environment.html

https://forums.autodesk.com/t5/3ds-max-forum/max-2022-crashing-after-every-render/td-p/11095739

4. Temporarily move the textures to a local drive to see if the issue persists.

If the issue persists then please attach a minidump here or contact us via ticket.

https://support.chaos.com/hc/en-us/requests/new

[wmiler]

I'm using 3ds Max 2024 and Corona 11 HF1,
but I tried to solve it by installing several different versions of Corona and 3dsMax. I installed the latest version of 3dsmax and Corona, but without success.
1. The NAS seems to be correct, as you can see in the attachment, I tried changing it there.
two . Permissions are all released.
3. I also tested changing the UNC path, I even checked this option in the 3dsmax settings.
4 . The problem only occurs with CoronaBitmap, with the 3dsmax bitmap it is normal. And the problem only happens if the texture is on the NAS. On a local HD everything is normal.

[wmiler]

https://we.tl/t-fsGCeL9srG?utm_campaign=TRN_TDL_05&utm_source=sendgrid&utm_medium=email&trk=TRN_TDL_05

I went to wetransfer, recording the screen when the problem occurs.
3dsmax doesn't give the error screen, it simply freezes, so I recorded it with ProcessMonitor.

[Avi]

Hi,

Thanks for the video and your test.

Can you let me know if the problem is only isolated to Corona bitmaps? while loading other corona assets like luts and Corona proxy are working fine for you?

Is it possible for you to upgrade to Windows 11 or to make sure your windows is fully updated when you are making these tests?

[wmiler]

The problem only occurs with CoronaBitmap.
With the 3dsmax bitmap it is normal.
Every model, proxy that has any material with Coronabitmap, causes problems when trying to open or import.
Old scenes with Coronabitmap sometimes open, sometimes not. And when it opens, then it freezes.
The problem is happening on all our computers.
We have computers with Windows 10 and 11, all of them updated.
I tried updating everything, 3dsMax, Corona, Windows, but it doesn't work.
I tried help with ASUSTOR support too, they suggested changing the HDDs, but that didn't help either.

[pokoy]

Have loosely followed the thread, so sorry if it's been mentioned and tested already, but could out of core features have something to do with it? They're created only for Corona bitmaps so might be worth trying to disable that feature.

[maru]

Good call!
@wmiler please try the following:
- open any existing scene, or even an empty scene where you are able to reproduce the crash
- go to Render Setup > Performance
- disable "Automated out-of-core textures" checkbox at the top
- save the scene
- open the scene again
- check if it still crashes or not

[emmanoel3d]

i have the some problem, my NAS is ASUSTOR AS6508T, CoronaBitmap not working, viewport is very very slowly. When we do convert coronabitmap to bitmap, the scene works well.

[emmanoel3d]

appears in the left side bottom the message: 0 shaders compiling, when i try open the scene. I need turn off the network to open the scene, is crazy.

[emmanoel3d]

Good call!
@wmiler please try the following:
- open any existing scene, or even an empty scene where you are able to reproduce the crash
- go to Render Setup > Performance
- disable "Automated out-of-core textures" checkbox at the top
- save the scene
- open the scene again
- check if it still crashes or not

did not work

[wmiler]

It didn't solve it.

Below is the video demonstrating it.

[emmanoel3d]

Good call!
@wmiler please try the following:
- open any existing scene, or even an empty scene where you are able to reproduce the crash
- go to Render Setup > Performance
- disable "Automated out-of-core textures" checkbox at the top
- save the scene
- open the scene again
- check if it still crashes or not

maru, can you send it to the developers for any solution? because it seems like something serious that will affect studios