AvroLanc

Rates tracking works by tracking a scene and then using the rate of change of line of sight to determine the slant range. Obviously it’s less accurate than laser range. And yes it’s debatable whether or not the coordinates generated would be sufficient enough for JDAM.

It can use an angle tracking / rates solution without a valid laser. Similar to the ARBS / DMT in the harrier. Although I'm sure the laser would be more accurate. Being WIP it's not entirely clear that this is indeed what's happening. I think we're missing some symbology.

The Hornet can create and store up to 9 Markpoints. To be honest, I would value improvements to the NAV system, markpoints / offset points much more than any new weapons at this point.

+1 Would be especially interested in thermal coatings and fuze types. Retard 1000-pounders would be a useful addition.

Haven't watched vid, but Super Search is when you use the HCU in DDD mode and pull the trigger to 1st detent. It will give you a +/-10 degree azimuth search using current bar setting.

I actually think the RTS RWS option next to osb 5 on the DDI should be a selectable option, when in STT. Currently doesn’t work. However it does when ACM is used for an STT. Pressing it should return the return the radar to search, similar to the undesignate NWS button. This is what jak525 was referring to.

The Mech nose fuze setting on a Paveway II pulls the nose arming wire for the 'thermal battery' that powers the guidance section.

Ahh Ok. Abort cues makes sense. Thanks. I believe so. Would be great if we could configure fuzing options on the loadout screen. Same goes for laser codes...... I believe ED plans to model the JPF and DSU-33 airburst for JDAMS. Will be interesting to see how they get loaded/optioned? (Seeing the old M904 mech nose fuze on a JDAM is just wrong)

This has probably been brought up before...but the VSI on the Attitude Indicator has a scale limit of +/- 5m/s, but the max vert. speed indicated is never more than +/- 3 m/s....ever.... This bug has been in since launch, can it get looked at?

Indeed. In addition, my question is what the significance of the pilot choosing/specifying between an electric instantaneous vs. delayed fuze in the SMS? Does the jet care? It’s not as if the ballistics will be affected by a timer function on a FMU-140 tail fuze? Always been unsure of this one.....

The common misconception is that AUTO is for level delivery. AUTO is perfectly capable of diving delivery, I use it 99% of the time. Combined with a radar slant range, or TGP laser range (ok, both not available yet), it’s preferable, takes away the human reaction factor when you mash the pickle during CCIP. If you’ve got an accurate waypoint elevation BARO ranging may be more accurate than RAD ALT, depending on terrain under release point.

Well not really, there’s no reason CCIP should be more accurate. CCIP is using the exact same inputs and calculations as AUTO. Auto should be more accurate when given a precise aim point, generated by the TGP or WP designate.

Ok, that's useful information. Thanks. Az/El sounds like a massively useful page.

Ok, so it might not be 'realistic'. But are you going to implement the realistic NCTR displays? If not, then a semi-realistic solution might be the next best thing.... Just thinking out loud.

Can I make a reasonable suggestion for the display of NCTR data. Currently, to view the NCTR ID of a hostile, you have generate an STT lock, SCS down to the SA page, to slew, or now 'Step' to the contact. Only then can the aircraft ID be seen, at which point you've lost seconds and your head can't be further down in the cockpit. Wouldn't it be more sensible to show the aircraft ID somewhere on the radar page. Maybe in the top right border. This would allow the quick and easy ID of a contact as soon as a STT lock is made. Since the NCTR displays are probably classified anyway, and since any solution ED implement for us arguably won't match the real system, it would seem a very sensible QOL thing to add. For that pop up unknown 10 miles in your face. Ala Mongo's Mig-21. IRL F/A-18's had NCTR displays well before SA pages were added anyway. Thanks.

Good decision. Effects and visuals can compensate somewhat for the lack of feel. Wholeheartedly agree.

I expect the visual (ie the actual flir image) to have to be adjusted to look right on the green monochrome DDI versus the A10’s colour display otherwise it’ll look odd. Different displays / resolutions etc. Not to mention the osb, menu symbology.

Expect symbology to be similar but with differences. I wouldn’t say the visual element is all there. That all needs coding and implementing correctly.

The fact that we haven’t seen a single screenshot of a TGP DDI display should be a big clue that the TGP is nowhere near complete. We’ve been given screenshots and info for almost every other new feature. It’s bizarre that it entered ‘internal testing’ and the end of May..... and the engineer responsible was ‘still confident of a end of June release’ a couple of weeks ago. Having said that, it’s obviously a massive task that they must get right.

Absolutely. Can’t see why this can’t be implemented relatively quickly? Same goes for additional HOTAS functions like swapping HSI/SA/EW , etc.

No timeline yet. But when there is, it's planned for not promised. Then add 6 weeks + another OB cycle or two for bug fixes....... It'll come though. Just have to be patient, ED have delivered so far.

Thanks I'll try. I should add that I'm getting between 2-5 mins of normal game play before the black screen starts.

Ok, so I've been using the Rift S in DCS for about 3 weeks. Yesterday I start having a problem where the rift goggles will black out for a few seconds initially, then a few moments later shows a complete black screen, that persists. DCS continues to run in background and tracking is still working as seen on my monitor. But goggles are black screen. Rift S work absolutely fine with other games and apps, so not goggles I assume. I've tried 2 different USB 3.0 ports now, with and without a powered hub. Any ideas? Updated graphics drivers did nothing.

Hot runway starts as well. Every spawn for me.

The TARDIS Tornado Advanced Radar/Map Display Information System, huge display didn’t get installed until a bit later. The early service Gr.4s (Iraq war timeframe), still had the old CRPMG in the back with a digital MFD map for pilot upfront. Storm shadow and Paveway III were early cool weapons. I’d still rather have a mature Gr.1 for some classic Tornado roles. And a Germany / Central Europe map of course.