Solomons campaign planes stacked on top of one another

[JollyRogerTwo]

I'm not new to simming but I am new here. I purchased my first sim in the 1980s.Back then computers were chipped out of rock and they ran on steam power...

 

Forgive me if this is a common question or has been answered before. A quick search did not turn up an answer.

 

I have 3 SF1 installs. Edward's KAW and Solomons campaigns and WOV. KAW and Solomon's are patched to '06 and WOV is patched to '08. They are running smooth as glass under Win XP home service pack 3. I'm having a ton of fun with them and especially enjoy how customizable they are.

 

THE PROBLEM:

I have seen this problem only in the Solomon's campaign. When I set the single mission to begin on the runway in the control panel all goes well until I pop into 3D. When I do I'm on the runway alright but facing crossways on the tarmac. My prop is as dark as the inside of a black cat at midnight. If I pop out of the cockpit (F6) and release the brakes I am treated to seeing my plane come right out of another plane and taxi across the grass ignoring the runway. As they say "That just ain't right".

 

I'm a complete novice at modding and the innards of SF but to me it looks like there is something gone wrong with some ini file somewhere not giving the planes the correct coordinates to line up on the runway or something. I've looked in the terrain folder but can't find any 'airfield' or 'runway' INI. There are 6 files in the terrain folder in the KAW campaign named Korea_airfields.ini. Nothing like that can be found in the Solomon's terrain folder though. Might be named something else though. KAW runs perfect as does WOV.

 

Any ideas\/suggestions/ or words of deep sympathy?

Thanks.

Edited October 13, 2012 by JollyRogerTwo

[Wrench]

wrong airfield ini called out in the targets ini.

 

you'll have to edit the solomons targets ini, and extract all 5 of the desert airfield inis from the Desert.cat (consult the knowledge base above on 'how to', if you don't know), and drop them into the Solomons terrain folder

 

you'll be changing the pointer for EACH entry of every airfeild, to have the point to the correct airfield ini

 

example:

 

Name=Henderson Field

Position=682001,353997

Radius=6000.000

ActiveYear=0

Location=1

Alignment=FRIENDLY

AirfieldDataFile=desert_airfield3.ini

NumSquadrons=1

 

change to read as above; each airfield changes to point to the 'new' desert airfield

 

***_airfield1.ini, becomes desert_airfield1.ini, and so forth.

 

Idon't remember what they were called originally, as that map has been through at least 2 rebuilds; during which they've been changed to the desert airfields.

 

that map is really old, and really wrong when it come to target/target locations. Of course, if you USE the new map, your campaign goes to hell, as the campaign targeting won't match the terrain.

[JollyRogerTwo]

Wrench,

 

Thanks.

 

I know where that is and how to deal with it I think.

 

I have your excellent Solomon's terrain V3 update but have not installed it until I get this issue resolved. I realize that nowadays you have your hands full just dealing with Gen 2 questions. It is somewhat of an imposition for me to expect you guys to be able to go backward in time to deal with my problems with Gen 1. SF2 is not available to me and isn't likely to be so I must deal with the few problems I have.

 

I appreciate your willingness to help and reading these pages, I'm continually astonished at your extraordinary memory for details.

[JollyRogerTwo]

Wrench,

 

Superb! Do you ever tire of being right?

 

Genius is a wonderful thing to observe. Years of practice and hard work behind it but so easy to implement that fix. Allies Gut!

Have there been any additional ideas, prohibitions, suggestions or information added before I install your Solomons_Ver3?

 

Thanks again.

[Wrench]

I never tire of being right ... according to my wife... it ain't all that often!!! As for details, that's how I was trained. EVERYTHING is in the details!!

 

just a little editing of the data in MAY be required to remove the 08 and/or SF2 type shader statements. But that's easy! Follow the 'converting terrains to SF2' instructions kinda/sorta backwards, and all should be good (that is, of course, if I added them in the first place!)

 

if not, just ask.