AvroLanc

OB 2.5.6.50726 JDAM flight times are still not calculated correctly. Strangely, they appeared to work in Wag's recent video....any chance we might get this build? Upload of 3rd track on this issue below. JDAM TTI Test 2.trk

No one’s claiming that the LGB nose fuse is an actual fuse....but there’s a wire connection to the nose fusing mechanism in the pylon. When that NOSE wire is pulled upon weapons release it starts the battery that powers the guidance unit. The nose fuse option needs to be selected in cockpit in order for this to happen.

I’m not 100% certain for LGBs. I know the nose arming wire pulls the battery start, and obviously the tail wire pulls the fuse in the tail (ELEC). Most aircraft have options to set NOSE or TAIL or both. Hornet has MECH or ELEC. Does the Hornet know to pull the nose wire when LGB is used, even with the MECH (nose) selected OFF? Might be a bug if my logic is correct.

Indeed. Do normal 'Unknown' tracks still have the normal proportioned staple shape? Haven't checked yet... The new symbol may represent the beginnings of something new? Ground tracks? Although I was expecting those to be X shaped, if other aircraft's implementation are a reference.

This is correct in sim. Only one fuze is needed, they’re independent. Two for redundancy. I think incorrect is MFuze for LGB. In RL MFuze should need to be on, since it pulls the start wire on the guidance unit battery. Without it, it goes dumb. Would be nice to see this changed. Edit: Although I'm assuming here that Hornet logic is Mech Fuze is always Nose Fuse and Elec Fuse is always Tail.

It was certainly used during Operation Deliberate Force, in 1995. Datalink performance was bad apparently. Frequency interference issues with F-15E's using GBU-15s. It seems strange that a weapon with 54nm range, only has optimal datalink range of about 40-50nm. Maybe this was a by product of using a 'off-the-shelf' Walleye datalink?

Ok for this issue, please see the attached track. First drop in AUTO TOO and the predicted flight time is something like 39s. Actual bomb TTI is alot longer. Second drop in MAN TOO and flight time is predicted 1:40s. Bomb impacts well before timer expires. These 0:39s and 1:40s seem to be hard coded - all my drops show one of these two figures. Could actually be fixed, since Wag's JDAM video shows correct behavior. Did it make it's way to our OB build? or did it break since? JDAM TTI Test.trk

We haven’t got SLAM-ER yet. Original SLAM doesn’t TF.

My point still stands. Inherent limitation of how RL Hornet deals with GPS weapons. Needs a tweak to datalink page switching, otherwise it’s ok.

This is correct if SLAM follows the same logic as JDAMs. Unboxing SLAM will de-power all weapons with a restart needed... However, selecting another weapon without touching the SLAM button won’t, I.e. you can have SLAM powered up and use hotas to bring up AA mode and Aim-120, and SLAM will stay aligned. The problem we have I think, is that there needs to be a DL13 datalink page on the main TAC menu in addition to one via STORES. This would avoid having to power off the SLAM when resetting the datalink for the next missile.

The backup ICS should be working, at least it was a few weeks ago. I triggered a failure of the primary ICS using the ME failures. Jester came through very quiet and muffled after failure, swapped over to backup and it was back to normal. I was surprised at how well such little details are simulated.

Make sure you weren’t trying to change code with the TRIG option boxed. This may prevent code change.

The new TGP are among the most useful changes in the recent patch. Proper tracking modes Flashing LTD/R HUD LTD/R and L ARM status HUD FLIR track Time to Release and TTI on FLIR page All add to experience of using pod. Thanks. Just need to sort lighting issues and JDAM TTI's...... Keep up good work ED.

No it's not normal. FLT times still don't work. However, it seemed to work in Wag's recent JDAM video. To the exact second. He was either using a newer build where it's fixed, or a bug crept back since then. The pre-drop times are not being dynamically changed, whereas in Wag's video they are. Can you provide a track. It'd do it, but schedule is tight today.

Well yes, the persuasion or argument is needed because they’ve so far ignored every comment on the issue.....

Yeah, I think there’s sufficient evidence that it was a capability for our era of Hornet. It depends whether ED feels they have the depth of technical docs to support it. I’ve changed my mind on this, it would be an awesome addition. The argument from us need to be that it’s implementation will enrich many modules...... A10c II could benefit from VMF coding as well and F-16 has a similar thing with IDM CAS messages.

Can confirm, looks like pilot only, but it makes it extremely difficult to read lights. Especially caution panel.

Good, ambitious plan though

Why has nobody asked about the specifics of a Suite 4+ aircraft? What era/timescale does this represent? Isn't the RL strike eagle up Suite 10 ish by now? Suite 4 is much older anyway, is the modern UFC appropriate for the bulk of that Suite's use era? What does it offer over the analogue one? The classic strike eagle UFC is the Analogue, we won't see enough of the latest avionics to make the Digital version seem current/immersive.......

My sympathies also. More clarification on patch notes would be good or even, dare I say it, additions to the manual, would be most welcome. It seems the normal Wags video was missing on this too. Referencing the real world manual is a minefield of frustration too......too much missing in DCS. My guess is that ED know these features are far from complete and won't do a video until then. I think even a mistake was made with this build, and a dev (Mr Pitts?) came on here to apologise. Hoping for a more functional AUTO mode next week........

You need to be in AG mode and with the LTD/R switch on.

Ok, thanks. Since we don’t have any IZLAR showing at all at the moment, it’s hard to tell what what’s going on with relative IZLAR sizes, QTY or not.

Just PP I believe. But that was there before last week as well, multiple QTY with one pickle in PP has been in since beginning.

Ok, good news. Thanks.

Not correct. QTY can be and is used for multiple aim points at once. It works this way already if you have PP’s set up. The problem is the display of IZLARs and AUTO mode.