Hard Light Productions Forums
Modding, Mission Design, and Coding => The FRED Workshop => Topic started by: kodiak7251 on December 31, 2009, 01:05:51 pm
-
I start Fred2 - create a mission and try to go into the campaign editor.
My campaign editor glitches when i start it up . I then run the de bug editor. and it posts that I have over 130 of each type of ship.
Is this a setting I have accedently turned on - or ????
I had both babylon and wing commander loaded and i think it was confusing the fred (i had one for each) programs. so I blew away everything and just loaded babylon.
I still get the same errors.
-
I had both babylon and wing commander loaded
How exaclty ?= You do know that tbp and wcs are separate games and you shouldn't mixh them with FreeSpoace-
-
First of all, clean up your installations.
WCS belongs in its own, separate folder (like C:\games\wcs), as does TBP. The error you are getting indicates that you tried to load TBP with a regular 3.6.10 build; You should use the Inferno build that comes with the Zathras mod.
-
The last try - I blew everything away, and just loaded tbp by itself, --- I still get the same problem.
I even blew away the old freespace 1 and associated fred for that.
In any case when I go into campaign - I set up a campaign, and save it. and then it goes into error mode.
If I try to use one of the other fred2 versions - I get an error that states that I have over 130 ships, and it goes no further.
-
I get an error that states that I have over 130 ships, and it goes no further.
Obviously you have a table file, or table files, that define over 130 ships. The thing is that there are limits on how many ships and weapons you can have:
Standard Build
Max Ships - 130
Max Weapons - 200
Inferno Build
Max Ships - 250
Max Weapons - 300
So basically you could use an Inferno build (and an Inferno variant of FRED2 Open), but if you don't know why you have over 130 ships, you should really find out. Check all \data\tables\ folders and make sure there are no extra .vp files in \freespace2\ .
-
Yeah, when you are FREDing for TBP, you NEED an Inferno build. Use the ones provided with Zathras.
-
Here's the thing. TBP shipped with a non-inferno build and more than 130 ships. Even using the default exes it is going to be over the number of ships. FRED simply ignores ship 131+ but it may be that the campaign editor doesn't.
Either way if it's crashing on save you probably have the campaign file already created.
-
So if I have a lot of test missions in my mission folder - (even if I haven't assigned them to the campaign) does the campaign editor count all of them ?
this may be my problem.
also - what is an inferno build - does this relate to the INFERNO mod ? - I have Zarathustra - but I don't own a Freespace2 original disc. so it wont load.
as you can tell - I am not familiar with how the modding is made - I have no problem making missions and campaigns on my Freespace1 program. I have many missions made in the BABYLON MOD, and a story line for a campaign, I think if I can get thru this hurdle I can complete it.
-
So if I have a lot of test missions in my mission folder - (even if I haven't assigned them to the campaign) does the campaign editor count all of them ?
It's the ships (as in, ship types) that are the problem. If there are too many, horrible things happen.
also - what is an inferno build - does this relate to the INFERNO mod ?
Partially. Inferno had lots and lots of new ships and because of it, Inferno builds happened. They're otherwise (I think) like regular builds (fs2_open_***** and fred2_open_*****), except the limits for different ship and weapon types have been upped to the numbers above.
And pilot files created with regular builds won't work with Inferno builds. And vice versa.
I have Zarathustra
:wtf: The what? If you have TBP, and if you've installed Zathras correctly, you should see fred2_open_3_6_10_INF.exe somewhere, hopefully in your \tbp\ folder. Use it.
-
There have been other issues with too many missions in the mod. Campaign editor could well have an issue like that. It's never been documented but it could exits.
It's a good idea to keep test stuff in another directory when you don't need it. I just create a folder under my missions folder and move that stuff there. Just move it up into your mission directory when you need it.