Swift.

Stupid question, but is that repeatable or just a coincidence?

Are you sure that's a bug? I mean, TOO Lock would have been introduced for a reason in the later softwares.

Remember that the aircraft still needs to figure out the range to the designation. When you designate within 70 degrees off forwards, it can use AGR to get an accurate ranging to your new designation, but if you designate backwards like you describe, then it has to rely on the Digital Terrain Elevation Database to get an approximate range, which obviously reduces the accuracy of the designation. Leading to the drifting you might be seeing.

My understanding is Mech is Cables to the Actuators. You still needs hyds for the surfaces to actually move.

I'm interested about how well INR and SCENE should stabilise. Looking at various cruise videos, you see 95% of the time INR is used and very occasionally its SCENE. I wonder why that is.

SLEW shouldn't change how you select waypoints, only add the ability to slew the map underneath the selected waypoint to change the location of said WP.

I don't play on IC servers, but I'll pitch in with some of the fixes that affect the core files, that I use anyway: A-10C TAD Scale Fix - Adds the missing TAD scales for A-10C, I'm sure there is a report somewhere of this. - https://www.476vfightergroup.com/downloads.php?do=file&id=399 Mods/Aircraft/A-10C(_2)/Cockpit/Scripts/TAD/TAD.lua RWR Symbols mod - Fixes and/or creates custom RWR symbols for different threats. Could be replaced by the corresponding setting in the eventual mission planner Scripts/Aircraft/_Common/Cockpit/AN_ALR_SymbolsBase.lua AN ALR69 Sounds - Fixes the sounds produced by the A-10s RWR to more accurately reflect RL Mods/Aircraft/A-10C(_2)/Cockpit/Scripts/AN_ALR69V/device/ALR69_param.lua A-10 IFFCC AAS Profiles - Configures the IFFCC AAS to accommodate different threat aircraft in the AA Master Mode - https://www.476vfightergroup.com/downloads.php?do=file&id=416 Mods/Aircraft/A-10C(_2)/Cockpit/Scripts/IFFCC/IFFCC_param.lua Additional Controls mappings - adds in the critically missing controls bindings that production HOTAS such as winwing rely on Mods/aircraft/FA-18C/Input/FA-18C/joystick/default.lua I havent checked if these all break IC, but they are examples of fixes that are required to play DCS that might be affected.

It is odd that the PPLIs don't extrapolate like tracks do. Especially when you think about all the MSI stuff going on...

Yeah it looks like theres a whole load of this already on the TGT Data page

That BIT message indicates there are BITs that do not show a 'GO' status. If you navigate to the BIT page on the SUPP menu, you will see several flashing lines of text in the centre. Click on STOP (top right) to stop these flashing and clear the BIT advisory.

What we need is for ED to implement all of the comm submenus, even if all of the actions are non functional. SRS will take up the slack.

Correct, thats why they dont carry HARMs there...

TBH, the DL13 we have is probably closer in capabilities to a DL9 anyway

How steep and fast are you attacking?

Thats effectively what I did, but the Target Diamond was bang on. I suppose its possible that having the pod onboard meant nothing drifted at all, but still....

What I did was create a waypoint and slave the pod to it to check the location, then undesignate the WP and circle for hours, then upon redesignating, you'd expect the pod to point at a drift location. However the pod and the diamond in the HUD pointed at the original location

I haven't been able to find a good way of measuring drift in DCS because waypoints don't move even after two hours of circling with no GPS. If you've got a good repeatable method Is be interested in seeing it as I'm sure there is a bug that can be reported here. Real like ASN-139 drift rates are negligible at best, I've see test results of 0.0 NM/Hr drift

The AUTO part of the AUTO/Loft works fine, the Loft part doesn't but its useless so why worry about it.

That doesn't sound right at all

A more accurate concern to think about might be that up until a certain OFP hornet could only do 3 decimal coordinates. Cant remember the exact OFP but it wouldn't surprise me if it was 21X

I assume ED still has some hornet SMEs they can ask. Perhaps tie in with them first?

It's not correct as is, at least not in actuality. The problem lies in convincing ED to do the work without hard evidence beyond anecdotes

I have no evidence, but have always thought it strange that the lights can't dim down to nothingness. It goes from 0 to 5 and then smoothly up to 10, if that makes sense.

Very potentially, I've just heard anecdotes from various pilots that it's range only. Perhaps they never used a KC10 idk.

To bring this thread back on track, this wasn't about the XY bug. But rather about the fact that IRL tankers only show range as if they were using yardstick.