Special Aircraft Service

Please login or register.

Login with username, password and session length
Advanced search  
Pages: [1]   Go Down

Author Topic: AIR- and PLANE.ini files after introduction 'Check Points'  (Read 2626 times)

0 Members and 1 Guest are viewing this topic.

henkypenky

  • member
  • Offline Offline
  • Posts: 958
  • BAT 4.2 Flashpoint & WAW
AIR- and PLANE.ini files after introduction 'Check Points'
« on: August 12, 2017, 04:47:20 AM »

Hello, I have a 'problem' with the AIR and PLANE.ini files, which looks to become worse with the introduction of 'Check Points'. I only use historical aircraft and have no interest in non-existent aircraft like, for example, Lagg-3RD, La-7R, Mig-3U and all Dragonflys. Up to the checkpoints, that wasn't so bad, after an update, put an hour to place '//' in the AIR.INI and that was it. Now I understand that with each new "Check Point" folder #WAW3 will be replaced with a newer version. As you understand, I'm not so happy because I think there will be more 'Check Points' than updates.
First I have the question if deleting the AIR.INI lines of unused planes will harm the game.
Second I would like to suggest that the 'old' #WAW3 is not deleted but renamed, so that the user can save his own files and delete it when he wish to do so. (I nearly lost my SKINMOD folder with the intallation of 'Check Point Charly", fully realising that this was my own fault and I really did RTFM, but still.  :-[)

Another item in this is the grouping of the planes; for me the Thunderbolt Mk I is a RAF Fighter Command plane, but it is in the USAAF Fighter chapter. The same goes for a number of other planes, Mustang Mk**, Corsair Mk** etc.
Than there is the sequence of the planes; I did considerable trouble to sort the Spitfires more or less on type and than year of introduction, so my AIR- and PLANE.ini for the two gun Mk Vc is as follows:

SpitfireMkVc16lbsN    air.SPITFIRE5C16LBSN 1     Spitfire F Mk Vc2 1941   
SpitfireMkVcLFCLPN   air.SPITFIRE5C2LFCLPN 1    Spitfire F Mk Vc2 cw 1942   
SpitfireMkVc             air.SPITFIRE5C2 1             Spitfire F Mk Vc2(T), 1942 (default)   
SpitfireMkVcFB          air.SPITFIRE5C2FB 1          Spitfire F Mk Vc2(T), fb 1942   
SpitfireMkVcLF          air.SPITFIRE5C2LF 1          Spitfire Lf Mk Vc2(T), fb 1942   
SpitfireMkVcLFCLP      air.SPITFIRE5C2LFCLP 1     Spitfire Lf Mk Vc2(T), fb cw 1942   
SpitfireMkVc16lbs      air.SPITFIRE5C216LBS 1      Spitfire F Mk Vc2(T), 1943 (default)   
SpitfireMkVc2AK        air.SPITFIREMKVc2AK 1      Spitfire Mk Vc2 Abk 1942   
SpitfireMkVc2cwAK   air.SPITFIREMKVc2cwAK 1   Spitfire Mk Vc2 Abk cw 1943

First two columns are from AIR, third from PLANE. I must add that I use Knochenklutschers 'filterless' Mk Vc, as I consider this a 'better' render that the 'Riken' version. For me my own list is much more clearer than the one supplied, so herewith my third (or ist it the fourth?) request; can these files be 'cleaned up' so that its more obvious which plane one picks in the QMB. Also the WEAPON file could do with some TLC as some entries are not very clear.     

Hope I will not be seen as 'ungratefull' for this comment / request, as I really appreciate all the hard work the team does for us to give us the best WWII simulator around.

Edit: did you know that the AIR.ini that comes with Sea Lion has 1085(!) entries?? No wonder I could not completely understand  :)   

Logged

PO_MAK_249RIP

  • CMON U SPURS!
  • member
  • Offline Offline
  • Posts: 2112
Re: AIR- and PLANE.ini files after introduction 'Check Points'
« Reply #1 on: August 12, 2017, 06:52:36 AM »

You can quite easily edit your own air.ini by either deleting or '//' out the aircraft you dont want, it wont affect the game and I think its proven that a reduced air.ini actually helps performance. I've reduced mine lots (I'm still on CUP but heavily modified) especially deleting the myriad of Spits/Bf109/A6M.......et al.
Logged
Corsair Carbide case, Intel core i5 4690 3.5ghz with Arctic Cooler, Asus Rock H97 performance, MSI Ventus XS OC 1660GTX 6GB DDR6, 32GB Patriot Viper 1600Mhz, 256GB/500GB Crucial SSDs, Windows 10 64bit.

Vampire_pilot

  • member
  • Offline Offline
  • Posts: 8630
Re: AIR- and PLANE.ini files after introduction 'Check Points'
« Reply #2 on: August 13, 2017, 09:59:47 AM »

Fun Fact: BAT just introduced that as a feature. Check

.../BATMODS/#WAW_00-AIRBOOST BOB/

that's what you want to do with your own custom air.ini
Logged

ol' Navy

  • member
  • Offline Offline
  • Posts: 606
Re: AIR- and PLANE.ini files after introduction 'Check Points'
« Reply #3 on: August 13, 2017, 01:24:49 PM »

Fun Fact: BAT just introduced that as a feature. Check

.../BATMODS/#WAW_00-AIRBOOST BOB/

that's what you want to do with your own custom air.ini

Once you have done this (enabled it), it is reversible, is it not.  I am thinking that it what JSGME does for you, but as often happens, I could be wrong.  Thanks for advice.
Logged

Griffon_301

  • SAS Team
  • member
  • Offline Offline
  • Posts: 2199
Re: AIR- and PLANE.ini files after introduction 'Check Points'
« Reply #4 on: August 14, 2017, 01:03:38 AM »

just my two cents from creating my own theatre packs out of the base WAW...
as long as the content is packed in sfs files, you can just delete out what you want...
for the planes this means that you can safely erase any lines containing the planes you do not want in the air.ini.
also, as long as you stay in the syntax in the headers in the air.ini, you can add your own headers .. for example I have created additional USN Bomber headers throwing in all dive bombers, torp bombers and patrol bombers there are; I did the same for the IJN and IJA aircraft ...

it is really fairly easy to create a custom air.ini, but when new EPs are released, you might need to amend your custom air.ini to include any new planes that came with the new EP and which you might want to have included in your air.ini....

Logged

henkypenky

  • member
  • Offline Offline
  • Posts: 958
  • BAT 4.2 Flashpoint & WAW
Re: AIR- and PLANE.ini files after introduction 'Check Points'
« Reply #5 on: August 14, 2017, 03:35:54 AM »

Hi, thanks for all the feedback guys. Since posting I've tried to delete some entries; works ok and as long as one has a 'original' AIR.ini file at hand its as difficult as Ctr/C CtrV to restore things. Main issue; the original could be so much better. But keeping my own AIR.ini wil be a good solution.
Hope Monty and his team will reconsider the renaming of the #WAW3 folder.
Logged

whistler

  • Modder
  • member
  • Offline Offline
  • Posts: 2784
Re: AIR- and PLANE.ini files after introduction 'Check Points'
« Reply #6 on: August 14, 2017, 05:34:15 AM »

Hope Monty and his team will reconsider the renaming of the #WAW3 folder.

That can't be (easily) done. The installer renames #WAW3 to -#WAW3 and then in the next expansion what should the installer do if it finds a -#WAW3 because the user did not delete it?

My advise is to first run the installer and point it to an empty folder. The installer will generate a log (how cool is that from Mike Storebror  :) ), then you can open the log, review what the installer does, and proceed manually as you please.
Logged
NG-HUD v3.6.1 | NG-MAP v3.2 | NG-CAM v2.0 | NG-PAL v1.2: https://www.sas1946.com/main/index.php/board,93.0.html

Griffon_301

  • SAS Team
  • member
  • Offline Offline
  • Posts: 2199
Re: AIR- and PLANE.ini files after introduction 'Check Points'
« Reply #7 on: August 14, 2017, 08:10:20 AM »

ehm and that is the reason why I do all installation stuff myself manually...i know what I renamed, where i copied what and how everything interacts with each other :)

what I forgot to add...you can also delete out all maps you dont want or need in the all.ini, i do not know if that helps performance-wise, but it is possible :)
I did that for my WAW and EAW theatre packs and it works like a charme....no need for ETO maps in PTO scenarios and vice versa...

but as a word of caution...if you are only casually flying the old modded lady, better to stick what BAT provides as it is a truly magnificent and comprehensive pack!
Logged

PO_MAK_249RIP

  • CMON U SPURS!
  • member
  • Offline Offline
  • Posts: 2112
Re: AIR- and PLANE.ini files after introduction 'Check Points'
« Reply #8 on: August 15, 2017, 12:25:37 AM »

I have done the same as Griffon besides thinning down my (CUP) air.ini I have added new headings for countries and split them into Fighters/Bombers/Naval.....etc. Its great fun actually 👍
Logged
Corsair Carbide case, Intel core i5 4690 3.5ghz with Arctic Cooler, Asus Rock H97 performance, MSI Ventus XS OC 1660GTX 6GB DDR6, 32GB Patriot Viper 1600Mhz, 256GB/500GB Crucial SSDs, Windows 10 64bit.

Bigmug

  • member
  • Offline Offline
  • Posts: 118
Re: AIR- and PLANE.ini files after introduction 'Check Points'
« Reply #9 on: August 18, 2017, 08:15:39 AM »

Hi!
Why not changing the air.ini via JSGME? Make a copy of the a.m. /BATMODS/#WAW_00-AIRBOOST BOB folder, rename it to Henkypenkies_Special_Birds_Edition (for example ;)) wipe out / add the things you need, and activate or deactivate it as desired, as BAT expansions usually don't touch it. Keep a backup outside the game, just in case.
You can let all the excellent stuff delivered by the BAT team untouched in future (so it will work, whatever changes you apply).
Works fine with maps I'm using and I'm going to rework the air.ini for my notebookinstallation of the game soon, as enabling #WAW_00-AIRBOOST BOB made the game playable again (fps from 10 - normal edition to 65 and higher with enabled #WAW_00-AIRBOOST BOB).

Cheers,
BigMug. 
Logged

henkypenky

  • member
  • Offline Offline
  • Posts: 958
  • BAT 4.2 Flashpoint & WAW
Re: AIR- and PLANE.ini files after introduction 'Check Points'
« Reply #10 on: August 18, 2017, 12:36:17 PM »

Thanks forall the feedback guy's, atm I'm busy to delete all planes that I for sure will not use. Number of entries 956 form original 1085, going to delete all the 'aces planes' as well; never used these in my Il-2 history. Be sure that I have a 1085 entries copy at hand as one will never know..
Logged
Pages: [1]   Go Up
 

Page created in 0.335 seconds with 25 queries.