Hard Light Productions Forums
Modding, Mission Design, and Coding => The FRED Workshop => Topic started by: Colt on July 17, 2019, 03:17:18 pm
-
So I was doing some editing, but when I went to save the mission, I got an error about some sexp expressions (this usually happens when inserting new events between other events). Whenever this happens I just press continue and then proceed to fix them. This time however I got the following error.
Error: Failed attempting to reload mission after saving. Report this bug now!
File: freddoc.cpp
Line: 658
ntdll.dll! ZwWaitForSingleObject + 20 bytes
KERNELBASE.dll! WaitForSingleObjectEx + 147 bytes
fred2_open_3_8_1_20190514_69ebdd0_x64_SSE2.exe! <no symbol>
fred2_open_3_8_1_20190514_69ebdd0_x64_SSE2.exe! <no symbol>
fred2_open_3_8_1_20190514_69ebdd0_x64_SSE2.exe! <no symbol>
fred2_open_3_8_1_20190514_69ebdd0_x64_SSE2.exe! <no symbol>
fred2_open_3_8_1_20190514_69ebdd0_x64_SSE2.exe! <no symbol>
fred2_open_3_8_1_20190514_69ebdd0_x64_SSE2.exe! <no symbol>
fred2_open_3_8_1_20190514_69ebdd0_x64_SSE2.exe! <no symbol>
fred2_open_3_8_1_20190514_69ebdd0_x64_SSE2.exe! <no symbol>
fred2_open_3_8_1_20190514_69ebdd0_x64_SSE2.exe! <no symbol>
fred2_open_3_8_1_20190514_69ebdd0_x64_SSE2.exe! <no symbol>
fred2_open_3_8_1_20190514_69ebdd0_x64_SSE2.exe! <no symbol>
fred2_open_3_8_1_20190514_69ebdd0_x64_SSE2.exe! <no symbol>
fred2_open_3_8_1_20190514_69ebdd0_x64_SSE2.exe! <no symbol>
fred2_open_3_8_1_20190514_69ebdd0_x64_SSE2.exe! <no symbol>
fred2_open_3_8_1_20190514_69ebdd0_x64_SSE2.exe! <no symbol>
fred2_open_3_8_1_20190514_69ebdd0_x64_SSE2.exe! <no symbol>
fred2_open_3_8_1_20190514_69ebdd0_x64_SSE2.exe! <no symbol>
fred2_open_3_8_1_20190514_69ebdd0_x64_SSE2.exe! <no symbol>
USER32.dll! DispatchMessageW + 1702 bytes
USER32.dll! DispatchMessageW + 450 bytes
fred2_open_3_8_1_20190514_69ebdd0_x64_SSE2.exe! <no symbol>
fred2_open_3_8_1_20190514_69ebdd0_x64_SSE2.exe! <no symbol>
fred2_open_3_8_1_20190514_69ebdd0_x64_SSE2.exe! <no symbol>
fred2_open_3_8_1_20190514_69ebdd0_x64_SSE2.exe! <no symbol>
KERNEL32.DLL! BaseThreadInitThunk + 20 bytes
ntdll.dll! RtlUserThreadStart + 33 bytes
Every time I try to load the mission in FRED I get a window that says it is unable to load the mission file. How would I go about fixing this?
-
Can have a wide range of causes. IIRC running a debug built _might_ be able to bring you to the point where it happens, not 100% sure.
-You forgot a space after an event name ("Destroy Gemini ")
-Change hierarchy of events so "is-event-true-delay" will show <Gemini Event>
basically everything that throws out a error (apart from the usual GTF Ship 0 not part of wing stuff) can cause FRED to refuse to load your mission nowadays.
-
-Change hierarchy of events so "is-event-true-delay" will show <Gemini Event>
Yep that's what it was.
Also I remembered that I could edit the mission via a text file :banghead:. All's working now!
-
-Change hierarchy of events so "is-event-true-delay" will show <Gemini Event>
Yep that's what it was.
Also I remembered that I could edit the mission via a text file :banghead:.
Be super careful with that, 1 typo and you've got a good chance to end up in the same issue again.
-
-Change hierarchy of events so "is-event-true-delay" will show <Gemini Event>
Yep that's what it was.
Also I remembered that I could edit the mission via a text file :banghead:.
Be super careful with that, 1 typo and you've got a good chance to end up in the same issue again.
Pfff... Real Freders use notepad!
-
Copy + Paste = Win
-
Confirmed that sexps with illegal entries (bad hangar bay assignments, ships that don't actually exist, etc.) cause FRED to treat a mission as entirely corrupted rather than spit out a list of the errors in the mission like normal. I'm working on a Github issue now.
E: Posted. (https://github.com/scp-fs2open/fs2open.github.com/issues/2067)
-
Yeah, the game should at least spit out what might be the cause even if it can't load the mission.
-
Confirmed that sexps with illegal entries (bad hangar bay assignments, ships that don't actually exist, etc.)
Posted. (https://github.com/scp-fs2open/fs2open.github.com/issues/2067)
Yikes. Gonna be super careful for the time being. Thanks for finding that.
-
Possible fix submitted. Next nightly (not today's) will probably have it. Until then, you can try editing any bad sexp in notepad.
-
Thank you~ :yes: :yes: