Tom Kazansky

Let me add this to the confusion;

as title says. I would consider it very useful to be able to toggle cockpit tooltips on/off while in the plane. (Of course, they should stay allowed/restricted by multiplayer server hosts.)

Although I've always been in the Bf-corner of the ring, I found an interesting PDF with information from Switzerland that it wasn't that easy to say Bf or Me is right: https://www.b17museum.ch/newspdf/63.pdf (I'm sorry that I haven't got the time to translate it into English for it's not copy and paste.) It shows that "Me 109"s were sold to Switzerland. edit: seems worth to be mentioned: the documents are from "Messerschmitt A.G., Augsburg" and show the date "Oktober 1938"

https://www.zinnfigur.com/Buecher-Medien/Buecher/Luftfahrt/Deutschland/Prien-Jochen-Stemmer-Gerhard-Bock-Wilfried-Balke-Ulf-Die-Jagdfliegerverbaende-der-deutschen-Luftwaffe-1934-1945-Teil-14-Einsatz-im-Mittelmeer-1-1-bis-15-9-1944.html

Are you aware that the keybind for active pause has moved to the GUI-Layer section of the settings? (Happend many months ago, though)

I did not want to say ED does not trust long-term customers but it would be cool if there was an exception to the 2FA rule for long-term customers with a certain amount of modules. Don't get me wrong, I'm o.k. with ED's decision to protect their business.

Would be cool if we could earn a state of trust.

That would make ED's move completely sensible. Nothing good in the world without some guys making the worst of it. My solution is to buy every module I'm interested in like I used to do it before free trials. Worked for me and ED I guess.

A shot in the dark: Are there clouds and do you fly below or above those? I.e. does this issue also occur without clouds or when flying above them? Certainly clouds should not make cockpits dark at night but I'm just trying to sort out strange new lighting errors. Edit: just read that clouds have already been mentioned several times, so disregard my post.

Is Google Authenticator still saving critical files unencrypted on your smartphone like the Wikipedia site claims?

Good to know. Thank you.

Do the VKB T-Rudders have a damper? I have an eye on the Virpil rudders but they don't have it.

Glad you got it sorted and found the culprit. And thanks for the feedback. Must be really cool to fly the Huey with pedals. Have to check that out some day soon.

If you don't have real rudder pedals and just use the twist axis of your stick it should be on.

In the special options of the UH-1D, do you have the checkbox "rudder trim" on or off?

Happy Birthday DCS World & ED! Having my Lock On and Lock On Flaming Cliffs boxes right here beside me all the years, I only regret missing some of the first years of DCS Word. Thank you for an amazing job, not only dealing with every new hardware/software challenge but also with the gusty wind here in the forums from time to time. You've allways made the best of all this! "Thank you for the last 15 years. You made our dreams come true!" - Eagle Dynamics "dito" - me (Made you a little present for your anniversary by buying a module of yours with 60% discount that I have avoided so far, but I'm sure this will turn out to be a nice present for myself )

thanks @BIGNEWY !!! it had something to do with the AVIRA antivirus. Crazy enough, I only had to disable it for exactly one start of DCS and the error message was gone. Just for testing and against all what I know, I turned antivirus protection on again, and the issue was still gone. well, again you are my Hero of the day BN! Big thanks!

@BIGNEWY hi, this issue still exists, is it perhaps connected to the server maintenance from Aug 28th? Am I the only one reporting such an issue? Could you please give me a clue how to get rid of this? (as said above: it only affects my A-10C, not my A-10C II and not my FC3, F-5E and BS2 that I also bought on Steam in 2016 - before the Starforce-changes in 2017) edit: here is the error message (in German) that shows 23h 59m at each start and that the A-10C is the only module affected:

Guess I'll wait one or two days. Maybe it's just a server issue. After that I'll decide if I link my accounts or open a ticket. What I don't get is, why are my Ka-50 BS2, my FC3 and F-5E are not affected and why does the time period always start at 24h on each start. There must be something going wrong. I can't believe this is the way it is meant to be. Thank you anyway.

Thanks for your help. I never confirmed or re-confirmed my Steam account to the ED shop. It was not necessary for the last 7 years. I bought the A-10C in 2016 and it was transfered to the Standalone DCS in 2017, before we had to link the Steam account to ED for modules like Mirage 2000C and later. BigNewy stated here: "Again, this only affects the M-2000C and future Steam DLC projects. It does NOT affect any existing sales. For example: past and future purchases of A-10C, FC3, F-15C, etc, are not affected by this." btw. my FC3 also works, and was bought before my A-10C.

Today I allways get an Authorization failure ONLY(!) for my 7 year old A-10C (my A-10C II and all other modules work). I have bought it on Steam 2016 and transfered it as this was possible those days. I had never ever connected my Steam account to ED. Wasn't needed. Is this a known issue? edit: I still get this error message on each start of DCS but what is odd: the time the authorization is valid is allways(!) 2d 23h 59m, I mean, If the authorization had failed before (earlier today), shouldn't this countdown show much less hours than allways start from 24h? edit2: I'm using the Stable, Standalone Version od DCS, error occurs at ST nad MT

This. Was discussed here:

Yeah, roger that.

If I understand the OP correctly, the warning occurs when the user tried to add the modifier to the list of the P-51 modifiers. Imho this is not because he used the same modifier for his AH-64. I do that all the time without issues. It seems that the modifier button is already used with another keybind of the P-51 by default. Which is not unusual for a button 4. I often see the first 4 or 5 buttons used by default when I come to a new module.

Or Or this! 100% agreed. Sorry @Trigati Didn't read your valid post carefully enough. Edit: renaming the modifier does not help as long as the button is already used in the plane.