Jump to content

jonsky7

Members
 View Profile  See their activity

  • Posts

    1095

  • Joined

  • Last visited

 Content Type 

Posts posted by jonsky7

    STREAM DECK PROFILES LIBRARY

    in PC Hardware and Related Software

    Posted

    8 hours ago, Phoenix FR said:

    When i search in dcs interface, i can't find the gear lamp and the gear command. I used the lua you link.

    I search for the MkIX, not the clip wing

     

     

    I think you might have to research and install the DCS-Export Script https://github.com/asherao/DCS-ExportScripts
    and then the DCS Interface plugin for Export Scripts https://github.com/enertial/streamdeck-dcs-interface?tab=readme-ov-file

     

    Sorry I can't be more help.

    STREAM DECK PROFILES LIBRARY

    in PC Hardware and Related Software

    Posted · Edited by jonsky7

    1 hour ago, Phoenix FR said:

    Is someone has a Spitfire and Mosquito profil ?

    It seems that the spitfire script is not completed and has some missing parts (landing gear light,...)

    I don't use streamdeck, but I do use the DCS-Export Script, which is updated for streamdeck if I'm not mistaken.
    https://github.com/asherao/DCS-ExportScripts

    If you are using the DCS-Export script for streamdeck, the Spitfire landing gear lights are
    [49] = "%1d",    -- Gear Lamp Down 
    [48] = "%1d",    -- Gear Lamp Up
     

    SpitfireLFMkIX.lua SpitfireLFMkIXCW.lua

    MosquitoFBMkVI.lua

    Being able to fully trim the aircraft from the navigator's position in SP could help in using the radios.

    in Bugs and Problems

    Posted

    On 3/20/2024 at 5:05 PM, Lau said:

    I understand the logic behind not allowing the navigator to reach the elevator trim, but in SP and since there is no AI pilot, it would be nice to allow players to fully trim the airframe from the navigator's position. I believe this could help SP using the radios while they monitor and adjust the flight controls. It feels weird to be able to use roll, fly the airplane but not be able to use the elevators trim, I forgot to check yaw...

    The navigator should be able to fully trim the aircraft in SP (Roll, Pitch, Yaw).

    Best,

    Lau

    I don't know if you know, but there is a lovely autopilot Mod made by pxllux, can fly straight and level, or hold altitude in a turn.

    https://www.digitalcombatsimulator.com/en/files/3330835/

    • Like 1
    • Thanks 1

    Multi-monitor set-up guide & help (unofficial)

    in Multi-Display Bugs

    Posted

    21 hours ago, Corsac said:

    I'm using a multi-monitor setup as well to export MFCD. It works fine but when the second monitor disconnects (because I switch it to a different input), DCS will compress the whole screen on the first monitor instead of just dropping the second viewport. And when the second monitor gets back, it doesn't expand back the image.

    Is there a way to force DCS to redetect the monitors?

    I haven't had this issue for a long time but what used to work was just mouse clicking the desktop on the second monitor, DCS would automatically resize. 

    However, that wasn't because one of my monitors was disconnecting.

     

    Also, using Alt+Enter to switch to windowed mode, and back again (so Alt+Enter x2) also used to work for me.

    "Thump Thump" while on the ground

    in Bugs and Problems

    Posted · Edited by jonsky7

    4 hours ago, draconus said:

    What about engines? ECS? RWR? How do you live with that?

    Though I have never flown an F15E, I personally can't believe that you would be able to hear that thump over the sounds you have just mentioned, or certainly not as loud as it sounds right now.

    I only really noticed it in the tutorials, where the aircraft is set up for you, and you're sitting there on the ground while going through the training steps.

    Maybe it's my incredibly fabulous bassy headphones making it worse, hence why I asked if I could have the sdef file so I could mod it for me.

    My original comment may have been a tad OTT, apologies 😬 

    • Like 3

    DCS Super Hercules mod by Anubis

    in DCS Modding

    Posted · Edited by jonsky7

    If anyone is interested I've modified the keybindings files to include the CDUs, aka CNI MU

    Hercules ver 6.8.2.zip

     

    Or copy this code into Hercules/Input/Keyboard/default.lua

    Quote

    --- PILOT CDU
    {down = CNI_MU.pilot_CNI_MU_SelectKey_001, value_down = -1, name = _('Pilot CDU LSK 01'), category = _('CDU - Pilot')},
    {down = CNI_MU.pilot_CNI_MU_SelectKey_002, value_down = -1, name = _('Pilot CDU LSK 02'), category = _('CDU - Pilot')},
    {down = CNI_MU.pilot_CNI_MU_SelectKey_003, value_down = -1, name = _('Pilot CDU LSK 03'), category = _('CDU - Pilot')},
    {down = CNI_MU.pilot_CNI_MU_SelectKey_004, value_down = -1, name = _('Pilot CDU LSK 04'), category = _('CDU - Pilot')},
    {down = CNI_MU.pilot_CNI_MU_SelectKey_005, value_down = -1, name = _('Pilot CDU LSK 05'), category = _('CDU - Pilot')},
    {down = CNI_MU.pilot_CNI_MU_SelectKey_006, value_down = -1, name = _('Pilot CDU LSK 06'), category = _('CDU - Pilot')},
    {down = CNI_MU.pilot_CNI_MU_SelectKey_007, value_down = -1, name = _('Pilot CDU LSK 07'), category = _('CDU - Pilot')},
    {down = CNI_MU.pilot_CNI_MU_SelectKey_008, value_down = -1, name = _('Pilot CDU LSK 08'), category = _('CDU - Pilot')},
    {down = CNI_MU.pilot_CNI_MU_SelectKey_009, value_down = -1, name = _('Pilot CDU LSK 09'), category = _('CDU - Pilot')},
    {down = CNI_MU.pilot_CNI_MU_SelectKey_010, value_down = -1, name = _('Pilot CDU LSK 10'), category = _('CDU - Pilot')},
    {down = CNI_MU.pilot_CNI_MU_SelectKey_011, value_down = -1, name = _('Pilot CDU LSK 11'), category = _('CDU - Pilot')},
    {down = CNI_MU.pilot_CNI_MU_SelectKey_012, value_down = -1, name = _('Pilot CDU LSK 12'), category = _('CDU - Pilot')},
    {down = CNI_MU.pilot_CNI_MU_KBD_A, value_down = -1, name = _('Pilot CDU Keyboard A'), category = _('CDU - Pilot')},
    {down = CNI_MU.pilot_CNI_MU_KBD_B, value_down = -1, name = _('Pilot CDU Keyboard B'), category = _('CDU - Pilot')},
    {down = CNI_MU.pilot_CNI_MU_KBD_C, value_down = -1, name = _('Pilot CDU Keyboard C'), category = _('CDU - Pilot')},
    {down = CNI_MU.pilot_CNI_MU_KBD_D, value_down = -1, name = _('Pilot CDU Keyboard D'), category = _('CDU - Pilot')},
    {down = CNI_MU.pilot_CNI_MU_KBD_E, value_down = -1, name = _('Pilot CDU Keyboard E'), category = _('CDU - Pilot')},
    {down = CNI_MU.pilot_CNI_MU_KBD_F, value_down = -1, name = _('Pilot CDU Keyboard F'), category = _('CDU - Pilot')},
    {down = CNI_MU.pilot_CNI_MU_KBD_G, value_down = -1, name = _('Pilot CDU Keyboard G'), category = _('CDU - Pilot')},
    {down = CNI_MU.pilot_CNI_MU_KBD_H, value_down = -1, name = _('Pilot CDU Keyboard H'), category = _('CDU - Pilot')},
    {down = CNI_MU.pilot_CNI_MU_KBD_I, value_down = -1, name = _('Pilot CDU Keyboard I'), category = _('CDU - Pilot')},
    {down = CNI_MU.pilot_CNI_MU_KBD_J, value_down = -1, name = _('Pilot CDU Keyboard J'), category = _('CDU - Pilot')},
    {down = CNI_MU.pilot_CNI_MU_KBD_K, value_down = -1, name = _('Pilot CDU Keyboard K'), category = _('CDU - Pilot')},
    {down = CNI_MU.pilot_CNI_MU_KBD_L, value_down = -1, name = _('Pilot CDU Keyboard L'), category = _('CDU - Pilot')},
    {down = CNI_MU.pilot_CNI_MU_KBD_M, value_down = -1, name = _('Pilot CDU Keyboard M'), category = _('CDU - Pilot')},
    {down = CNI_MU.pilot_CNI_MU_KBD_N, value_down = -1, name = _('Pilot CDU Keyboard N'), category = _('CDU - Pilot')},
    {down = CNI_MU.pilot_CNI_MU_KBD_O, value_down = -1, name = _('Pilot CDU Keyboard O'), category = _('CDU - Pilot')},
    {down = CNI_MU.pilot_CNI_MU_KBD_P, value_down = -1, name = _('Pilot CDU Keyboard P'), category = _('CDU - Pilot')},
    {down = CNI_MU.pilot_CNI_MU_KBD_Q, value_down = -1, name = _('Pilot CDU Keyboard Q'), category = _('CDU - Pilot')},
    {down = CNI_MU.pilot_CNI_MU_KBD_R, value_down = -1, name = _('Pilot CDU Keyboard R'), category = _('CDU - Pilot')},
    {down = CNI_MU.pilot_CNI_MU_KBD_S, value_down = -1, name = _('Pilot CDU Keyboard S'), category = _('CDU - Pilot')},
    {down = CNI_MU.pilot_CNI_MU_KBD_T, value_down = -1, name = _('Pilot CDU Keyboard T'), category = _('CDU - Pilot')},
    {down = CNI_MU.pilot_CNI_MU_KBD_U, value_down = -1, name = _('Pilot CDU Keyboard U'), category = _('CDU - Pilot')},
    {down = CNI_MU.pilot_CNI_MU_KBD_V, value_down = -1, name = _('Pilot CDU Keyboard V'), category = _('CDU - Pilot')},
    {down = CNI_MU.pilot_CNI_MU_KBD_W, value_down = -1, name = _('Pilot CDU Keyboard W'), category = _('CDU - Pilot')},
    {down = CNI_MU.pilot_CNI_MU_KBD_X, value_down = -1, name = _('Pilot CDU Keyboard X'), category = _('CDU - Pilot')},
    {down = CNI_MU.pilot_CNI_MU_KBD_Y, value_down = -1, name = _('Pilot CDU Keyboard Y'), category = _('CDU - Pilot')},
    {down = CNI_MU.pilot_CNI_MU_KBD_Z, value_down = -1, name = _('Pilot CDU Keyboard Z'), category = _('CDU - Pilot')},
    {down = CNI_MU.pilot_CNI_MU_KBD_1, value_down = -1, name = _('Pilot CDU Keyboard 1'), category = _('CDU - Pilot')},
    {down = CNI_MU.pilot_CNI_MU_KBD_2, value_down = -1, name = _('Pilot CDU Keyboard 2'), category = _('CDU - Pilot')},
    {down = CNI_MU.pilot_CNI_MU_KBD_3, value_down = -1, name = _('Pilot CDU Keyboard 3'), category = _('CDU - Pilot')},
    {down = CNI_MU.pilot_CNI_MU_KBD_4, value_down = -1, name = _('Pilot CDU Keyboard 4'), category = _('CDU - Pilot')},
    {down = CNI_MU.pilot_CNI_MU_KBD_5, value_down = -1, name = _('Pilot CDU Keyboard 5'), category = _('CDU - Pilot')},
    {down = CNI_MU.pilot_CNI_MU_KBD_6, value_down = -1, name = _('Pilot CDU Keyboard 6'), category = _('CDU - Pilot')},
    {down = CNI_MU.pilot_CNI_MU_KBD_7, value_down = -1, name = _('Pilot CDU Keyboard 7'), category = _('CDU - Pilot')},
    {down = CNI_MU.pilot_CNI_MU_KBD_8, value_down = -1, name = _('Pilot CDU Keyboard 8'), category = _('CDU - Pilot')},
    {down = CNI_MU.pilot_CNI_MU_KBD_9, value_down = -1, name = _('Pilot CDU Keyboard 9'), category = _('CDU - Pilot')},
    {down = CNI_MU.pilot_CNI_MU_KBD_0, value_down = -1, name = _('Pilot CDU Keyboard 0'), category = _('CDU - Pilot')},
    {down = CNI_MU.pilot_CNI_MU_KBD_dot, value_down = -1, name = _('Pilot CDU Keyboard .'), category = _('CDU - Pilot')},
    {down = CNI_MU.pilot_CNI_MU_KBD_DEL, value_down = -1, name = _('Pilot CDU Kyb DEL'), category = _('CDU - Pilot')},
    {down = CNI_MU.pilot_CNI_MU_KBD_CLR, value_down = -1, name = _('Pilot CDU Kyb CLR'), category = _('CDU - Pilot')},
    {down = CNI_MU.pilot_CNI_MU_KBD_plusmin, value_down = -1, name = _('Pilot CDU Kyb +/-'), category = _('CDU - Pilot')},
    {down = CNI_MU.pilot_CNI_MU_KBD_UNDERSCORE, value_down = -1, name = _('Pilot CDU Kyb _'), category = _('CDU - Pilot')},
    {down = CNI_MU.pilot_CNI_MU_KBD_FORWARDSLASH, value_down = -1, name = _('Pilot CDU Kybd /'), category = _('CDU - Pilot')},
    {down = CNI_MU.pilot_CNI_MU_CommTune, value_down = -1, name = _('Pilot CDU Mode Comm Tune'), category = _('CDU - Pilot')},
    {down = CNI_MU.pilot_CNI_MU_TOLD, value_down = -1, name = _('Pilot CDU Mode TOLD'), category = _('CDU - Pilot')},
    {down = CNI_MU.pilot_CNI_MU_NAV_CTRL, value_down = -1, name = _('Pilot CDU Mode NAV CTRL'), category = _('CDU - Pilot')},
    {down = CNI_MU.pilot_CNI_MU_INDEX, value_down = -1, name = _('Pilot CDU Mode INDEX'), category = _('CDU - Pilot')},
    {down = CNI_MU.pilot_CNI_MU_EXEC, value_down = -1, name = _('Pilot CDU Mode EXEC'), category = _('CDU - Pilot')},
    {down = CNI_MU.PILOT_Network_Sync, value_down = -1, name = _('Pilot CDU Mode Network Sync'), category = _('CDU - Pilot')},


    --- COPILOT CDU
    {down = CNI_MU.copilot_CNI_MU_SelectKey_001, value_down = -1, name = _('Copilot CDU LSK 01'), category = _('CDU - CoPilot')},
    {down = CNI_MU.copilot_CNI_MU_SelectKey_002, value_down = -1, name = _('Copilot CDU LSK 02'), category = _('CDU - CoPilot')},
    {down = CNI_MU.copilot_CNI_MU_SelectKey_003, value_down = -1, name = _('Copilot CDU LSK 03'), category = _('CDU - CoPilot')},
    {down = CNI_MU.copilot_CNI_MU_SelectKey_004, value_down = -1, name = _('Copilot CDU LSK 04'), category = _('CDU - CoPilot')},
    {down = CNI_MU.copilot_CNI_MU_SelectKey_005, value_down = -1, name = _('Copilot CDU LSK 05'), category = _('CDU - CoPilot')},
    {down = CNI_MU.copilot_CNI_MU_SelectKey_006, value_down = -1, name = _('Copilot CDU LSK 06'), category = _('CDU - CoPilot')},
    {down = CNI_MU.copilot_CNI_MU_SelectKey_007, value_down = -1, name = _('Copilot CDU LSK 07'), category = _('CDU - CoPilot')},
    {down = CNI_MU.copilot_CNI_MU_SelectKey_008, value_down = -1, name = _('Copilot CDU LSK 08'), category = _('CDU - CoPilot')},
    {down = CNI_MU.copilot_CNI_MU_SelectKey_009, value_down = -1, name = _('Copilot CDU LSK 09'), category = _('CDU - CoPilot')},
    {down = CNI_MU.copilot_CNI_MU_SelectKey_010, value_down = -1, name = _('Copilot CDU LSK 10'), category = _('CDU - CoPilot')},
    {down = CNI_MU.copilot_CNI_MU_SelectKey_011, value_down = -1, name = _('Copilot CDU LSK 11'), category = _('CDU - CoPilot')},
    {down = CNI_MU.copilot_CNI_MU_SelectKey_012, value_down = -1, name = _('Copilot CDU LSK 12'), category = _('CDU - CoPilot')},
    {down = CNI_MU.copilot_CNI_MU_KBD_A, value_down = -1, name = _('Copilot CDU Keyboard A'), category = _('CDU - CoPilot')},
    {down = CNI_MU.copilot_CNI_MU_KBD_B, value_down = -1, name = _('Copilot CDU Keyboard B'), category = _('CDU - CoPilot')},
    {down = CNI_MU.copilot_CNI_MU_KBD_C, value_down = -1, name = _('Copilot CDU Keyboard C'), category = _('CDU - CoPilot')},
    {down = CNI_MU.copilot_CNI_MU_KBD_D, value_down = -1, name = _('Copilot CDU Keyboard D'), category = _('CDU - CoPilot')},
    {down = CNI_MU.copilot_CNI_MU_KBD_E, value_down = -1, name = _('Copilot CDU Keyboard E'), category = _('CDU - CoPilot')},
    {down = CNI_MU.copilot_CNI_MU_KBD_F, value_down = -1, name = _('Copilot CDU Keyboard F'), category = _('CDU - CoPilot')},
    {down = CNI_MU.copilot_CNI_MU_KBD_G, value_down = -1, name = _('Copilot CDU Keyboard G'), category = _('CDU - CoPilot')},
    {down = CNI_MU.copilot_CNI_MU_KBD_H, value_down = -1, name = _('Copilot CDU Keyboard H'), category = _('CDU - CoPilot')},
    {down = CNI_MU.copilot_CNI_MU_KBD_I, value_down = -1, name = _('Copilot CDU Keyboard I'), category = _('CDU - CoPilot')},
    {down = CNI_MU.copilot_CNI_MU_KBD_J, value_down = -1, name = _('Copilot CDU Keyboard J'), category = _('CDU - CoPilot')},
    {down = CNI_MU.copilot_CNI_MU_KBD_K, value_down = -1, name = _('Copilot CDU Keyboard K'), category = _('CDU - CoPilot')},
    {down = CNI_MU.copilot_CNI_MU_KBD_L, value_down = -1, name = _('Copilot CDU Keyboard L'), category = _('CDU - CoPilot')},
    {down = CNI_MU.copilot_CNI_MU_KBD_M, value_down = -1, name = _('Copilot CDU Keyboard M'), category = _('CDU - CoPilot')},
    {down = CNI_MU.copilot_CNI_MU_KBD_N, value_down = -1, name = _('Copilot CDU Keyboard N'), category = _('CDU - CoPilot')},
    {down = CNI_MU.copilot_CNI_MU_KBD_O, value_down = -1, name = _('Copilot CDU Keyboard O'), category = _('CDU - CoPilot')},
    {down = CNI_MU.copilot_CNI_MU_KBD_P, value_down = -1, name = _('Copilot CDU Keyboard P'), category = _('CDU - CoPilot')},
    {down = CNI_MU.copilot_CNI_MU_KBD_Q, value_down = -1, name = _('Copilot CDU Keyboard Q'), category = _('CDU - CoPilot')},
    {down = CNI_MU.copilot_CNI_MU_KBD_R, value_down = -1, name = _('Copilot CDU Keyboard R'), category = _('CDU - CoPilot')},
    {down = CNI_MU.copilot_CNI_MU_KBD_S, value_down = -1, name = _('Copilot CDU Keyboard S'), category = _('CDU - CoPilot')},
    {down = CNI_MU.copilot_CNI_MU_KBD_T, value_down = -1, name = _('Copilot CDU Keyboard T'), category = _('CDU - CoPilot')},
    {down = CNI_MU.copilot_CNI_MU_KBD_U, value_down = -1, name = _('Copilot CDU Keyboard U'), category = _('CDU - CoPilot')},
    {down = CNI_MU.copilot_CNI_MU_KBD_V, value_down = -1, name = _('Copilot CDU Keyboard V'), category = _('CDU - CoPilot')},
    {down = CNI_MU.copilot_CNI_MU_KBD_W, value_down = -1, name = _('Copilot CDU Keyboard W'), category = _('CDU - CoPilot')},
    {down = CNI_MU.copilot_CNI_MU_KBD_X, value_down = -1, name = _('Copilot CDU Keyboard X'), category = _('CDU - CoPilot')},
    {down = CNI_MU.copilot_CNI_MU_KBD_Y, value_down = -1, name = _('Copilot CDU Keyboard Y'), category = _('CDU - CoPilot')},
    {down = CNI_MU.copilot_CNI_MU_KBD_Z, value_down = -1, name = _('Copilot CDU Keyboard Z'), category = _('CDU - CoPilot')},
    {down = CNI_MU.copilot_CNI_MU_KBD_1, value_down = -1, name = _('Copilot CDU Keyboard 1'), category = _('CDU - CoPilot')},
    {down = CNI_MU.copilot_CNI_MU_KBD_2, value_down = -1, name = _('Copilot CDU Keyboard 2'), category = _('CDU - CoPilot')},
    {down = CNI_MU.copilot_CNI_MU_KBD_3, value_down = -1, name = _('Copilot CDU Keyboard 3'), category = _('CDU - CoPilot')},
    {down = CNI_MU.copilot_CNI_MU_KBD_4, value_down = -1, name = _('Copilot CDU Keyboard 4'), category = _('CDU - CoPilot')},
    {down = CNI_MU.copilot_CNI_MU_KBD_5, value_down = -1, name = _('Copilot CDU Keyboard 5'), category = _('CDU - CoPilot')},
    {down = CNI_MU.copilot_CNI_MU_KBD_6, value_down = -1, name = _('Copilot CDU Keyboard 6'), category = _('CDU - CoPilot')},
    {down = CNI_MU.copilot_CNI_MU_KBD_7, value_down = -1, name = _('Copilot CDU Keyboard 7'), category = _('CDU - CoPilot')},
    {down = CNI_MU.copilot_CNI_MU_KBD_8, value_down = -1, name = _('Copilot CDU Keyboard 8'), category = _('CDU - CoPilot')},
    {down = CNI_MU.copilot_CNI_MU_KBD_9, value_down = -1, name = _('Copilot CDU Keyboard 9'), category = _('CDU - CoPilot')},
    {down = CNI_MU.copilot_CNI_MU_KBD_0, value_down = -1, name = _('Copilot CDU Keyboard 0'), category = _('CDU - CoPilot')},
    {down = CNI_MU.copilot_CNI_MU_KBD_dot, value_down = -1, name = _('Copilot CDU Keyboard .'), category = _('CDU - CoPilot')},
    {down = CNI_MU.copilot_CNI_MU_KBD_DEL, value_down = -1, name = _('Copilot CDU Kyb DEL'), category = _('CDU - CoPilot')},
    {down = CNI_MU.copilot_CNI_MU_KBD_CLR, value_down = -1, name = _('Copilot CDU Kyb CLR'), category = _('CDU - CoPilot')},
    {down = CNI_MU.copilot_CNI_MU_KBD_plusmin, value_down = -1, name = _('Copilot CDU Kyb +/-'), category = _('CDU - CoPilot')},
    {down = CNI_MU.copilot_CNI_MU_KBD_UNDERSCORE, value_down = -1, name = _('Copilot CDU Kyb _'), category = _('CDU - CoPilot')},
    {down = CNI_MU.copilot_CNI_MU_KBD_FORWARDSLASH, value_down = -1, name = _('Copilot CDU Kyb /'), category = _('CDU - CoPilot')},
    {down = CNI_MU.copilot_CNI_MU_CommTune, value_down = -1, name = _('Copilot CDU Mode Comm Tune'), category = _('CDU - CoPilot')},
    {down = CNI_MU.copilot_CNI_MU_TOLD, value_down = -1, name = _('Copilot CDU Mode TOLD'), category = _('CDU - CoPilot')},
    {down = CNI_MU.copilot_CNI_MU_NAV_CTRL, value_down = -1, name = _('Copilot CDU Mode NAV CTRL'), category = _('CDU - CoPilot')},
    {down = CNI_MU.copilot_CNI_MU_INDEX, value_down = -1, name = _('Copilot CDU Mode INDEX'), category = _('CDU - CoPilot')},
    {down = CNI_MU.copilot_CNI_MU_EXEC, value_down = -1, name = _('Copilot CDU Mode EXEC'), category = _('CDU - CoPilot')},
    {down = CNI_MU.COPILOT_Network_Sync, value_down = -1, name = _('Copilot CDU Mode Network Sync'), category = _('CDU - CoPilot')},

     

    • Like 2

    Scripted "cockpit interaction" problem

    in Bugs and Problems

    Posted · Edited by jonsky7

    This post is quite old but I thought I would share the solution.

    The action required is

    "Start playing actor" and the value should be 2,

    this sets DCS into the navigator seat, although you will still be in the pilot seat. This is only required for switches not accessible from the pilot seat.

    Be sure to add "stop playing actor" at the end of the actions.

    While the "actor" is doing their thing, pilot only switches will be locked out, so best not make the actor do stuff for too long.

    [How to] Multi monitor MFCD display export set-up guide - July 2023 (updated)

    in Multi-Display Bugs

    Posted

    4 hours ago, NoLegalMoves said:

    Thanks, i’ll give it a go this weekend (about pilot seat height). The stick, i m afraid is a more, well sticky issue.. The buttons won’t even show as depressed in the windows controller settings whereas I have the main axis working.. I wrote a ticket to vkb but bizarrely they’ve ignored it so far (3 days). I think I’ll take it appart this weekend and clean the contacts as I’ve seen it suggested elsewhere. There’s always something with this many pieces of hardware, i guess.

     

     

    VKB, you didn't say which one so if it's a gunfighter, it could be it has just lost its calibration settings which could be fixed through their software.

    It could be the joystick to base contacts, or just the clamp has become loose.

    Or the wire inside that goes from the board to the base connection has come loose at the board. The wires used are very thin and I've had to replace 2 of mine. Though I think it was the x axis ones on mine. 

    Transfer steerpoints from the F10 map into the aircraft - DCS: The Way

    in DCS Modding

    Posted · Edited by jonsky7

    3 hours ago, Luthor033 said:

    VR issue

    Ciao.  Super mod that help us a lot.   Thank you.

    It will help VR users a lot to have a joystick key mapping.   

    At the moment, when I make a waypoint on the map I need to take off my VR and use my mouse on the monitor or on the keyboard to find the right buttons to memorize and transfer in the CDU.   

    Instead If you give us a joystick key mapping, we will do everything inside the VR. 

    Do you have in program to realize it ? 

     

    You could probably use VoiceAttack to do this if there is nothing else.

    Voice attack usually works by performing keypresses and other things when you say a command, but you can also program voice attack to do a command when you press a key, or a joystick button.

    So when you press a joystick button you can have voice attack press a key, or multiple keys like LCTRL+A for example.

    You can also program voice attack to move the mouse pointer to a specific point on your monitor. As long as "TheWay" opens in the same place each time you run it, that should be good.

    You can also program voice attack to move the mouse and then press a mouse button.

    The free version of Voice Attack let's you have 20 seperate commands IIRC, and each command can do multiple steps.

    Eg

    Move the mouse pointer 

    Press Left mouse button

    Move the mouse pointer

    Press right mouse button

    Play a sound.

     

    Just an idea 💡 

    • Like 2

    [How to] Multi monitor MFCD display export set-up guide - July 2023 (updated)

    in Multi-Display Bugs

    Posted

    5 hours ago, NoLegalMoves said:

    So not to appear ungrateful or anything BUT…

    I can’t help myself, being a perfectionnist…

    My triple 4k +3 MFDs lua file works great except for distortion on the side screens (left screen appears leaning left, right screen leaning right).. On the ground or leveled flights it looks like the nose is pointing up if i look at the sides.

    Is there a way to correct for that? I tried to play with viewdx viewdy, but doesn’t not seem it’s the right lever..

    Also I tried to place all my TVs into a single giant viewport (center) but when I do that i keep losing the right screen (which is what i was struggling with initially). Looks like this might be a DCS bug?

    On a different topic, my stick suddently stopped working..  Hugh! 

     

     

    I haven't tried a setup like yours so in all honesty, I just don't know. 

    I did a quick search to see if there was a missing "rotate dx" or something but nothing looked particularly obvious.

    Only other thing I could suggest is altering your "head position". A simple test could be achieved by using the seat height adjustment in the jet.

    If it looks like that would improve the situation there is a way to "make yourself taller/shorter and save that as the default view.

    Also, The standard default view set by DCS is slightly downward looking, you can check this by zooming all the way in, you will see that it zooms into the instrument panel, and not through the centre of the HUD. For single screen this is understandable as it will include some instruments. So changing the default to be straight ahead might give you the result you're after.

    I think you have to disable track ir, if used, press numpad 5 to select centre view, then use the numpad keys to alter view, and then RCTRL+NUMPAD 0 saves the view.

     

    As for your stick not working. DCS uses specific hardware IDs to assign buttons, and if you unplug usb cables and plug them back in, the hardware ID can change as thus lose the bindings etc.

    You can load them back in through the controls options screen. Select the column for your stick, then press the load profile button. Navigate to aircraft folder in your saved games, config, input, and load the profile for the correct device.

     

     

    [How to] Multi monitor MFCD display export set-up guide - July 2023 (updated)

    in Multi-Display Bugs

    Posted

    39 minutes ago, Red_Pilot said:

    Does anyone know if there is a "MFCD" for MiG 21? Can we see radar screen in the "MPCD" area? 

     

    Yes, it should export to either "RP22" or "RIGHT_MFCD"

     

    So if you make an config entry called RP22, it will go there, otherwise you can have it export to RIGHT_MFCD.

    Looks a bit dark though, I don't know how to turn it on, just downloaded the trial version to check it.

    • Thanks 1

    [How to] Multi monitor MFCD display export set-up guide - July 2023 (updated)

    in Multi-Display Bugs

    Posted

    29 minutes ago, NoLegalMoves said:

    Hey Jonsky,

    Yep that was my mistake, just figured it out before your reply!

    I configured resolution to 13088 instead of 12288 and boom! IT WORKS!!!

    wow.. i almost feel as emotional as when I finished my first marathon! lol

    Downside is a massive framerate hit, but should be able to fix adjusting settings

    YAAAAAY!!!!

    Hey Jonsky thanks a lot for your time. means a lot. Very generous of you.

     

    Awesome!! Glad you got it working in the end! 👍

    [How to] Multi monitor MFCD display export set-up guide - July 2023 (updated)

    in Multi-Display Bugs

    Posted · Edited by jonsky7

    24 minutes ago, Darkdiz said:

    So idiot-boy here went in and changed the resolution on his monitors, now DCS starts up with the settings icon unreachable (off-screen). How do I reset this? Pretty sure its a lua file somewhere

    You can delete the file:-

    Saved games > DCS > Config > options.lua

    or around line 65 is the graphics options

    2 hours ago, NoLegalMoves said:

    Hey Jonsky7,

    Big thanks for all the help.

    I used your 4k file and had to make a minor correction. I think the x coordinates for center and right are off. But aside from that BIG thanks. it's good to start clean on how it should be configured!!

    I had to do a couple of edits on my end because bizarrely, my system insisted on a 4096x2160 resolution for the main screens. When going back to 3840x2160, it failed to scale properly and I was left with big black bars on each side of the main screen even after reboot.

    I also changed back the position of the MFCDs to the top right corner to optimize total rendered pixels.

    There were some major improvements with your file from what I've experienced before

    -FOV is corrected

    -HUD is sharp

    -Cockpit view is centered

    -Frame rate is greatly improved (i really don't get that one, but will take the win)

    On the negative, the MFCDs are not working. (they just show windows desktop view). I'm starting to think it might be a hardware issue.. cables?? 

    Again, thanks so much for all the help. I'm going to continue experimenting this week end.. If anything, these improvements raised my spirit and motivation a bit.

    Let me know if you have other ideas.

    4K_JF.lua 1014 B · 0 downloads

    Hmmm, in DCS settings have you set the resolution to 13088x2160?

    4096+4096+4096+800

    • Like 1

    [How to] Multi monitor MFCD display export set-up guide - July 2023 (updated)

    in Multi-Display Bugs

    Posted · Edited by jonsky7

    Edit, Just looked at both your files again, you were missing the first _ in the first line
    _ = function(p) return p; end;

    I have no idea how important that is mind.

     

    And on your later post with pictures, your CFG name doesn't match the one you have selected in DCS settings.

     

    1. You have a very large display, but you have selected "1 screen" effectively

    I'm not super knowledgeable on how to set up a 3 screen properly but you probably want something like the below. That should fix the super zoomed in view.
    That is setting up 3 views, instead of 1 view stretched out over 3 displays.

    For 2560x1440 resolution x3, setting a resolution of 7680x2040 in the DCS setting page

    2K.lua

    The viewDx and viewDy, are offsets to looking straight ahead. 
    You'll notice the Left view has a viewDx of -1, and the right is 1

    You may need to adjust these, I'm not sure what measurement they use (probably radians or something), so it will take a bit of fine tuning, or a bit more research into multiple display cockpit view.
    Needless to say that a more negative value of "viewDx" moves the camera left, and a more positive one moves it right.

     

    2. The blurriness of the HUD in your picture simply looks like the HUD brightness is set too high, if you use the knob on the UFC, that should fix that problem.

     

    3. I've looked to see what the Max Resolution actually means, most answers point to the amount of VRAM the GPU has that limits the amount of Pixels it can generate. When I've seen other people have an issue, part of the screen goes black, or has no output. So if you have the menu displaying on your MFD monitors, I agree that you are probably not hitting a limit. As far as I can tell, the Menu screen is rendering as 3D application, judging by GPU usage and power draw when sitting in the menu screen. 

    I'm not sure why they are displaying a plain blue screen though.
     

     

    4. You can absolutely try dragging you MFD monitors to under your "TVs" in windows and reconfigure the setup file. ( I can see you've already done that )

     

    5. Is your monitor "3" set as the Main Display in windows?

     

    For 4K Tv's 

    11520x2760

    4K.lua

    [How to] Multi monitor MFCD display export set-up guide - July 2023 (updated)

    in Multi-Display Bugs

    Posted

    12 hours ago, NoLegalMoves said:

    Hey, I'm a noob here and trying to follow all the advice but after 3 weeks of trying everything i was told i'm starting to think what i m trying to do is not possible. Any help would be a godsend...

    My setup is 3 - 4k TVs

    I also have 3 independent monitors for the MFCDs

    I don't understand what i m doing wrong but MFCDs are not showing up on my screens, the main view is ex-centered, the field of view seems zoomed in too far (pictured is max wide angle 140 degrees). And yes, I tried Helios, with and without Nvidia screen spanning  and every combination i could think of.

    Here is my predicament (see attached files)

    thumbnail_IMG_8340.jpg

    thumbnail_IMG_8341.jpg

    DCS settings.jpg

    JF_Manual_Monitor_Config.lua 607 B · 0 downloads

     


     

    Are you using Helios?

    The default names for those MFD exports are

    LEFT_MFCD

    CENTER_MFCD

    RIGHT_MFCD

    I think I've heard Helios changes the names sometimes. If you are NOT using Helios, use the names as above.

     

     

    Otherwise. you may be exceeding the limits of your graphics card in 3D applications, are you running your TV's at 4K? More than 1 graphics card?

    The Max resolution of most graphics cards is
    7680x4320

     

    The Siren Tour - User made mission

    in Missions and Campaigns

    Posted · Edited by jonsky7

    Hi,

    Just thought I'd share this mission that I made. It is a FULL mission, from cold and dark, a flight over the channel into France, and back again to landing. It takes about 1 to 1.5 hours to complete. You will need "The Channel" map, and WW2 Assets pack.

    Whilst doing some reading on the great Wooden Wonder, I came across this term "Siren Tour". Although I only managed to stumble across a few mentions of the term, it peaked my interest.

    An introduction to the Siren Tours is provided at the start of the mission, but as I understand it, they were raids of small bomber groups, going in with the main purpose of setting off air raid sirens and all that goes with it like heading to air raid shelters etc.

     

    I had the idea of maybe making a campaign, but creating just this one mission, with all the foibles of the DCS Ai and mission making, took a great deal of time. There is a scripted navigator who flicks switches and tunes the navigation radio. I did look into Ai voices etc, and some are used, but for the most part they are quite there yet with no way to infer emergency or panic etc.

     

    Available in user files section

    https://www.digitalcombatsimulator.com/en/files/3335873/

     

    links to references of the term "Siren Tour"

    https://www.rafcommands.com/archive/09862.php

    https://www.rafcommands.com/archive/11386.php

    https://www.aviationclassics.co.uk/issue-10-de-havilland-mosquito/

     

    • Thanks 1

    [How to] Export displays like RWR and CMSP set-up guide - Jan 2021

    in Multi-Display Bugs

    Posted

    On 2/2/2024 at 2:55 PM, Purzel said:

    *kicked again*

    What is the viewport for the F/A-18C?
    I've got one little 480 x 480px monitor plugged into my GPU (it works, it shows the desktop), is there way to connect it and get it run without that helios stuff?

    Somewhere I've found this code:  

      F18_RWR =
{
    x = 3421;
    y = 305;
    width = 480;
    height = 480;
}

    Any ideas what could be wrong?
    Or how I could connect it via USB

    Thx!

    RWR_Viewport.jpg

     

    The RWR is not exportable by default in any aircraft, which means it requires modification of game files. These files are in the cockpit scripts portion of the aircraft game files and are subject to checks for modifications by the "Integrity Check". 

    If the server you are playing on has the option "Require Pure Scripts = Yes", you will be kicked for applying said modification.

    So whether that game file is modified by Helios, or manually, you will be kicked from servers requiring "Pure" scripts.

    Also, if the server has this option set to No, you will still see a red shield (Intergity check fail) when you leave the server and go back to the server list, or if you play a bit of single player and then go to the multiplayer server list. The workaround is to restart DCS.

    A few posts up you will find a list of the default exportable displays. Exporting any of these does not effect the integrity check and should allow to play on "pure scripts only" servers without being kicked.

     

    The solution is to either not export the RWR and play on any server you like, or do export it and find a server you like that does not require pure scripts.

    and

    beg ED to make the RWR exportable by default.

    • Like 1

    [How to] Multi monitor MFCD display export set-up guide - July 2023 (updated)

    in Multi-Display Bugs

    Posted

    17 hours ago, FastNeatAverage said:

    @jonsky7Please forgive the repeat (assuming it's been asked), but I can't find the topic in this thread anywhere. After applying the kneeboard relocation fix quite some time ago I'm now failing IC check in MP servers. It appears to be associated with the mod of the device-init.lua

    Is there a work around for this or do you have to choose between seeing your kneeboards and playing on an MP server with IC check enabled?

     

    After having a brief look through the multiplayer server list, it looks like a few more servers have the option for "Require pure scripts" set to yes lately.

    Unfortunately when a server has this option set to yes, there is very little in the way of allowed modifications, if any at all.

    You should be able to still play on any multiplayer server where this option is set to "no", you may get an IC failed notification when you leave the servers, if this is still the case you need to restart DCS to reset the IC check.

    • Like 1

    [How to] Multi monitor MFCD display export set-up guide - July 2023 (updated)

    in Multi-Display Bugs

    Posted · Edited by jonsky7

    On 12/21/2023 at 1:42 PM, Red_Pilot said:

    Hello! After installing the second monitor, I do not see the control indicator in FC aircraft (MiG29, Su 27 and 33) and unfortunately I cannot find where (init_file?) the files for the indicator are located. Maybe someone knows the location of these files for these aircraft?

    FC3 has a different coding structure. Most of the files are locked away in encrypted files. 

    There's an "aircrafts/common" folder somewhere. It may be in there but I'm not at my computer to check. 

    • Like 1
    • Thanks 1

    Autopilot doesn’t work (probably no bug)

    in Bugs and Problems

    Posted

    26 minutes ago, BaronVonVaderham said:

    How do I check for jitter? And if there, how to eliminate that?

    i use a winwing f-16ex stick

    You could open the controls indicator, which IIRC is RCtrl and Enter.

    This brings up at small display in lower left corner showing control inputs. If it's moving about with no stick input, then your joystick might have a bit of jitter.

    • Like 1
×
×
  • Create New...