D4n

any indication in this dcs.log what caused the disconnect? I thought server crashed, but seems only I was disconnected. (WW2 Normandy server, I landed on neutral airfield and requested refuel+rearm) https://pastebin.com/tUtDuxwB

Have you finally started working on this, ED?

PLEASE start enforcing SRS on the realistic Syria server! Having 5 Hornets on the team and NONE of them on 264 MHz is plain frustrating

Interesting details, thanks Yaga!

When trimmed for Mach ~1.2, pulling joystick fully back doesn't pull stick back all the way in cockpit unless you then also trim up again. Unrealistic behaviour, or? See trackfile. MiG-29ScannotPullStickAllTheWayBack.trk

OMG WOW, ED also changed MiG-29S blackout without mentioning it in any changelog!! Now, MiG-29S kills you without a warning aswell!!

Yep totally understandable, I PMd you after all "Hello, please close my thread and mark as [invalid] or so [...] Thanks.

Ok apparently there was a similar bug in a previous patch.

Oh ok, CTFRaven on Discord wrote it's a map issue. I'll tell him it's not.

Why do you worry about some "config library" on my PC? xD

I requested that in January already, but it seems ED decided that other things are more important... https://forums.eagle.ru/showthread.php?t=261151

Currently, the problem is that only-basic-A-10C-owner players cannot fly A-10C from airfields where all basic A-10Cs slots are occupied while plenty of A-10C_2 slots are still available and vice versa, tank killer pilots can only fly basic A-10C when all tank killer slots are taken. Please allow mission creators to enable multi-use of A-10C slots. (So that tank killer owners can always fly tank killer since they paid for it)

Many players experience this with servers that have for example 47 out of 50 slots occupied. dcs.log + .trk file attached. 20201004-171311.trk dcs.log.txt

Because (most likely) nobody in DCS flies with a gamepad, as it wouldn't make any sense on earth to fly in DCS with a GAMEPAD (instead of a joystick) That's the good part, DCS already detects my Speedlink Thunderstrike gamepad as a "USB network joystick" instead of detecting it (for example) as "Thrustmaster T.16000 Joystick", so ED already implemented gamepad-detection!!

and a big part of the "everyone else" group are those who are working on making better people out of the cheaters by turning them into the "everyone else"-people :)

the brutal interruption isn't recorded due to some freeze-issue, DCS appears to close itself as it is stuck loading the "close the trackfile-substructure code part and load the main menu" part it seems. (sadly DCS isn't open-source, otherwise I might've been able to log what is going on there maybe? I've had this occur multiple times already, open a long multiplayer trackfile, watch it for 10-20 minutes (do a lot of fast forwarding, but ofc. not to the point where it entirely freezes), and then back to main menu WILL CTD DCS (could possibly also be related to me alt-tabbing to another Windows program right after you click "back to main menu", not sure though, usually Windows is super stable when it comes to using Alt-Tab)

By you, yes, NOT by ED. Are you a software programmer? No. See, ED can fix it until we get their master-programmer to state here that they "can't fix it". It's SO easy, all they have to do is a "is a Gamepad plugged in?"-check, and "IF yes, THEN ignore all gamepad input". EZ as 123...

Meaning, just another example of how unreliable the built-in DCS crash reporter still is :/

Hi, it used to be that unless you were landed at an airfield, returning to spectators mid flight/death-spiral/ditched-in-a-field would score you a death. Currently, players can exploit PvP multiplayer by leaving the slot when they are about to get shot down by another player to avoid it to count as a death (or as a kill for the shooter). This is important for MP servers that export kill/loss pilot statistics data. Why was this system changed to how it is now? To reproduce: run the attached .miz, fly a few seconds, return to spectators, open scoreboard, still says "0" in the "loss" column. Fly-test.miz

dcs.log attached. dcs.log.txt

trackfile attached. JF-17 ACE Ai crashing.trk

updated trackfile attached below. SpitfireRudderTrimNotWorking.trk

Also, I just had a chat with the developer of WhiteKnight, he warned me to not use WK as it can seriously break your windows installation with the tinyest user-mistake. for those TLDR: ED, please fix this once and for all very soon!

negative