I appreciate the response and explanation and I hope my question wasn’t taken as an insult. I wasn’t even sure if my eyes were deceiving me hence the ‘is it just me…’ in my comment. Sometimes background, paint scheme, lighting, etc, can really change how things appear. It just seems to me in the two quartering front shots of the plane in flight that the nose seemed a bit more slender than I’m used to. Again, just curious if it was my perception and if anyone else agreed with me (note that they have not lol). It certainly matches the 3-view example you’ve provided. Really looking forward to these and the Baron in particular!
Edit: Also excited to hear that he’s been going with weightier controls. I’ve always felt that the controls in MSFS are too responsive as well so I welcome the change. FWIW, I feel like the Arrows have some of the best feeling controls in an MSFS plane so any closer to that would be awesome.
Hopefully this reply, from Nick at Black Square, might help alleviate some fears and put right some misconceptions. Have a read, some useful info for you all we hope:
While I have seen many threads that correctly group MSFS compatibility into “MSFS 2020 Legacy (ported)”, “MSFS 2024 Native”, and “MSFS 2024 Modular”, it is important to understand that the “modular” aircraft structure has no impact on the features available.
To quote from Asobo themselves, “There is no feature that is limited to modular or non modular only.” This modular structure is only relevant to how models and components are loaded in the aircraft, and does not affect user experience in any way. For the type of aircraft that I develop, there is little utility to the modular system, and it does not limit the features available to me.
The primary purpose of the modular system is to allow for reuse of resources between different aircraft, and different variants of the same aircraft. Supposedly, it also improves loading times and performance via LOD usage in larger aircraft. In some ways, I could argue that this actually reduces graphical fidelity by encouraging lazy reuse of ambient occlusion textures, and slow LOD switching. I know that many users are also not fond of the strictly enforced and aggressive LOD system, so I would not welcome it into the structure of my aircraft any more than is already required by MSFS 2024.
In summary, all of my aircraft for MSFS 2024 are “MSFS 2024 Native” and can support all new MSFS 2024 features. There is no technical difference between “MSFS 2024 Native” and “Compiled in MSFS 2024”. The “modular aircraft system” is only relevant to model/texture reuse, and particularly benefits larger aircraft.
I’m glad to hear that you’re all looking forward to the Professional Series. You can always find me on the Just Flight Community Forums to answer all your questions!
Someone here once wrote that there are two file systems that can be used, but both can be 2024 native. I’ll see if I can find that. I had the same assumption, which prompted the response.
Ah, just saw the post above mine that goes into more detail than I ever code.
The 20% discount for existing users is quite generous. I think I have some JF points to spend as well.
Good to know. I am referring specifically to the vertical speed indicator where the needle will not sit at 90 degrees. It seems to be pulled above or below the line by some magic force. Therefore, you are either climbing or descending, never level. I’ll check again once I install them.
EDIT: nevermind, I’m back to the old issue where 2024 won’t remember my control settings, so I’m not even going to try.
Sorry to bring this up here, but when will the Dukes and Starship be avaiable in FS2024-Marketplace? They are out for weeks now (on the Justflight-website) and still don´t show up in the Marketplace. And now there is a big sale for the highest rated aircraft, that also metions the Dukes for a discount and they are simply not avaiable. This is frustrating.
We’re as frustrated as you, no need to apologise. We’ve done all we can but there are issues with the ingestion process for the Marketplace, not just with those, but other products of ours too. We’re chasing and hoping for progress on a daily basis but to a point it’s out of our hands, sorry.
The marketplace is a joke. I have only bought items there which literally aren’t available anywhere else. The really good stuff is always best bought direct from the developers as their support is as good as their products are. If you really want something, why torture yourself by only buying it at the weakest, most unreliable outlet.
We’ve been told on several occasions that the ingestion process is a speedy affair. And what we hear from some developers is this is not the case. I hope they get your release pushed soon.
Friendly reminder that folks flying an Xbox have no choice of marketplace. This also extends to those of us who started out on Xbox (some of whom bought a lot of DLC) and now fly a PC. There maybe a lot invested in that MP content, especially now as some DLC can be upgraded at a discount to buying new.
I know at least one use-case was recently clarified and that’s items that are 2020-native must first go through the 2020 Marketplace process before becoming available in 2024, even in cases where it’s just a version update hitting your My Library and not the 2024 Marketplace itself (like the A2A Comanche). That shouldn’t necessarily apply to these aircraft, but it does explain some of the delays.
At times it is and at other times it isn’t. Since the 2024 products were included we’ve experienced a few problems. Problems that seem to take a while to sort out and remedy.
I know you likely can’t say much for NDA reasons but are these issues specific to 2024 like file structures and naming conventions, like PMDG has reported previously?
I’m in this situation. Bought quite a lot from the MP when on Xbox, now own a PC.
I’ve transferred quite a few things (including JF content) from MP to Contrail, but for some reason it is now not possible to transfer JF to Contrail, the option is no longer available, not sure why that is.
