Flappie

I strongly agree, for I've been reporting previous issues he made me aware of. But I don't work at ED, I can't "hire" him.

For you, it is. I studied programming a long time ago, but I'm too lazy. Thanks a bunch, I'll check and report.

Superb track! Thank you. I'll report the issue.

@T.Power Please provide a DCS track.

Thank you very much, @Pju. You helped me find the source of a big multiplayer hassle.

I've just found a way to reproduce this issue on purpose: when closing the Chat window using the "Chat show/hide" while the Chat window is open and active (a message can be typed in), the Escape key cannot be called anymore. The user must then show the Chat window again so the Escape key works again. I'll report this.

They have no purpose in the General category, indeed. Simply unbind them and the warnings will be gone. I'll report these.

I have no idea of to test this. Can you please provide a simple .miz file with your script?

I've just tried in a simple SP mission with 100 ground units. I didn't observe any stutter (Ryzen 3700, 64 GB of RAM, 1080 Ti). Can you please try this track and tell me if you reproduce the issue? If not, please attach your own tracks (preferably short ones). target search OK.trk

Gents, can you please try this? If you already have a file named autoexec.cfg in "Saved Games/DCS/Config", edit it and add this line: no_device_hotplug = true And if you don't have such a file, here is it. Does it change anything for you? autoexec.cfg

I cannot reproduce your issue, even when I use the launcher. Are you sure the setting is not enforced by your mission file?

Then you are certainly affected by this bug: It's reported internally.

I've made this request to devs a few days ago.

There's an error in your autoexec.cfg file. load error Config/main.cfg:[string "C:\Users\kston\Saved Games\DCS.openbeta\Config/autoexec.cfg"]:3: '<name>' expected near '\' Rename it to "autoexec.cfg.bak" and see if it helps.

Thanks for the heads up. Issue reported.

I managed to speed it up: Edit .\DCS World\Mods\aircraft\F-5E 2024\Cockpit\Scripts\clickabledata.lua Spot line 323 Replace 0.0125 by 0.0250 Save and enjoy. Before I ask devs to change this value, I'd like to make sure 0.0250 is satisfying. Can you gents try it and report back, please?

Work in progress. "negative drag of payload" error messages are in the process of being fixed, but there's a lot of them.

Hi, the Event Viewer won't say much. It's better to open your latest crash .zip file (you'll find it in your Saved Games/DCS.../Logs folder) and edit the dcs.log file it contains. Here's a troubleshooting guide. Please attach the whole zip here, we'll see if we can help you.

Apologies accepted. I was answering another user who said it had never been fixed. Thank you both for the screenshots. They were added to the internal report, and devs are now well aware that the issue has returned. I won't be able to help a lot more on this issue since my CPU is too old to be affected (Ryzen 3700), but our fellow affected tester will be able to test potential fixes, hopefully soon enough.

This was fixed at some point. TALD OK.trk

A track would be welcome. @[DE] T-Bone Since you've just changed your GPU, ensure your former GPU driver is completely uninstalled. You can use DDU.

Yes, "steps" are tiny for both keyboard and mouse (and I guess for other devices too).

A fellow tester who had been experiencing this issue before October tells me the issue is back for him too. I'll report the return of this issue.

When you spawn in, the knob is at the end of its course (to the right), which is why LAtl + LShift + V does not work. Press and hold LAlt + LShift +X first, then you will see LAlt + LShift +V working as well. It's just very sloooooow. I'll report this.

I think you're the guy getting a little out of control here. I said "it HAD been fixed". English may not be my first language, yet I remember pretty well that "had" + "been" + "fixed" equals "was fixed in the past, may have changed later on". Please correct me if I'm wrong. One more thing: when I take time to answer a bugs and problems thread, it means I care. You're obviously barking up the wrong tree.