Hard Light Productions Forums

Modding, Mission Design, and Coding => FS2 Open Coding - The Source Code Project (SCP) => Topic started by: TrashMan on January 10, 2006, 06:04:37 am

Title: Sigh...backwads compatible my a**
Post by: TrashMan on January 10, 2006, 06:04:37 am
Different version of FRED obviously have eachother.

I just found a tester for my campaign and he was testing some missions I made and was well. Then I dowbloaded CVS 01072006 (FS2Open and FREDOpen), mostly becouse of the nameplate fix.

However my tester has Linux and he can't use the CVS version.
and here's hte problem. He can't test any mission edited with the latest FRED. and I can't open any of those mission in any of hte older FRED's (every time I start an olde FRED I get an error:

Error: mv_tech-wep.tbm(3):
Error: Required token = [$Model file:], found [+nocreate]
in weapon: @Subach HL-7.

What the hell am I supposed to do now?
I'm in the middle of FREDing the last missions of my campaign and I need testing. :mad: :hopping:

Title: Re: Sigh...backwads compatible my a**
Post by: karajorma on January 10, 2006, 07:25:44 am
So let me get this straight. Judging from your thread title you want FRED to work with missions made in any future version of FRED too?

Heres how you do that. When a new version is released don't download it. Just rename your version to have the same name. Tada! You'll be able to save missions even in your FRED_r_30122007.exe and still have them open in old versions of FRED.

Backwards compatibility means that your missions created now will open in versions of FRED created in the future. Not that they will open in older versions. The only way to ensure that old versions will open all newer version's missions is to stop upgrading FRED at all. Coders can't see into the future and make FRED ready for every change that may occur :rolleyes:



On the other hand if you want to ask something sensible like how to get your mission to open in an older version of FRED what you could do is try removing the media VP files or rolling back to the 3.6.7 ones as that is probably the source of your problems.
Title: Re: Sigh...backwads compatible my a**
Post by: Wanderer on January 10, 2006, 07:37:55 am
You could try to remove all .tbms and include their contents to the respective master table files. As it seems that modular tables are the problem, or rather the lack of XMT support in the older builds.
Title: Re: Sigh...backwads compatible my a**
Post by: Mr_Maniac on January 10, 2006, 07:52:06 am
However my tester has Linux and he can't use the CVS version.
Why not? ;)
He could check out the CVS-Tree and compile it.
Or...
I have binarys :)
Wait... I'll tar them and put them up...
Then I will edit this post :)

EDIT: Here's the Link to my
2005/01/10 - CVS-Build - Debug and release, nomal and Inferno ~ 8.5 MB tar.bz2 (http://home.arcor.de/mr_maniac/Bilder/fs2open/fs2_open_20050110_linux.tar.bz2)
Title: Re: Sigh...backwads compatible my a**
Post by: TrashMan on January 10, 2006, 09:16:54 am
On the other hand if you want to ask something sensible like how to get your mission to open in an older version of FRED what you could do is try removing the media VP files or rolling back to the 3.6.7 ones as that is probably the source of your problems.

Soroy for the outburst, but it's realyl bugging me. Teh campaign was at a stand-still for various reasons and just now, when it got rolling really fast again and so close to completetion I hit a brick wall :(

I think the problem is the extended table files, since there's nothing else I can think of that would crash older FRED builds on loading.
I was thinking on putting back the older core.VP is that 's the onyl way around it.

@Mr_Maniac

Hey, thanx. If this works you'll get a cookie! :D
Title: Re: Sigh...backwads compatible my a**
Post by: WMCoolmon on January 10, 2006, 11:32:39 am
The mediaVPs are your problem, not FRED. Although the namplate fix is probably not going to work for your tester, either.