QuiGon

We need this for the DCS A-10C!!

I have no idea. I haven't touched the stable in many years.

Because most people want to use the new stuff as soon as it becomes available and not wait for several additional weeks (or sometimes even months) before it becomes available to the Stable. Also, OB has been running pretty well in recent years, so it's not really an issue at all. Also, and this might be a surprise (well, not really), OB gets bug fixes SOONER than the Stable, so it's often the case that issues that are still in the Stable have already been fixed in the OB.

I was indeed not aware that they're different things (I've never used either of them), so thank you for pointing this out!

I'm pretty much always using autolase (usually with a 11 sec timer). Never had any issues with it.

Game Mode has been discontinued and removed from the game entirely: https://www.digitalcombatsimulator.com/en/news/changelog/openbeta/2.8.2.35759/

To manually fire the laser in th F-16 you need to press the first trigger detent, but that has nothing to do with Mavericks as the F-16 doesn't have laser guided Mavericks.

I don't think the PVU alignment takes position into account, at least not in the F-15E where this is already implemented. AFAIK it will just meassure the aircrafts movement over ground (as you said) and thus neutralize (or minimize) the drift rate of the INS, regardless of what the actual aircraft position is. See this comment on PVU alignment on the F-15E from KlarSnow who is a former F-15E WSO afaik: AFAIK the CCIP issue has nothing to do with position drift, but with the INS drift rate as a result of wrong velocity meassurements. Hence a position fix will probably not fix the CCIP issue, but I haven't tried that yet tbh. The bug is described throughout this thread, including various tests:

I'm pretty sure GPS in DCS becomes available in 1994, not 1986. A precision velocity update (PVU), which afaik is what the Hornet should do when selecting IFA RDR, would only fix the drift rate of the INS, but not the actual drift. But as you have said yourself: these finer aspect of the Hornet's INS aren't really implemented yet. There's also a nasty side effect of the Hornet's insufficent INS implementation: When flying without GPS the CCIP bomb mode will not work properly. It will accumulate an offset over time (especially in missions where wind is present), causing the CCIP pipper to be completely off target. That happens even when using AGR.

Uhh, nice! That's really good to know!

Yeah, this would be really nice to have!

Guys, napalm bombs and their effects were already announced 3 years ago by ED when the Hornet was released into EA: So yes, they are planned. It's just a matter of time.

I agree, that's indeed something that is missing and should get added.

Sorry, aber mit diesen dürftigen Info-Häppchen wird dir hier kaum jemand helfen können. Du müsstest uns mal im Detail erläutern wie deine gesamte Startup-Prozedur aussieht, bzw. noch besser: mal ein Track Replay davon posten, damit wir wirklich sehen was du da tust und wo du etwas falsch machst.

So in the end there are already enough options to make everyone happy if I understood correctly?

I guess the Argentinians realized that too at the very last moment and thus canceled the invasion just moments after it started On a more serious note: I can imagine they counted a lot on air superiority and air support to make these movements possible

Well, that's part of accurately simulating an aircraft, which not just includes simulating the good parts, but also the bad parts as well. I find the lack of high AOA maneuverability of the Viper also quite annoying, but it's just how the aircraft is. I would never come up with the idea of wanting to have a high AOA maneuverability mode getting implemented for the DCS Viper, even if it would be entirely optional. It's just not a feature of the Viper IRL and thus shouldn't be in DCS, just like magic Mav boresighting isn't.

Hmm, bin mir nicht sicher, ob ich hier etwas missverstehe, aber hast du es auch mal auf der leichtesten Stufe probiert? Das es auf der schwersten Stufe schwergängig ist sollte doch eigentlich nicht überraschen

Da können wir anhand dieser recht dürftigen Beschreibung auch nur wild raten. Da müsstest du uns schon mal genau sagen was du alles machst, bzw. noch besser uns ein kurzes Track Replay von deinem Startup zur Verfügung stellen.

Hot starting should provide you with a fully completed startup, but as Mav boresighting is something that should be done after takeoff, I wasn't sure if this is included in a hotstart. Looks like there is the answer: That would make sense, as it's something that should be done when airborne (which is also why I don't understand the argument that it prolongs the startup and takes away lifetime).

I hope this also gets implemented to the other modules if it turns out, that that exists on them as well IRL.

Absolut, da war ED in der Tat etwas schlampig.

I'm using this one, which can either be used with a power cable attached or wireless with the attached batterie: https://www.amazon.co.uk/Wireless-TrackClip-Reflector（Match-TrackNP-Tracking/dp/B08HS7PNGK/ref=sr_1_5?keywords=trackir+5&qid=1693561584&sr=8-5

Von MUSS habe ich doch gar nichts geschrieben? Denn wie du richtig sagst MUSS man ihn nicht aus lassen, nur warum SOLLTE man ihn an machen wenn er keine Funktion hat? Daher SOLLTE man ihn aus lassen, MUSS es aber nicht (Schalter anzumachen die man nicht braucht oder die gar keine Funktion haben ist keine gute Angewohnheit).

I have to agree with the others in regards to the version numbering. It's quite odd and confusing. Apart from that your work on the manual is awesome!