Ramsay

IIRC (after the 1st launch) at times the 2nd LMav may indicate it's operational (HUD and MFD show a scanning X), but won't detect a laser spot until the 2nd LMav is caged/uncaged again. It seems like a bug were the cockpit/HUD can retain the "ready" status of the 1st LMav fired, while the 2nd LMav is still caged (cycling the cage/uncage button avoids this). https://forum.dcs.world/topic/332066-various-struggles-with-mavs-and-lmav/?do=findComment&comment=5274529

Can't reproduce your problem. Tested Caucasus map, Open Beta 2.9.2.49940 Short track attached to check on your own PC, if you still have issues, please attach a short track and dcs.log file. F-15E NavFLIR Test, Senaki.trk

The "general" date for GPS to function in DCS i.e. F/A-18C, JDAMs, etc. is March 24th 1994, IIRC the "official" date when the constellation of GPS satellites was completed. An exception to this the F-15E which didn't receive it's EGI until 1998.

Targets illuminated with the generic FC3 1113 laser code are "marked" with a diamond in the A-10A's HUD. AFAIK the A-10A's Pave Penny is enabled by default so players can quickly "spot" a FC3 compatible JTAC's lased target(s) and employ their weapons, etc. The DCS A-10A cannot carry/drop GBU's and IRL 1113 is invalid for GBU-12, etc.

Negative, RWY 33 with 0 wind is consistent with the original (DCS 1.2 and prior) ATC behaviour. The erroneous ATC behaviour (effects most maps/airports) is for 1-2 m/s head/tail winds and introduced with the initial release of DCS 2.5 (2018). https://forum.dcs.world/topic/172761-open-beta-25-kobuleti-ndbs-without-function/?do=findComment&comment=3421379

TL;DR: AFAIK the same as a "normal" ground start. Detail: For JFS assisted restarts, Engine RPM needs be be below 30% or the shaft pawl (pin) will shear (simulated) and engine fail to start/need repair. As with a "normal" start, go from engine cut off to idle at the appropriate time/rpm. Windmill restarting isn't modelled yet.

I note in options.lua that the Preload Radius is set to 150,000 m, AFAIK this will consume lots of RAM and can cause problems, IIRC the general recommendation is to set it 60,000 m unless running off a HDD (and have lots of RAM) or if you only have 16GB of RAM (where it should be reduced to 30,000). YMMV

Yes, the Discord preliminary change log for the NEXT Gazelle update lists a fix (subject to change, etc.).

Agreed. NO, the mission editor allows invalid laser codes, this is not a reason NOT model a RL physical limitation. IRL GBU-10, GBU-12, GBU-16, etc. cannot be set to 1111, etc. GBU-58 may differ as it has an umbilical connection to the aircraft and it's code can be changed whilst in flight. The "allowable" operational laser codes are decided on by joint "standards" committees to prevent conflicts between different services/users, hence why certain weapons/designators have a limited range of settings. So the GBU-58 in practice, may be limited to the same range of codes as the GBU-12, etc series.

This is by design, the bombs have physical dials set by the ground crew i.e. the 2nd digit can't be set less than "5" https://forum.dcs.world/topic/244040-gbu-laser-codes-since-update/?do=findComment&comment=4405162

AFAIK this is already included in the "Flight Model", what is still WIP is engine modelling, hence why the torque indication may be "rock steady". This is also modelled i.e. right pedal causes the helicopter to climb / torque to increase approx. +5%, left pedal causes it to descend / torque to decrease approx. -5% (depends on how aggressive the pedal input is). As said, AFAIK the engine modelling "re-work" is still WIP, so the engine/rpm governor responsiveness may still be WIP or receiving SME feedback. Tested DCS Open Beta 2.9.2.49940, Gazelle SA342L with Sand filter, Sinai

Unfortunately DCS's ATC behaviour is a hard coded ED feature and the ATC/ILS desync that occurs with a moderate headwind can and does effect all maps. AFAIK it's not something a map team can fix and requires ED to rework/fix the core DCS ATC/ILS logic, however it appears to have a low priority (perhaps because it's non-combat related). There's the promise of a DCS ATC rework sometime in the future but that still appears a long way off, so for now - players need to keep DCS's idiosyncrasies in mind when flying or designing missions.

Have you tried a Install Repair ? Which mission/module are you testing this in ? A quick test using Open Beta with the Gazelle 342L and F-15E in Single Player showed no issue using LALT+Left Mouse button.

Only by creating/editing a flight plan using the Mission Editor before loading/flying a mission.

No, set the cp value using it's TRUE heading, that doesn't change over time.

The best guide to using the FD with a VOR approach I'm aware of is in Chuck's guide on page 152. https://chucksguides.com/aircraft/dcs/c-101cc/ It covers the steps but unfortunately the FD and HSI pictures are a little confusing as the Heading bug wasn't set to match the 45° intercept the FD uses once the VOR radial is reached/captured (note it's also possible for the FD to steer away from the radial if it has the "wrong" initial heading). As the VOR radial only gives lateral FD guidance, vertical/Altitude guidance (if required) is set using the regular FD "Altitude" mode. Tested using C-101EB and C-101CC, DCS Open Beta 2.9.2.49940

The DCS Open Beta F-15E radar is working in Single Player, I'm not on the Stable branch or flown MP recently - so can't comment on your specifics.

These are my favourites for the TPOD HTS ... and SSS modes. https://forum.dcs.world/topic/324103-help-with-ir-mavs/?do=findComment&comment=5199684

TL;DR: No, it's the MSL altitude, so -9 is scanning 9,000 ft BELOW Sea Level. Detail: From page 311, DCS_F-15E_Flight_Manual_EN, 2023-12-12.pdf

It's a general/long standing DCS bug/feature that only single player missions/campaigns log their flight hours in the log book i.e. IIRC training missions and multiplayer aren't counted. Once you start using the mission editor or fly some user created Single Player missions - you should find your logbook updates as expected. Logbook Doesn't Count Training Mission Flight Hours Tested DCS Open Beta Multi-thread 2.9.2.49629, Caucasus SP F-15E Air spawn.

I'm not connected to Polychop in anyway, however I appreciate they have stuck around (rather than walked away) to maintain and improve the Gazelle. Comment: This is my own personal take on the "situation" - Yes, I would have liked a Gazelle update this month. IMHO everything else you've said is off topic / unhelpful. Detail: The original Polychop team dissolved several years ago, however a couple of the original dev's kept the "Polychop" name and have dedicated their time to developing an improved flight model, a new module - the Kiowa and to maintaining/improving the existing Gazelle. After a serious illness/accident ? timelines changed and a couple of new members/volunteers joined the team to "help" - including rebuilding the underlying Gazelle code from scratch, the new flight model, 3D assets and textures, weapons, etc. which we enjoy today. Remember the people you are complaining to are the ones that stuck around / joined to "fix" the module. • The work is done part time (usually along side a full time paid job) and schedules change • the code may have been written by another coder or no longer work as intended • it often requires research, development and testing (this isn't a production line with known solutions) • there are "internal" dev development plans, these aren't available to the public as everything is "subject to change" and depend on technical progress, internal testing, changing prioritisations, etc. • With ED you have a free trial to test before purchase. • For Steam you have 2 weeks / 2 hours play to decide on your purchase. After that, you've bought the product "as is", outside of exceptional circumstances - that's the end of the matter.

No, the NS430 GS value can be close to IAS when low/slow, but high and fast it follows the higher GS, under reporting by ~10% For a F-14B at 0.8 IMN @ 30,000 ft, • NS430 gave GS = 432 Kt • Cockpit IAS = ~310 KIAS • Cockpit Info Bar (LCtrl+Y) IAS = 293 KIAS • F10 Map GS = 479 For info. 0.8 IMN Airspeed converter https://aerotoolbox.com/airspeed-conversions/

Open Beta looks excellent with most (if not all) of the NS430 Magnetic and True bearings reading correctly. I'm not sure about the Ground Speed (perhaps still WIP) as it seems to report a speed higher than IAS but ~5-10% less than the GS reported by other methods i.e. F10 map, INS, etc. this seems confirmed by ETE overestimating the time taken to fly a route leg. Either way, GS is much better than it was, please pass on my thanks to which ever team is responsible. Detail: ✔ Distance 31.6 NM ? Ground Speed 383 KTS (correct value ~424 KTS) ✔ Ground Track 128°M (IMHO within limits) ETE 8:14 (incorrect should be approx. 4:28) ✔ Desired Track 128°M ✔ Bearing to waypoint 128°M (IMHO within limits) null Tested in DCS Open Beta Multi-thread 2.9.2.49629 using F-5E, F-14B, SA-342L and MB-339A, Caucasus Map

Testing with the latest Open Beta 2.9.2.49629 - this doesn't seem fixed i.e. behaviour with RNAV and TACAN CDI, etc. remains the same when tested from Nellis.

The DCS AV-8B N/A is regularly included in Steam Sales i.e. 50% discount in Sept., 30% discount in the Summer Sale, etc. https://steamdb.info/app/759130/