Jump to content

jonsky7

Members
  • Posts

    1365
  • Joined

  • Last visited

6 Followers

About jonsky7

  • Birthday 10/07/1976

Personal Information

  • Flight Simulators
    DCS
    FSX
    P3D
  • Location
    UK
  • Interests
    Aviation
  • Occupation
    Licensed Aircraft Engineer

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Really disappointed that the CDU going blank didn't get fixed for today's update either (23 Jul 25)
  2. Yes, you can not manually enter a resolution in the DCS Launcher, start the game and use the settings menu.
  3. I wouldnt say I took over development exactly. I have however took some other people's mods for theWay and combined them. 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.
  4. 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.
  5. 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'.
  6. 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.
  7. 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.
  8. 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.
  9. 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.
  10. 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
  11. 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.
  12. 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)
  13. 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
      • 2
      • Like
×
×
  • Create New...