BarTzi

Based on the placeholder LSO camera (it's based on a picture you can find online), I wouldn't call this feature (or hook touchdown) complete or even working.

I reported the same bug a few months ago: https://forums.eagle.ru/showthread.php?t=250571

It doesn't make it easier to code. Probably not a high priority item for the dev team at the moment.

The most official source is the Hornet manual. It says the D/L system will not be expended. We will have to wait for ED to confirm this.

No - Here is a screenshot I took now. You can clearly see the light is strong enough to blind you if you don't take the gain of the NVG down or remove them completely. You can also see it using F2 view. You have to have your external lights on for it to work.

It's in the game.. you are bumping a thread that was opened around the time the Hornet was released...

Sniper (from the F-16), 9X, Scorpion, proper implementation of JDAM (impact angle, azimuth), Complete JTAC overhaul and removal of laser code selection for GBU's from within the cockpit.

Can also confirm this - thanks for posting.

Are you displaying the radar on your left DDI?

This is what I usually do: Stay in LTWS -> mark L&S -> hit 'castle switch right' when you want to switch to STT -> wait a second and then hit PB-10 (top right corner of the DDI). One less PB to hit is always good.

Try to briefly get a STT lock. From there- TWS should be on PB10 (instead of the usual PB5). It will go to TWS with AUTO scan centering activated (which is how it's done in real life)

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.