Itoo Software Forum

Author Topic: Forest Pack crash when using Custom Edit and Random Samples  (Read 611 times)

normandthegang

  • Newbie
  • *
  • Posts: 1
Forest Pack crash when using Custom Edit and Random Samples
« on: August 23, 2023, 09:42:35 PM »
Hi everyone!
We have an issue with forest pack crashing.
Forest pack crashes when using Custom Edit Item mode, along with Enabling Animation random samples mode.
The file will crash when clicking render (we are using Corona 9 Hotfix 1). We have tried a few different trees along with the forest pack supplied sample trees. It still crashes. We have upgraded to the latest 8.22 version from 7.31.
We upgraded because we were also experiencing issues with the same settings ( custom edit mode + enabling animation ) in forest pack, but it was not crashing, but the forest pack itself would disappear from the view port completely.
That was while using ver 7.31.

Once we upgraded to ver 8.22, the files would now crash upon clicking render, instead of disappearing.
I attached a screenshot of the issue with a file reproducing the problem:
https://drive.google.com/file/d/1TxZBGJNs-72TMvNsHyuUNKIWT-mEWiUQ/view?usp=sharing

Has anyone experienced the same problem?

Michal Karmazín

  • iToo Software
  • Hero Member
  • *****
  • Posts: 2486
Re: Forest Pack crash when using Custom Edit and Random Samples
« Reply #1 on: August 24, 2023, 09:01:24 AM »
Hi,

I'm sorry to hear you're facing these troubles. I've done some tests with your scene and I can reproduce this problem with IR (the Production Rendering Mode works just fine). It seems to be an “IR issue”, right?

In my tests, unchecking the Animation > Animate only at render time option avoids this problem.

Unfortunately, the IPR / IR mode has several limitations and it's hard and sometimes even impossible to fix issues that occur with the Interactive Rendering as 3ds Max wasn't primarily designed for it and a series of cheats are being used (from the renderer side and from our side) to make it work. We'll check what can be done in future versions (it'll need to be investigated more in deep by our main developers).

Best regards,