OTOY Forums

I explained badly.
in your post, you talked about deelay issue in evaluation scenes and in the shared videos you made all movable proxy and then you render.
But about deelay issue I can not say to be related to movable proxy at this time.
Deelay issue happens with or without movable proxy.
there are Istance, octane proxy and movable proxy.
Each of them has its own function and can be used with others.
Movable proxy and istance are not same thing and octane proxy corresponds to vray proxy or something like that.
I said movable proxy eats resources in rendering performance.
shorter time (depending size file) during valuation but slower in render;
use them all together is not always a reasonable choice, because it can increases final render time.
You can easily test this.
I could use instance and not need to use movable proxy.
I'm doing several tests between 2.22 and 4.23 to understand issue reported,
it is not apparently continuous and not with all the files unfortunately.
I strongly hope to see this issue resolved soon.
Regards
Paride

I just did the switch to 3dsmax 2017 and latest Octane Version. Now I run into trouble. Max crashes while opening batch rendering scenes and even worse the material conversion doesn't work on Forest Pack Pro materials (merged and xref'ed).

Sometimes it works and sometimes not. The problems seems to be that I get grey materials. Always on Xref materials. I really can't track it down.
It says: "Unexpected item status" in "Current scene" menu.

What can I do?

Hi,
Thanks to everyone for your feedback !
We will be checking those issues, and especially the evaluation time, that is indeed quite slow for big scenes!..
Try to keep the '1.9 materials' conversion system deactivated when working on recent files..
Also if you can post scenes that makes 3dsMax crash (using "Save as" / "Archive", to include all assets), that is always very useful.

Have a look to the 3.04.3 - 4.24 version, it may help on some current issues..
Cheers