Tom Kazansky

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.

Are you aware that you can give a modifier a new name when creating it i.e. adding it to the list of a module's modifiers? This could be usefull in your case.

Hatte folgenden Übersetzungsfehler bei der F-16C vor ein paar Jahren im englischen Forum gepostet. Den gibt's heute bei meiner aktuellen Stable Version noch immer: Die Bezeichnungen der Key-Bindings für Trimmung Nase runter und Nase hoch sind vertauscht. Nicht schlimm, aber wohl schnell zu lösen, denk ich. Danke. EDIT: Gefunden und in der Übersetzungsdatei gefixt. Sollte mit einem der nächsten Updates sichtbar sein. Danke dir!

I see myself creating an additional pilot in the DCS Logbook, that only flies the F-104. Maybe set to mortal and count the maximum hours those guys stay(ed) alive. Could be a new and challenging experience.

Aerges has made great modules so far. If they manage to create those flaws too, the F-104 could be one of the most interesting cold war jets. I mean this beast is unforgiving to pilot errors like no other in DCS.

Yeah, I got that. And there is no fuel burning engine that will change that without carrying its own oxygen with it like a rocket. As I mentioned before my tests don't contradict what is correctly stated before about t/w ratio. They just show whether the thrust combined with the energy gained before t/w drops below 1, by thin air, is enough to get to 30k feet.

After your reports about the names and the missiles I checked the version of my file again, and have to say, I klicked on the wrong line for uploading. The correct mission is this one P.S.: 1.) It makes sense to set fuel to unlimited for longer training flights with high "health points" at the start, as you mentioned. (With limited fuel I've learned about the afterburner usage of different planes.) 2.) What is odd: I tried my first uploaded mission (05.04.04...) again and although the pilots names were different from the script, the hit counter still worked correctly. Maybe someone with better knowledg of scripting could tell me why. ice 05.04.05 AA Training FA-18 vs. X (LUA-hit-counter works).miz

In VR I use the seat adjustment for AAR, dogfight and landing (some times). I had no problems with finding a good spot for AAR in the F-15E. I started to use a switch of my HOTAS (throttle) for seat adjustment (or vertical camera adjustment for modules that don't have the other) while I was learning the Mirage 2000C.

He said "without conformal fuel tanks". Our F-15E can't go 90° to 30k after take off. I tried. I also expect a Eurofighter can do it, not only because of the thrust to weight ratio but also because of the fact that its engines are optimised for high altitudes.

Good to read. Yeah, those AA missiles weren't meant to be there. A relic of a test, that I didn't remove before uploading. I hope you get your server project running.

And please add bindings for Gear up and Gear down (we only have a toggle and a special 2way switch) EDIT: Please disregard this post! We already have those two bindings but they are like "hidden in translation" in my German version. For all people with the same version, who didn't see it like me: We have: "Landing Gear Lever Toggle..." "Landing Gear Lever UP else DOWN" and we have: "Fahrwerksausfahrhebel - FAHRWERK AUSFAHREN" "Fahrwerksausfahrhebel - FAHRWERK EINFAHREN" So, we have all we need. thanks.

Bitteschön

I've found the source of the code right here in the forums and, after all those years, I want to thank you @Bushmanni for a lot of fun with this method of A2A-training!

@cpt_milkeye LATE EDIT: the attached mission is not the correct mission bc of an upload mistake of mine. I added the correct one with my post on Friday 25th (v 05.04.05) I've been using exactly what you described for a number of years. There is only 1 thing the mission (not the script) adds: As soon as the "health" of a plane reaches zero, it gets vulnerable and you can kill it. For "unlimited" training just set the health to 1000 or more. I like to see a burning bandit at the end of the day, so I like this feature. I did not create the hitcounter script. Just found in in the WWW 2017 and AFAIR I did not change more than variable names, if any. So I don't take credits for the script. I never shared it btw. until totaday. (end of disclaimer ) So here it is: customEventHandler = {}; function customEventHandler:onEvent(event) if (world.event.S_EVENT_HIT == event.id) then local target = "unknown"; if event.target:getCategory() == Object.Category.UNIT then if event.target:getPlayerName() then target = event.target:getPlayerName(); elseif event.target:getName() then target = event.target:getName(); end; end; if (target == "Pilot Red" and trigger.misc.getUserFlag("1") >0) then local hits = trigger.misc.getUserFlag("1") -1; trigger.action.setUserFlag("1", hits); elseif (target == "ice" and trigger.misc.getUserFlag("2") >0) then local hits = trigger.misc.getUserFlag("2") -1; trigger.action.setUserFlag("2", hits); end; end; end; world.addEventHandler(customEventHandler); Here is my mission where I added the output and other little things. To adjust the "Health-Points" of the enemy plane and your own, simply edit the 2nd and 3rd trigger values in the ME. I'm German, so they are called "F1 Gegner-Leben" (="Enemy-Lifes") and "F2 Player-Leben" ("Player-Lifes"). default is: F1 = 30, F2 =10 Because I do my weapons trainings 99% of the time on the Nevada Map (NTTR) I only have the mission for that map. And I use the F/A-18C for both planes in this version of the miz. (see attachment) EDIT: the names of the pilots/units are important for the script. So mine is "ice" and the enemy is called "Pilot Red". EDIT2: I use the stable version of DCS 2.8.7.42718 which (today) is 1 version behind. Hope that doesn't matter. ice 05.04.04 AA Training FA-18 vs. X (LUA-hit-counter works).miz

Lost my own bet to some extent. Tried it with a clean F-15C but needed to reduce fuel to 10% (means almost empty), which allowed only the climb (right after take off) and a save landing right after "falling" down. But: The F-15C just reaches 30k feet within a stall regime and has to use the altitude to recover to a stable flight. So, my conclusions: 1.) Even the T/W ratio of the F-15C is not enough to play starship - certainly not in normal/safe configurations. So the Hornet wil be doing worse by design. 2.) Everything what is posted here to explain why "T/W >1" does not mean you have a VTOL aircraft is correct. (Will repeat this with the Eurofighter/Typhoon as soon as I get my hands on it )

I need to correct my own post: After testing, the Hornet does climb/decent even in auto flaps configuration by increasing/reducing thrust. But just a little bit. (Maybe enough to get oscillation when you are not used to it). The rest of my post still stands: there is not much room in an AAR situation for VVI adjustments by power.