Pilot Career: How To Suppress Tactical Codes On AI Wingmen?

[KodiakJac]

Is there a way to suppress the automatic tactical codes assigned to your flight's AI wingmen?  I've started a Fw 190 A-3 Pilot Career, and there are some great custom skins for JG51, but they already have tactical codes.  Maybe I'm blind but is there a box I can check somewhere to suppress the automatic assignment of tactical codes to my AI wingmen in a Pilot Career?

[LukeFF]

You would have to edit the relevant squadron code file which can be found in the scripts.gtp file and then run it in mods-on mode. If this is for Stalingrad, then it'll be the file with the 14 prefix. 

[Skycat1969]

You'll also have to manually assign each custom skin to an aircraft at the start of each mission. And if you're doing that anyhow, I think you might be able to set up the game's code system to show no codes on a specific aircraft.

[KodiakJac]

@LukeFF

 

Wow, this is a blast from the past of my RoF days!

 

Ok, I've unGTPed the scripts.gtp file, and I'm now looking at the fw190a3.txt file in "...luascripts/worldobjects/planes"

 

Do I set...

EnabledDecals=true

to false

 

Are the tactical codes called decals?  If not, what am I looking for?

 

Or am I looking for a field in the 14squadrons.cfg file to edit?

 

Thanks, Luke!

 

 

@Skycat1969

 

"You'll also have to manually assign each custom skin to an aircraft at the start of each mission."

 

I know how to do that.

 

"And if you're doing that anyhow, I think you might be able to set up the game's code system to show no codes on a specific aircraft."

 

And that is what Luke is explaining how to do above.

 

Thanks!

Edited January 12, 2024 by KodiakJac

[LukeFF]

@KodiakJac, the file you want to look at is called something like 14squadronscodes.cfg. Search for the Fw 190 A-3 entry (there is only one Fw 190 squadron on the map), and then you'll see a listing of codes for that unit: two for the commander and assistant commander, and then 40 entries for the rest of the unit. Depending on which codes you want to change, you'll just want to change your entries to "".

 

24 minutes ago, KodiakJac said:

Ok, I've unGTPed the scripts.gtp file, and I'm now looking at the fw190a3.txt file in "...luascripts/worldobjects/planes"

 

Do I set...

EnabledDecals=true

to false

 

That may also work, but I've never tried it. 

 

Hope that helps!

[KodiakJac]

@LukeFF

 

Thanks, Luke!

 

I'll try the fw190a3.txt file first and see if that works, as it would be a little less labor intensive.  If not, I'll dive into the 14squadronscodes.cfg file.

 

Cheers!

[Ram399]

2 hours ago, KodiakJac said:

14squadronscodes.cfg

This is how I remove ID markers for my careers, but I don't replace anything, just ripping the relevant code out and leaving a blank entry for the squadron works fine.

[Skycat1969]

If EnabledDecals=false doesn't work, here's how to edit the squadrons-codes file to disable the fuselage codes:

 

In SCG the specific files for Battle of Moscow are in folder 13 and in the Scripts folder.

 

1. Find the skins file, click at the top, hit CNTRL+F to open a search box, and type: JG 51.

 

2. Write down the squadron number(s) that result for JG 51. Here is what I found:

    [squadron=201151]  = "I./JG 51"

    [squadron=201451]  = "IV./JG 51"

    [squadron=201351]  = "III./JG 51"

 

3. Make a copy of the squadrons-codes file in 13 to a location you are comfortable editing it.

 

4. Open the squadrons-codes file you are editing. Find [squadron=201151].

 

5. Look at the first aircraft (plane="LuaScripts\WorldObjects\Planes\Bf109F2.txt"). If you do not want the code decals for this aircraft, delete the entire section between [code] and the first [end]. Or, I think you can delete the entire squadron entry; or just all the "%22%20%20" numbers after each '=' sign.

 

6. Continue to the next squadron, [squadron=201451], and repeat until you have accounted for all squadrons and aircraft.

 

7. Create an SCG folder in your main Data folder. Inside that, create a subfolder named 13 and a subfolder named scripts.

 

8. Copy your edited squadrons-codes file to your new Data/scg/13 folder. Copy it again to your Data/scg/scripts folder, but this time rename it to 13squadrons-codes inside the scripts folder.

 

Repeat this process for folders 14 (Stalingrad), 15 (Kuban), 18 (Bodenplatte) and 22 (Normandy) as you desire.

[KodiakJac]

On 1/12/2024 at 3:57 PM, KodiakJac said:

@LukeFF

 

Thanks, Luke!

 

I'll try the fw190a3.txt file first and see if that works, as it would be a little less labor intensive.  If not, I'll dive into the 14squadronscodes.cfg file.

 

Cheers!

 

I never came back with an answer on the results of trying the fw190a3.txt file first.  It didn't work, so I had to edit the 14squadronscodes.cfg file to suppress the tactical codes.

 

And I just had to do it again for the 28squadroncodes.cfg file to suppress the Albatros D2 tactical codes because in Jasta 6 during Oct 1916 it was placing a tactical code of 2 on all of the aircraft.  Wasn't sure how to identify Jasta 6 in the 28squadroncodes.cfg file, so I just commented out all of the entries for the Albatros D2 tactical codes.

 

@LukeFF if you see this, is there a way to identify Jasta 6 in the 28squadroncodes.cfg file so I wouldn't have had to comment out all of the Albatros D2 entries?  And maybe I needed to anyway, as if there was a problem in Jasta 6, it might have been a problem for all Albatros D2 squadrons.  Thanks!

 

Edited May 22, 2024 by KodiakJac

[LukeFF]

14 hours ago, KodiakJac said:

 

I never came back with an answer on the results of trying the fw190a3.txt file first.  It didn't work, so I had to edit the 14squadronscodes.cfg file to suppress the tactical codes.

 

And I just had to do it again for the 28squadroncodes.cfg file to suppress the Albatros D2 tactical codes because in Jasta 6 during Oct 1916 it was placing a tactical code of 2 on all of the aircraft.  Wasn't sure how to identify Jasta 6 in the 28squadroncodes.cfg file, so I just commented out all of the entries for the Albatros D2 tactical codes.

 

@LukeFF if you see this, is there a way to identify Jasta 6 in the 28squadroncodes.cfg file so I wouldn't have had to comment out all of the Albatros D2 entries?  And maybe I needed to anyway, as if there was a problem in Jasta 6, it might have been a problem for all Albatros D2 squadrons.  Thanks!

 

It's probably the unit code ending in 006, but I'd have to check the config files.