File save error 3ds max unknown class superid

[coilbookmedia]

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 use 2018.4 max Thanks 

3ds max unknown class superid =0x200, classid =(0x18071679, 0x145247eb))

Your post subject line has been edited by @hagen.deloss: File save error

[coilbookmedia]

I attached the bugged scene.  Please autodesk tell me why after I try to save and get this error scene becomes unopenable after max is closed.  Maybe this scene can help you 

[hagen.deloss]

Hello @coilbookmedia

Thanks for posting in the forums! This sounds really frustrating, and it could potentially be an ALC/CRP infection. Here is an article that walks through steps on how to tell if your scenes have been corrupted with the CRP, and steps to get rid of this nasty 3DS Max issue. Here is the link for detecting if its an ALC corruption.

If the test you run returns false, we can continue troubleshooting to see what the issue is. If the test is returned true, please let me know and I will send you a private message with next steps.

Please select the Accept as Solution button if my post solves your issue or answers your question.

[hagen.deloss]

@coilbookmedia

I took a look at your scene just now and am getting the same crash results as you. It looks like you have a few plugins installed. including madcar, octane, and Phoenix. I'm wondering if those have something to do with this crash.

If you can, open a blank scene, and file>import>merge the scene and see if it loads up for you.

Let me know if this works, and we can continue exploring other troubleshooting avenues 😄 talk to you soon!

[hagen.deloss]

Hi @coilbookmedia,

Do you by chance have an earlier version of this file that you can open? One of the developers here at Autodesk is looking into your crashed file and wanted to see if he could isolate what object in the scene is causing the crash. 

It looks like a node within your scene with the name "PhoenixFDLiquid AVA" may be one of the reasons for the crash.

Any automatically saved files as close as possible to the problem file would be super helpful!

[Juha_P]

I have the same issue here. It seems,  it's Phoenix FD related. I eliminated objects one by one until I saw that there's one Particles foam helper object that corrupted scene save. I selected the rest of the scene and I didn't got the error.

I also did the tests and got false for both of them.

[hagen.deloss]

@Juha_P

Thanks for posting on this thread! 

I don't believe folks on our end were able to narrow down the cause of the crash, but it sounds like contacting Chaosgroup would be in order, as Phoenix FD is their product. Do you have the most recent version of the plugin?  

Here is a link to their forums

If you have a test file that you can send me, I can try to get some more information for you! (If able, feel free to either send me a file sharing link in a private message, or attach the .max file here on the forums).

Looking forward to helping resolve this issue 😄

[hagen.deloss]

@Juha_P 

Any questions or insights on my previous post? It would be helpful if you had time to give an update?

[Juha_P]

Thanks for asking,

Actually the error message disappeared as soon as it had appeared. I didn't change anything.

I don't know, maybe I'm suffering insufficient memory. 32 GB in my HP Z640 seems to be way too low for Phoenix FD. I see lot's of crashes too. Windows task manages shows 106 GB memory consumption during render time. I have made some inquiries for a new HP Z8, but got no quotations so far.

[Anonymous]

Hi guys I had the same error and found this thread while searching for a solution. I accidentally "fixed" it on my own while browsing. The reason is*: if you are running Vray activeshade it can't save. It went away when I closed the activeshade window, and came back when I turned it back on. 

*at least for me

[alejoreyes]

Hello, it seems I'm having a similar problem here, only in my case the message is related to a different Class SuperID:

Unknown class: SuperID =0xC10, ClassID =(0x39E763DA,0x51ED61A0)

In my case, I'm using Particleflow and some custom OSL shaders edited inside the slate material editor, but not 3rd party plugins.
I was able to export to FBX but as you can imagine, most of the modifiers stacks are lost as well as all particleflow events and some of the OSL custom shaders have not been kept.
When I try to open the affected file, it seems to start loading but it suddenly throws a file open error message "Invalid file- only partially loaded." but nothing is actually loaded.
When I try to merge from the affected file, it throws an application error message "An error has occurred and the application will now close. No scene changes have occurred since your last save."

I would like to know if there exist any tool to debug the max file, or at least try to understand what is this problem related to.
@hagen.deloss can you help me with this?  I'm stuck with this and have a delivery for next week.

[justinworks1989]

When I faced a similar error msg.   (Unknown class: SuperID =0xC10, ClassID =(0x39E763DA,0x51ED61A0) I found it was because max was processing to much to save, so in my case I opened my uv editor and switched "Pick Texture" to "Reset Texture List". This solved my issue and I was able to save.   ---   3D Theo.