Ramsay

The Razbam F-15E discord was/is full of RWR discussion about the changes, AFAIK from the SME replies, the new behaviour is correct i.e. matches the real.

Following SME feedback, new A/A contacts in search (Nails) have no "new guy" tone.

ED tried that, all that happened was people complained the "patch" couldn't be downloaded. A case of "not being being able to please all the people, all the time", so ED reverted to only publishing the "official" changelog once a new patch is "live".

IIRC cage/uncage will re-centre the IRMav seeker, however when uncaged, it will slave to the INS (target designation, last target point, etc.), HUD flight path marker or Aircraft centreline/HUD watermark - depending on the last sensor/system you've been using and where in a designation-undesignation chain you are i.e. the NWS button changes the FoV without a target lock, however with a target lock (closed cross hairs), NWS button unlocks the target and boresights the IRMav to the flight path marker. It's covered on page 223 of Chuck's AV-8B Guide but I haven't tested it in detail recently. AFAIK DCS's INS designation logic is imperfect and Razbam hope to improve it with a system rework some time in the future.

TL;DR: Although the default loadout of 2x AGM-65G and Sidearms is depreciated and the aircraft spawns without it's original Sidearms - the AGM-65G's will RDY if given enough time. Detail: For the IRMav to "RDY", the aircraft needs to be in A2G mode and the IRMV selected/powered up i.e. "boxed" on the MFD for approx. 3 minutes It's important to note that the AV-8B's TPOD is treated by the weapon system as if it's another "weapon" and when selected, will deselect the IRMav, etc. https://forum.dcs.world/topic/324103-help-with-ir-mavs/?do=findComment&comment=5199684 The AGM-65G still functions despite being depreciated in DCS i.e. the AGM-65G was a place holder for the AGM-65F now in game. Tested in DCS Open Beta Multi-thread 2.9.2.49940

Please post a short .miz or .trk file demonstrating the problem and I'll take a look.

Lol. The old Eclair control box was removed from the DCS cockpit in November 2019 and cockpit revised to match the real as flown by the AdA. https://forum.dcs.world/topic/170893-dcs-world-changelog-and-updates-of-open-beta/?do=findComment&comment=4068013

Didn't find a problem when dispensing 64 flare and chaff using the Eclair-M 6/0 (48 flares, 0 chaff) configuration. https://forum.dcs.world/topic/339510-edit-countermeasures-count-in-me/?do=findComment&comment=5344356 The only thing that might catch you out is that AFAIK, you MUST ensure DCS's chaff/flare sliders are set to 234/64 when rearming. Attached is a track where I dispense 64 flares using countermeasure program 5 (1 chaff + 1 flare), if you continue to have issues please attach a short track file. Tested using an air spawn M-2000C (Eclair-M 2/4 and 6/0 configurations), Caucasus Map, DCS Open Beta Multithread 2.9.2.49940 M2K Eclair-M 6_0 64 Flare Test, 2_9_2_49940.trk

The switches are spring loaded from RESET to ON. Yes. Right mouse click - toggles between OFF and ON Left mouse click - momentarily moves the switch from ON to RESET position before allowing it to spring back to ON The individual CAS switch positions can also be assigned to keyboard/joystick. RESET re-engages a (disconnected) axis after a fault has cleared, while OFF disengages the problem axis. Tested DCS Open Beta 2.9.2.49940

Thanks for the track. What happens is the aircraft gets damaged in the first turn when taxiing from the hanger to runway threshold. External view Before this point , I could take control and test the AP on the ground i.e. by pressing the AP buttons so they light, etc. Taxiing at a slower pace, I taxied and took off without damage and engaged the AP in flight as normal - so your startup routine looks sound, rather you'll need to watch out for ground handling and/or over speeding during taxi and take off.

That description doesn't help. Try the Instant Action F1EE Refuelling Mission and engage the Autopilot (the aircraft starts in level flight and is well trimmed). If you continue to have issues engaging the autopilot, save the track file when you exit the mission and post it here (for others to look at). (the default track location is "Saved Games\DCS\Tracks") Attached is a short track file where I engage the autopilot. F-1EE Test AP Using Refuelling Mission.trk

AFAIK it can be a nearby waypoint or target point you've got selected but you are broadly correct. This video may help but I think you already have a good understanding of the principle. I suspect that (like in my case) the targeting system had "fixated" on the first target point created, so offered grid squares near that. Slewing an existing target point closer to the target area "should" have allowed you to edit-in the precise coordinates later, so it's definitely worth retrying that method.

You need to create a waypoint/target designation near the desired grid square, if you've already designated a TOO/waypoint you may find the ODU grid selection limited to squares near that point until you either create/designate a new waypoint/target point or erase/zero your existing target point i.e. T1 In my test, Designating WP 2, 3 or 4 gave TOO ODU options to select grid EU for a NEW target point. The AV-8B's designation logic isn't user friendly but it's hard tell how much of the rough edges we see are due to DCS/Razbam and how much is just the way the aircraft is in RL. For example - I initially created a TOO Overfly Point and it took me a while to workout how to stop the system focusing on the nearby T1 target point and let me designate 140 NM away, near WP 2, 3 or 4. AFAIK Razbam are hoping to start a designation/INS rework later this year. It should have worked i.e. • I created a TOO Overfly Point (T1) near WP1 • Used the EHSI Data page to slew T1 to Grid EU • Exited Data mode, then re-entered it to • Select UTM mode, select Grid EU, then edited the co-ordinates to match my target. • Exiting Data mode, I confirmed target bearing, distance, altitude and coordinates were as expected

Took me a while to workout what I "think" is going on ... • Strangely the mission has "no weather" set (usually seen in older missions that haven't been updated), which means the night sky (stars/moon and clouds) aren't rendered and (some?) ambient lighting effects get broken. • Spawning directly on the runway at Batumi doesn't give many visual clues • It takes a while (time acceleration) for the NavFLIR to oversaturate. • Gamma=3.5, SSS, SSLR and SSAO don't help but aren't the root cause, rather it seems to mainly be the missing weather and poor location.

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