Serious Flash Troubleshooting
- Started
- Last post
- 21 Responses
- Citizen01
This is the second time this has happened to me in the last two weeks.
I spend several hours on actionscripting, finally getting whatever function to work. I save it. Go to bed.
Next time I work on it, all the actionscript is exactly the same as I first worked on it the day before (an earlier build), meaning all the work I did during the past day is non-existent.
I check the timecode for when the document was modified, and everything looks perfectly normal. Yet all the work seems to be from an earlier build. That workstation isn't hooked up to the internet and no one else uses the computer, meaning I doubt anyone tampers with it.
Obviously, this pisses me off since I basically have to redo all the code again, but I'm wondering if anyone has experienced something similar or knows what I should do.
I suppose I could reinstall my MX 2004, but I've done plenty of documents before and this has never happened (only recently).
- Nac0
until you figure out the problem can you just save a separate copy....like if your original fla is untitled.fla....then save it again as untitled2.fla just in case?
- Citizen010
Yeah, until I find out what's going on, that's what I intend to do.
- murmur0
I have had several conversations with coworkers in the last few weeks asking if they had overwritten my FLA files with day old copies, or if the server was doing a random restore. I think I'm having a similar problem as you. The trouble is it is inconsistent at best.
- Pixter0
Groundhog_day.fla
- gabe0
dude, you seriously need to start versioning your FLAs. problems like this (and other, more serious ones) can be avoided.
every time you make any kind of advancement within an FLA, save it out as name_02.fla, etc.
i've easily had 8 or 9 versions of an FLA in the first day of starting to work on a site, and that's just for the structure of the site. after all, it's only HD space. the minute you have a corrupt flash file (or problems) like the one you're having now, it makes it all worth it in the end.
sorry, i know it doesn't help your current situation, but it really should be standard practice for anyone working within flash
- armed_rob0
sounds like a bad dream!
Export the script before going to sleep and then import it in the morning...
- rabattski0
sounds odd, but did you rename the file physically while you had the fla open and still worked in it?
- Nac0
true...external .as baby!
- imakedesign0
good tips gabe!
do you not back it up anyway?
- Engage_London0
i always end up with about 50 versions of files to avoid feck ups... trouble is you end up naming it final.fla... then you get
final2.fla
final3.fla ....final50.fla...
definitefinal1.fla...
quite confusing!
- imakedesign0
it would be cool if the next version of flash cached version of a fla, kinda of like what final cut pro does.
- UndoUndo0
we've experienced this problem here, but as said above now do versions to stop this happening. i.e at the end of a working session and at the atart name the file version0.8.fla etc etc
- Linkan0
Are your running 7.0 or 7.2? Selecting and editing actionscript via the "quick navigation" or whatever its called next to the actionscript window in 7.0 had the unfortunate side effect of not saving your changes (worked when selecting frames in the timeline). That bug was fixed in 7.2 though...
- System-Idle0
I've had these probs,
I think it is something (bug) to do with using save instead of save as.
using save dosent save the whole file, just appends the new content to the already saved file.
using save as forces the comp to save a whole new version of the file.
i found using save as, avoiding the shortcuts and keeping various backups got around this prob.
:)
- Citizen010
Wow, I was totally surprised by the number of responses, since I initially only got one response.
I versioned my files not as frequently as I think everyone else suggested. Like maybe once every few days (meaning, after like a week, I'd have version3.fla at best). I've definitely changed that practiced since, and I haven't experienced any problems, so I greatly thank those that suggested such an "update" of my own saving practices.
- Marky0
I had this happen to me a few times. I'm glad to hear I'm not the only one, I thought for a sec I was going mental!
M.
- vb_0
i always end up with about 50 versions of files to avoid feck ups... trouble is you end up naming it final.fla... then you get
final2.fla
final3.fla ....final50.fla...
definitefinal1.fla.. .
quite confusing!
Engage_London
(May 18 05, 03:10)---
haha, so true!!
i have it like this:
brochure_001.ai
brochure_002.ai
brochure_002a.ai
brochure_003.aifolder final:
brochure_fin.aibrochure_fin01.ai
brochure_fin02.aifolder fin-def (wtf?):
brochure_fin_def.ai
brochure_fin_def01.ai
brochure_fin_def01a.aibrochure_fin_def_printready.ai
- rabattski0
that looks so familiar janne.
now i trained myself that when i have a final version i throw everything else in a folder called workfiles and just have one file sitting in the root of the job.
- vb_0
yeah i should do that too.
i am always very persistent in keeping all the bad files as well.. haha.
- rabattski0
oh i keep everything as well although i only do (filename)001 etc. when it's a drastic change and not some minor stuff. i've learned that i remember those anyways so i end up with less files but still i keep everything but then in the end it's slammed in one folder.