AvroLanc

This was definitely implemented in the A10, probably still is if not bugged. Generating a markpoint with laser ranging versus not ranging (with exact same LOS) would produce two slightly different locations. Of course it was most noticeable with shallower lines of sight.

In the 2.5.6 Ka-50 the intercomm system is working regardless of electrical power being available. The 'caution tone' test sounds and the intercomm ground crew interaction (door closed) works with both battery power off and intercomm power switch off. Previously you needed the intercomm power switch to be on to enable these functions. It 100% worked correctly in 2.5.5, I tested it last week. Track attached. Many thanks. KA-50 Intercomm off bug.trk

It's now beyond frustrating there's no Hornet additions. It's clear that the 'so called' modern jet team' is working either on 'Warthog 2' for a USAF contract..... or is committed to other projects. It's beyond frustrating that 7 months after the TGP release, zero features have been added to it's functionality. Let alone other items mentioned. It's beyond frustrating that there's no communication regarding a clear road map for Hornet plans. No mini-updates for ages. Please be patient... Quite how this is supposed to be feature complete this year is anyone's guess.

This will happen if you’ve either got no navigation (waypoint, airfield, fiixpoint, or target) point selected or have the DH/DT switch set to the middle position. The trimmer command will set the current heading as the steering command in this situation.

A TGP is not a wide area search sensor, while a decent Air to Surface radar can be. While a A/G radar is less essential than it was in the 80's - both for searching for and finding the target and providing weapon aiming/ranging information - it's another tool in the toolbox. Even now airforces recognize we won't always be doing urban CAS against lightly armed insurgents i.e the last 15 years. A lot of effort is being made with current day AESA radars, that can SAR map large areas and use AI to auto ident and classify different targets. A/G radar is not dead. Our Hornets radar isn't AESA crazy capable but 100% should be modeled as best as can be. However, maybe JDAMs, INS/NAV, and A/A should get immediate attention.

I agree with this. I think my concern is what exactly will ED’s ‘feature complete’ state will actually look like. The weapons are not a worry. They are in a published list of features already. It’s the systems detail that needs work, a lot of work. What happened to improved JDAM features or actual INS or data cartridges. All features mentioned many months ago, that never saw the light of day? It’s time a short term roadmap is outlined with goals for the next few months. Otherwise we’re in a perpetual flexible ‘later in EA’ realm of broad statements. A return to proper Hornet (and viper) mini updates would be awesome. But followed through with real visible progress. Some simple low hanging fruit like e.g Markpoints would surely be a good start. Who sees Hornet V.2 in 4-5 years as the real feature complete state. Maybe harsh, but the past progress is disheartening.

I think the course line is automatically drawn in some situations, such as a TOO designation correct? Are you in touch with RAZBAM at all? This would be a super useful addition.

So I'm avoiding 2.5.6 for now...Can anyone answer... Do we get the original AN/AAQ-28(V) with the vent and hatches on the right side if we mount the pod on centreline still? and maybe the new 'cheek' pod with vents on left side if mounted on station 4? Are there two versions of the pod depending where you mount? Also, has the colour changed? It looks more grey than blue now. Cheers.

Has ED modeled a proper 3D mount/fairing for the TGP on STA 4? Or does it just unrealistically simply bolt on to the missile recess?

It’s only settable when airborne. It should be possible on ground as well of course. Bug that’s been there since day 1 of EA.

My understanding was that the HUD symbology was additional items such as; LTD/R and L ARM status (printed at top of hud, including flashing when firing) and the masking circle on HUD. PS, I made a post in this thread about HUD TDC function, which has been labelled and deleted as thread hi jack. Fair enough, but with the lack of a LOS symbol, HUD designating would represent the next best thing capability wise and the issue was directly related. It was intended as a helpful discussion point.

I don’t have a specific reference for that that I can post, but I’m assuming the team has got access to some reference material used to model stuff like CCIP and AUTO etc. I’d be very surprised if that same material doesn’t detail a TDC HUD designate function. It’s a pretty basic and simple A-G aiming mechanic. Note that the very same function will become essential if JHMCS air ground modes are added. Assign TDC to JHMCS with sensor select UP twice (once to HUD, twice to JHMCS), look to put aiming mark on target, TDC depress to create target point. Almost all issues that lack of TGP los symbol has are mitigated by HUD TDC designating.

This is not totally correct. You should be able to use the TDC to designate a TGT using the HUD in any AG mode including CCIP. It should work with pretty much any weapon as long as in A-G master mode. A press of TDC depress should bring up a slewable TDC diamond that can be moved on the HUD. Unfortunately it’s not implemented yet. Although it sort of works in AUTO mode for bombs only at the moment. It’ll be crucial for designating a visual target, since it’s the only way to slave the TGP line of sight visually. There is no separate TGP LOS symbol.

Agreed. Reported by me a while ago. Not response yet. https://forums.eagle.ru/showthread.php?t=257539

I’m not sure if it works, but it does in the Hornet TGP. Since they share similar code and are similar dev pace, then Viper one may.

IR Pointer. Visible through NVGs for marking purposes. Did you try to use NVGs with it on?

Excellent post Santi. Thank you for your effort summarising this. Hopefully most items will get addressed in time.

But I take it the Viggen will be feature complete with campaign and others bits......Q4 2019 and all that.

It looks like TOT calculation is wrong. At the moment the TOT feature is not predicting time of arrival at a waypoint. It merely shows you the difference between the CURRENT time and the fixed TOT set at the WP. This is not very useful. I would expect the TOT to predict ahead what time you'll arrive at the waypoint, and then compare THAT with the fixed TOT set for that WP. It's the only useful way to use the TOT ufc feature.... Is it known WIP?

I've had them working fine. It's WP's 36-39 for the 'channels'. Use PP1, PP2 etc as labels in ME.

Does the Master caution reset logic work correctly? In our familiar western aircraft a failure will occur and illuminate a caption on the warning panel or such like, this will then illuminate the master caution light. The master caution light can then be reset to extinguish it and re-arm the system for alerting of any subsequent alerts. What we see in the Thunder is a MC light (and HUD warn) that stays on the whole time a warning exists. It appears pressing it mutes the aural warning, but the light and HUD warn remains. It's somewhat annoying to have the HUD flash, but also I think it's inhibiting future warnings (and the aural)...Which is bad. Can this be how it works IRL? I'm finding some great little details built into this great module, but a lack of detailed systems manual is hurting.

I agree and my first thought on watching all the pre-release vids was to expect that... Namely, if no TRUE HDG is input during the countdown, the alignment will default to NORM or 'long/slow'. Unfortunately this doesn't appear to be the case ATM. You get FAST anyway. Maybe it's waiting to be implemented.

Yeah, but INS is not only used for position data. It's essential for attitude and velocity as well. It should take longer than 30 secs.

It seems only the 'Fast' alignment is implemented at the moment? How would you force the system to enter a 'Normal' alignment? and how long should it take?