jonsky7

Sorry to hear that it wiped your keybinds. I use the Quaggles input command injector. You can make modifications in a separate file and it leaves the default keybindings files alone. Added benefit is that there is no need to modify the default files each update.

The 'name' and the 'category' can be anything you like, they are just what shows up in the controls menu, first and second columns. You weren't far away though. In the clickable data you have the device name, devices.APN_209, and also there's reference to the buttons. The low setting was easier device_commands.Button_2 But the high setting said buttons 1, and 3, I just had to test them. There was also some reference to some values, 0, 0.1, 1 IIRC. Button 1 is the push to test on the HI Knob. Like I mentioned, for a rotary encoder, you might have to change them to 'down' rather than 'pressed'.

Well you're not wrong {pressed = device_commands.Button_2, up = device_commands.Button_2, value_pressed = 0.01, value_up = 0, cockpit_device_id = devices.APN_209, name = _('RAD ALT LO SET DOWN'), category = {_("RAD ALT")}}, {pressed = device_commands.Button_2, up = device_commands.Button_2, value_pressed = -0.01, value_up = 0, cockpit_device_id = devices.APN_209, name = _('RAD ALT LO SET UP'), category = {_("RAD ALT")}}, {pressed = device_commands.Button_3, up = device_commands.Button_3, value_pressed = 0.01, value_up = 0, cockpit_device_id = devices.APN_209, name = _('RAD ALT HI SET DOWN'), category = {_("RAD ALT")}}, {pressed = device_commands.Button_3, up = device_commands.Button_3, value_pressed = -0.01, value_up = 0, cockpit_device_id = devices.APN_209, name = _('RAD ALT HI SET UP'), category = {_("RAD ALT")}}, You can adjust the values in the part value_pressed = 0.01 value_pressed = -0.01 0.05 seemed too fast to me, but 0.01 may be a little slow. Maybe 0.02 would be good. Copy into both keyboard and joystick "default.lua" files. "Pressed" means the action will be repeated as long as the key/button is held down or you could change that to {down = device_commands.Button_2, up = device_commands.Button_2, value_down = 0.01, value_up = 0 (probably better for a rotary encoder) if you want to move the setting a certain amount each key press, like the notch in the mouse wheel Regards Jon.

The "winwing" config file looks good But you are currently using a config file called "wwtMonitor". Also I'm not sure what is going on with the set resolution in the DCS launcher. I would suggest changing or at least checking that in the settings menu of DCS itself.

Reported bug already

Yes, it happens in ALL aircraft while exporting displays. It seems when exporting, the cockpit display also gets an additional render on top of the original. And like stacking astronomy photos on top of each other, this increases the display brightness.

Do you export that display? If so, that is the problem, exporting the display messes with the in cockpit display brightness. VERY LONG standing bug.

Per user request, Version 4.3 Released for direct copy to Core Game, I've updated the first post with a modified file. It leaves ED's implementation intact, so there will be 3 sets of keybinds for the CDU's, LEFT / RIGHT / ACTIVE. I've copied the MFD's over too, seems to work, let me know if there is any issues. As far as I can tell, Quaggles doesn't require any file changes, but you might need to re-do your keybinds. Cheers Jon

I haven't done a huge amount of testing with this but... ED's modules' exports are usually named LEFT_MFCD and RIGHT_MFCD as you know. The CH-47's files that have the exports in them, in GCBase and are there but commented out (not activated), as you mentioned, have 4 screens labelled LEFT_MFCD, and only one RIGHT_MFCD. When I tried simply removing the comments, to activate them, the exported screens were overlaying each other on the export monitor. So I was thinking that maybe, they were waiting for the "seat swap" code to work (like the Apache), where the MFCD exports would change depending on which seat you were sat in.

When you say stuttering, do you mean as you are moving your head? or Constant stuttering once you've moved your head to a new position? I've just tried the apache, I export both MFD's and the TADS, and while the TADS has a bit of a delay (suspect it is supposed to do that), otherwise not really much to report. Has anything changed in those last two weeks? New Driver for GFX ? (seem to recall a few things saying new nvidia drivers were awful)

When George is pilot and you select a height in the Barometric region, George STILL continously alters altitude based on ground elevation. IMO he should just maintain a barometric altitude. Thanks

I think it is OH58D or OH-58D

Did you switch on "PRECISE" mode?

You can export a second view, but I don't think you can exclude it from TrackIR etc This is the actual viewports section, just need to get the syntax right. The whole "viewports" section has opening and closing brackets {} Each viewport has opening and closing brackets inside the viewports section You'll notice the closing bracket after the "center" section now has a comma, and the last one doesn't I'm pretty sure Dx values adjust the view left and right and 1 = 90deg, although you can use many decimal points ie 0.999999998

I don't know of any other way than changing the monitors' resolution in Windows display settings BEFORE running DCS. Either that or setup the config file for full resolution, then use DLSS to increase the frame rate. (I dont know much about it) Seems like running exports messes up the "fullscreen" rescaling.

As far as I'm aware, the list on page 1 is up to date. Under the section "advanced editing by aircraft type"

GU MAIN VIEWPORT should be GU_MAIN_VIEWPORT Is there a specific aircraft you are looking that is not listed on page 1, in the part with the title Advanced editing by aircraft type. ?

I don't think it is exportable by default. You could probably do the display export mod, it will break IC on pure scripts required servers though. https://forum.dcs.world/topic/258735-how-to-export-displays-like-rwr-and-cmsp-set-up-guide-jan-2021/

Is this when you start the game? Or after the monitors have gone to sleep (switch off). My screens go all weird if I let them "sleep" when the game is running, only a restart will fix it. If it is when you start the game, you could try adding a "Displays Table" to your monitor config file. How to do that is explained on the first page of this thread.

Seems strange. Is the tablet always plugged in and acting as a display, or do you plug it in to play DCS? If you plug it in to play DCS, does it ever take over "Main screen" in windows display settings?

Adjusting the original file will break all of the Integrity checks I believe, meaning you won't be able to join any multiplayer server. Doing it with the modified files at least let's you play on servers that DO NOT require pure scripts. It's been a while since I tried doing it the way you suggested so that might have changed. There is an alternative solution. You could place your ddi displays to the left of your main display in windows display settings. You would have to alter your monitor config file for the new positions. There's also the possibility of needing to add a "Displays table" to the config file. Info on that can be found on page 1 of this thread.

The free version of voice attack allows 20 commands (IIRC) to be programmed. It is however only $10 and in my opinion extremely worth it. For the most part, voice attack is an automated key-pressing program, where each command is voice activated. So you would say something like "Set up Viper MFD", and then voice attack would simulate pressing keys in the order you set them. You can add pauses between keys, do modifiers and keys {eg Ctrl+A, Ctrl+Shift+A etc), make the mouse click, hold the mouse button, move the mouse around, and many other things. In order to fully utilise this feature, it is necessary to set keybinds for the things you want VoiceAttack to use. eg A user by the name of @Bailey worked with the developer to create a code that uses DCS BIOS - a script that directly communicates with DCS. That is a little bit more difficult to set up the commands, but the keys are sent directly to DCS, which means while it is running a command, you can do other things, even minimise DCS, and all the button presses still work, and you don't have to set up a keybind for every button in the cockpit, or any at all for that matter, Thanks Bailey! (the odd thing doesn't work, DCS BIOS doesn't usually work for axis commands unfortunately) As Razbam didn't use the normal macro-sequencies.lua file for their start ups, I found this really useful for making my own F-15E start-up sequence. This section looks really long, but it does in fact press every key almost simultaneously. null As MAXsenna mentioned, you can also use it to operate the mouse, to move the kneeboard for example. null It really is a remarkable tool.

I'm not 100% sure on how the graphics card maximum resolution works, but most of them these days are listed as 7680x4320. I have come across several people who have tried to do multiple monitors with larger than the 7680 horizontal resolutions who have had the partial filling of a screen problem. But that might also be a DCS maximum. You could always try putting the right monitor under the centre monitor in Windows display settings, and put your MFDs under the left then reconfigure the monitors. See if that works?

That was an amazing show, very well done to all! Lest we forget.

So I was pondering on what the best solution for this was for a while, a special version that removed a dobber down action, an option select screen (VR people don't like those) etc. When I was testing though, it's not ALL the Steerpoints 21 and above, somewhere in the 100's range, it goes back to being able to auto-sequence again(bug?) Then it occurred to me that if we simply dobber up from the Steerpoint number select instead of down, we can miss out the auto/man selection altogether. Takes a fraction of second longer to enter 1 waypoint, shouldn't be any different at all for 2 or more because we had to go back to the start anyway. So I present my version 2.5.8, which should do the waypoint entry regardless of the Steerpoint numbers used. https://github.com/jonsky752/DCSTheWay/releases/tag/2.5.8 No other changes from 2.5.7