IPR + save = crash

Just wondering if anyone else has this issue. If I hit save while IPR is running I get a failed save message and a crash with no recovery. Very annoying of course. I think I’ve set my cameras up today 3 times and lost it all because of this…
Some people I know do have this issue too so it’s not just me but I’m wondering how widespread it is.

max 2026. Vray 7.20.04

Tested on Max 2025 / Vray 7.20.04, in a simple shaderball scene (Just plain 3dsMax geometry). No issues here.

Installed 2026, with Vray only as plugin, also no issue. Maybe a plugin? ForestPack? RailClone? Do you also have it in a simple scene with only Max and Vray stuff?

It’s so random it hard to pin down, but yes I will endeavor to provide a scene at some point.

Narrowed it down to ForestIvy.

Share a scene whenever you can, please.

done.
mandatory 10 characters.

Tested saving with IPR and ForestIvy on 2025 with FP 9.1.5 (not latest, year old or so), and it doesn’t crash here. So maybe something got borked in a FP update.

Chaos support reports they are getting the same crash. It must be some specific thing happening post-save like an FP node rebuilding and failing somehow.

Better to contact iToo as well then I suppose, glad I didn’t update/pay for a renewal yet. Their latest updates are riddles with annoying bugs (the core lock freeze, delete not working anymore after opening the listers, etc,…)

omg so THAT’s where this bug comes from. SO annoying.

But what is this bug? I probably know it, but the name I’m not familiar with…

Yeah the delete bug should normally be fixed (last year around november) but it came back, not sure if they fixed it completely, I still didn’t refresh my subscription cause they fixed it right after mine ended. I just scripted my own delete and bound it to shift+delete otherwise I would restarting Max every 5 minutes.

The other bug was the one we were all chasing for 2 years where having multiple Max instances open slowed down our workstations when saving, having huge lag. They fixed it in 8.2.5

  • CPU Affinity Correction: An important fix was implemented not just for Forest Pack but also for RailClone. Previously, both plugins incorrectly set the CPU affinity of the 3ds Max process to core 0, leading to CPU overhead when running multiple instances. This update rectifies that, optimizing performance for users running complex or multiple projects.

Ah yes that one…

Yes, this crash should be fixed at the Itoo side. Not only the save process can lead to crashes, but hiding/unhiding/ deleting FP nodes. It looks like multiple FP nodes should be presented in the scene including FP Ivy.

Forestpack is extremely unstable in general in my experience. It’s probably responsible for 1/2 my crashing. If only Chaos scatter was a little more developed I would ditch FP entirely.

We have identified and fixed the IPR issue. It happens when there are ForestIvy and Forest objects in the scene.

We’ll publish a Forest Pack update in the next days.

Thanks for the quick Fix Carlos!

For anyone else who might need the info: Itoo created a patch and it seems to have solved the problem. It will be included in a future public update.