Millenium bug in SF2?

[AntEater]

Hi, another one of my very popular problem threads :D

 

I noticed that in my install, service dates after 2000 seem to be no longer accepted.

If a plane has a service entry in 1994 and an end date of 2004, it will just be available 1994 in single missions, for example

I guess there's an .ini file somewhere that regulates the game start and end dates and that I got a version with an end date of 2000 in some mod.

Problem is I don't know which file I should look for.

[+PureBlue]

You can fix it if you know Cobol

 

open options.ini and check under

[singleMission]

 

also some terrains will have date limits in their terrain.ini. But the above should get you going. (I got my end date at 2050)

[Wrench]

is this on a specific terrain, or globaly over the entire game?

 

http://combatace.com/topic/55030-adjusting-beginning-ending-years-for-sf2-series-terrains/

[JediMaster]

Yeah, you have 3 .ini's to check. The options.ini, the ones for each terrain (which will have to be extracted for a stock terrain), and the _DATA for the plane itself. If all 3 aren't post-1982 you get stuck.

I know the Desert terrain isn't date-limited, but I'm pretty sure all the others are.

[AntEater]

Options.ini did it, but I never figured out what went wrong in the first place.

Thanks a lot (again;))

Edited August 3, 2011 by AntEater

[JediMaster]

Did you patch? Did you get a DLC? Any of those will overwrite your options.ini AFAIK.

[AntEater]

I think I fixed it, but I don't exactly know how :D