LastRifleRound

That says it drifts less, not that fixes are working

Was it fixed recently? Wasn't mentioned in any notes. It was not doing that before.

The bigger problem here is why isn't FIX and cursor slew working correctly? No matter how large or small the drift is supposed to be, it cannot currently be corrected. This is a pretty big problem and certainly not intended. MOVING THE CURSOR should update the whole flight plan in an F16. That's why Cursor Zero is so important to understand in the Viper. FIX just resets the cursor zero point to the cursor's current position (be it radar, HUD, TGP, etc), but slewing the cursor is what moves the flight plan. The current Viper does not do this despite the fact that this behavior is well-documented in the dash manual.

I guess anyone interested should have reviewed the tracks the months ago when they were posted. I think we'll just discuss them unless someone wants to pay us for our work. We'll keep letting people know this stuff doesn't work. If ED wants to confirm it they can re-create the tests. If they think that's too much work, fine. Out of my hands. It's too much work for me, too.

There are 4 tracks in the thread linked above, and posts indicating hours of work @Nealius put in to demonstrate this. Other users also posted videos and images demonstrating it. Anyone else replicating this work would do nothing but confuse the issue and that thread dead-ended back in November with no real official response. I see no reason to re-create the hours of work that would take if the initial input wasn't taken seriously to begin with.

It's pretty sad this thread dead-ended because no one wanted to directly address the primary questions at hand. 1. Is 240m of drift within 1/2 hour of normal (no extreme maneuvers) flight with GPS on acceptable? It is undoubtedly happening, the evidence posted in this thread and the work @Nealius put in demonstrate this clearly. 2. Why does FIX not update subsequent waypoints, with our without GPS on? You guys need to go with preponderance of evidence. This clearly isn't right. Either you shouldn't have made videos telling people to use FIX, or FIX isn't working properly, and I'd bet my house FIX isn't working properly. There is no way on God's green earth that FIX only updates the single waypoint you use it on. There is no way the Kalman filter filters out fixes because it weighs LITERALLY every single INS data point the same. It doesn't. There is no way the Kallman filter rejects nav fixes because they don't exceed 300m, but doesn't reject also the INS data that induces drift under 300m. The logic itself is incoherent. Out of curiosity @Nealius have you tried using ACCAL for your first fix with GPS off?

Nope, referenced right from the Hornet TACMAN. That's how it's supposed to work. EDIT: Also, what I described is not how the F16 offset behavior works.

That's because it isn't fully implemented for the Viper or the JF17. It is in the Hornet. I can see why, as the Viper docs don't really say what happens when you FTT other than it tracks a return. FTT looks for the point of greatest return in the cone and tracks it, which HOPEFULLY (but often isn't) is your target. For large buildings, ships, and other large return, isolated objects it can add precision as it's not relying on your interpretation of the radar imagery. However, the radar will lock the greatest return, regardless of whether or not it's your target. If you have the Hornet you can test this. Put several static objects relatively close to each other, slew the radar over them then SCS to initiate FTT. You'll see the lock doesn't necessarily pick your target. Often, you can keep re-initializing the FTT and will pick different targets each time. FTT really is typically used for ships, otherwise the AG radar is used more as cueing for sensors or eyes, particularly with the help of offsets.

Of course not

Easy comms was disabled. It may not be a bug, but the comm trigger point seems to be either too far past the airfield or mis-firing somehow. I noticed the gear fault earlier than I was "supposed" to. Since the fix is scripted, the manual was no help and following the real world procedure does nothing until you trigger the dialogue. I was in the air 5nm from H4 for 15 minutes fiddling with it before the radio dialogue triggered. At about minute 10 is when I paused the sim to ask the forum.

Nevermind. Comms bug in campaign. Was supposed to happen but trigger didn't trigger.

Playing the first actual mission in the Gamblers campaign. Fly all that time, it's time to land, I hit the gear lever and it immediately bounces back up. Try it on my hotas, hitting the g key, clearing all keys then doing it, playing with the yellow knob below it, nothing works, gear lever goes down half second then bounces up. I'm at 200kts, 5000ft. I don't understand what's happening.

Well my replies keep getting deleted, so I guess you win? Your testing is flawless, and no one should use the forums to critique the handling of anything from ED. You absolutely can and should ask for tracks as many times as you want for the smallest and easiest explained items, and you absolutely should not under any circumstance worry about anything in your software unless some random paying customer has jumped through at least 4 hoops for it. I concur completely and yield the floor to you.

Do you understand that I am telling you that following the instructions in the JDAM training mission DOES, in fact, guarantee the same failure case every time? If you fly that mission and follow it as intended, you WILL get dud bombs. Do you understand that I DID describe the failure. It is a dud bomb. Do you know what that is? I think you do, so I'm not sure what other detail I could provide. It's rather elementary already, isn't it? It's not a CBU and has no tail fuse. It's an air start training mission, so no ME access, and rearming isn't possible. Either setting the e-fuze to INST makes it go boom or it does not. Why won't you fly the mission? Why leave it for customers to waste their time wondering if they did something wrong? Why is it ok for you to ask me to fly the 15 minute thing AGAIN just to record what I already explained here, but it's NOT ok for me to ask you to fly it? You're on the testing team, are you not? Do you only test things users bring to you, or do you do proactive testing? If you do proactive testing, what is the difference between you testing this mission sans track with no one asking and you flying it now? Do you just assume after major changes all the training missions work without actually checking them? I did nothing but follow the instructions (some bombs get e-fuze to instant, others get delay 1). That 100% leads to a dud bomb. I'll pay you $200 if you go in that mission (public release, not your test build), fly that mission as instructed, and DON'T get a dud. That's $200 for 15 minutes of work. If you're so sure I'm wrong without a track that's a great deal. But I think we both know I'm right and you'll probably just be wasting your 15 minutes, just like I would be.

You do not have to do A SINGLE THING THAT I SAY. Just fire up the FA18 JDAM training mission that COMES WITH THE GAME. Follow the instructions THAT YOU PROGRAMMED INTO IT. Report back your results. Good luck!!