Let’s be honest… you’re sharing your opinion, not (all) everyone’s. I get that you’re frustrated, and that’s fair, but a lot of us are finding real value in the sim, enjoying it for what it offers, and looking forward to seeing it (greatly) improve over time.
1 Like
Curious, what happened to “We think most of the add-ons will work from DAY ONE” promise? Well, that turned out to be nothing else but a pile of lies. The fact that this product was released without an SDK to facilitate the port overs is criminal in itself. My blood is boiling just writing this post.
5 Likes
Yeah, everything works for me. I just want some improvements such as LoD for Xbox and some bug fixes.
One of Jorg and Seb’s first commitments, in my opinion, is to get 3rd parties all the access and debugging tools they’ve been begging for since November. Then the sim may have a chance. Career mode is already stale; the same missions over and over with buggy default planes… hopefully they’ll have additional fixes coming and additional changes in career mode too, but please give our 3rd party devs a fighting chance.
1 Like
Personal Comments and Observations
Not exactly. The SDK was available to First Party Dev Partners first - because they had to deliver planes and other items MS commissioned for the launch. In the meantime, the SDK was fine-tuned and then released to General Public, which includes all other Third Parties. The timeline between that release and launch made it really tight for all other vendors to start re-tuning their FS’20 offerings. Some made it - Raul Simbom (FSReborn) is an example. His Sting S4 shows up as Enabled in FS’24 for his previous customers when their library is migrated. But that was a herculean effort on his part. Many of the popular products are, not coincidentally, made by First Party Partner Devs, who obviously had to service their Microsoft sim launch commitments first if they had them.
3 Likes
After the second msfs 2024 patch, all msfs 2020 content was set to disabled by default, this was to prevent some non compatible content from not allowing msfs 2024 to launch.
As a result, any msfs 2020 aircraft or scenery needs to be enabled manually via the msfs 2024 my library.
This includes all my aircraft offerings (FSR500, Sting S4, TL3000), the operation is quite simple, you go to my library, find the vendor FsReborn and enable the aircraft, this is normal, even when my products are fully compatible, this is still required because the 2024 marketplace is still offline and I am unable to sign the products off (as officially approved for usage and for sale inside 2024). Once the msfs 2024 marketplace opens, I will be able to do so, and people will also be able to buy directly my offerings inside msfs 2024.
In the meantime, people can buy these planes inside msfs 2020 marketplace, they automatically transfer to msfs 2024 and once they are enabled / activated in the 2024 library they will remain active.
The 3 aircraft works exactly as they did back in msfs 2020, no bugs, no problems (except for normal 2024 bugs) and fully functioning inside msfs 2024.
Hope this helps to clarity,
Raul
CEO FSReborn
8 Likes
In my eyes, this post reinforces the original point I was trying to make. FSReborn put in a “herculean effort” and made sure their products worked for their 2024 users. Some developers have done this but more need to do the same. Or, at least communicate some intention and timeframe for doing so.
Let’s support the ones trying to make 2024 workable/livable while politely reminding the others we need to them to move faster.
1 Like
If the problem is the complicated SDK, why not make it simpler to use? Or does the very nature of MFS24 make an easier SDK impossible?
Edit: or is it the fact that the game is so buggy make 3rd party devs job harder?
1 Like
SDKs by their nature are effectively recipe books, except they’re object oriented computer code languages. So, not really simplified no matter what.
Add to that the more Arcane 3D art work which is an entirely separate workstream and you have a very complex and technologically intense framework in order to build a SimObject (i.e., plane, airport, etc).
In order to mature FS’20 into '24, many things in that book had to change. And they’re still being developed, so add a bit of concurrency into the mix.
TL:DR there’s no simplifying how to make content for the sim.
I think you are missing the many points given here in defence of the third party devs. Just because some devs have products working that doesn’t simply extrapolate to they worked harder than the ones who don’t. It’s really not as straightforward as you are making it out to be. You can support who you want for whatever reasons you want but I’ll continue to support devs that make good products and provide good support. We’ve seen what rushing things out does and I’d rather show patience and allow them time.
This gotta have everything now mentality rarely helps.
1 Like
Raul had his motives to move at the pace he did. Some of it was public and known, some of it more private. That doesn’t make it any less of an amazing feat, but he has his circumstances and that’s how he did it.
Notably the studio I work for couldn’t move because of our commitments for products included in the sim launch as commissioned by Microsoft. We had (and still do) a full roadmap of multiple products that we planned to push out in late Q4, now pushed back.
We’re slowly getting back on track, but we were one of the few studios who had their commissioned products ready in time for Jorg’s series of Product Demo Q&As leading up to launch. So by no means were we taking our time leisurely.
So saying that folks are dragging their heels and aren’t communicating isn’t really fair. You can’t judge one studio’s pace against another, especially if they’re on the Partner Marquee. Even if they’re not, there’s plenty of obstacles to get through to even deliver a forward compatible product.
If you really want to support the Devs at large in order to get more 2024 content to market (small m), the best thing you can do is be patient. Segregating and calling out folks whose roadmap isn’t complete or fleshed out (and thus they’re not ready to talk about it) isn’t supporting or incentivizing them in any way.
4 Likes
say it a little louder, for those in the back…
1 Like
I have very specifically not mentioned the names of any of the developers who appear less on top of this transition. I’ve mentioned a few who I feel have done it well but have gone out of my way not to criticize anyone specifically. Given the complexity of the situation and some of the specific cases, that would be unfair. That said, there are developers who I’ve purchased many products from who have said absolutely nothing about their 2024 plans–that’s just not right either.
Also, I’m not of the mindset that we should be patient or that giving developers more time definitively or generally leads to better products in the long run. We have all seen many wildly delayed products be absolutely terrible when eventually released–I’d love to name some but won’t. Time and patience do not always equate or lead to quality and market success.
Wait a sec, this is just not true. A 3080 costs more than a Series S all on its own. Then there’s all the other components, many of which also cost more. A Ryzen 7/Core i7, for starters
Hey I don’t want to sound rude or anything but after reading this whole thread I had to chime in.
I personally feel you have no idea what you’re talking about.
You’ve been corrected multiple time already about your erroneous comments.
Instead of asking 3rd Party Developers to “save” MSFS2024 and blaming them for not releasing the product you want or not disclosing their Roadmap you should instead blame Microsoft/Asobo MANAGEMENT for greenlighting this clearly unfinished product to satisfy shareholders and higher ups by increasing their revenue numbers on a excel spreadsheet.
THEY should be held accountable for this giant mess. They’re the ones pulling the strings. Not the developers. Especially not the 3rd party ones…
Have you seen the amount of bug-logged threads there is on this very forums? It’s very clear this whole thing was released prematurely and now every developers are scrambling around to figure out what to do next.
it’s really presumptuous from you to ask for some small pationate developers to “save this game” while instead, you should clearly blame MS/Asobo MANAGEMENT.
Sorry to sound rude but to me, it sounds like you don’t know anything about game development and you should rethik this whole idea of it
11 Likes
3rd party devs saved MSFS2020. Since some of them are now on board with asobo but I’m not sure that has helped with 2024.
I dont agree with the in my control part. There is plenty of documentation to find on why you arn’t always in control. Indoctrination is just an example, there are far worse things to find though. The human mind is complicated and at the same time “easy” to trick.
On topic. Again, most 3rd party 2024 aircraft/scenery works in compatibility mode (i.e minimal effort, not that that is bad per se, it just muddies the water a bit in this case). There are a handfull that completely made a conversion.
@DoutorFunga here you go
1 Like
This thread is exhausting. So much entitlement and misplaced outrage on display is also frankly depressing.
Here’s a gentle reminder: all those third parties you want to “save” the new sim have amazing aircraft and utilities available for the old sim, which continues to provide a solid, rewarding simulation experience today, just like it did on November 18. Go fly those products in FS2020 and let people take whatever time they need to learn the ins and outs of the new SDK for ‘24. Go fly those products in FS2020 and let Asobo continue scrambling to fix the bugs, flesh out the new SDK features, and fix the remaining big showstoppers.
And while you’re doing that, save your outrage for MS, not Asobo, not those unnamed third parties (and we know who you’re bashing because you’ve bashed them in other threads for a long time - some of us pay attention). Go delete Excel from your PC in protest if you must. Maybe delete Edge or Copilot too. No one wants the latter anyway. 
3 Likes