Trouble making the VRS Superbug "Combat Capable"?

[stearmandriver]

Hi,

I'm trying to load up the combat training missions out of KOLM, and I keep running up against FSCAI (latest version) not recognizing my VRS Bug as combat capable.

I have added it to the vehicles database in the FSCAI program by duplicating the entry for the stock FSX Hornet and only changing the name and atc_model to "F18E" (taken from the aircraft.cfg).

I have also added the F18E to the combat.cfg file in the FSCAI folder.

Still no dice. When I open the mission menu with shift-J while on the ground at KOLM, it displays a header like "missions available for an F18E", so it seems to be reading the atc_model parameter correctly. If I change my era to other than default, I have the option to view ineligible missions, and I do see the 3 combat training missions available. It says I'm ineligible because I must be in a combat capable aircraft.

I was able to load up the combat drop mission at Copalis and destroy the targets placed there and at the intermediate airport, so that part worked.

But does anyone have any other ideas how to convince FSCAI that the VRS Super Hornet is combat-capable? I feel like there must be something very simple that I'm missing...

Thanks!

[hajolippke]

Have you tried changing the ATC-model to "F18" instead in your aircraft.cfg?


HAJO

[stearmandriver]

Well, no, I haven't. I'm usually hesitant to change things in the aircraft.cfg, because I don't know what other addons might rely on that information (would it make vLso think I'm in a classic Hornet instead of Super Hornet for instance?).

I'll give it a try for diagnostic purposes, but would still like to understand why what I've done so far isn't working? What else could I do to tell FSCAI an aircraft is combat capable?

[Dutch Owen]

Apr 13, 2020 17:31:39 GMT -5 stearmandriver said:

Well, no, I haven't. I'm usually hesitant to change things in the aircraft.cfg, because I don't know what other addons might rely on that information (would it make vLso think I'm in a classic Hornet instead of Super Hornet for instance?).

I'll give it a try for diagnostic purposes, but would still like to understand why what I've done so far isn't working? What else could I do to tell FSCAI an aircraft is combat capable?

Make a copy of the file "Combat.cfg" in the Config_STD folder and place it in your Config_USER folder. You can then modify it to add entries for model numbers not already in there, like "F18E" or whatever the Superbug model number is. Then it will recognize it as combat-capable.

Dutch

[stearmandriver]

Apr 13, 2020 19:08:55 GMT -5 Dutch Owen said:

Apr 13, 2020 17:31:39 GMT -5 stearmandriver said:

Well, no, I haven't. I'm usually hesitant to change things in the aircraft.cfg, because I don't know what other addons might rely on that information (would it make vLso think I'm in a classic Hornet instead of Super Hornet for instance?).

I'll give it a try for diagnostic purposes, but would still like to understand why what I've done so far isn't working? What else could I do to tell FSCAI an aircraft is combat capable?

Make a copy of the file "Combat.cfg" in the Config_STD folder and place it in your Config_USER folder. You can then modify it to add entries for model numbers not already in there, like "F18E" or whatever the Superbug model number is. Then it will recognize it as combat-capable.

Dutch

Thanks Dutch!  I actually just returned to the forum to say that I got it working, and saw your post here which basically contains the answer - I had to add F18E to the Combat.cfg file in the Config_STD folder, not the regular Config folder.  I am sure this is contained in documentation somewhere and I just missed it.  All good now though!

[Dutch Owen]

I think it would make life easier if you copy that file with your mods into Config_USER. If you leave the modified version in Config_STD it will be overwritten on each new release.

Dutch

[stearmandriver]

Already done, thanks!