I downloaded Capt Sim C130, but when I select the aircraft in FSX this is the screen I get:

 

 

If I click OK, this is the screen I get:

 

 

 

If I click the "Close" option, FSX does a CTD.

 

I've got loads of payware aircraft on the PC, including 3 other Capt Sim aircraft, all work fine. I've downloaded it 3 times now, taking all the usual precautions, UAC off, Anti virus off (for download and install), explorer not chrome, Admin rights, etc, but this happens every time. Had no luck on Capt Sim forum, thought I'd try here, in case someone recognizes the screens, and maybe has a suggestion.

Eugene

Did you contact the vendor?

On their official forum yes, but not directly by email, could be an idea, it's rare that these things happen to just one person...

It's an older 2002 plane that you may be trying to use in FSX.

Sounds plausible Jim, but just checked my Capt Sim account, I've downloaded "C-130 X-perience All-in-One Pack", which is the FSX upgrade,

(file name csp131_1300.exe 100.61 MB), so I think I've got the right one, but thanks for your input..

Eugene

I have the CS C-130 and it works fine with FSX on my machine.

Check your Aircraft.cfg file against this one

 

Inside CS_130 file (SimObject/airplanes)

 

 

 

The Sim= bit in the config file needs to read

 

Sim=c130 (whitch is short for c130.air, the air file...without knowing what air file to load, the sim doesnt know what plane it is.

Also check where the sim is starting...cud be that you have saved a flight with an aircraft that you deleted.

 

Open the file AppData -> Roaming -> FSX

 

Find FSX.cfg, open it ( with notepad )

 

Press Control-F

 

type [uSERINTERFACE]

 

A couple of lines of text under this bit, and one will say:

 

SITUATION= (bla bla bla)

 

Delete anything after the '=' so it reads ''SITUATION=''

 

Also, do you still have the default trike in fsx?

Thanks Spook, Looks pretty much the same, just a few variations on varients... here mine

 

 

I just installed it on a default FSX install and I found no problems at all. Do you have a default FSX install? I'm wondering if some part of the install has gone to the wrong location somehow. Another thing to check is you have 8 CS..130 folders in your SimObjects Folder.

 

There should also be a Captain_Sim folder in the FSX progs folder with a 130 folder containing 7 subfolders.

Situation reads

 

SITUATION=c:\users\fltsim\documents\flight simulator x files\SafeFSX.FLT

 

Will reset to your suggestion (backing up just to be safe) and will try again. Yep, still have the trike, will try loading that then changing aircraft, is that what you were going to suggest?

Yes sorry should have said to back it up 1st

 

no, but i have seen this before when someone has deleted the trike... ( because the sim uses the default trike as a defualt startup aircraft in the defualt SITUATION)

Yep, It was installed to the default FSX folder, and all seems to be there, 145 files in 7 folders in the Microsoft Flight Simulator X Captain_Sim folder (C130).

And 8 C130 folders in the Roaming/FSX/SimObjects folder.

Just tried the amended fsx.cfg, after starting the default trike and changing aircraft to the CS C130, but still no luck, but many thanks for your input guys, at least I'm eliminating stuff.

Strange... i just used your config file for the c130 and no problems, so its not that...you have all the required files needed... so :unknw:

 

Unless something isnt being aloud to write to a file as you have FSX in 'Programe files' ( protected, admin or not)...but if that was the case i would imagin more people would be having the problem, and although there is stuff related to this error name your having none of them relate to CS130.

I hate problems like this, lol.

 

Can you be 100% sure you havnt done anything to the default aircraft, any of them?

 

Just to be clear, you open the config, changed the 'situation' to ''situation='', saved the changes ( was you aloud to save this?) then started fsx...and the trike was in the aircraft window?>

good idea, right click on FSX folder and choose properties, set "write" and "modify" permissions for the "Users" group on the FSX folder and allow subfolders, then reinstall the 130.