AvroLanc

Not at the moment. It’s either BARO or RADAR altitude, determined by the position of your HUD altitude switch. Note the B or R under the HUD alt box when in AG mode. BARO uses the current waypoint elevation as the target elevation. The TGP laser should also provide the most accurate slant range/HAT, but this isn’t modelled I’m sure. The Air to ground ranging radar mode (AGR) should use radar slant range for HAT when it’s gets implemented. Likewise the Fixed Target Track mode FTT. Although a standard MAP radar NAV desg. will just uses BARO alt. This is all in theory, I’m not sure DCS actually simulates a proper HAT calculation.

The 1.2 s option is modelled. It’s called PRI on the DDI. There should be a secondary 4.0s mode when the FMU-140 is not installed. The MK339 fuze has only the 1.2 pri and 4.0 option modes. Strangely the 3D model has the mk339 fuze, while we have prox fuze settings. There’s a proper 3D model for the prox fuze in the DCS model viewer.

Yeah, I think it’s designed to be used in combination with a selected course line and probably the Coupled autopilot mode. You get a vertical FD bar for lateral guidance. You’d dial in a course and the FD along with the AP would fly the attack long that course. There’s a bank angle setting that can limit the max bank angle the AP can use to intercept. I think. I can imagine it only being useful in certain situations. Mine laying might be one. Laying a string of mines along a straight pre planned heading. Actually would be quite interesting from a mission variety point of view.....ED bring back the planned mine payloads?

Any idea when we might get the cross track error indication when in AUTO SEQ?

Sorry posted in wrong forum, but yes I’m talking about Raven One.

Yeah, been this way since release. It’s a bug that may get fixed once the Coupled Autopilot modes get implemented. Auto makes the most sense in Coupled mode anyway. There should be a cross track error indication in Nm at the HSI bottom right (In Auto SEQ) as well.

Really enjoying the campaign, so far on M3. One thing I've noticed for all missions so far.....the timestamps given in the briefings don't match up to the real time, either local or UTC, once in game? E.g. M3 has a 0800 start time in the briefing, but once in game it's 0600 UTC / 1000L? Am I missing something? It just seems odd. Otherwise excellent.

Mark points in the Hornet work like waypoints. You’ll need to switch to each mark and then Waypoint Designate each Mark point before you drop. So it’s a bit more convoluted. You only get 9 mark points too.

Absolutely. Some of the quality of life features and bug adjustments for AA radar modes would add more than another TGP with similar capability as the one we’ve got. Hopefully any work on the AZ/EL page will force/require/encourage some additions to the radar in general.

Just bumping this. Excuse me, not meant to be impatient or demanding. Santi - I assume you're still on top of these important missing features, now you have a more official role? Many of the bugs still apply today.

Yeah, good idea for possible expansion feature later down the road. The LST/NFLIR pod would offer a NAV FLIR display in the HUD. Which would be nice. (Not sure if ED will model the ATFLIR version). A two pod set up would be unique and would add flavour and interest down the road. The Skipper rocket powered LGB would be nice too.

+1 A ‘feature’ that was attempted but never really finished. I’ve made posts about this before, must have been about a year ago. I was told to wait for WIP to complete. It would be nice to have the TONE1 and TONE2 options as well.

PM'd some specifics but an available manual online makes a reference to NOT SOI being shown on both the FCR and WPN pages. As well as a TGP 'NOT SOI'. Nowhere is the HSD referenced as a candidate for NOT SOI. It's not a sensor, in the strictest sense. There's also plenty of pictorial evidence available, see pics. All the pics show other MFD pages as SOI, indicated by the white outline, note how 'NOT SOI' is not on the HSD. Although not all confirmed as USAF Block 50's, this functionality is so common throughout the blocks that I'd argue specific block version isn't an issue. See also this vid. Some good shots of HSD, Not Soi is absent. Have the team positive evidence that it should be there? Cheers.

In the lastest OB, the F-16 HSD included a 'NOT SOI' (Sensor of Interest) message when the HSD hasn't been made priority with DMS down. This is incorrect I believe, no 'NOT SOI' should ever be shown on the HSD. It doesn't match any documentation I've ever seen. Since the HSD is not a 'sensor' then this message should only apply to FCR, TGP, HAD and WPN page. No track attached since it's pretty obvious.

The cold start procedure hasn't fundamentally changed. On the ground put the INS knob to GND and wait approx 8 minutes for the 0.5 OK status, and then put the knob to NAV or IFA. INS DEGD message probably means you didn't wait for the full alignment, or you haven't put the knob in IFA.

I don't think the close range issue is really an issue, more of a limitation of the tech it's simulating. Remember, in the time frame when the Air to Ground radar was most useful, you'd be rolling in pretty close with dumb bombs anyway. You'd be close enough to make a final precise targeting adjustment. It's only now with AESA SAR etc that aircraft like the F-35 can make detailed SAR images from standoff ranges, to attack with a stand off weapon.

What about intentionally entering a wrong LAT LONG for WP 0 and aligning off of that. It should show consistently wrong aircraft position (assuming no GPS) for the duration. I'll try but I suspect it's not coded that way yet. All the same. Nice changes. Maintain momentum everyone.

I think you can just ignore those defaults as listed in manual for now. I use the SET function to configure how I want it once airborne. This looks like something to be included in the data cartridge functionality ED has planned, but the work around is easy enough for now.

Just beginning to get hyped up with the upcoming KW. Will the simulation include any functionality for the IDM or ATHS system datalink? I've not dived into the system specifics yet, but my intial understanding is that on the KW the main use is calling fire support missions? Both airborne and artillery. Does it provide a team member/wingman position or target handover capability? Will this be featured at all? Could it integrate with either Combined Arms or MP?

No sorry, not available yet. I meant it should come later during EA.

I mused on this awhile ago, but it got little attention. From what I can see the Hornet doesn’t possess the ability to transmit a markpoint as a permanent location record. (Unlike the F-16 and A-10). It looks like the current designation can be sent to be displayed on the SA page. This from all 3 team members. But of course it will only be displayed as long as the designation is maintained, if you see what I mean. Unless of course the SA page has the ability to store a markpoint at the cursor position......which would be most useful.

Well it’s unusable in two of the flight profiles they've chosen to implement (med and high). It needs adjusting to be more logical. A descent to a much lower search altitude a short while before coming active.....

Good news. But I noticed that CZ doesn't highlight when a slew is in the system. My understanding is that CZ should highlight (similar to SP when Wags selects that), to show a slew has been made. Otherwise it's difficult to recognize the need to Cursor Zero. Thanks.

Lol, the actual thread topic was hijacked by a simple switchology question. I’m surprised the 60 flare issue hasn’t been addressed before. Considering the Hornet has been stuck with 30 since release. There appears to be a big inconsistency in modelling logic here.

Yeah less than impressed with that. I'd go with pizza, extra toppings if you can dig around and find the answer to my question, or at least stimulate some discussion......