What's wrong

K

Killer Svend

SOH-CM-2024
Hi gents
The old fool has been tangeling with his computer again and downloaded Rami's fine Barbarossa campaign, I thought that I was very careful,following the instructions,but someting is not ok,knowing for sure that it is my owm fault. I made a complete new install of CFS2 just to be sure of not to many disturbances from other sources. So on the campaign list is a lot of countries, 3 of the can be flown us,jp and ussr. When select a country the name come up in the window as i.e. American/par and all the others also with a /par !!, The ussr screens are fine but it refuse to show ranks and medails,despite they are appering ok in the uries file. Pressing Advanced info' result in a crash to desktop. Despite all this the campaign it self operates perfect. But I would like to earn a Lenin medail. Can someone help ??
Killer Svend:salute:
 
Humble suggestions

Until Rami or other Savvy people gives the correct answer, I just want to give my humble advice. Please check that you have the extended country .cfg installed. If the countries are numbered in another way than the campaigns are written for, the sim cannot find them for you to fly. Second, be sure that you do have missions for those countries to fly, otherwise obviously the sim cannot offer anything. I had a long fight once getting some french missions to work, until I found out that they were written to have France as country number 7, while I had my country .CFG having it as number 17, thus no-fly until I changed that number in the missions.
Finn
 
I would check the Country.cfg file first, but if thats fine then just have a look at this post

http://www.sim-outhouse.com/sohforums/showthread.php?53944-Compatability-questions&p=589705#post589705

Check the contents of both UIRES folders, if they are different then this might be the problem. To fix simply copy and paste the contents you need in your UIRES folder and paste them into the UIRES folder in your cfs2 root folder AND the UIRES folder that appears when you click compatability files.

(back everything up just to be safe)
 
What might make things a little easier for you, is to install CFS2 outside of the program files folder. Anywhere on your hard drive is fine, just so long as it is not in either the (Drive letter):\Program Files or (Drive letter):\Program Files (x86).

As far as CFS2 crashing to desktop, one possibility is this (From Cody Coyote's Mission Building Handbook): There are two other issues that you should be aware of.

If during the mission you go to Advanced Information, one of two things will happen; either the Advanced Info screen will appear as it normally does and you can continue to fly the mission or the game will Crash to Desktop (CTD).

Second, if you open the mission using Mission Builder and edit any facet of it one of two things will happen; either Mission Builder will CTD at some point or the mission will edit and save normally but you will find yourself at the wrong starting position.

Both of these issues share the same cause, the runway ID number that you choose to use for your new take off point. Whenever you use either the Take Off or Land at Base commands in Mission Builder the game accesses the airbases.dat file and copies the necessary information from that file and writes it into the mission. It always overwrites the existing information in the mission file. If the runway ID number in your edited mission doesn’t exist in the airbases.dat file, Mission Builder CTD’s.
You will recall that in the Wake Island example we did not change the runway ID number. It wasn’t
necessary since ours was the only flight leaving from that runway. While we did change the take off coordinates, we didn’t change the runway ID number.

When you edit this type of mission in Mission Builder the game will overwrite your entry with the correct coordinates for runway 8015, placing you back at the end of the runway. You will need to manually re-edit the file to return to the hangers.
In the Henderson example we created a new runway entry. You’ll recall that I said you could use any 4-digit number for this new runway entry. The number you select will be one of two things; it will either match another runway entry already in the airbases.dat file but not used in this mission or it won’t. The number you use will determine what happens when you edit the mission in Mission
Builder.

If the second runway ID number matches an ID number for another runway in the airbases.dat
file (as in our example where we used 8015, Wake’s ID), when you save the mission, Mission
Builder will place you at that runway (you’d find yourself starting the Henderson mission at
Wake).

If the second runway ID number doesn’t match an existing ID number in the airbases.dat file
(for example, using 9999), the Mission Builder will CTD during the editing process.
Something similar happens when you try to access Advanced Information in a mission. If the game finds the runway ID numbers that you used you will see the Advanced Info screen and the game will play normally. If you used a non-existent ID number the game will CTD.

I'm not exactly sure how Rami designed this mission, but it is one possibility.
 
You must log in or register to reply here.
Back
Top