BarTzi

Should have been ATFLIR from the beginning regardless of the new IR tech state.. oh well - nothing we can do.

I want to start this thread by saying that I have no intention to break rule 1.16, so I will not provide any documentation here. As seen in the recent video posted by Wags- scan centering defaults to 'manual'. You have to set it to 'auto' yourself. -> Additionally, if you lock a target with STT and then switch to TWS - the radar should be forced to auto-scan centering (around the now L&S target). Is this modeled/counted as one of the TWS features, or planned to in the future?

Imagine if they manage to tie it up to some VR controllers. That would be fun.

I second this. It's a very important addition, and I wish ED could share more information about the deck crew night ops. (The pessimistic me say - if it wasn't on their trailer it probably does not exist)

TWS != complete Hornet A/A radar. They have a lot more work on the other A/A modes as well.

What was the format you used? did you use 'precise'?

It's the TGP that was released super half baked - not the Hornet itself. There was silence on that front (TGP) since it was originally released, but that's probably because of the priorities at that time (Viper)

It's going to happen sometime in the future. ED said December will be a great month for the Hornet, and that TGP improvements are planned. Personally- I would like to hear about: -Slave to target and CZ -Missing symbology such as: coordinates, range, scale, airplane orientation, north arrow -HUD symbology -Status of SP and A/A mode

+1 - came across this bug report after reading the same paragraph in NATOPS, and there are indeed a few inconsistencies with the way the switch behaves: 1. When you start on a carrier, hook bypass is set to 'carrier' and is held there - which is correct. You should not be able to move it from 'carrier' to 'field' until you have power. 2. When you start on an airfield (no power) - hook bypass is set to 'field' and this is not correct. If you then move it to 'carrier' it will be held there, which is the correct behavior. The logic is correct - the initial position of that switch, in that case, isn't. It doesn't matter where you land- when the plane has no power it should move to 'carrier' 3. Hook bypass should automatically move to 'carrier' when you deploy your hook (you should not be able to move it to 'field' again when the hook is down). This doesn't happen all the time. If you start in the air, and hook bypass is set to 'field', it won't move to 'carrier' when you deploy your hook initially. You have to first toggle the switch to 'carrier' and then back to 'field' to make this happen. (This is displayed in the track I attached) It seems like something with the initial position of the switch messes up the logic (which is correct). Hook bypass.trk

Do you have a source for that? I believe they have plenty of resources to model the basic functionality of the pod (FLIR page had half of the ATFLIR symbology before the LITENING was added). Didn't they say that they want to introduce it with the new IR tech they are working on?

I don't think they ever changed it. They wrote it won't be functional, which is why I'm asking, just to make sure.

It might have it in real life. ED did a good job detailing in the manual itself which features are yet to be completed. They did go over datalink in the manual and chose to write that this functionality will not be available, and not that it will be available later in EA. This is why I'm asking. Also - I'm not sure the Viper has this capability in DCS (Wags did not demonstrate this in his video). We will have to wait for the update to drop.

Forgive me for bumping such an old thread, but since the manual states that: "The option select window of AIC, F/F1, and F/F2 will have no function", does that mean that we will not be able to create a flight from aircrafts that are not grouped together in the mission editor?

Can you share some info on that? I have no idea what it does.

You are setting yourself for a disappointment. The new Viper features are complex and can also introduce new bugs/instabilities to the sim. They will still need to squash/sort those before they start working on any new Hornet features, and this will probably take more than a week.

Why are you so triggered by the A/G radar? It's not the silver bullet to solve all problems in the sim. If you fly the Viper I think that's the last thing you should be worried about right now. It's amazing to me how you guys decide that ED has been working on it non stop for five years just from a very old and almost irrelevant screenshot. Also, keep in mind that they informed us the engineer assigned to it left the company and they had to find a replacement. So no, they most likely didn't work on it for five years straight, and that's understandable. They also don't have a particularly big team to rely on, so that's something to keep in mind. At that time (2015), no module in the sim would benefit from it. So you can say they didn't really have to push it forward and go out of their way to make it happen. Now they have two modern airplanes in early access, and it is most likely coming down the road. If I had to take a guess- they want the planes to reach a certain level of maturity and have a fully capable and complete A/A mode for the radars of both planes before they even start integrating the simplest A/G modes. I see that you are coming from years of flying in other sims. It doesn't look like you understand the way ED handles EA products yet.

This is what you will see in the attached track: Using the hornet free flight mission, I try to modify WP1 which is at: N 41 55 98 E 41 51 78 I want to change just the second line (E) - to: N 41 55 98 E 41 51 60 However, when I bring up the WP entry mode in the UFC - I can't access the E or W coordinates. The UFC will register N (number 2) or S (number '8') first only, and only then allow editing the E (number 4) or W (number 6). This means, that in order to change just the last part of the coordinate, I have to re-type the first line (N 41 55 9'8'). Is this intended? WP coordinate entry bug.trk

Thanks. I missed that.

Some rotary switches don't light up when you turn on the internal lighting. The text around the switch will light up, but the tip of the switch itself won't, making it impossible to know the position of the switch without using NVG. Left console: Right console:

NATOPS. "2.9.2.1 Autopilot. The basic autopilot (heading hold) is engaged by selecting the A/P pushbutton (at which time pilot relief options appear on the UFC) then selecting the ON/OFF pushbutton. Engagement is indicated by the A/P advisory on the DDI. Selecting the ON/OFF pushbutton is not required if ATTH, HSEL, BALT, RALT, or CPL (MC OFP 13C AND UP) option on the UFC is desired. At this time the aircraft maintains the existing pitch attitude. If roll attitude is less than or equal to ±5° at engagement, the magnetic heading is maintained. If roll attitude at time of engagement is greater than ±5°, the roll attitude is maintained. The pitch attitude hold reference can be changed with pitch CSS to any value between ±45° pitch. The pitch attitude reference can also be changed with the trim switch on the control stick at a rate of 0.5°/second. The roll attitude hold reference (if roll is greater than ±5°) can be changed with roll CSS to any value between 5° and 70° of roll. The roll attitude reference can also be changed using the trim switch on the stick at a rate of 2°/ second. The magnetic heading reference (if roll is less than or equal to ±5°) can be changed, or initially set with roll CSS. The roll trim switch also can change the reference magnetic heading." Also from NATOPS: "The automatic flight control system (autopilot) has two basic modes: pilot relief and data link. The pilot relief mode consists of heading hold, heading select, attitude hold, barometric altitude hold, radar altitude hold, control stick steering (CSS) and coupled steering. The data link mode consists of automatic carrier landing (ACL), precision course direction, and vector approach." @imacken @daarseth, please read this comment and the previous one. Clearly shows when it holds heading and when it holds the roll. A/P advisory should not be on when you select an autopilot mode using the UFC. It should only be displayed under certain conditions. Let's shift the focus back to the bug report.

It's called heading hold. That's the official name for it. This is what heading hold does: At this time the aircraft maintains the existing pitch attitude. If roll attitude is less than or equal to ±5° at engagement, the magnetic heading is maintained. If roll attitude at time of engagement is greater than ±5°, the roll attitude is maintained. The pitch attitude hold reference can be changed with pitch CSS to any value between ±45° pitch. The pitch attitude reference can also be changed with the trim switch on the control stick at a rate of 0.5°/second. The roll attitude hold reference (if roll is greater than ±5°) can be changed with roll CSS to any value between 5° and 70° of roll. The roll attitude reference can also be changed using the trim switch on the stick at a rate of 2°/ second. The magnetic heading reference (if roll is less than or equal to ±5°) can be changed, or initially set with roll CSS. The roll trim switch also can change the reference magnetic heading. This is what ATTH does: Attitude hold is engaged by pressing the option pushbutton next to the option display window displaying ATTH. Engagement is indicated by a colon in the ATTH option window. At this time the aircraft maintains the existing pitch and roll attitude. The pitch attitude hold reference can be changed to any value between ±45° with pitch CSS or with the trim switch on the control stick (0.5°/second). The roll attitude hold reference can be changed to any value between ±70° with roll CSS or with the trim switch on the stick (2°/second).

Like most cockpit switches- I use my mouse. It's not a hardware issue (I checked that before posting. Watch my tracks to better understand this). As I explained before: engaging RALT outside the altitude limitations and BALT under certain conditions activates another autopilot mode. It should not do that. @imacken in-game at the moment it will behave almost the same as ATTH.

Exactly- and thanks for helping me explain this. The problem is I end up in heading hold under certain conditions when I choose another autopilot mode. The easiest way for you to test this is to try and engage RALT above 5000 feet and see what happens. No colon will appear next to RALT, but 'heading hold' will be activated (but it will also make the stick a bit stiff like it does when you try to pitch when BALT and RALT are activated). @Arctander - great track showing that issue :)

You are setting yourself up for a disappointment. You are exaggerating the capabilities and usage of the A/G radar. It is also very hard to develop and I would not expect it anytime soon. Most likely one of the last major features for the Hornet \ Viper.

@BuzyBee Not sure if this was mentioned here - can you use instructor mode to change the time of day within a DCS session?