error saving file

[cb LLC]

Hi I started randomly getting this file save error Unknown class super id. Once I hit ctrl s and get this message file basically is ruined. If i close max and reopen file it is a bad file. What causes this random error ? I used 2018.4 max
it seems it happens a lot when phoenix is calculating and material editor is open with phoenix ocean textures



Thanks

[Svetlin.Nikolov]

Hey, I tried a simple Ocean quick setup preset here with the mtl editor open while simulating and hitting save constantly, but couldn't get the error.

1. Does it happen with a latest nightly for you?

2. Are you using the defscanline Phoenix install?

3. Would it be possible to send over a simple scene that can make the issue reproduce, so we can catch it?

Thanks!

[cb LLC]

Hey, I tried a simple Ocean quick setup preset here with the mtl editor open while simulating and hitting save constantly, but couldn't get the error.

1. Does it happen with a latest nightly for you?

2. Are you using the defscanline Phoenix install?

3. Would it be possible to send over a simple scene that can make the issue reproduce, so we can catch it?

Thanks!

Hi Svetlin,
I am using 3.11.01 Nightly, Build ID: 2018061628337

I attached the bugged scene that you cannot open (maybe you have the tools to find out why), I i will try to send the working scene soon.

This problem is very rare and now I am not sure if it is related to phoenix. If it happens again I i let you know.
I am not even sure what the error even means but I searched in your forum and some people had similar problem related to vray I guess.
I am using default scanline version with octane.

Thank you

[Svetlin.Nikolov]

Dang, I don't think we can open that - seems like the scene is corrupted and not fully written. I will try here to repro it using Max 2018 with V-Ray uninstalled and the defscanline Phoenix build...

[Ivaylo Katev]

this ID is of an object temporary used during the simulation, that should not be saved, but perhaps the new max versions are acting differently in some cases

[Svetlin.Nikolov]

cb LLC , can you grab a latest nightly just in case? During the last 2 weeks there were some issues as side effects of implementing instancing for the Phoenix volumes in 3ds Max, but the latest nightly is stable.

[cb LLC]

cb LLC , can you grab a latest nightly just in case? During the last 2 weeks there were some issues as side effects of implementing instancing for the Phoenix volumes in 3ds Max, but the latest nightly is stable.

Thank you I will. By the way I am using 2018.4

[cb LLC]

this ID is of an object temporary used during the simulation, that should not be saved, but perhaps the new max versions are acting differently in some cases

I do remember activating active body for the ship to float but had problem with it. It might be the active body then.

[cb LLC]

cb LLC , can you grab a latest nightly just in case? During the last 2 weeks there were some issues as side effects of implementing instancing for the Phoenix volumes in 3ds Max, but the latest nightly is stable.

BY they way can we copy grids as instances now with different start times ? Thanks

[Svetlin.Nikolov]

I do remember activating active body for the ship to float but had problem with it. It might be the active body then.

Oh, this is a very good clue!

BY they way can we copy grids as instances now with different start times ? Thanks

Mmm, you could do that before as well - note that instances have all settings the same between them. Also, Phoenix automatically shares the RAM of loaded caches if they are opened by several different simulators, no matter if they are copies, instances or references, or completely different simulators. However, if you e.g. set the start frames of 3 copies to 1, 5 and 10, these caches cannot be shared no matter if instancing is supported or not.

[cb LLC]

Thank you!