Page 1 of 3

#$@$#@$ FRED

Posted: Sun Oct 10, 2004 2:59 pm
by Singh
Ok, now this is just ridiculous.

Dont you hate it when you spend not hours or days, but WEEKS on a mission and have it inches close to perfection - when all of a sudden something W#O$(@$#$ in FRED makes it totally NOT work in FS2 at all?

I was near completion for my NTB intro mission (which just happens to be a BoE mission that took AGES to fix up) when all of a sudden, it starts to crash in FS2 for absolutely NO particular reason after my fighters/bombers arrive, even though it was working MINUTES before. The only changes in FRED were additions to briefing and debriefing text, and now it refuses to work no matter WHAT i do!!

Just e#$@#@$ great. I am beggining to NOT like fred very much :x

Posted: Sun Oct 10, 2004 3:04 pm
by Shinobi
That sucks. Use FRED 3.5.5 as the more recent ones corrupt missions. Have you tried to reverse your changes to prior corruption?

Posted: Sun Oct 10, 2004 3:10 pm
by Singh
Shinobi wrote:That sucks. Use FRED 3.5.5 as the more recent ones corrupt missions. Have you tried to reverse your changes to prior corruption?
The problem is I use some of the SexPs associated with the newer FRED, and cross-compatibility isn't exactly an option either.

Thing is, im not even sure if its a FRED problem either, since FS2 could be causing the error (it gives it to me in both 240822 and the new Taylor build :( ) or something wrong with the .tbls........I don't think I can reverse it back, since i made several attempts to fix the error, so the .bak file might just have it by now :(

Posted: Sun Oct 10, 2004 3:20 pm
by Hunter
Backups.. Backups.. Backups...

Posted: Mon Oct 11, 2004 1:36 am
by Hippo
yeah... try the .bak files... they might work...

Posted: Mon Oct 11, 2004 1:39 am
by Grimloq
gawd, i hate when that happens... i did something like that ,'cept for D2. D2 missions are tenfold easier than D3 ones, but still... about 6 weeks, and it was perfect. then, my computer decides that its an 'unused file' and deletes it :x

Posted: Mon Oct 11, 2004 5:28 am
by Black Wolf
If you've spent weeks making the mission, then spending several hours going through the .fs2 file in notepad manually looking for the error shouldn't be such a problem - I strongly suggest you do that if the .bak doesn't work.

Posted: Mon Oct 11, 2004 7:05 am
by Goober5000
Aye. It could be something as infuriatingly simple as Black Wolf's variable problem a few weeks ago.

Posted: Mon Oct 11, 2004 7:06 am
by Black Wolf
Indeed. That's what prompted me to suggest it actually. If I'd done that in the first place I could have save both of us a lot of trouble.

Posted: Mon Oct 11, 2004 1:32 pm
by Hippo
That whole thing where variables can't have spaces?

Posted: Mon Oct 11, 2004 1:49 pm
by Black Wolf
Ja

Posted: Mon Oct 11, 2004 1:51 pm
by Hippo
Pff... I never used variables... They were too buggy... I might again someday, but i always found it really reliable (though lengthy) to use a lot of or's and and's and and-in-sequences's for stuff where like, shipyard-completed used the variables for the argo's... I SEXP'd it :p

Posted: Mon Oct 11, 2004 6:12 pm
by Black Wolf
I used to be like you. Never again. Variables kick arse once you get used to using them.

Posted: Mon Oct 11, 2004 8:06 pm
by karajorma
Gotta agree with Black Wolf's sentiment on this one.

It's not even like variables are hard to use! I actually used them in the first non-walkthrough mission I ever made :) It was only once I started reading posts online that I discovered that people thought they were hard :)

Posted: Tue Oct 12, 2004 1:33 am
by Hippo
Yeah, they're indeed simple, i just usually prefer to use sexp's, since if they're done correctly, they can be more dynamic (albeit really hard to debug)...