fausete

Please guys, there's no need to be salty about it. We have it in our to-do list and have not forgotten about it but you're very welcomed (and it might be very helpful) to remind us about things that need to be completed, just in case.

Okay, thanks for the reports. We're going to check the total FOV of the sight, in case there's a problem there.

Hello, we've been checking this and we've found the radar target indicator limits are correct and it's working as intended. The situation you are describing comes from the 2D display of a collimator sight and is actually present in all DCS modules. To sumarise, the target mark limits are beyond the instantaneous sight FOV with the default head position. If you move the pilot head forward or sideways (depending on target position) or use VR, you should be able to see the orange square in the limits of the HUD.

Hello, we've been checking this and we've found the radar target indicator limits are correct and it's working as intended. The situation you are describing comes from the 2D display of a collimator sight and is actually present in all DCS modules. To sumarise, the target mark limits are beyond the instantaneous sight FOV with the default head position. If you move the pilot head forward or sideways (depending on target position) or use VR, you should be able to see the orange square in the limits of the HUD.

Hello, It is a known issue, the radar shouldn't emit when in standby, hence why there is no interception symbology. We're working on it.

Hi, this was fixed internally a while ago and will be available in the next update!

Performance should generally better than that.

Hello! I don't know how accurate this test is but it's certainly not up to date anymore.

Hi! It's fixed and overhauled internally, will be available with the next OB patch.

Hello, You should worry about it, as it might lead to failures if it's on for a long time. In auto mode it usually works very well, have you made sure that the AUTO/MANUEL switch is on AUTO? On the other hand, if you're flying the EE I've just noticed that the HOT/COLD argument is inverted (which will be fixed), maybe that is contributing to the issue you are describing. If none of this helps, please provide a track so we can check what is going on. Thank you.

Good catch Brems, fixed internally. Thank you!

The EE doesn't have a radio altimeter. That reading comes from the barometric central and it's limited to 1900 ft.

Reported and fixed internally. Thanks for the comment tho!

Regarding drift: Absolutely, it's what will cause a coordinate error un the long term and it's a separate and distinct error from the alignment error. This part is still being worked on but accelerations should play a role on the magnitude of the coordinate drift.

Okay, to shed some clarity on alignment types. In all cases, the coordinates used are introduced by the user, that doesn't change with the type of alignment. The alignment type affects the gyrocompassing, the precision in which the real heading is established by the INS. ALCM means alignment from memorised heading (Cap Memorise), so as long as the last heading of the INS was correct and the aircraft has not moved since turning off the INS, ALCM is going to give the same results as ALN. ALR is fast alignment, which will have a heading error. Currently the error is too big in this mode and we're polishing the alignment to correct this. Nevertheless, a certain degree of error is expected in this mode, which results in the INS not guiding in the correct (shortest) route to the next waypoint. Hope this clears things and explains what you're seeing.

Essentially these are the right answers. You have to be careful with the throttle when at high AoA, going from idle to AB while having an AoA > 20-25º is very risky.

Noups, it is just leftover test code, sorry

Corrected internally, thank you for noticing!

Thanks, I'll send it to the 3D/texture guys to take a look at it.

Hi! Can you post a picture?

Works as it should. Clicking on it doesn't make it turn off in the real aircraft either.

It's the same manual as in Docs but we've uploaded it here because we hadn't deleted the old manual and it was causing confusion. Also some stable players wanted access to the EE manual and the corrected bombing tables, which are currently only present in OB.

Hi! ALCM works with the previous memorised heading, if it was not right (say if Enigma is not using the 'INS always right at start option' or the aircraft was moved with the INS not in NAV mode) then the end result won't be right. In any case, there's some issues in the alignment we're ironing out.

Glad it's finally working then. I don't think the solution was our doing, maybe ED's or just something else broken on the install that has been replaced by the hotfix. In any case, enjoy the EE!

The tables are updated in the new manual already. The problem is the old manual is also there in the same folder but it will be deleted in the next update.