Shimmergloom667

Yeah, that would have been much more important than the A/G honestly, yet here we are with everyone having different priorities again :D

Dude, chill. Nothing gets swept under the carpet, even if some stuff takes strangely long to fix while it seems to be an easy thing to fix. Still: stop backseat moderating their workflow, file bug reports and wait. There is literally little else you can do, since working yourself up about it will not speed up bug fixing one bit.

If it's masked then no HUD symbology would show up anyway. Also it has a minimum of three queues showing you where it points: the targeting pod relative view square on the FLIR page itself, the angles it is looking at in degrees off boresight on the FLIR page and the targeting pod indicator on the SA page. If you need it looking forward for whatever reason: simply double-tap NWS for VVSLV or SP. Again I suggest you invest more time to learn how to actually use it now, with basically all of it's functionality finished.

And if it's venting: better stop that and invest a few minutes of your time here

Also the F-Mavericks specifically seem to have a little bug right now, which doesn't impede the TGPs functionality, though: https://forums.eagle.ru/showthread.php?t=253903

The pod is the same, the integration into the planes avionics is different. And honestly I don't get what you are trying to say, the integration works perfectly well.

You don't *hold* NWS for anything in the Hornet.

Seriously, there is nothing weird going on with the targeting pod and you are simply frustrated since you didn't take time to relearn the additions which are pretty much final since OB 2.5.6.53756 from August 18th. Because nothing fundamental changed since then, and the basic logic is even a bit older right now. You talk about short and long presses of NWS as well, where the Hornet integration only has press and "double-click", that is pressing NWS twice in a short time (to switch between SP and VVSLV). I suggest you watch Wags videos from June and August: As well as RedKites Video from very recently, which sums up all changes perfectly and very detailed:

I never hot start, so I can't comment on that. In a regular cold start we had flawless DL yesterday, though.

D/L should be back and working, the issues you describe aren't present for me anymore since OB 2.5.6.55847

You can do that, though - I never, ever burned out the Laser, no matter how long the mission was that I was flying, and 100% those missions had more than 20 min lasing cumulative

That is intentional. "Fast" trim only with weight on wheels and T/O trim selected. You only need that for takeoffs, anyway.

Hit T/O trim, then trim more through the regular trim hat on the stick. Also "check trim" advisory 9 times out of 10 means you didn't FCS reset during startup @ OP

You are not. Starting the Jet manually is integral to my enjoyment of a long mission.

Exactly, same observations, this is also why I added an MP track earlier.

Walked very carefully with the squad through this, and another evening with no Datalink indication of flight members AS flight members on the SA page. Only surv tracks.

Is it even possible to edit paid campaigns and have them still work correctly? Because I agree with the OP: if the paid campaigns have hotstart aircraft in every mission they would be wasted money for me.

Depends on the phosporic tube used - they may be greyscale or greenscale both.

I am not toxic, YOU said it can be ruled out in a flick. Can it, though?

Same question to you - if you can easily rule out that "Correct as is" is wrong, where is your proof?

Ok, very quick and dirty: Small MP mission, flight of 4 Hornets in MP, Datalink engaged for all, regular settings. Expectation: see flight members as green, circle HAFUs with letters inside to denote position in flight, we only get regular HAFUs, though. E2D in the air. Quick vid: Track: https://drive.google.com/file/d/1R-ESWveHv1maJMColgfT4aH08D3C8UeM/view?usp=sharing

The funny thing is: this has nothing to do with what anyone "believes", only with being able to deliver proof that it works otherwise. Can you prove that? (and seriously, weird design, UI or workflow choices in applied systems are nothing new, neither are they in the military)

Didn't work for my squad as well, will try to fetch a track as well

But the AMPCD is pretty fine now, even with map - tweak contrast and brightness a bit and its perfectly usable

Sometimes it works, most of the time it doesn't for me. This will probably get hotfixed in no time, anyway.