jonsky7

I dont own the Kiowa so I cant say, sorry

So, If I select "Single Screen" as my monitor config, and go into ALT-F1-HUD view, MFDs also show. The F-18s shows 3 MFDs along the bottom, and they take up half the screen. Is this what you want to resize/relocate? ok, I've had a look at the F-18 some more Without any exports in in the monitor.cfg file I get By changing values in DCS World\Mods\Aircraft\FA-18C\Cockpit\Scripts\Multipurpose_Display_Group\AMPCD\Indicator\AMPCD_viewport_cfg.lua 4 sets of numbers, same order as monitor.cfg files {x-pos, y-pos, width, height} It now looks like This does not look the same for all aircraft it seems, or even displays in the same aircraft. I can't see anything obvious to change size and position of the Left and Right MFDs??? Something to look into maybe?

Hello again, Due to the ongoing bug with the CH47 Chinook CDU where the screen goes blank while trying to access certain pages, or the page doesn't change, I have modified how the waypoints are entered. I have removed the ACP entries, so now the LAT/LON coordinates are entered directly into the FLPN/ALTN FPLN pages. I believe this solves an issue that can pop up when two or more ACPs are entered with the same name, i.e. when you create a new list of waypoints in "TheWay". If ACP 1 already existed, and a new ACP called 1 was entered, when the ACP 1 was being entered into the FLPN, the user would have to select which ACP 1 was to be used. There is no way for "TheWay" to see the "new" Waypoint selection screen, so it could get out of sync with DCS and create INPUT ERRORS. This new method also speeds up the creation of a FLPN, as it doesn't have to create the ACPs first. It seems that the underlying CDU systems are working as they should, and it is only the CDU display output that is bugged. So you are still able to create new, and add to existing, ALTN FPLNs. (the display just doesn't follow along when data is entered) The ALTN FPLN summary is still updated, and the route can be shown on the HSD by enabling it. https://github.com/jonsky752/DCSTheWay/releases/tag/v2.5.9 Cheers Jon

WhaaaaaaaAAAAAAAAT!! Still not fixed?

Doesn't seem to be much wrong there, but you can try this one F18_4-screens_v2.lua I have created a displays table, based on your display settings above (4 screens now?) which tells DCS which screens to use and where they are. You CAN NOT run in fullscreen mode and keep DCS open while reading a PDF, that is a Windows "feature" and nothing to do with DCS, just run in windowed mode (fullscreen off) I don't think it makes a difference anyway when running multiple monitors.

What is your current monitor config file? And where are your monitors positioned in windows display settings? And what resolutions are they?

Thank you both, much appreciated! Yes, I had trouble with that too. It can work fine multiple times, then it doesn't. I haven't checked it for a while though, maybe something broke.

Really disappointed that the CDU going blank didn't get fixed for today's update either (23 Jul 25)

Yes, you can not manually enter a resolution in the DCS Launcher, start the game and use the settings menu.

Seems fine to me at the moment

I wouldnt say I took over development exactly. I couldn't have made this from scratch as I don't have the knowledge. However, I have been able to add a couple of aircraft, and make some minor mods and fixes. I have also taken some other people's mods for theWay and combined them into one. I thought they made good additions, after testing and minor modifications, I thought I would share it here. There are some fixes in "my branch" that will not be in the official branch, F16 DED entry being one of them.

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.