Could not load scene into memory. Your document may be damaged."

[Stellar_partner5EEF]

My document (and recover file of it) were recently corrupted when I was rendering another project and animating in Adobe Animate 2024 at the same time. Yes, I know it was a bad idea to put my laptop to so much work at one time. A message of "Could not load scene into memory. Your document may be damaged." is being displayed (attached screenshot). I tried doing all the advised things, but they don't work:

• I opened it on older, 2023 version
• I renamed it to .rar file and tried fixing archives, nothing.
• I tried importing an .xml file, but it says one line of the code is broken (attached screenshot).

Other files of this project are fine, but this scene is not, and I will have to re-do it if I don't recover it. I could also just try to get the assets back themselves, and just re-do the animation. Is there any other way to recover at least some parts of it?

I tried attaching the damaged file itself here, but I can't do that. If there is a way to do it, then maybe someone also please tell, so that someone clever could see it and inspect what's wrong.

[kglad]

you could try using winrar to repair it.  that works about 10% of the time.

you could check for a recovery file, if you had that enabled.

and you could save as an xfl to recover assets used.

finally, save frequently with increasing version number appended to the file name.

[Stellar_partner5EEF]

Tried them all, sadly none worked

[kglad]

what's in your xfl?

[Stellar_partner5EEF]

the .xfl file loads exactly in the same way as .fla file: it displays the "Could not load scene into memory. Your document may be damaged" message. I also tried importing them (xml, fla and xfl) to the stage and library by going to File > Import > Import to stage, none work.

[kglad]

in this situation, you don't load the xfl. inspect for assets.

[Stellar_partner5EEF]

I'll try that, but how do I inspect the assets then? The .xfl file is like 9kb for some reason. Only .xml file that's called DOMDocument.xml is full of some code and I think it has some info still saved, since I can see the names of the layers that were in the document and some other info there.

[kglad]

how large is your fla?

[Stellar_partner5EEF]

A few kilobytes large. At this point I am just re-animating the scene, but still for future it would be good to know what to do if such thing happens again (besides not rendering and animating at the same time, lesson learned lol)

[kglad]

best practice: prevent this from happening, or at least, minimize the work lost.  ie, save your fla files frequently with increasing version number appended to the file name*. periodically close and reopen the latest version.  if it opens successfully, you can delete prior versions.

*

for testfile.fla, save as testfile_v000.fla, then testfile_v001.fla, testfile_v002.fla etc.  you can create a shortcut for an jsfl file that does this automatically:

var doc = fl.getDocumentDOM();

var uri = fl.getDocumentDOM().pathURI

if(!uri){

alert('SAVE YOUR FILE. \n\nAn initial file save is needed to establish your save directory and file name that will be used to append version numbers.');

} else {

var a = uri.split('_v');

if(a[a.length-1] && a[a.length-1].length==7 && a[a.length-1].substr(-4)=='.fla'){

// subsequent save

var version = findNextVersionNumberF(a[a.length-1]);

var prefix = a[0];

for(var i=1;i<a.length-1;i++){

prefix = prefix+'_v'+a[i];

}

var bool = fl.saveDocument(doc,prefix+'_v'+version+'.fla');

} else {

// first save

a = uri.split('.');

a[a.length-2] = a[a.length-2]+'_v000';

bool = fl.saveDocument(doc,a.join('.'));

}

if(!bool){

alert('SAVE ERROR.\n\nSave manually (eg, file>save as...)');

}

}

function findNextVersionNumberF(s){

var version = Number(s.split('.')[0]);

return formatF(version+1);

}

function formatF(n){

var s = String(n);

while(s.length<3){

s = '0'+s;

}

return s;

}

[Nick Gioia]

Good Code Kglad

[kglad]

i use a log of ctrl-shift-s, my shortcut for that jsfl file.