amalahama

Don't worry, you will be able to pay 70$ for another unfinished early access module from ED soon.

I don't understand, it works fine in the Ka-50, it shows the elevation lines...

My feelings share with many in this community is that we have more modules than we can master in years, however we would pay to third parties providing a proper "context" to use them (e.g. terrain and AI assers). This is a business still to be explored

It will come eventually - in the meantime there are so many basic features that needs attention so badly!

Yeah, OFLY position update looks like the clumsiest way to update your INS, I don't understand why there is no a Radar or HUD INS update mode. It seems there is something missing in the functionality

So we are forced to perform INS updates in modern fighters too.

Out of curiosity: if I select INS as only source for navigation, would eventually drift? Would it be necessary to perform P.U. in order to keep navigational accuracy?

Maybe, IDK. IRL, it's not really a HW computing power limitation or something, but more related with a rough, rush low cost Litening integration into the Hornet system.

It's not related with data quality on the Hornet. It's just not realistic for the Litening and how it's been integrated in the a/c. You are facing same challenges as RL pilots did. Hopefully soon however, with the AG radar and markpoints, it would be a bit easier to point the pod to the location of interest

At least as AI, yes. Flyable I highly doubt it

Hi everyone, I have the impression this module is almost there, but broken stuff like broken AA radar, incomplete INS functionality and other minors features missing (synthetic runway full implementation) impedes the full experience to many. Why don't Razbam just put on the table the resources to finish off this module and keep people happy?

Hi +9999999999 to this Maybe it doesn't have to be the full SDK, but just those bits that allows proper interaction with the core - even if modders must still have to program most of the features. Or it can be released for educational / non commercial use only. Having to sign an NDA for having access to the API is madness in my opinion. Best regards

I'm quite confident that route lines don't overlay OSB labels...

Nice. However JSBSim is a multipurpose library and probably quite heavy, not well suited for carrier operations, plus they need access to ED SDK anyway to bridge the library with the FM. Not sure whether it's the best option, but hopefully they will find the way

Fair enough, a Mig-29A is not a proper opponent against modern F-XXs

Why people keeps referring to 1.5.6 when it was obviously an OP mistake?

We only want the knob animated, we're fine with the previous pilot leaving the aircraft properly set (so kind!)

Please make it available through Spotify!

Hi Compared with that other modern combat flight simulator, the AI asset portfolio pales in comparison. We need A400Ms, C-27Js, C-295s, A330 MRTTs, F-22s, Eurofghters and Rafales, Gripens, J-10s and others that populate our virtual skies. Does ED have a real roadmap to implement those? Might we help somehow, via paid AI asset packs?

When will AFM be implemented in this bird? Thanks

I rather prefer the early 2000 timeframe - JDAM/JSOW, Link 16 being in their baby leaps but still far from god's eye sensors of today, and documentation seems reasonably accessible without getting into trouble

That something as trivial and important as TOT is still absolutely missing is a hint on the real status of the module

+9999999999999999999999 It's one of those immersion-killer bugs that the M2000 still has after I don't remember how many years

My bet. No

It would be great. It's one of the most shameful bugs currently online in the Harrier. Getting CCIP/CCRP right with winds is closely behind