All Activity

Since MSI update, hornet radar is super borked. NWS does not swap L&S and DT2 designations in TWS or RWS mode, nor cycle through valid tracks if no DT2 selected. There doesn't seem to be anyway to select a target other than the currently selected MSI L&S. I've had some luck spamming the hell out of designate over the DT2 but it's unreliable. To reproduce: playtest the hornet radar for literally any amount of time. Track file N/A. This isn't on the list of known issues...how was this not caught before release?

We'll check this again, and fix if needed

We'll check this again, and fix if needed

Hey guys, I just built a new system and now I´m on the lookout for a new display as well. What are you guys running .. any recommendations in the 4k / 27" range? Flat or curved? Not really sure what I want as there are so many options now. I´d also use it for 3d work and image editing etc. ..

We'll check this again, and fix if needed

Hi, Anybody else fly the Huey with a FFB stick? Isn't there an issue with latest build? Seems there is an issue with the virtual spring feature, the stick feels too soft now, and force trim does not work anymore. Thanks

We'll check this again, and fix if needed

We'll check this again, and fix if needed

We'll check this again, and fix if needed

We'll check this again, and fix if needed

We'll check this again, and fix if needed

Thanks for responding!

We'll check this again, and fix if needed

We'll check this again, and fix if needed

We'll check this again, and fix if needed

We'll check this again, and fix if needed

Ok, we'll check and rectify if needed

Hi, we double check this again

We'll see what we can do when we have time 🛠

Hi, we'll take a look when we have time

Hi, we'll look into adding it

If you disable the call for cabin altitude <11,500 feet that would fix the situation where the call is made if you dive below the cabin altitude and it takes longer for cabin altitude to catch up than the current jester logic.

Survival rates from ditching did improve dramatically during the war, above all by planning and integration with surface rescue craft. However, early war, rates were pretty diabolical.

While I agree with you on the state of EA of ED modules, let me play a bit of devil's advocate here, since I think a part of the community has some blame here too. When the F-18 launched in EA, ED's plan (as per Wags - and I'm going off memory here so I'll be paraphrasing) for Early Access was to release a module with the basics functioning, at a point where everything that would be needed for a RL young pilot to start training on the type would be there, and then develop weapon systems and advanced avionics as time progresses - in the order it would be presented to a new RL pilot. But then came the community and they complained they couldn't blow stuff up... My personal priority for early access would be 'aviate-navigate-communicate': have a good flight model at EA launch that only needs minor adjustments, have all the navigation tools working (at least TACAN, ADF, manual waypoint/flightplan creation, etc), and have the radios in working order. I really don't care about weapon systems at that stage: I want to practice take-off and landings, fly the pattern, get used to the in-flight behaviour, do some in-flight refuelling (if available in that model), do some basic navigation and free flights. There are plenty of other modules available to please those who want to "blow stuff up" in the meantime (though that was less so when the F-18 first launched). Part of the community wants everything to work properly on day 1 so they can do their Rambo-style "you and what army?" scenarios immediately. And as a result you have the module released in a half-baked state with a lot of systems sort-of working, sometimes, on a good day unless there's a full moon and Mercury is in retrograde - and the community starts complaining again... That, and a lot of people expect every module to be as detailed and in-depth as the A-10, and for some reason only ED knows, that is not the case (not possible?). While ED claims to have a "standard" for EA and post-EA, when every module has a different "standard", clearly the word "standard" means something different for ED than it does for a lot of the community. So here we are... And the more modules there are in EA at any one time, the larger this problem becomes as it becomes a juggling exercise for ED... Do I like this? Nope, but I'm part of an old-school minority and I suppose from a business point of view you can't blame ED for trying to please a larger part of the community so they can keep their finances in order...

I have the same problem. if you put your pod in snoplow mode, do you have the same bug as me ? (one post below)