Crash * Posted December 22, 2019 Share Posted December 22, 2019 Hello. It would be nice to have some additional keybinds for the Ka-50. Salvo on a three way switch. Or the position lights. Only on key for all 4 stages.:( 5 System Specs: AMD Ryzen 5 3600, RX 6900 XT, 64GB RAM // Tobsen CM Kollektiv, VPC CM3 Throttle, VPC WarBRD Rudder Pedals, VPC T-50 CM2 + WarBRD Base VR: HP Reverb G2 Helis: UH-1H / KA-50 3 / Mi-8 / Mi-24P / SA-342 / AH-64D Jets: F-5E / F-14A/B / F/A-18C / MC-2000 / A-10C II / AV-8B / AJS 37 / MIG-21bis / F-16C / F-15E / F-4E (soon) WWII: Spitfire / WWII Assets Pack Tech.: Combined Arms / NS430 / Supercarrier Maps: Nevada / Persian Gulf / Normandie / Syria / South Atlantic Waiting for: BO-105 / OH 58D / CH-47 Chinook / G.91R / Tornado IDS / A-7E Corsair II Link to comment Share on other sites More sharing options...
Fri13 Posted December 22, 2019 Share Posted December 22, 2019 All switches should be operable with just left click and single button too. But as well all multiple choice ones have "up/down" or "clockwise/counterclockwise" bindings, as well direct bindings. i7-8700k, 32GB 2666Mhz DDR4, 2x 2080S SLI 8GB, Oculus Rift S. i7-8700k, 16GB 2666Mhz DDR4, 1080Ti 11GB, 27" 4K, 65" HDR 4K. Link to comment Share on other sites More sharing options...
Kailux Posted January 6, 2020 Share Posted January 6, 2020 +1 on this. Full fidelity aircraft but the button assignment is on FC3 level. Id totally fly this bird more often but i hate putting switched up-down-up-down-up to cycle the ingame switch when i could just bind it to some 3-way switch on my THWH. Gone for good. Link to comment Share on other sites More sharing options...
Schlomo1933 Posted January 6, 2020 Share Posted January 6, 2020 +1000 Link to comment Share on other sites More sharing options...
metzger Posted January 7, 2020 Share Posted January 7, 2020 +1 [sIGPIC][/sIGPIC] Link to comment Share on other sites More sharing options...
jonsky7 Posted January 8, 2020 Share Posted January 8, 2020 (edited) +1 on this. Full fidelity aircraft but the button assignment is on FC3 level. Id totally fly this bird more often but i hate putting switched up-down-up-down-up to cycle the ingame switch when i could just bind it to some 3-way switch on my THWH. I have some modified switches to work as toggle switches, ie the switch in the heli is operated by either moving a TMWH switch up or down, instead of having to go up-down-up to toggle the switch. The switch position can get out of sync with the heli but can be resolved by mouse clicking a cockpit switch to match the TMWH position. I honestly can't remember if I made them or got them from somewhere else. The following can to be copied and pasted into DCS world/Mods/aircraft/Ka-50/input/Ka-50/joystick/default.lua I just put it under the line that says: keyCommands = { It shouldn't alter any of your current keybinds, it will make new entries in the keybind list -- Custom {down = iCommandPlaneModeCannon, up = iCommandPlaneModeCannon, name = _('Gun Select Toggle'), category = _('Custom')}, {down = iCommandSwitchMasterArm, up = iCommandSwitchMasterArm, name = _('Master arm on/off Toggle'), category = _('Custom')}, {down = iCommandHelicopter_Rotor_Lock, up = iCommandHelicopter_Rotor_Lock, name = _('Rotor brake On/off toggle'), category = _('Custom')}, {down = iCommandPlaneLaserRangerOnOff, up = iCommandPlaneLaserRangerOnOff, name = _('Laser standby On/Off switch toggle'), category = _('Custom')}, {down = iCommandPlaneWheelParkingBrake, up = iCommandPlaneWheelParkingBrake, name = _('Wheel brake parking toggle'), category = _('Custom')}, {down = iCommandPlane_AmmoTypeSelect, up = iCommandPlane_AmmoTypeSelect, name = _('Cannon Round Selector toggle'), category = _('Custom')}, {down = iCommandPlaneGear, up = iCommandPlaneGear, name = _("Gear lever toggle"), category = _('Custom')}, {down = iCommandPlane_WeaponMode_Manual_Auto, up = iCommandPlane_WeaponMode_Manual_Auto, name = _('Weapon system control switch Manual/Auto toggle'), category = _('Custom')}, {down = iCommandPlane_AutomaticTracking_Gunsight_switch, up = iCommandPlane_AutomaticTracking_Gunsight_switch, name = _('Automatic tracking/gun sight toggle'), category = _('Custom')}, {down = iCommandPlane_FireRate, up = iCommandPlane_FireRate, name = _('Cannon rate of fire setting toggle'), category = _('Custom')}, {down = iCommandPlaneModeHelmet, up = iCommandPlaneModeHelmet, name = _('Helmet-mounted system On/Off toggle'), category = _('Custom')}, {down = iCommandSwitchMasterArm, up = iCommandSwitchMasterArm, name = _('Master arm on/off toggle'), category = _('Custom')}, {down = iCommandPlane_K041_Power, up = iCommandPlane_K041_Power, name = _('K-041 Targeting system power switch Toggle'), category = _('Ins Targeting Mode Controls Panel PVR')}, {down = iCommandPlane_RouteMode, up = iCommandPlane_RouteMode, name = _('Engage/Disengage Route Mode toggle'), category = _('Ins Collective Stick')}, Edited January 8, 2020 by jonsky7 1 Link to comment Share on other sites More sharing options...
ghost84 Posted February 21, 2020 Share Posted February 21, 2020 +10000 Gear Up / Down should have separate key bindings. And there are many more missing. 2 Link to comment Share on other sites More sharing options...
Bourrinopathe Posted February 27, 2020 Share Posted February 27, 2020 Yes please! We need more key bindings. As mentioned above, many essential controls are just toggle switches: landing gear, master arm, laser standby/active, etc. Additionally, brightness knobs axes could also be very useful (ABRIS, HUD, etc.). 2 /// ВКБ: GF Pro MkII+MCG Pro/GF MkII+SCG L/Black Mamba MkIII/Gladiator/T-Rudder MkII | X-55 Rhino throttle/Saitek Throttle Quadrant | OpenTrack+UTC /// ZULU +4 /// /// "THE T3ASE": i9 9900K | 64 GB DDR4 | RTX 2080ti OC | 2 TB NVMe SSDs, 1 TB SATA SSD, 12 TB HDDs | Gigabyte DESIGNARE mobo /// Link to comment Share on other sites More sharing options...
rrohde Posted February 27, 2020 Share Posted February 27, 2020 Yes please! We need more key bindings. As mentioned above, many essential controls are just toggle switches: landing gear, master arm, laser standby/active, etc. Additionally, brightness knobs axes could also be very useful (ABRIS, HUD, etc.). Totally agree! :thumbup: PC: AMD Ryzen 9 5950X | MSI Suprim GeForce 3090 TI | ASUS Prime X570-P | 128GB DDR4 3600 RAM | 2TB Samsung 870 EVO SSD | Win10 Pro 64bit Gear: HP Reverb G2 | JetPad FSE | VKB Gunfighter Pro Mk.III w/ MCG Ultimate VKBcontrollers.com Link to comment Share on other sites More sharing options...
Hunter_5E Posted February 28, 2020 Share Posted February 28, 2020 +1 It would be great if we could use switches properly like in the A10C module. I'd also like to see some more axes added. The Shkval is always much darker in a viewport than in cockpit for some reason so I always have to adjust brightness/contrast for it at the start of a mission. Often have to adjust it in mission as well so those axes would be very welcome. Link to comment Share on other sites More sharing options...
Crash * Posted February 28, 2020 Author Share Posted February 28, 2020 A 8-way keybind for the skhval would be up-to-date. A laser on and a seperate laser off. Since BS1 there are much better HOTAS on most desks, with more more switches and buttons and hats. :smartass: 1 System Specs: AMD Ryzen 5 3600, RX 6900 XT, 64GB RAM // Tobsen CM Kollektiv, VPC CM3 Throttle, VPC WarBRD Rudder Pedals, VPC T-50 CM2 + WarBRD Base VR: HP Reverb G2 Helis: UH-1H / KA-50 3 / Mi-8 / Mi-24P / SA-342 / AH-64D Jets: F-5E / F-14A/B / F/A-18C / MC-2000 / A-10C II / AV-8B / AJS 37 / MIG-21bis / F-16C / F-15E / F-4E (soon) WWII: Spitfire / WWII Assets Pack Tech.: Combined Arms / NS430 / Supercarrier Maps: Nevada / Persian Gulf / Normandie / Syria / South Atlantic Waiting for: BO-105 / OH 58D / CH-47 Chinook / G.91R / Tornado IDS / A-7E Corsair II Link to comment Share on other sites More sharing options...
flanker0ne Posted March 18, 2020 Share Posted March 18, 2020 (edited) Missing axis {action = 3001, cockpit_device_id = 7, filter = {saturationX = 1, saturationY = 0.5, deadzone = 0, invert = true, slider = true, curvature = {0}}, name = _('HUD Brightness Knob')}, {action = 3002, cockpit_device_id = 8, name = _('IT-23 TV Brightness Axis')}, {action = 3003, cockpit_device_id = 8, name = _('IT-23 TV Contrast Axis')}, {action = 3008, cockpit_device_id = 9, name = _('ABRIS Brightness Axis')}, {action = 3001, cockpit_device_id = 23, name = _('Helmet device Brightness Axis')}, {action = 3006, cockpit_device_id = 46, name = _('ADF Volume Axis')}, {action = 3002, cockpit_device_id = 49, name = _('R-828 (VHF-1) Radio Volume Axis')}, Still require some finetuning to accept secondary settings (slider, invert, saturation ecc) by default, but it work Edited March 19, 2020 by flanker0ne SCOPRI DI PIU': https://www.amvi.it/joinus.php DISCORD COMBINEDOPS The Battle Planning Tool Link to comment Share on other sites More sharing options...
Bourrinopathe Posted March 19, 2020 Share Posted March 19, 2020 What a relief! The most annoying controls for me were the Shkval TV brightness and the Night Vision Goggles and monocle reticle brightness. Thank you, flanker0ne! For those not familiar with the config file, the new lines should be placed below axisCommands = { (within this category) /// ВКБ: GF Pro MkII+MCG Pro/GF MkII+SCG L/Black Mamba MkIII/Gladiator/T-Rudder MkII | X-55 Rhino throttle/Saitek Throttle Quadrant | OpenTrack+UTC /// ZULU +4 /// /// "THE T3ASE": i9 9900K | 64 GB DDR4 | RTX 2080ti OC | 2 TB NVMe SSDs, 1 TB SATA SSD, 12 TB HDDs | Gigabyte DESIGNARE mobo /// Link to comment Share on other sites More sharing options...
Kailux Posted March 27, 2020 Share Posted March 27, 2020 Posts here are very helpful (thanks for posting), but having it fully implemented by ED still is my no. 1 wishlist item for the BS. Having all buttons and switches implemented in the controls setup like they are in the A-10C would be awesome. 1 Gone for good. Link to comment Share on other sites More sharing options...
flanker0ne Posted March 28, 2020 Share Posted March 28, 2020 Yes, a merge can be usefull From what i remember HOTAS/Home cockpits Abstractions Missing Axis Flashlight SCOPRI DI PIU': https://www.amvi.it/joinus.php DISCORD COMBINEDOPS The Battle Planning Tool Link to comment Share on other sites More sharing options...
Tone71 Posted April 22, 2020 Share Posted April 22, 2020 Just wanted to add a +1 from me too and a thank you to all of the helpful posts! Windows 10 Home, Intel Core i7-9700K @ 4.6GHz, Gigabyte GTX 1070 G1 Gaming (8GB VRAM) on 34" LG curved monitor @ 3440x1440, 32GB RAM, TrackIR 3 (with Vector Expansion), Thrustmaster Warthog HOTAS, Saitek Combat Pedals, Thrustmaster Cougar MFDs. Link to comment Share on other sites More sharing options...
LeCuvier Posted April 22, 2020 Share Posted April 22, 2020 Here are my added commands for maintained 2- and 3-position switches. They actually use the cockpit commands defined in "clickabledata.lua": {down = 3002, up = 3002, value_down = 1, value_up = 0, cockpit_device_id = 23, name = _('Helmet-mounted System 2-Pos. On/Off'), category = _('Ins Targeting Mode Controls Panel PVR')}, {down = 3001, up = 3001, value_down = 1, value_up = 0, cockpit_device_id = 11, name = _('Laser standby 2-Pos ON/OFF Switch'), category = _('Ins Targeting Mode Controls Panel PVR')}, {down = 3017, up = 3017, value_down = 1.0, value_up = -1.0, cockpit_device_id = 12, name = _('Automatic tracking/gun sight 2-Pos AT/GS'), category = _('Ins Targeting Mode Controls Panel PVR')}, {down = 3001, up = 3001, value_down = 1.0, value_up = -1.0, cockpit_device_id = 12, name = _('Master arm 2-Pos ON/OFF'), category = _('Ins Weapons Status and Control Panel PUI-800')}, {down = 3006, up = 3006, value_down = 1.0, value_up = -1.0, cockpit_device_id = 12, name = _('Cannon round selector 2-Pos HE/API'), category = _('Ins Weapons Status and Control Panel PUI-800')}, {down = 3004, up = 3004, value_down = 0.2, value_up = 0.1, cockpit_device_id = 12, name = _('Weapon mode Burst Length 3-Pos HIGH/MEDIUM'), category = _('Ins Weapons Status and Control Panel PUI-800')}, {down = 3004, up = 3004, value_down = 0.0, value_up = 0.1, cockpit_device_id = 12, name = _('Weapon mode Burst Length 3-Pos LOW/MEDIUM'), category = _('Ins Weapons Status and Control Panel PUI-800')}, {down = 3020, up = 3020, value_down = 1.0, value_up = 0.0, cockpit_device_id = 12, name = _('Cannon rate of fire 2-Pos LOW/HIGH'), category = _('Ins Weapons Status and Control Panel PUI-800')}, {down = 3005, up = 3005, value_down = 1.0, value_up = -1.0, cockpit_device_id = 12, name = _('Weapon Control 2-Pos MAN/AUTO'), category = _('Ins Weapons Status and Control Panel PUI-800')}, {down = 3007, up = 3007, value_down = 1.0, value_up = -1.0, cockpit_device_id = 51, name = _('Lighting Night Vision Cockpit Switch 2-Pos ON/OFF'), category = _('Ins Wall panel')},These commands avoid the synchronization problems mentioned by Jonsky. LeCuvier Windows 10 Pro 64Bit | i7-4790 CPU |16 GB RAM|SSD System Disk|SSD Gaming Disk| MSI GTX-1080 Gaming 8 GB| Acer XB270HU | TM Warthog HOTAS | VKB Gladiator Pro | MongoosT-50 | MFG Crosswind Pedals | TrackIR 5 Link to comment Share on other sites More sharing options...
LeCuvier Posted April 22, 2020 Share Posted April 22, 2020 Missing axis {action = 3001, cockpit_device_id = 7, filter = {saturationX = 1, saturationY = 0.5, deadzone = 0, invert = true, slider = true, curvature = {0}}, name = _('HUD Brightness Knob')}, {action = 3002, cockpit_device_id = 8, name = _('IT-23 TV Brightness Axis')}, {action = 3003, cockpit_device_id = 8, name = _('IT-23 TV Contrast Axis')}, {action = 3008, cockpit_device_id = 9, name = _('ABRIS Brightness Axis')}, {action = 3001, cockpit_device_id = 23, name = _('Helmet device Brightness Axis')}, {action = 3006, cockpit_device_id = 46, name = _('ADF Volume Axis')}, {action = 3002, cockpit_device_id = 49, name = _('R-828 (VHF-1) Radio Volume Axis')},Still require some finetuning to accept secondary settings (slider, invert, saturation ecc) by default, but it work For the IT-23 commands I noted that they need to be used with Saturation Y = 50%, Slider = TRUE, Invert = TRUE. I have not implemented the other axes as I do not have any spare axis; but they might require similar settings, as the software tends to use only the upper or lower 50% of available signal range. LeCuvier Windows 10 Pro 64Bit | i7-4790 CPU |16 GB RAM|SSD System Disk|SSD Gaming Disk| MSI GTX-1080 Gaming 8 GB| Acer XB270HU | TM Warthog HOTAS | VKB Gladiator Pro | MongoosT-50 | MFG Crosswind Pedals | TrackIR 5 Link to comment Share on other sites More sharing options...
flanker0ne Posted April 23, 2020 Share Posted April 23, 2020 (edited) From my attempts, I realize that the pre-settings (filter) for axis work only if you pre-assign a joystick axis. If the line start with {action = ... and not with {combos = ... DCS ignore any pre-setting (filter) Edited April 23, 2020 by flanker0ne SCOPRI DI PIU': https://www.amvi.it/joinus.php DISCORD COMBINEDOPS The Battle Planning Tool Link to comment Share on other sites More sharing options...
kingpinda Posted September 3, 2020 Share Posted September 3, 2020 yeah man at least have more than 1 bind for 3 way switches. I want to be able to map the desired heading track to my warthog path altitude switch but in game there is just one command for the switch. at least have 1 bind for up and 1 bind for down. now it cycles in 1 direction. Link to comment Share on other sites More sharing options...
Razor5-1 Posted April 18, 2021 Share Posted April 18, 2021 On 2/21/2020 at 8:03 AM, ghost84 said: +10000 Gear Up / Down should have separate key bindings. And there are many more missing. Literally went looking for what you've said! I am getting a Virpil control panel with the gear lever. But the KA50 is literally a button for the gear unfortunately! 1 Link to comment Share on other sites More sharing options...
LeCuvier Posted April 19, 2021 Share Posted April 19, 2021 For Landing gear UP/DOWN separate bindings add these to "default.lua": 1. For a pair of pushbutton-type switches: {down = 3001, value_down = 1.0,cockpit_device_id = 34, name = _('Gear Lever DOWN'), category = _('Ins Forward panel and gauges')}, {down = 3001, value_down = -1.0,cockpit_device_id = 34, name = _('Gear Lever UP'), category = _('Ins Forward panel and gauges')}, 2. For a single maintained ON/OFF switch (ON => UP, OFF => DOWN): {down = 3001, up = 3001, value_down = -1.0, value_up = 1.0, cockpit_device_id = 34, name = _('Gear Lever 2-Pos UP/DOWN'), category = _('Ins Forward panel and gauges')}, LeCuvier Windows 10 Pro 64Bit | i7-4790 CPU |16 GB RAM|SSD System Disk|SSD Gaming Disk| MSI GTX-1080 Gaming 8 GB| Acer XB270HU | TM Warthog HOTAS | VKB Gladiator Pro | MongoosT-50 | MFG Crosswind Pedals | TrackIR 5 Link to comment Share on other sites More sharing options...
Schlomo1933 Posted May 3, 2021 Share Posted May 3, 2021 @LeCuvier : could you please make a mod for all the relevant switches ? Gear, Laser, Helmet sight, gunrate and ammotype ? that would be realy nice and helpfull Link to comment Share on other sites More sharing options...
LeCuvier Posted May 4, 2021 Share Posted May 4, 2021 Here are all the specials I created, some for myself and some for other simmers: {down = 3002, up = 3002, value_down = 1, value_up = 0, cockpit_device_id = 23, name = _('Helmet-mounted System 2-Pos. On/Off'), category = _('Ins Targeting Mode Controls Panel PVR')}, {down = 3001, up = 3001, value_down = 1, value_up = 0, cockpit_device_id = 11, name = _('Laser standby 2-Pos ON/OFF Switch'), category = _('Ins Targeting Mode Controls Panel PVR')}, {down = 3017, up = 3017, value_down = 1.0, value_up = -1.0, cockpit_device_id = 12, name = _('Automatic tracking/gun sight 2-Pos AT/GS'), category = _('Ins Targeting Mode Controls Panel PVR')}, {down = 3001, up = 3001, value_down = 1.0, value_up = -1.0, cockpit_device_id = 12, name = _('Master arm 2-Pos ON/OFF'), category = _('Ins Weapons Status and Control Panel PUI-800')}, {down = 3006, up = 3006, value_down = 1.0, value_up = -1.0, cockpit_device_id = 12, name = _('Cannon round selector 2-Pos HE/API'), category = _('Ins Weapons Status and Control Panel PUI-800')}, {down = 3004, up = 3004, value_down = 0.2, value_up = 0.1, cockpit_device_id = 12, name = _('Weapon mode Burst Length 3-Pos HIGH/MEDIUM'), category = _('Ins Weapons Status and Control Panel PUI-800')}, {down = 3004, up = 3004, value_down = 0.0, value_up = 0.1, cockpit_device_id = 12, name = _('Weapon mode Burst Length 3-Pos LOW/MEDIUM'), category = _('Ins Weapons Status and Control Panel PUI-800')}, {down = 3020, up = 3020, value_down = 1.0, value_up = 0.0, cockpit_device_id = 12, name = _('Cannon rate of fire 2-Pos LOW/HIGH'), category = _('Ins Weapons Status and Control Panel PUI-800')}, {down = 3005, up = 3005, value_down = 1.0, value_up = -1.0, cockpit_device_id = 12, name = _('Weapon Control 2-Pos MAN/AUTO'), category = _('Ins Weapons Status and Control Panel PUI-800')}, {down = 3007, up = 3007, value_down = 1.0, value_up = -1.0, cockpit_device_id = 51, name = _('Lighting Night Vision Cockpit Switch 2-Pos ON/OFF'), category = _('Ins Wall panel')}, {down = 3006, value_down = 1.0,cockpit_device_id = 2, name = _('Battery 1 Cover Open'), category = _('MODDED')}, {down = 3006, value_down = -1.0,cockpit_device_id = 2, name = _('Battery 1 Cover Close'), category = _('MODDED')}, {down = 3001, value_down = 1.0,cockpit_device_id = 34, name = _('Gear Lever DOWN'), category = _('Ins Forward panel and gauges')}, {down = 3001, value_down = -1.0,cockpit_device_id = 34, name = _('Gear Lever UP'), category = _('Ins Forward panel and gauges')}, {down = 3001, up = 3001, value_down = -1.0, value_up = 1.0, cockpit_device_id = 34, name = _('Gear Lever 2-Pos UP/DOWN'), category = _('Ins Forward panel and gauges')}, {down = 3022, up = 3022, value_down = 1.0, value_up = -1.0, cockpit_device_id = 12, name = _('Jettison Fuse 2-Pos ARM/DISARM'), category = _('Ins Weapons Status and Control Panel PUI-800')}, {down = 3002, up = 3002, value_down = 1.0, value_up = -1.0, cockpit_device_id = 59, name = _('K-041 Targeting Power 2-Pos Switch ON/OFF'), category = _('Ins Targeting Mode Controls Panel PVR')}, {down = 3006, up = 3006, value_down = -1.0, value_up = 1.0, cockpit_device_id = 33, name = _('Autopilot Altitude Hold Mode 2-Pos BARO/RALT'), category = _('Autopilot Panel')}, {down = 3003, up = 3003, value_down = -1.0, value_up = 1.0, cockpit_device_id = 28, name = _('Autopilot Desired Heading/Desired Track 2-Pos DH/DT'), category = _('Autopilot Panel')}, Note: most of the lines I created for myself are for maintained 2-position ON/OFF switches. You can easily create two separate bindings for pushbuttons. Take the first line of code above. It switches the HMD ON when the switch goes from OFF to ON, and it switches the HMD OFF when the switch goes from ON to OFF. For a pair of pushbuttons, we split this into two lines: {down = 3002, value_down = 1, cockpit_device_id = 23, name = _('Helmet-mounted System ON'), category = _('Ins Targeting Mode Controls Panel PVR')}, {down = 3002, value_down = 0, cockpit_device_id = 23, name = _('Helmet-mounted System OFF'), category = _('Ins Targeting Mode Controls Panel PVR')}, The two lines are almost identical, only the value_down is = 1 for ON and =0 for OFF; and of course the names must be different. 1 1 LeCuvier Windows 10 Pro 64Bit | i7-4790 CPU |16 GB RAM|SSD System Disk|SSD Gaming Disk| MSI GTX-1080 Gaming 8 GB| Acer XB270HU | TM Warthog HOTAS | VKB Gladiator Pro | MongoosT-50 | MFG Crosswind Pedals | TrackIR 5 Link to comment Share on other sites More sharing options...
Bvv.Fr Posted May 17, 2021 Share Posted May 17, 2021 (edited) On 2/28/2020 at 7:33 PM, Crash * said: A 8-way keybind for the skhval would be up-to-date. hello any solution for that? ican't make a macro with voiceattack or other app but i would prefer directly in DCS. i can write every simple one key mapping/binding but this one il more complex, i wrote some complex function for the F14 but not try yet for the KA-50 if someone has already done the job? i think we won't have any improvement because the BS3 is coming.... Edited May 17, 2021 by Bvv.Fr this game is incredible Link to comment Share on other sites More sharing options...
Recommended Posts