Gabreil

I've just read an article on the helios website regarding the helios profile stopping working after the update. It seems to indicate that the reason things have stopped working is due to the addtion of new keybinds and shifting keybinds id's. From what i can deduce - e.g. if Your button was bound to a DCS CH47 command which for example had an ID of 100, the update now makes ID 100 something else... hence saved joystick/keyboard .lua files now not working. Thats how i understand it... i may be wrong.

@Rudel_chw Thanks. Your image showing the list of joysticks and their ID numbers is exactly what i have for the CH47. None of the controllers have changed. As i mentioned the method i've used for the past couple of years has worked flawlessly, so i am quite happy with the way ive tried to restore saved files. This is directly related to the CH47 - and i think the addition of extra keybinds is the most likely cause. I now have lots of Red ! in my config setup which were not there prior to the update.

Before i did the update to the latest version, as always, i did a full backup of DCS World folder and Saved Games folder. Normally, after the update i copy/paste the backup input folders back into DCS which restores all the keybinds for my various controllers. I've done this numerous times in the past and its always worked. This time, doing the same thing has resulted in almost nothing working. A few keybinds work but for the most, when looking in DCS Contorller configs, there are no keybinds listed against the device. Has something fundamentally changed with the way the controllers now work with the associated joystick and keyboard .lua files? For the CH47, its pretty much put me back to square one.. with hours and hours of configuration down the drain. I'd be keen to hear if others have experiend this and if its had the same impact as it has for me.. and perhaps if you've managed to get around this? For reference i've replaced from backups: DCS\mods\aircraft\CH47\Inputs (which normally restores all my saved keybinds) Saved Games\config\inputs\CH47 Saved Games\DCS\InputCommands\CH47 Just to add... Even if ED could give a brief explanation on whats changed and if its even possible to re-import backups would be helpful.

I've not updated as yet.. So, no idea if the install has updated doucmenation embedded. @BIGNEWY is there documentation to explain the new features please?

So looking forward to seeing this in DCS. I grew up watching the BO105 (civilan version) doing work on Lighthouses.. The sound it makes and the sleek look is amazing... and just thinking about it sends tingles down my spine... Keep up the great work

Thanks... Finally got it working. Having never tried it before, even with the keybinds the indicator did not show up when in the pilots seat. I flipped to the Gunner seat and did the keybings that then worked. Back in the pilots seat the keybinds then worked. It as if something needed to be written to a .lua file when in the gunner seat to then work in the pilot seat. But all good now... Glad its working as its pretty awesome..

Does the Gazelle Minigun variant have AI for the Mingun?

To be fair, once you learn the cockpit.. which with its simpisity is quite quick, the english labels are not really needed. Helpful for a couple of days when learning.

I finally figured it out. When changes are made - they are saved in the options.lua (Saved Games\DCS\Config). I forgot that i am using Baileys app to run different DCS.exe files which i use for when at the PC and connecting remotely - each of which have a different options.lua associated. So, when i was making changes in DCS, they were not saving.. A quick edit of the option.lua for the .exe files and all working now. @Gladius I'm using this mod to convert to english cockpit https://www.digitalcombatsimulator.com/en/files/1956481/

A lot of views but no answers as yet. Could someone who does fly the Gazelle confirm if they make the selection to english that it remains peristant after DCS has been restarted? If i can confirm that, then i'll know if i need to figure out whats wrong my end or just live with it!!

Hi All, I've got the mod installed for English labels. I can get it working ok. But, i cant make it persistant. If i change to English under special - After restarting it defaults back to default. Any suggestions on how to make it persistant please?

Tried to change the brightness of the MFD's today for night flying. Got a bit of a mixed bag of results.. When directly at my PC - Only the Pilots inner MFD brightness button works. None of the others. If i remote RDP onto the pc and run the sim.. I can dim both pilot and copilot inner/outer MFD's..... baffles me!! Should they be working normally?

Asked the question over the Virpil forum as well.. And it can be done.. Here is the answer which i was given, and it works. I eventually found another way also of doing this.. If you double click on the Dial Axis, there are check boxes which you can use.. Not as good as the one below. As long as you realise the big dials only go so far Left/Right then its a good use of them if you dont have a need for them being Axis. Mine are now mapped to FM & UHF radios volume Up & Down. I cant take credit for this.. Flugzeuger provided the solution on Virpil Forums. Attached example shows how to do axis to button, for example for axis slider (it can be for other axis, example dial) P2 means number 2 in Axis to button. If axis dial - it will be number 3 in axis to button. Range You can choose which is comfortable for You (0-50, 25-70 etc) Go to button TAB Press Button 42 Enter physical button, for example 49 Then press physical number for button, save it, and save vpc device And axis will work like button.

Hey All, Got a Virpil Panel 1. I've got the two large axis dials redundant at the moment.. Is there a way to convert these in the Virpil software to act as rotary/encoders the same as the 3 small dials at the bottom of the panel?

First time i've ever seen this.. Anyway to recover without restarting the mission?

Think i have it working now.. I had tried statics before but couldn't get it to work. They have to be quite percisely placed to block the spots. Slight off and the other aircract spawn on top of them.

ahh. thanks. Was looking in the main arms layout.

I've looked in the weapons load out options.. Unless i'm missing something obvious i cant see guns/ammo

I've got a CAS mission with F18 flying off a carrier. All works fine. Is there away to disable the F18 using bombs only... and not Guns?

Ok, i'll look at doing that

and what would be the best solution to prevent that area from being used by the AI ?

I've spent countless hours trying to get things working for consistency... For the most part i've got things working.. But cant seem to figure out how to avoid the scenario where AI planes seem to get stuck and wont park. They stop just forward of the bridge every time. In this situaion nothing can land... Any suggestions... i'm open to re-arranging things if thats what it takes As you can see in the image, this is what tends to happen

Perfect.. thanks for the confirmation and additional info on optimism of target choice...

Anyone care to confrim please?

When placing ground units in ME.. Would i be correct in stating.. Anything inside the green circle is too close and wont be engaged Anything outside the Red circile is too far and wont be engaged therefore Targets must be outside of the green, but inside the red for things like artillery to work?