Tom Kazansky

I'm not at my PC, so I just ask: is this issue also seen in Channel and Normandy maps?

As a user of the stable version of DCS I just did AAR with the viper and can say there is no deadzone and no lag even/especially on the smallest inputs. I saw very precise and "calm" response. I thought this would be correct as is. Has this behavior really changed with the latest open beta?

I verry much hope there are no dead-zones implemented. Those would be poison for precise flying while AAR.

For me it is certainly not a big problem not to have freeflight missions right from the start, but to be fair, such missions are more than placing a single aircraft in a map. Self designed missions don't have surprises, or "wow-moments". Especialy those with only one aircraft are not vivid. I don't think the OP means that one can't place a plane and some waypoints in ME. Freeflight missions for me are more than that. I obviously can wait some weeks for a new map's missions, but I would appreciate to klick on a freeflight mission for new maps, start on a crowded air base and have some aircraft in the air, that I don't have set there myself knowing exactly what the are going to do. So if the question is: Are freeflight missions critical for a (EA) map? I'd say no. Are they a good way to start with a new map or a new aircraft: It is definitly a YES for me.

Agreed. Are there missions for the Harrier or the Mirage?

Und ich hatte Sorge OT zu führen, wenn ich poste, dass ich mich feu, dass Multicore vor Vulkan kommt, weil ich mir was Vulkan wohl bringen wird schon in drei Monaten kaufen kann (RTX 40X0) aber was (CPU-)Mulicore bringen wird nicht.

Don't know whether it is related but the last time I read about similar problems in a German thread, it was caused by the option "synchronise HOTAS" in the DCS settings.

Ok. That "no" killed the pilot's log on the last death as you might imagine. Maybe some more experienced guys than me can help you fix your log file and revive your pilot. The log file is editable but I'm not an expert.

That's interesting. So that box (or dropdown menu) called "invulnarable" says "yes"?

There is a box in the logbook where you can chose whether the pilot can be killed or not. This is for those who really want to be afraid of dying. In both cases your pilot can be killed in a mission but that box decides whether the log will go on. Never tested it myself though.

+1

+1 the older we get...

thanks. seems to work better than I thought.

Well, it was not your fault. I for one find the title accurate and this topic interesting. But now this thread might be renamed to "What is a pilot ?" And you should start a new one like "How dependent is the frontseater on the backseater?". Sad. edit: this is no offence to those who helped defining what makes a pilot. That's interesting too.

+1

A-7 is not all of the truth. It is the two-seater version of the A-7 imho.

Yes, and think about the Thunderbirds. It does not seem to be worse than a moving stick.

Absolutely this! Deadzones are poison for precise flying like AAR or tight formations anyway.

AFAIK the first versions of those force sensing sticks did not move at all but pilots had a too hard time to get used to it. Long story short: what you see in those videos does not reflect the amount of force that is used, so you should not want to transfer that to your non force sensing stick imho.

As I tried it last time, I used a smartphone with an USB connection to my PC for e few minutes, activated DCS offline mode and that was it. Before changing hardware you can do the same steps to go online and after that to go offline again. That's not a big effort and obviously not expensive. Doesn't have to be your smartphone. So that's a fair deal ED offers us imho.

1. Passiert das nur im Multiplayer oder auch in SP Missionen? 2. Hast du noch andere Eingabegeräte angesteckt? (Lenkrad, Game-Pad,...) 3. Ist der Server auf PAUSE wenn du anfängst? (Blöde Frage, ich weiß, aber das geht tatsächlich.) 4. Passiert das auch wenn du gar keine Eingabegeräte eingesteckt hast außer Maus und Tastatur?

That's unexpected indeed.

So we have two different behaviour with the same procedure. @BIGNEWYThis is not a case of missing public information, imho. Plz, take another look at this, if this is different from OP's track. Here is a very short track with 2.7.11.22211 current stable DCS that shows the bahaviour on my Hornet, that seems to be different from @Swift.'s. I just did the WYPT -> WPDSG -> undesignate procedure 3 times. FA-18C 2.7.11 WPDSG and undesignate Caucasus 01.trk (current stable, no mods)

I can't use your track because I have the current stable version. But just to clarify: When I designate a WYPT with the ATFLIR of the Hornet (with WPDSG) and undesignate, the "TGT" always changes to an unboxed "WYPT" on the HSI top right button. No matter how often I designate the waypoint and undesignate. Shouldn't this be the correct behaviour? Did I miss something here?