Super Grover

@Voyager The INS accumulate drift all the time, not only at high G. Of course, high G manoeuvres may introduce more significant errors. However, those are mostly position errors, and attitude errors are less pronounced. On the other hand, there are two ways for break the INS completely: by pulling too much G, and as a result of a random failure (emulating all other aspects why the device can break). One common misconception is that the skewed pitch on the HUD comes as a result of a broken INS (IMU). Quite often the scenario is: the IMU breaks, the AWG-9 detects that failure and automatically switches to AHRS/AM, the AHRS becomes the attitude source for everything, including the HUD. However, the AHRS can easily tumble, because it's designed to work for +/-82° only. Usually, that shifted/rotated pitch ladder is just a result of heavy manoeuvring in the combat phase before the IMU broke. As an exercise showing the limitations of the AHRS, you can manually switch the INS mode to AHRS/AM, do some aerobatics, and observe how the accuracy of the attitude displayed degrades. @Talonx1 The magnetic compass/sensors are sensitive to the magnetic field of the carrier and can easily be off by 10° or more.

Just wanted to ask if you are sure it was "T" and not "TC"? Because Ticonderoga should show "TC" ( http://www.heatblur.se/F-14Manual/general.html#threat-symbology ), and if it was "T", I'll start looking for a bug in the RWR code :smilewink:

The RWR doesn't have any means to know if you are the target or someone else, and hence a conservative approach: if there's a potentially lethal missile flying towards your aircraft, you must be warned about it. It is possible to lock and launch at a friendly aircraft by mistake, and there's a reason why we all know "buddy spike" so well. We know that the AI SAMs in DCS never make such silly mistakes as blue on blue launches, so you may ask why to show those missiles if they can't be lethal in DCS? - Just because we try to simulate the real device as realistically as possible, and who knows, maybe one day the AI will stop being that perfect in judging who is red and who is blue . Summarising: all "N", "F", and other settings are ignored in the critical ring. So when the RWR thinks that you may be the target, it always warns you about it.

The bug has been solved internally, and it's being tested now. It was introduced as a byproduct of fixing another bug and slipped into the release build unnoticed. Sorry for the inconvenience.

It worked the last time I tried it (although some time ago), and the code is there. And you shouldn't be able to break the INS at 8G, at least the threshold in the code is set higher than that. Oh, and BTW, if you have "Random System Failures" set to on, the INS and other devices will sometimes break too (maybe the INS a bit more often than the rest).

Usually, it's a mechanical failure, which means that the whole INS has to be replaced by the ground crew - only DCS "repair" function can make your INS fully functional again. In terms of in-flight re-alignment, it's impossible with the F-14A/B. You can erect the IMU to a state where it can serve as the attitude source, but you can't restore full INS abilities.

Thanks for sharing your observations. I haven't noticed such problems with accuracy, but I'll take a look, and check if there's anything we can do to improve the precision for you. However, this as well might be just the nature of the weapon or the profile used for the attack (the bombs use very rudimentary steering), or the networking thing, and then we won't be able to do anything on our end. I'll let you know about the results.

I'm sorry that the radio doesn't work for you. However, I've just tried that cold start instant mission, using both Easy Communication and regular radio settings, and the radios have worked. We would need more information to help you with setting the radios up. Please describe all your actions precisely, if possible include screenshots. Alternatively, you could record a video. I'm sure we will find a way to fix the radios for you, no matter if it's a bug or some mistake in the procedures.

Thank you for the report. Your observation is correct - Jester forgets about switching the NAV MODE to OFF. However, I've already asked him to be more focused when performing alignment and he promised to improve after the next update. Jester is a nice guy :-)

Thanks for reporting this. It's a bug which I introduced when I added the code ensuring that Jester moves the switch out of OFF once airborne. I'll correct it.

It's * not ǂ The whole string is a BIT code. When it's close to "XXXXX *1 444" it means that everything is fine.

As I explained in the previous posts, it's highly improbable that what you experienced was due to the carrier's magnetic field. You don't have to wait 10 minutes to correct the compass readings after a catapult launch. You can fast slave the compass heading using the HDG push button on the COMPASS panel: number 5 here http://www.heatblur.se/F-14Manual/cockpit.html#compass-control-panel Press it with your LMB and hold until the SYNC indicator shows no deviation. It will work only when your wings are level, your speed is constant, and your vertical speed is zero.

Hey Bruce_D, I'm sorry that the kneeboard doesn't work as you would like it to work. Indeed your observation is correct, and the TACAN list won't show the stations/units that are inactive when you enter the cockpit. This is a limitation of DCS and the method used to prepare the list. The kneeboard can't predict all intentions of the mission creator, and it's not a substitute of advanced flight planner. It was also our intention to make it realistic - so it's not updated once airborne. However, we understand that the feature you're asking for is important for you and we will update the kneeboard if we find a proper way to include those late activated units on the list.

I'm sorry to read that you had troubles using the radios. There are multiple reports in this thread, and I can't get a consistent picture of what isn't working for you. Unfortunately, most of the reports don't contain enough detail to reproduce the conditions under which the radios don't work. Thus, I can't tell if something is a bug or a user error. The radios and radio communication may seem to be simple, but it's the opposite. Multiple options available (Easy Communication, F-14B radio menu special options), two radios and one intercom, and two sets of controls make it quite a complex system. Therefore, I need to ask you to include more details in your future reports related to the radio systems. Please describe all the actions you take in the simulator. Specify if you are using Easy Communication or not and if you use any radio related special option. Take screenshots, and if possible, please include the mission.

Hey Andrei, I'm sorry that the radios don't work for you. However, I'm quite sure that unmodded DCS can't show "VHF FM" in any radio menu of the F-14. The only possible options are "UHF ARC-159", "VHF/UHF ARC-182", and "ICS". If you're using "Easy Communication", then you can also have "AUTO". Thus, the only possibility that you have "VHF FM" is that one or more files are corrupted or that you are using a mod that replaced some radio communication files. Could you repair your DCS and remove all mods? Then, make sure that you're using standard controls for the radios. Launch your F-14 and stay in the pilot seat. Try opening the menus using: - RALT (Right ALT) + \ to open "UHF ARC-159" - RCTRL (Right CTRL) + \ to open "VHF/UHF ARC-182" - RSHIFT (Right SHIFT) + \ to open "ICS" - \ to open "AUTO" - but only when using "Easy Communication". If any menu title is different, please, take a screenshot. Try communicating using the radios, remembering to set correct frequency. When using "Easy Communication", you can skip frequency tuning, and use "AUTO" to select the station you want to communicate with - the frequency will be set for you automatically. Also note, that some of the bands on the ARC-182 use manual modulation (AM/FM) settings. Finally, ensure that the AI units have correct frequencies assigned in the mission editor - otherwise, you may be unable to contact them. If this doesn't work for you, please describe in details all the steps you take in DCS to setup your radio. If possible, please include screenshots showing your radio display and radio menu. Finally, please write if you're using "Easy Communication".

There was a bug in the code which loads mission editor settings. It's corrected now in the open beta branch. However, a part of the behaviour which you observed is still valid. Imagine a situation in which you loaded 60 flares and 0 chaff, and you don't use LAU-138. In this case, the correct settings for your ALE-39 are: L10 - F, L20 - F, R10 - F, R20 - F. You can always check what is the correct settings in your kneeboard. Now, you (as the RIO) use the chaff switch to release one chaff. It does nothing because no ALE-39 section is marked as chaff. Imagine that you don't change your loadout but you set L20 to C on your panel. You press the chaff switch again, and the system releases one flare. It's because the system is not aware of the actual loadout and it uses the settings dialled on the control panel. You commanded to dispense one chaff, but the only section marked in the programmer as containing chaff is L20, so the sequencer sends one release impulse to that section, and the dispenser ejects one of the cartridges loaded in that section. And all cartridges in that section are flares, so it releases one flare.

Hey! Thanks for reporting your observations. @|DUSTY| I've checked HAWK online, and indeed sometimes it gives no launch indication. I investigated it further, and it looks that sometimes in multiplayer you can be tracked by multiple subsystems of one SAM system. In such a situation, the first strongest locking subsystem may be not the subsystem engaging you with a missile, and we are checking for the missiles guided from the strongest lobe. I've corrected this by checking all subsystems and not only the strongest one. Should be available in the next update. Side note: "sometimes" in my case was 10-20%. For 80-90% it gave correct indications. @mattag08 Now, "U" should appear only for some unknown types, not in the database. I checked it online and offline today, using the latest open beta, and it worked correctly. However, I found that the HAWK CWAR radar wasn't in the database, so I added it. I think that multiple "U" you got was because of the mission (maybe spammed with CWARs ?) and not the RWR.

Thanks for the reports. I tried Eclipse twice using a debug build so I could get more info should it have crashed. But it didn't. Hard to tell what caused the crashes for you and if it was the F-14. However, we will keep testing, and of course, crash logs that you will send us may help.

The simplest answer is that we emulate lobes (main and side) of radar beams for all AI units. It should reduce the distance at which the ALR-67 will inform you about being locked or about a missile launch when you're in a side lobe of a radar tracking another aircraft. It has been discussed in this thread: https://forums.eagle.ru/showthread.php?t=237416 and some other RWR threads.

Thank you for reporting this. It's fixed now internally. It will be available in the next update (not today's update). It also closes these bug reports: https://forums.eagle.ru/showthread.php?t=236268 https://forums.eagle.ru/showthread.php?t=236289

The ICS PTT button works as an additional Jester menu toggle button only when flying with Jester (so not with a human RIO) and when the special option 'OPEN MENU: RADIO MENU KEY FOLLOWED BY PTT (SRS PRIORITY)' is selected. To open the ICS radio menu with this option selected, you should press the radio menu key (default '\') and follow it with the ICS PTT key/button (default Right Shift + '\').

Today, I committed a change which adds the functionality you asked for. It will enter one of the next updates.

Well, when using WIDE FOV, there's no wider FOV, so that it will drop it. But it should switch from EXP to NARROW, and from NARROW to WIDE. At least it did it when I tried it for the last time.

Thank you for these kind words. I'm glad you like the LANTIRN Yes, you described it precisely. The object you want to POINT track must be of a proper visual size - not too small and not too large. It must be easily identifiable - the background can't be cluttered with other hot objects. So it will lock on a single building or a tank in a field. But it may be unable to initiate POINT on a building in a city or a vehicle hiding in an urban area. The pod monitors track quality continuously, so you may successfully start tracking, but then the track may be dropped because the view has changed. The pod will automatically switch to a wider FOV when the tracked object becomes too big to fit the frame.

During development of the LANTIRN, I watched probably all GBU delivery video available. Almost all used manual lasing. And I remember maybe only one or two in POINT, the rest in AREA. My observation is that auto lase works quite well in DCS for stationary targets when the pilot is precise in following the release cues from the LANTIRN.