Corrupted My Files

[Czech6]

Messing around or modding I seem to have corrupted a file in WOV. Here's what I get right after the loading screen:

 

http://i8.photobucket.com/albums/a21/Czech6/img00015.jpg

 

Any help figuring out what .ini file I messed up?

[Lexx_Luthor]

What patch version?

What modding or messing?

Do the view controls work when you see that?

Need more info.

 

Could be a terrain problem...that looks like the white abyss beyond the north/south map edge but that should only be visible pre-Patch2008. Only 17km altitude so terrain *should* be visible unless you look at into the abyss?

[Lexx_Luthor]

EDIT...or Enviro problem...actually, it looks more like the terrain "fog" taking over the terrain.

 

Maybe bad TARGET.ini file so airfield is outside map. Notice the camera X,Y positions...I can't read them, but they are curiously rounded off large numbers indicating default placement of camera due to mission run failure.

[Czech6]

What patch version?

What modding or messing?

Do the view controls work when you see that?

Need more info.

 

Could be a terrain problem...that looks like the white abyss beyond the north/south map edge but that should only be visible pre-Patch2008. Only 17km altitude so terrain *should* be visible unless you look at into the abyss?

 

October 2008 patch. Can remember what I was working on. I think I was either comparing the ini files in WOV to another TW sim, or doing a cut and paste. I must have had my cursor in the wrong file and accidently typed something. It was only later when I tried to run WOV that this showed up. View controls do not work in that view.

 

I've been swapping out files from a backup copy to try and isolate the location, but with no luck. So far changed out Options, Startup, Viewlist, Flightengine, Missioncontrol, and Huddata.

 

Changed out the target.ini but no joy.

Edited January 11, 2009 by Czech6

[Czech6]

Changed out the complete terrain file with a backup, but no change. Also, changed out the Environmentsystem file. Also, no change. I'm going to install WOV and patch to another drive and start moving my mods over as I'm out of ideas.

[Lexx_Luthor]

Cool as long as you are backed up. I decided to move back to SF 2006, deleted my SF 2008, then my 2006 WOULD NOT EVEN START.

 

It was a tiny error in Options that crept in for some reason. Of course I figured it out after I started again from my unpatched SF 1.0 backup, after moving all my stuff over, in the end I found the single tiny error in ONE small ini file. Backups man backups.

[Czech6]

Cool as long as you are backed up. I decided to move back to SF 2006, deleted my SF 2008, then my 2006 WOULD NOT EVEN START.

 

It was a tiny error in Options that crept in for some reason. Of course I figured it out after I started again from my unpatched SF 1.0 backup, after moving all my stuff over, in the end I found the single tiny error in ONE small ini file. Backups man backups.

 

Thanks for your help. With the price of external hard drives these days, I've bought two over the last year. I keep a copy after each patch. I may also do a document compare and see if it highlights some minor typo that I've missed.

[Czech6]

It's never where you expect it to be. I was trying to see if the AircraftFormation.dll would work in FE and fix the AI formation antics, and I must have did a cut and paste instead of a copy and paste. Lesson learned - always compare the files in the folder of the bugged version versus a backup version.

[Lexx_Luthor]