Ok here is the key.
Can you confirm only “native” 2024 products can be offered in the 2024 Marketplace?
Because AFAIK the P180 by FlightFX is not the “native” version but the 2020 compatible with 2024 version and I could enable it in the 2024 Marketplace.
I, we all, thought you can either make your 2020 products available in the 2024 Marketplace or provide native 2024 packages.
Maybe your company only wants to offer the native 2024 package in the Marketplace but then is a Justflight decision and not Microsoft’s at this point I’m not sure which one it is.
At this point I’m not sure about these things:
We were told lies about what can be offered in the 2024 Marketplace.
FlightFX has rules that only applies to them and not other devs.
JustFlight is correctly understanding what can be offered in the 2024 Marketplace.
As far as we’re aware, and have confirmed with the Marketplace team, only 2024 ‘native’ packages can be submitted directly/specifically for the MSFS 2024 Marketplace. To be clear, by native, I mean a package built within MSFS 2024, not necessarily one that takes advantage of all the new features.
Where it gets even more confusing though, and not directly relevant to the point that I was originally making about our MSFS 2024 Marketplace releases, is that there is the option to let MS/Asobo port across the MSFS 2020 package, which a developer can chose to approve for a) access to existing MSFS 2020 owners via the 2024 library and/or b) release for purchase by new customers on the 2024 Marketplace.
Unfortunately, as far as we’re aware, there is no method for supplying different MSFS 2020 and 2024 packages via that method, i.e. the package that you submit for MSFS 2020 Marketplace, let MS/Asobo port and then approve for release in MSFS 2024, is identical on both platforms. At least in our experience, that significantly restricts you in that there are 2020 and 2024 specific features and approaches that we don’t consider acceptable on the other.
For that reason, we won’t be approving our MSFS 2020 ported packages for release to new customers on the MSFS 2024 Marketplace, but they should still be available to existing MSFS 2020 owners via the 2024 library menu, just with the ‘not creator approved’ tag. Presumably that’s the method used by the P180. Instead, we will be bringing MSFS 2024 native packages to the Marketplace, which will be free-of-charge to existing MSFS 2020 owners. In the meantime, you’re welcome to use the MSFS 2020 ported versions, but we can’t promise full compatibility.
Like I say, not a clear subject at all, and something we’ve taken time to fully comprehend here at Just Flight too.
Thank you Martyn,
This is so confusing for devs imagine how we feel as customers. It’s a disaster.
The direct effect at least in my case is that I will port my JustFlight add-ons that I bought from the Marketplace to Contrail so I can get updates faster and I can install them in 2024 and from now on I will buy directly from the JustFlight store.
I’m writing this just to let the people in MS understand how we feel as customers and the consequences of their lack of communication and confusing announcements.
I know they read the formus so maybe at some point somebody will reflect on this, one can only hope.
So as far as I understand, there are three types of aircraft which can work in MSFS 2024.
MSFS 2020 native aircraft: built in MSFS 2020 SDK, maybe featuring some compatibility fixes to make them play nice with MSFS 2024. Example: all legacy aircraft
MSFS 2024 native “non-modular” aircraft: still using the MSFS 2020 non-modular simobject structure but built in MSFS 2024 SDK; typically conversions from MSFS 2020. Example: Just Flight Vulcan, Miltech CH47D, Classic Aircraft Simulation Piper Cub*
MSFS 2024 native modular aircraft: using the new MSFS 2024 modular simobject structure, and thus able to use all the fancy MSFS2024 bells and whistles. Example: iniBuilds A350
`* the CAS Cub is available as a 2024 aircraft in the Marketplace already
So in light of this quote…
…I’m interested to know whether the F28 will be converted to type 2 or type 3? I guess both are technically 2024 native. Would be awesome if it was type 3 but I can imagine that’s a huge amount more work for devs, modellers, texture artists, etc, since the model needs to be broken down into modules, which I assume has a big impact everywhere. And also, I’m saying it would be awesome based on some assumptions that the modular format would offer better performance due to more granular handling of LODs - my VRAM is already rather overstretched.
Am quite tempted to pick up the F28 since it looks very cool and way more fun than modern airliners!
We are committed to, and are actively working on ‘type 2’ for all our 11 existing aircraft coming from MSFS 2020. Depending on the advantages and disadvantages of ‘type 3’, we’ll probably stick with type 2 for the new releases this year too, but that’s TBC.
The RJ, F28 and Hawk are effectively type ‘1.5’, featuring numerous differences from their 2020 versions, hence us keeping those separate from the type 1 that we release only for 2020.
Every developer has a different definition of what constitutes a MSFS 2024 compatibility update for type 1. Our definition is an aircraft that works seemlessly like it did in 2020, or better. Something we can’t achieve by sharing the same package across both sims.
Thanks for the clarity, much appreciated. I also love to see how JF are committed to supporting your products for the long-haul, that makes it so much easier to buy with confidence!
Besides modular models / LODs, do you foresee many advantages to “type 3”? From perusing the SDK documentation it looks like a much more complex beast to develop!
I think that’s something that we’ll only have the opportunity to fully assess once we’ve finished work on the type 2 updates for our 11 existing aircraft.
Our dollar price will always be higher than the Euro price and the Euro price on our website is €46.76. That’s also the price that we advise SM should be charging. When I check that figure from here (UK) that’s the price showing on their website. But for users in other parts of the world you see different prices.
There are different VAT rates depending on where the user is based. We’re not sure if SM use the current exchange rates for the £/$ estimates they also display on their page (but they all contain the same VAT rate if your country displays VAT).
In your case it looks like you’re a Rest of World customer, so you’ll only see USD on our site, but SimMarket will show ex-vat €/£/$ price points as ROW doesn’t pay VAT.
We’d obviously recommend and encourage buying direct from us but totally understand you purchasing from where you can pick up the best deal. Do remember that 28% off offer concludes on 10th April.
Thank you just flight because I love this plane and now I can’t wait for the f70/100
In VR cockpit looks a little bit weird , the six pack looks smaller than real and the yoke is tiny, if you look real videos you can see that the real one is bigger than this, but that’s only you can appreciate in VR.
Yes indeed. They said that it’s too time consuming/costly to implement and too few actually use the features or words to that effect. I’m sad to see it missing though, I’d probably have chosen the RJ over the F28 if I knew beforehand. But I still love and cherish the F28 because it is amazing in so many other ways.
We will come back to consider adding failures to the F28 in a future update, depending on the level of interest from the community, but yes, the lack of interest in the failures added to the 146 and RJ indicate to us that only a small minority of the community want that feature.
Note that the systems logic complexity in the F28 does mean that you can simulate failures in a sense, for example switching off an electrical generator, but that has to be done manually via the cockpit controls rather than automatically via failure logic, and can’t be random etc.
A simple (granted I don’t know how simple it would be to implement) random failure option would actually go a long way. With the ability to set mean time between failures from realistic to accelerated. I understand that working circuit breakers etc would be quite a bit of more work. I love what you have done with the F28 already
Sweet! 2.1 just appeared in My library in 2024. I could have sworn it wasn’t 2.1 when I enabled it, but it is now showing as 2.1 and I can see that it is when in the cockpit and looking at the EFB.
(This Marketplace/Library is pretty whacky when it comes to indicating updated content for 2020 add-ons…)
Hey JF, this may be moot since, I think, there is supposed to be a 2024-specific version and I’m using the 2020 2.1 activated via my library in 2024 (Marketplace customer), but what is the method for updating the navdata when using Navigraph? This may really be a question for them rather than you, but the Navigraph Hub has a specific update for the JF products in 2020, but the 2024 part of the hub does not.
Also, do I set up the SimBrief Downloader to place FPs in the same relative location for 2024 as I do in 2020? (I may have this answered for myself as I mess about…) (Well, no, there isn’t an entry for the F28 in the downloader, so I have no idea how that is meant to work.)
