Hard Light Productions Forums
Modding, Mission Design, and Coding => The FRED Workshop => Topic started by: LostProphet on November 11, 2009, 03:07:54 am
-
i'm using mediavps and fred2 open 3.6.10 and created some mission. i tried them, wanted to edit them and wanted to try them out again. everything went fine but when i wanted to save them to keep my changes i wasn't able to save. a window showed up with errors or something, i clicked OK and all my work was gone
what's wrong?
-
Okay, touch nothing. If you're very lucky you might be able to save your work anyway.
Go into your mission folder and make copies of the Backup.00x files in there. Then try loading the copies in FRED.
Beyond that you've not given enough detail for me to be able to help you.
-
ok, i give you more info
let's say i made a mission called "X". i saved X as FS2 Open, FS2 Open Compability and FS2 Retail. I try mission X, everything works. now i want to edit it, like placing new ships and creating new events. the error checker says that no errors were detected.
sometimes i can save it and play it, but sometimes it crashes and all my work is gone.
enough info?
-
Does it give any error when it crashes? What version of FS2_Open? 3.6.10 official? What happens if you run the debug build instead? Can you post the log for the debug build? Does it actually save the mission before it crashes (It should do, FRED tends to crash on mission reload immediately after save rather than on save itself).
-
yes i'm using fred2 open 3.6.10, downloaded it last week i think.
where do i find the debug log?
no, it doesn't save before it chrashes. when i want to load the mission which crashed before, i get an error again and i can't open it.
do you mean fred2_open_3_6_10_debug?
-
The debug log (fs2_open.log) should be created in your FreeSpace2\data folder. Debug builds for the main executables are usually denoted by a d before the .exe extension, for example: fred2_open_3_6_10d.exe is the FRED2 debug build. Just load the mission into this and it should log the errors for you.
-
when i try to open the mission with fred2_open_3.6.10_debug an error appears.
i attached the log
[attachment deleted by admin]
-
Which mode are you using? I strongly suggest using FS2_Open unless you know what you're doing with compatibility mode. Also check that you don't have any ;;FSO 3.6.x;; style comments in your mission when you look at it in notepad.
-
I'm using mediavps, but does this influence missions I created?
I used to save the missions in FS2 Open, but once I couldn't start the mission, then I saved the mission in FS2 Open Compability and it worked.
so shall I delete lines where things like ;;FSO 3.6.x;; are standing?
-
Don't delete the lines, just the bit that actually says ;;FSO 3.6.x;; I find a search and replace (with the replace bit empty) tends to be the quickest and easiest way to do that. Just do 3 searches where x = 8, 9 and 10 and you should get rid of all or almost all of them.
-
I searched for the ;;FSO 3.6.x;; part and deleted it. I wanted to open the file but this error appeared again. It's always the same error, it appeared the first time when I wanted to save. Since then I can't open the file anymore, I've got the same problem with other missions I created. I couldn't open them anymore so I deleted them.
could it be that I don't have some files? that's so strange, the errors suddenly appeared :confused:
I attached a screenshot of the error
[attachment deleted by admin]
-
I think you'll have to attach/PM me the mission. If you still have the .bak attach that one too.
-
ok, here you go. I give you the bak-file as a txt-file, because I can't upload bak-files as you probably know
I hope you can find out what the problem is
[attachment deleted by admin]
-
No idea what happened to the .fs2 file there but the .bak was pretty close to fine. Had a couple of extra semicolons but that should not have broke it. Make sure you are using at least 3.6.10 final. Fixed mission (http://fubar5.fubar.org/fubar/FS2/LP_Fixed.fs2)
-
The mission file was borked by the whole ;;FSO 3.6.x;; nonsense.
-
The mission file was borked by the whole ;;FSO 3.6.x;; nonsense.
I know, I deleted this FSO things and saved the file but when I opened it again it was there again.
Strange thing, maybe I should just give up and concentrate more on playing than on editing
-
could it be that missions I created with the old normal FRED are influencing my new ones? they were in the same folder, I cut all of them out and put them in another folder and saved a new mission I just created into the missions-folder and it works
-
Be certain not to save in compatibility mode or all that stuff will come back.
-
I have the same issue. Starting build mission, rename ships, wings, make backgrounds. Save. Add hostile unit, save and it crushes. Try to open it again and the same thing as topic starter describe. Tried many times - all the same.
Then I've build the same mission in fred 3.6.9 and everything is fine - no errors, no crushes. Then I've tried to open this mission in 3.6.10 - it opens, but when I attempt to save it crushes and all the same thing again. And 3.6.9 no longer can open this mission too.
What is wrong? It was really big peace of work - I've opened mission file in notepad and it is completely ruined, all the data is messed.
Attaching the mission made in 3.6.9 and messed mission file
[attachment deleted by admin]
-
And does the solution mentioned in this thread not work? If it is the same problem, the same solution might do the trick....
-
And does the solution mentioned in this thread not work? If it is the same problem, the same solution might do the trick....
You mean placing it in different folder? I'll try...
EDIT: Tried - no help...
-
....
No, I meant this:
Which mode are you using? I strongly suggest using FS2_Open unless you know what you're doing with compatibility mode. Also check that you don't have any ;;FSO 3.6.x;; style comments in your mission when you look at it in notepad.
To repeat: Use a text editor to look for lines that begin with ;;FSO 3.6.x;; (where x is either 9 or 10). Delete the ;;FSO 3.6.x;; part. Then load the mission in FRED 3.6.10.
-
Yeap, found and erase ;;FSO 3.6.10;; - working fine now. Thank you again!
-
All you have to do is set FRED's save mode to normal rather than compatibility mode and the problem will go away.
-
All you have to do is set FRED's save mode to normal rather than compatibility mode and the problem will go away.
It was set to normal from the beginning.
-
Sorry, after deleting all the ;;FSO 3.6.x;; style comments