Page 1 of 1
4.10 Save image crash 3ds max
Posted: Fri Jul 22, 2016 1:56 pm
by ramone163
In 50/50 save image crash 3ds Max 2016.
Re: 4.10 Save image crash 3ds max
Posted: Mon Jul 25, 2016 4:56 pm
by rv3d
+1 really annoying
Re: 4.10 Save image crash 3ds max
Posted: Tue Jul 26, 2016 2:59 am
by azen
Hi,
Is there any consistent elements to the scenes that crash? Are there scenes that always crash every time you save? I have not been able to duplicate your issue yet.
Re: 4.10 Save image crash 3ds max
Posted: Sun Aug 07, 2016 10:32 pm
by profbetis
I'm experiencing this too. In order to save images, I have to use the full production render mode. This has another issue: when cancelling a render, the render engine fails until a computer reset. If you try to open the viewport or render material previews or try to start a new production render, it just hangs there and will refuse to render, but with no warning. A close and re-opening of the application has no effect.
Re: 4.10 Save image crash 3ds max
Posted: Mon Aug 08, 2016 2:32 am
by azen
profbetis wrote:I'm experiencing this too. In order to save images, I have to use the full production render mode. This has another issue: when cancelling a render, the render engine fails until a computer reset. If you try to open the viewport or render material previews or try to start a new production render, it just hangs there and will refuse to render, but with no warning. A close and re-opening of the application has no effect.
Hi,
Thanks for the elaboration. I will see what can be replicated from this.
Re: 4.10 Save image crash 3ds max
Posted: Wed Aug 10, 2016 11:17 pm
by oguzbir
Same here,
Saving directly from octane viewport creates this problem. Porting to max VFB and saving works.
Re: 4.10 Save image crash 3ds max
Posted: Sat Aug 13, 2016 5:02 pm
by profbetis
It seems I've remedied my issue on a particular file bu deleting some complex STL imported geometry. I don't imagine why that would have any impact on material previews or the production render, but it did fix the problem. Perhaps there is a memory leak somewhere?