Shahriar0

Thank you. I believe having an option under a more general setting such as Radar Setting still makes sense. Requirement for going on standby does not always happen during an engagement. I am also the type that don't rely much on Jester menu. I like to do as much as possible by jumping into the RIO seat and doing it myself. Obviously don't like to see Jester undo my work, in this cast turn radar back on. Thanks.

One of the steps on the checklist prior AAR is to put radar on standby. Problem is that Jester menu's Radar Setting does not have a Standby option, and also, when radar is manually put on standby mode, Jester immediately returns it back to On when control is back to the front seat! I believe Jester menu should add support for a Standby/On toggle option, as well as Jester himself not changing radar mode on his own. Thanks.

I noticed this right away when I did a bunch of sunset/night flying in a couple of modules. To me this proves that ED's testing does not include night flying, otherwise they would have noticed it. This is disappointing to say the least, specially with the lighting issues we have had since 2.5.6.

The very first thing I tested in 2.7.0.4625 was this issue. I am extremely happy to report that this problem is no longer present. Going to Map view and back to cockpit at night time does not produce those surface-of-the-moon-type textures before reloading the proper textures, as it was the case prior to 2.7.0. Many thanks to ED for finally taking care of this.

Still downloading the upgrade, but from the release logs I can say it is missing the early F-14A variants as it was promised many months ago that it would be out at the end of winter. Very much looking for it, perhaps in the next release?? Other than that, thanks as always for a great module. It's a pleasure to fly the Tomcat.

Bump.

Bump.

I believe a fix for this long standing bug is way overdue. At minimum, ED needs to comment on where this bug stands in their priority list and also when we can expect a resolution.

Thank you IronMike for taking this to the SMEs and getting their feedback. Yes, on behalf of myself and one member of the silent majority that you referred to in your earlier post and hinted that they may not be onboard with this issue (and infact was the person who prodded me to get this issue posted and which resulted in opening this can of warm), I would say, please "look into" this - and by that I am hoping the brightness to match other planes under the same gamma, light angle/condition/etc. setting. Thanks again.

And I would add that this brightness issue applies not just to "crappy monitors" or the ones with "limited" dynamic range, but to VR headsets as well - which do not have specific setting/control to adjust. My Gamma is 1.6 and that's what suits me and looks "correct" to my eyes. The point of reference for me is not the Gamma but comparison with other planes using the same Gamma setting. As long as I see the AoA Indexer light in every other plane under different light conditions and angels correctly, then naturally, I expect to see the same level of brightness in the F-14 as well. This reminds me of the landing light. It used to be good, and then in 2.5.6 went very dim in the F-14 until we voiced our complaint and it got fixed. Hope the same ending for AoA Indexer

Bump.

Still waiting for Heatblur to comment on this. BTW, the indexer lights are even harder to see in VR compare to the images provided above from monitor (thanks to the folks for chiming in and providing evidence.) In other words, you practically don't see them, specially the red one when coming fast. Please fix.

A picture is worth a thousand words! Thanks to Skysurfer's posted picture, you can see how the indexer was very much visible in daylight. I hope this gets fixed once and for all. Other than that, love the A variant. Only if I can slow it down on approaches :)

I know this has been brought up repeatedly and ad nauseum before, but the AoA indexer is absolutely not visible in day light. It is beyond frustrating. I can barely see it when I lean over (in VR) and squint. At the current state, it is useless and I consider it not working and therefore broken. In my opinion, Heatblur's answer that this is how it was(is) in the real F-14, is unacceptable to me. Please fix this.

Because it still flies today in IRIAF. Do we need another reason why this varient is needed? It was also the master of the skies in the Iran-Iraq war with so many kills under its wings.

And while we are impatiently waiting for the release of the F-14A, can we make sure the Iranian skin won't have the registeration/serial number 3-6080? The skin we currently use for the B variant bearing that number is fictional as the last purchased plane was not delivered to Iran due to the 1979 revolution. May I ask what number HB is planning to use instead?

I just came across this thread and found it to be extremely useful. I have been waiting for a long time to get keybinds for HSD Course and HUD Trim knobs (due to the fact that as a VR user I hate to reach for an external mouse to manipulate knobs with the scroll wheel.) Thanks to the bright folks on the thread, I can now use controls on my Hotas to change the HSD Course. What I am looking for is the same for HUD TRIM. I gave it a shot by using HUD_Knob_Trim but didn't work. Appreciate any help on this.

What I was merely trying to point out was the fact that extending the boom will make the plane fly uncoordinated. I use rudder trim to center the ball so I don't have to worry about the effect of flying uncoordinated and the slight rolling tendency as a result of it.

Every little thing helps, including retrimming the rudder after boom is extended. In the picture posted above, you can see the ball is not centered.

My apologies! I completely misspoke on this; flap position and turn indicator do work when viewed from rear cockpit only in single-player. In multi-player is still broken, as it was originally reported. To me it shows that the general coding is there but in multi-player these two do not get synched.

Just wanted to report that in the 2.5.6.52196 release, while this issue was not entirely fixed, but the negative impact of it has been greatly reduced. The transition from F10 map back to the dark cockpit now is about 2-3 seconds long, and the terrain outside does not turn into that ghostly surface-of-the-moon type look. The fog on the canopy is still there but less noticeable. At this point, this is tolerable to me and does not totally break the immersion. Obviously we will take any further improvement if it comes our way. Thanks.

I am pleased to report that in 2.5.6.52196 release, not only the flap position and turn/slip indicator do work when viewed from the RIO cockpit, but also the helmet of the pilot is displayed in the mirror (instead of RIO.) This is truly fantastic. Since there were no references in the patch note, I had little hope for a fix, but HB did come through. Really appreciate it.

I just shot a land-based ILS approach and all worked fine. No problem with the glide slope there.

Thank you for commenting and appreciate moving these two up in the queue.

Also, I had previously reported that Instrument/Console Brighten Up commands for Pilot/RIO do the reverse and actually Brightens Down the lights!! This bug is also still present. I was under the impression that in this release we would see fixes for all these little bugs that used to work but had gotten broken recently. Apparently I was too optimistic and perhaps naive.