diditopgun

Up ! I don't understand how it works too.

MWS deactivated on A10 and DDM unmounted on M2000. ;)

After more tests in-game, same conditions: No RWR launch warning: -F-14 -F-15 -Su-27 RWR launch warning: -F/A-18C -AJS-37 -A/V-8B -A-10C -Mirage 2000C :huh:

Very nice addition this HQ-7 ! (no word in ED changelog… fortunately I follow you on facebook) I tried to fly against it in the Tomcat. It appear as "U" on the RWR (3rd parties have to update their data base I presume), but there is no launch warning when a missile is fire at me. WIP ? MBT will be Type-99 I suppose ? ^^ And what about this untextured mobile TACAN station ? Can't assign any channel in advanced options, still WIP too I presume ?

Hi ! Bug still there.

I didn't do it about air combat performance. I just want to know if you have simulate something particular in your airspeed indicator (like some errors of any kind) or if it could be a bug or something else. Tomcat max speed is given for Mach >2.3, but in-game I never achieve such speed in level flight. But with the speed of 1340 KTAS Tacview and airspeed convertors around internet give me speeds of Mach 2.3xxx. So I just want to understand what could be wrong or not.

Aaaah yes.... It doesn't change coordinates, it's only a shift to my own position! That make sense, thank you Super Grover!

That's why I use ISA parameters QNH 29.92 and temperature 15°C at sea level with no wind. I presume Tacview is based on it ?

Hi ! Starting with a clean (no belly pylons) Tomcat, 50% fuel at 38000ft Mach 1.2 and then noted top speed just before running out of fuel: QNH 29.92;+15°C @SL; FL380; 1340 KTAS (external view); Tomcat airspeed indicator: Mach 2.25 ---> Tacview: Mach 2.35 QNH 29.92; -10°C @SL; FL380; 1370 KTAS (external view); Tomcat airspeed indicator: Mach 2.27 ---> Tacview: Mach 2.39 So with Tacview I can finaly reach that Tomcat top speed of Mach 2.35 in ISA. How can you explain this Mach number delta between in-game cockpit instrument and Tacview measurement ? :huh:

Hi ! Today I (RIO/hoster) did some test with a friend (Pilot/client) about LANTIRN's coordinates display to know if its link to the Tomcat INS or pod's GPS receiver; and VIS FIX INS update. Firstable, It seems coordinates displayed on LANTIRN don't suffer from INS drift, so can you confirm that LANTIRN pod is hybridized by GPS ? Then we noticed that typing new coordinates in waypoint1, update waypoint1 position on TID and LANTIRN QWp1 too as intended. But ! If we update waypoint1 position by a VIS FIX; it updates waypoint1 position on TID but not LANTIRN QWp1.

Yes the elevation indicator next to the DDD on its left. Number 22: http://www.heatblur.se/F-14Manual/general.html#detail-data-display-ddd-and-panel

Hi all ! There is really no radar antenna elevation indicator backlight ? How to deal with it at night ?

This happened on Persian gulf map (not tested on Caucasus) during multiplayer sessions. The host hasn't the issue, it's only on clients side. No issue in single player. About 180 degrees around the ship it is visible while on the other 180 degrees it disappears:

An old bug that we are all waiting to be address for years... Yep... in a flight simulator this bug is a shame.

Hi Super Grover ! I read your comments, HB navigation flight manual section, real flight manual, articles about gyromagnetic compass on the web, and tests in-game. Now I think I understand pretty well how the whole things are working (IMU, AHRS,...). Very great and deep system modeling ! Just a last question for you / Victory205 / SME: After catapult launch, does a fast slave by the HDG push button on compass control panel is a standard procedure ? Thank you !

https://forums.eagle.ru/showthread.php?t=237719 ;)

I was in continuous climb after catapult launch (for info, it's a "start from runway" mission, not cold and dark), maybe that was part of the problem. Is there an official procedure to follow after catapult launch about this ? I will do new tests this afternoon and try the HDG push button.

This morning I did a CASE III training with no visibility. At catapult position I observed a compas drift due to carrier's magnetic field. After carrier take off I flew straight on carrier's heading 090. It took about 10min and 40nm to have a correct compas heading (cross check with external view data). Then I turned back to the carrier and at about 30nm from it, compas start to drift again. So my CASE III pattern was a nightmare...

It's very narrow indeed, I thought it was wider. That's precisely my question. :thumbup: Yes PAL is my pal under 20nm :yes: Me too !

Thanks for your answer IronMike. Yes it's Tacview so maybe the target was at 10.01nm at trigger depress time. ^^ So if I well understand, if the missile seeker don't see the target before launch, it will go with an inactive seeker after launch. Pretty weird and useless on my point of view, but if it works this way I will deal with it.

Any words on how AIM-54 is supposed to work in boresight mode ? No "maddog" capacity like AIM-120 ?