D4n

ED mentions "services", those "services" are most likely what they mean by multiplayer-funcitonality, and specifically it's only stated that "due to your geographic location, the Services or some of their features, services, or content may be unavailable to you."... There's no mentioning at all of "server-owners are free to ban anyone they simply don't like, for whatever reasons that may be"... not anyone's "fault", but partial responsibility; Just note that ED includes the multiplayer-functionality in DCS.exe for a reason...: for customers like you and me to enjoy an interactive tactical-communicative experience with aviation-fans across the world... (and later on ofc. also for real military A-10C pilots to train, but afaik the very first intent of "Su-27 Flanker" multiplayer-functionality in the very very beginning of it all, 1995, was for civilian commercial users to enjoy the product, not to train real military operations of real Su-27-operators, or am I wrong? Maybe russian airforce or any airforce also experimentally "trained" something in Su-27 Flanker multiplayer )

Still an issue...

And for who do the server owners mainly put their time and effort? Exactly, for players like you and me, xtacy, who want a realistic tactical-comms experience and not for griefers or teamkillers (which none of us are). Point. And some server owners ofc. also enjoy flying on their own server with and vs. others, and some maybe even (sometimes) enjoy all the coding work they do

No I honestly can't, I get massive headache from the boredom in singleplayer, so I really can't... Then ED better ASAP add a notification to all module-pages in the Eshop that multiplayer is "not guaranteed because of possible partially irrational server-admins"

Yeah and then have how many concurrent players in my server, only 5? Or a whopping 10? Lol no thanks... Wrong, I bought all of my ~600$ worth of modules assuming that every "powerful" DCS server admin has common sense such as mentioned in my post about common gameserver policies on the previous page. Thats also a thing, I did pay... Quite a few times. (Patreon)

Aaaah good that you mention it, I also wasn't sure whether you knew: I was officially switched from red to blue after my own switch-request... Then that frustrating misunderstanding occured. There's no comparable place (PvP server) to move on to, that's a major point that I keep mentioning... I wouldn't be so sure about it not going to be "helping".

Yeah, and as mentioned before, several players of some squadron didn't adhere to those rules and never were prosecuted for it afaik, at least afaik their behavior only changed from "behaving disrespectful" to "not communicating anymore at all"... And it remains a fact that BlueFlag is a monopole dynamic PvP server...

I only used the free account after I created it, to fly Harrier again on red team, iirc after the incident I never used my real account anymore (which would've been for flying on blue on that server that the incident occurred on).

Wrong, only to solely play on my "old" team again, I already explained this to several people, due to a quite frustrating misunderstanding between me and a squadron that I wanted to fly/teamwork with, I was angry that they had suddenly coincidentally stopped flying on that server on that day (first I thought they stopped because they didn't want to fly when I'm flying near them, based on a past experience with some of that squadron) so I wanted to fly my Harrier again. And the "only 1 sideswitch per tour"-rule also contributed to the incident. Already did via forum PM, already explained exactly what happened to him, he read it on april 8th, he didn't reply... I wouldn't call it "my campaign", instead it's "I'm fighting for my case and for the rights of all DCS PvP players".

Exactly! Just another save-setting that it could save in the same config file as my other request here. https://forums.eagle.ru/topic/173889-save-map-settings-in-client-config/?tab=comments#comment-173909

Over 1 year later, still unable. And we can't expect all MP mission-creators to set a channel for AWACS on TF-51s, we honestly need an easy way option of it always working regardless of radio-channel (only as long as the radio isn't destroyed by some ingame-damage ofc.).

We all currently have to do a very involuntary pointing-finger workout to close canopy...... (scrolling mousewheel forward and forward and forward and forward to close it......) Already tried DCS-repair, didn't fix it. Is the keybinding working for anyone? brokenCanopy.trk

Exactly And most players in most DCS squadrons also adhere to those, but there are some DCS squadrons in which quite a few of their members fully ignore those rules, and yet get away with it, what a bizarre world we live in, eh, Nero? Negative, it only shows that I strive for clear rules for everyone, to minimize the risk for others to trap into the same s..t that I trapped into and to counter the risk of abuse of DCS server-admins (abuse-example: "whoa whoa, I don't like what this one player is doing, I don't give a ***** what other players on my server think about it, bam, insta-ban, ha!" out-of-nowhere... ) And you ignoring my mentioning of the super-super basics of ruling (1. warning, 2. kick, 3. ban) and you not giving your opinion on it doesn't help the DCS-community either, Nero...

I'm only banned on ONE server, Dagger... And even if some DCS players would be using more than 1 account to "bypass bans", maybe they have quite good reasons, have you ever considered that?

ETA for fix? It's quite frustrating

aaaand still happening.......... (almost 5 months later.) @RAZBAM_ELMO cutoffSTILLnotWorkinggggg.trk

dcs.logdcs.log

Basic administration policy like the following is usually common sense within the multiplayer-server-hosting communities throughout the entire gaming-industry, but due to my past experience with BlueFlag administration (which was mostly positive btw.), it seems it's for the best of all to make those MP-pilots (those who either never knew or forgot) aware of those again (the following, in fact, is a scaled-down version of actual guidelines of a Forbes-featured gaming-company): - Admins should make an effort to promote a culture of teamwork and communication through their actions on the server and through the creation of written server rules which do likewise. - Admins should encourage a fair, friendly and sportsmanlike atmosphere when mediating interaction between pilots (between "lonewolfs" and squadron-pilots for example). - Server owners and admins should ensure that they and their communities are conducting themselves in a reasonable and respectful manner, server owners and/or admins should be acted on accordingly (by DCS customers or ED staff) for any offensive behaviour in their server, chat/text, kick/ban reason or in bias/discrimination to these points through their actions. - Admins should only kick a player after an initial warning and giving the player sufficient time to comply to the warning, and only expected to ban if the player continued to not comply after a kick. - Admins should never suddenly impose rules that at the time are not in written form in either the mission-description or in the DCS-server's Discord-server (or another social platform). ‏‏‎ ‎ - Servers should make clear how players should conduct themselves while on the server and make clear how players can appeal a ban and via which platform (ED forum or Discord for example).

But Vikhrs hit moving targets... (afaik)

Delete, was a misunderstanding between some DCS players

Did you check trackfile?? Looks more like 120 RPM than 12...

See trackfile, and see rotation-speed in this video: https://youtu.be/fw95kHY3f1Y TarawaRadar.trk

Aaaah thanks it was caused by me having had to renam my folder into "DCSWorld" (no space) for the trim-bug workaround to work (space character is not allowed in .bat files it seemed). (https://forums.eagle.ru/topic/235198-trim-wont-work-if-quotusb-network-joystickquot-controller-is-plugged-out-during-flight/page/3/)

1 minute ~18 seconds currently, first time when launching after booting up Windows 10. After first DCS launch, it appears to only be 1/4 or half that time.

See .trk. Flares FLIR.trk