Jump to content

Recommended Posts

Posted

This happens with both the F4 and F14. If the jester wheel is used in mission. It will be stuck on screen in F1 and sometimes other views too in replay tracks

i7 13700k @5.2ghz, GTX 5090 OC, 128Gig ram 4800mhz DDR5, M2 drive.

Posted

That is because mouse actions and head movement on the UI isnt really captured during replays by DCS. That also leads to the tracks not working as expected, for example the aircraft taking off with a dead engine and not firing any weapons.

You can either control the the Jester Wheel via keybinds (for example the CW/CCW/Enter binds) or recreate your actions while the replay plays by pressing ESC and then mouse clicking on the right actions.

Posted
1 hour ago, Zabuzard said:

That is because mouse actions and head movement on the UI isnt really captured during replays by DCS. That also leads to the tracks not working as expected, for example the aircraft taking off with a dead engine and not firing any weapons.

You can either control the the Jester Wheel via keybinds (for example the CW/CCW/Enter binds) or recreate your actions while the replay plays by pressing ESC and then mouse clicking on the right actions.

I'll try that. I did try and use the L-shift + 1 but that didn't remove it.

i7 13700k @5.2ghz, GTX 5090 OC, 128Gig ram 4800mhz DDR5, M2 drive.

Posted (edited)
2 hours ago, Zabuzard said:

That is because mouse actions and head movement on the UI isnt really captured during replays by DCS. That also leads to the tracks not working as expected, for example the aircraft taking off with a dead engine and not firing any weapons.

You can either control the the Jester Wheel via keybinds (for example the CW/CCW/Enter binds) or recreate your actions while the replay plays by pressing ESC and then mouse clicking on the right actions.

If I press escape. They wheel isn't visible and nothing i bind for jester wheel has any effect in replays

Edited by Gunfreak

i7 13700k @5.2ghz, GTX 5090 OC, 128Gig ram 4800mhz DDR5, M2 drive.

Posted

Ok. Kinda got it working. However. Now it changes me to the back seat( unfinished back seat. And can't get back to the front 

i7 13700k @5.2ghz, GTX 5090 OC, 128Gig ram 4800mhz DDR5, M2 drive.

Posted

In your DCS file folder ''Config'/Camera'' Add this script in your ''1 camera'' or your ''BINO''. Can't remember which one.

F14_JESTER_MENU = 
{
        x = 0;
        y = 0;
        width = 1;
        height = 1;
}

Change the 0's to 1 to enable it or remove it completely when you want the UI to be back, the sad part is you can't remove the static from the radio jester uses but that might be removed from the options such as ''hear aircraft cockpit outside'' or other sound options (i haven't tested this)

(I have not tried with F4)

Win-11, I7-14700K, RTX-4080-S, DDR5 64GB 6400Mhz, Samsung 4K,60hz monitor, VKB-STECS Throttle, Virpil WarBRD base + TM-F-16 grip, TrackIR 5. Mostly F-4, F-14, F-16, F/A-18 and AJS-37. www.youtube.com/@valhallaab8399

Posted

That wont work with the F4 but you could just delete the UI from the folder. In the F4 the entire UI is "local" and fully moddable. It is in Mods/aircraft/F4/UI/JesterWheel

But it wont fix the problem, your UI inputs are not replayed and hence the aircraft is in a wrong state. If you make a coldstart with the UI using mouse or headtracking and then replay that, your aircraft will in the replay fly with engines off and no electric power. Consequently no weapons will drop, nothing works.

Same in the F14. you can hide the UI but if the UI actions arent clicked then the aircraft is in the wrong state.

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...