I think the goal for the NXi is 1ms loop time. I would imagine it’s slower than that currently. The RXP units currently run well under 200us. So while I’m sure there is some flexibility added with JS (I admit to being ignorant as to exactly how much flexibility, if any), I don’t see any performance improvement. In fact, it is a step back in performance.
I seem to recall that they confirmed it will not be 1:1.
If you are talking about yourself, I wasn’t referring to you, rest assured. But I have seen plenty of toxic people on both sides of the aisle, I will admit.
First off, and most importantly, this topic is not about the RXP Garmin units themselves. This topic is about the developers opening up communications with @CptLucky8, who has spent the last year and a half sharing his knowledge freely on these forums. From my point of view, @CptLucky8 should have been way up there on the consultants list for SDK decisions, but that’s just me.
Secondly, everyone took note of those features. Seems like the only people who let them “slip as if unimportant and without anyone taking note” are the devs themselves, who not only have not implemented them, they haven’t even said they are considering looking into implementing them.
I’m sorry, but I disagree. The only boundaries being pushed here as far as I can tell are scenery generation and graphics. And while AI scenery generation has not been attempted on this scale before (as far as I know), the graphics are kinda outdated for a game. Maybe even for a sim. I think X-Plane might have the edge in terms of graphics engine. Everything else (and I really do mean everything else) is a step back from existing flight simulators.
Isn’t that the approach employed by the devs? As far as I know, they want to make addon development available to as many people as possible, so they can work happily together and make the best simulator in the universe. That’s not me saying that.
Another thing I have to disagree with. While there certainly are new features that are improvements (despite my previous statements, JS/HTML, for example, is an improvement and a good thing to add to the simulator), for some rules no valid explanation was ever given. For example, no explanation was ever given for why third party developers cannot override the flight model. No explanation was ever given for why third party developers cannot inject weather into the sim. And no, saying that Microsobo want to have control over those features is not an explanation, and it’s certainly not one that implies everything fails without it.