Yaga

That's my understanding as well. I've always turned mine on, but the few times I've forgotten with a hot start, DL updates appeared to sync just fine. I haven't seen it confirmed whether it's actually doing something in DCS and the clock shows the correct time when it started in Off from cold. I suppose it's a moot point now.

Is this a cold start instant action? For any hot starts, the jet should spawn fully aligned, MIDS on and with DL working. Campaign could be using an out of date .miz. But iirc power cycling the MIDS switch has always been a surefire way to correct any problems as long as the alignment was done correctly. Try a stored alignment and wait until it is flashing on the HUD, switch to nav quickly (don't linger on the normal alignment position, double click through it) and turn MIDS on afterwards. If it's an old .miz you might see GPS time set to Off in the LST ENT DED page. If you want, turn it on, or don't.

The LST ENT DED page does indeed 'turn on' with GPS time set to On, whereas before it would be Off. Same was true for hot starts and was a recent update. Is there a specific issue you're encountering during startup? Idk if this is the correct behavior, but I haven't noticed any in my starts. GPS time shows correctly when verified against the f10 map clock. I'm not 100% sure GPS time does anything currently, but I could be wrong.

Great post. I didn't know we could use Mbccia's QuadViews with the Pimax OpenXR runtime. With Quadviews sharpening at 70 set in the companion app, are you still sharpening in DCS at .5 as shown in the screenshot? I've been generally unhappy with the results of my own endless tweaking, so I went ahead and copied your settings exactly sans DCS shadows & SSAO/SSLR. I was maintaining 90 fps previously, and still am; however, the image looks and feels better. I could be imagining it, but I'm happy to attribute it to your blend of settings.

If all the switches are turned on and you don't see DLworking, troubleshooting is almost always as simple as cycling MIDS Off/On. I'm in the habit of waiting until after alignment is complete and set to Nav before I turn MIDS on, but I don't think anything breaks if you turn it on before. Again, if it does break, just power cycle it and it should be fine. If that doesn't work, I suspect there may be an issue with your alignment.

You hear the same thing periodically in the F-16C on certain channels, but I'm not sure it works correctly. If you change freq, the static stops, but if you revert to the original freq it doesn't start again, even if you didn't move or change channels quickly. As far as I can tell it's somewhat random. I'm sure it's utterly obnoxious in FC3. Yuck.

Is the bug at least acknowledged internally? Please let us know if they need a track.. Would be nice to get this fixed.

It is the track history maintaining the return for x number of scan cycles. By default the jet has it set to 4. This means you'll see the most recent brick returned plus the bricks returned during the last 4(3?) scan cycles. As they become older they fade out. You can adjust the track history in the CTRL page in the FCR. Options are 1,2,3, or 4. I set it to 1 typically in order to declutter as much as possible. Currently, setting it low has the benefit of getting false contact bricks to go away quicker as well, which is nice. No clue if this is how it is supposed to work, but it is how it works in the current state of our jet.

Make sure you have your special settings gradient and deadzones set per his report prior to running the track. Sent from my Pixel 4 using Tapatalk

Please, elaborate and expand on this explanation a bit. Show us your functional understanding of what you quoted. We'll wait. Sent from my Pixel 4 using Tapatalk

Of course not. That'd be a needlessly stupid design.

The report shows different behavior between hot/cold starts. This is not hardware related.

Issues regularly make it past testing and into release builds. Versions get merged incorrectly. Builds are last minute. Fixable. The parts that work are stable and those that don't aren't. Is this what I'm reading? Is the MP Scoreboard no longer functioning a EA addon module-related feature? When an update makes south-bound launched missiles loft downward instead of lofting upward, that's not really a "complex modern fighter" problem, is it? With a dedicated team on it, I'm sure the pod will be well researched, correctly modelled and not have any inaccuracy persist beyond a reasonable time frame.

I'm not sure I understand why a 0 deadzone would cause A/P to disengage. This input would just be the noise normally filtered out, at worst. If this noise is enough to disengage A/P, it seems like you'd be focused on the jet being unflyable. The A/P tolerates some maneuvering within limits.

Sign ups are now closed. Please refer to the discord for all TACT 24-1 information going forward.