AvroLanc

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.

I've never ever seen AI wingmen generated contacts on the TID. I've definitely got the F2F mode and correct freq (300MHz) set. The wingmen ownship symbol shows, but no datalink contacts ever get pushed to the TID, despite my AI wingmen having radar on and calling out contacts... Are we 100% sure this is working and has anybody seen it?

With the exception of the added FLIR and GPS, an early Gr.4 is essentially not much of a leap forward over a mid 90’s Gr.1.

At a slight tangent to original problem: The AUTO option should enable a sequence cross track error indication in the bottom right of the HSI. This should be similar to the course deviation error when using the course knob. Course deviation shows the nm error followed by a C. For example 0.5C, 1.7C etc. This is correctly modeled. However, the Sequence deviation should show the nm error followed by an S. I.e 0.3S or -1.6S etc. There's no sequence cross track error indication currently modeled or displayed. Mentioned because a dev might be reading......

The true Tornado experience would be Gr.1, low level, bad weather, TFR, e-scope, offset aim point bombing, dumb bombs, low level lofts, JP233 etc. The sim of my dreams. And the most likely to happen. However...a Gr.4 with Brimstone, Paveway IV, Link 16 etc would be an awesome complement to the Hornet and Viper.

+1 that would actually be useful.

There's a new bug with the TTI 'Time to Impact' readout on the HUD. Not sure how long it's been there. When dropping in ripple mode with an interval set, the TTI in HUD shows a huge unrealistic time for TTI. Values such as 80-95 seconds are seen. However, dropping without an interval set ie. in singles or pure pairs, the TTI timer is correct. See attached track. I drop with an interval first and you see actual bomb impact with some 83s TTI left. The next drop is with a pair with no interval and the correct TTI is seen. Thanks. F-18 Auto TTI Bug .trk

Auto wing sweep never cleared for use in service AFAIK.

It's been like this since about 2 updates ago. ED changed something and it broke the lights. Hopefully HB can successfully liaise with ED to bring the lights back to how they were. It would be nice if we could get an status update from them. Two OB updates down the line and not yet fixed.

It isn't supposed to. Using the TCS for any kind of bombing is a 'gamey' cheat and isn't realistic.

Logic would say it should. At least me and you would design it that way. The manuals I’ve got aren’t clear on the HUD LTWS display. Maybe ED knows better but maybe they’re guessing too.

Ok thanks.

Thanks for the update. But can you say why? Others F-14 items wit higher priority? No dev time at all? I think we’re all looking forward to polish on the Tomcat. Details make the sim.

Yeah sorry I didn't mean to doubt you or anything, but I can't get it to work. I consider myself pretty confident with how the systems work, or at least supposed to work, so this little thing is frustrating me.

I'm using a TM WH, with no special mapping. Not having a problem in other press and hold functions. Doubt this is it tbh. Are you 100% sure you can repeat a multi QTY drop (with 1 pickle and hold) with the latest patch?

Yeah, I'm familiar with the new method of loading up to 6 PP into each bomb. The problem is that despite QTY boxing up to 4 STAs (with different TGT's in PP1 programmed in all) and holding the pickle button, only 1 Station will release. Tested twice now with JDAM.

I'm not sure that the QTY option is working as you describe. In fact I'm not sure of it's function at all now. Before, when the 'old' way was modelled. You could ripple 4 bombs on to 1 target using QTY. Which seemed logical. Now, I've just tested QTY 4 with 4 separately PP targets and I needed 4 separate 'pickles' to drop 4 weapons. I could have achieved the same with QTY 1 as the system auto steps to the next station anyway. I'm not sure what, if anything, 'QTY' selection does now. And, right from the start, didn't Wags insist that rippling 4 weapons onto 4 targets with 1 pickle wasn't possible IRL?

+1 Can’t be hard to add surely?

Since Jester has had the ability to use both TWS and RWS there is a new annoyance. It used to be that the player could enter the RIO pit and set up a 40 degree scan in TWS, return to pilot, and Jester would maintain that 40 degree scan in TWS. Now the default for TWS is locked at 20 degree scan - and Jester will set it back to 20 degree when you return to pilot. Not what I want... There appears to be no way of maintain a wide scan in TWS. Also he scans RWS at 40 degree / 8 bar. I would like 40 / 4 bar.... Any way of having these options in future?

I'd like to be able to read the RIO's push buttons again.