Lange_666

Update to the problem of long script stop times and dragged windows not staying in place after closing and re-opening TARGET. Updating to Windows (11 Pro) 24H2 from 23H2 seems to have solved the problem.

Using the keyboard, the gear goes up and down. But the same happens in other modules, not only in the F-16. If I keep it pressed (keyboard) it just performs one single action, either up or down depending on the state. To rule out an accidental double press I'm using TARGET's PULSE command to only send one single command when a button is pressed. It's not really necessary to do it that way but that's how I set it up. I just tested with the keyboard instead of the Warthog (no TARGET script running) and even with the keyboard the gear just goes up when I press the keyboard and comes down when I press it again.

I don't have that problem (no tinkering with the lua's here). One press the gear goes up, next press it goes down. Never a double action. Only testen F-16 as i don't have the F-4

It resides under the UI Layer: Names have changed over time... null

Must be something on your end because I don't see that when running your track.

Can't comment on the brand but 32GB is an absolute minimum these days. DCS uses up more than 50GB on the CW Germany map... It will not take long before 64GB will be the minimum.

Which driver version? I'm currently on 576.28

Works for me. What does not work with preset K?

Reset trim before take-off...

It's a RAZBAM module and they are not available right now due to a dispute between RAZBAM and ED.

CW Germany map can easily go over 50GB RAM with not much going on so....

Fill me in because the content is blocked (user tracking across sites and or advertising).

Pixelation like this comes from using DLSS which also creates ghosting. No pixel issue when using MSAA but then there's more shimmering.

If it doesn't work or partially doesn't work a few times it isn't a full proof solution. No need to wait a few days. It's not that i wait until Friday that it will change from working sometimes into always.

Reacted a bit to early I guess. Came from a multiplayer session, ended the game and exited was greeted with a 30 sec black screen on exit. Because of that, restarted DCS, selected a single player mission, loaded it, quit and exit... again that 30 sec black screen. Checked autoexec.cfg, bkg_load_signed_plugins = false still in place...