Corrupted fla

[craye]

Hello all,
I have a corrupted flash file, i was working on it when we had a power black out.

And with all that luck, i think i was saving it at that moment...

I google it to find some solutions but nothing seem to work.

Like the method with winrar or the swf decompiler...

So if someone know a solution, i will be very happy.

I think i lost a week of work...

I put the fla and the swf online if someone is willing to take a look:
https://wetransfer.com/downloads/896fc58e0afd53d3dd7140dd72ae14d020171129153531/0fc5a84fff9792dc23e4...

Thanks!

[kglad · Accepted solution]

http://www.kglad.com/Files/forums/02.zip

[craye]

Thank you for your files kglad.

But it make the fla really weird. (a lot of useless keyframes for example)

I'm guessing you made this fla based on my swf?

There is no proper way to recover my original fla?

[kglad]

correct.  i used sothink's decompiler to recreate a working fla.

and yes, it has errors and needs work but it does recover a lot of your assets.  there may be a way to recover everything in working order but that's more work than i'm willing to do unless hired.

[rayek.elfin]

Always, always, always use some kind of versioning during work. In particular with applications such as AnimateCC that saves everything in a single file: it is just too fraught with danger to keep working with the same file. For example, consider a tool like GitKraken to do it for you. Save a new version after each larger change/edit. Also simplifies the process of rolling back changes, or inspecting older versions.

We've all been in your situation at some point in our working lives.

Although I am aware this is "Mustard after dinner", as the Dutch are wont to express.

[_keyframer]

In addition to everything else that was already started, a good "best practice" is to open the file from the day before and immediately do a "save as..." with a new name. Repeat this for every day you work on the same file.

So...

Day 1: "My_File_01.fla"

Day 2: "My_File_02.fla"

Day 3: "My_File_03.fla"

and so on...

[rayek.elfin]

_keyframer  wrote

In addition to everything else that was already started, a good "best practice" is to open the file from the day before and immediately do a "save as..." with a new name. Repeat this for every day you work on the same file.

So...

Day 1: "My_File_01.fla"

Day 2: "My_File_02.fla"

Day 3: "My_File_03.fla"

and so on...

No need for that with Git: it takes the hard work of versioning out of your hands. No risk of making mistakes, and changes can be easily commented as well. Rolling back changes is pretty simple too. Want to test going into a new direction? Just create a new branch. Happy with that direction? Merge with the main branch. If not happy, delete the branch (but those changes/versions can still be maintained).

I would advise anyone who does manual versioning (like in your system) to adopt Git/GitKraken in their workflow. It takes one's workflow to the next level.