Lord Vader

Just some common sense into the mix. If I was an AH-64D pilot (or any other helicopter), I would privilege sight as best as I could, considering my "HUD" is already detached from the panel. So maybe while using the systems I would hunch down a bit, but I would certainly crank the seat all the way up to guarantee maximum visibility. Would the designer/manufacturer/instructors advise that? Probably not. But in the end, the seats aren't fixed and allow a customized position. In a simulation, any simulation, you depict standards, though. Remember that.

Thank you all for helping @AndreNLunderstand the logics. @NeedzWD40That issue was previously sent for analysis. Thanks for that.

Hi all, EOS-VIS is undergoing some refinement. Please test this again after the next Open Beta update and report back if this is still an issue for you guys. Thanks for understanding.

Hello @deltatango Please include tracks of the issues your mentioning. Currently I can't reproduce errors on any of those situations.

Hello @Lekaa I've raised this internally for analysis. Thanks.

Hello again guys. After further analysis, we've reviewed out documentation that refers to our F-16C Block 50 CCIP model and have found that the M3 document you guys are using as reference has a different explanation of the filters and what they do. This was refined by the manufacturer and our representation of the "FR OFF" functionality is correct. The track that was supplied, however, does seem to show a wrong depiction of the PPLI being shown despite being removed by the filter. That's because, unlike what the mentioned M3 document implies, that all "Friendlies" are removed, in this particular Block 50 CCIP update for the C/D versions, the indication is that only PPLIs (members and donors included) are removed but SURV targets supplied by the AWACS remains and that's what you are seeing in your track. I understand this may sound wrong, but this is what the documentation shows. So when you activate the filter "FR OFF" it is working, but you're still seeing surveillance tracks supplied by the E-2/3. If you remove the AWACS from the mission, you'll see this filter working correctly. That being said, while analysing this matter we've found another issue with the "FL ON" filter not correctly removing non-donors. This has been corrected internally and will be included in a future update. Thanks again for alerting us to this, appreciate your care.

Hey @ACME_WIdgets We need some more information about this. You say your joystick "zeroes" at 32. Is that a center point? If so, do you have a deadzone for that range? Do you have any other axis for aileron controls? Are you carrying a TPOD? Someone mentioned asymetric thrust, are your throttle axis synced for both engines? All these questions and some others are answered with a short track demonstrating the issue for our analysis. Thanks for understanding.

Hi @dmatt76 and @SaladinoSaurus I have reported this internally for further analysis.

Thanks, @Pyrocumulous I have reported this internally.

This requires a bit more investigating, then. I have raised this internally.

Hi @Tholozor I've added this to the original report, thanks.

Hey @HMSSURP I have reported this for analysis. Thanks.

Hey @tr4fic A lot of options have been discussed. It may happen in the future but I cannot make any promises for now.

Hi @adirtynurse I agree with the analysis that the engines appear to enter a shutdown/cut-off status when this occurs. In the second clip the left engine is even completely shutdown. I tried following your videos as best as I could and could not replicate the issue. I performed steep dives from high altitudes and never have engine shutdowns or cutting-off. I would review you keybindings and/or axis, maybe clear the fuel cut-off switches bindings and test some dives, then remap them.

Hi @Hofftariand @Milker I have reported this internally for analysis. Thanks.

Hi @Flanker35M I've sent this for internal analysis, but it will be at a lower priority for now. Thanks for bringing this up.

Hi @Gunslinger52 I'm trying to understand what you are saying. So, you say you move the IHADSS away and regardless if it was previously off, it will always return with the PNVS turned on? Is this it? If it is, I was unable to reproduce, please verify your keybinds and if the problem isn't there, please provide a track replay with the issue.

Hi @AndreNL We cannot reproduce what you are saying. Can you please supply a short track from both you and your friend in an MP environment so we can take a look?

Hey @ohbassoon I was able to reproduce this and have raised it internally for analysis. Thanks.

Hi @some1 We would require a non-classified documented reference stating that the Stand-by Indicated Airspeed gauge used on the F-16CM Block 50 CCIP does indeed work as you describe. The comparison with the F-5E isn't fair as the cockpits belong to different eras. Please send the documented reference to @BIGNEWYvia private message if you have it.

Hi again @GumidekCZ Please wait for the next Open Beta update and verify again if the issue persists. Sorry for the inconvenience.

Hi @GumidekCZ I've raised this internally for analysis. Thanks.

Hi @badatthis Not only it's hard to understand what you're trying to convey, please be more specific with what you're having issues with. And please attach a track file of the event happening.

Hi @Cydrych Thanks for the detailed report. I've sent this for internal analysis.

Hello @RogueRunner Yes, we need some more information on what you're talking about here. Please read this thread before you post: