6 minutes ago, ryanbatc said:

I'm saying I firmly believe they had a lot of pressure from MS to move forward with 2024 only.

And I'm firmly saying that's complete bull as ini already gave a reason why they went 2024 only months ago, they didn't want to maintain two different builds of the aircraft at the time.

 

I imagine it will be delayed into 2025 if they want to release both versions simultaneously

Edited December 18, 20241 yr by Tuskin38

8 minutes ago, Tuskin38 said:

It's not 'almost impossible' anymore. It takes a bit extra work, but nowhere near impossible.

It's impossible right now - how many PC12 paints are there?  C404?  C408?  PC24?  C172?  TBM930?  I'm a painter if you didn't know - the files are locked.  And the ones that are viewable via the VFS in Dev mode are available at LOD 01.  And we don't yet have a blender importer for gltf from 2024.  And for what I have seen, the UV's are messed up or contain mirrored textures so it's not possible to paint text on tails, engines, wings etc.

Myself, along with others will prevail like the Community always does, fixing things for Microsoft for free.  We'll figure it out.

1 minute ago, Tuskin38 said:

And I'm firmly saying that's complete bull as ini already gave a reason why they went 2024 only months ago, they didn't want to maintain two different builds of the aircraft at the time.

 

I imagine it will be delayed into 2025 if they want to release both versions simultaneously

Because they were pressured by MS into going 2024 only....  of course they don't want to do 2 paths...  that's more time and money invested on their end 

6 minutes ago, ryanbatc said:

because they were pressured by MS into going 2024 only

No they weren't. There's zero evidence of this, and inibuilds have said otherwise.

  

7 minutes ago, ryanbatc said:

or contain mirrored textures

Because Asobo makes their liveries with the decal method, so they have no reason for the textures not to be mirrored.

Edited December 18, 20241 yr by Tuskin38

2 minutes ago, Tuskin38 said:

I imagine it will be delayed into 2025 if they want to release both versions simultaneousl

Maybe.

Also, maybe seeing what the SIM and SDK were like early moved them to a plan B months ago.

3 minutes ago, BrammyH said:

Also, maybe seeing what the SIM and SDK were like early moved them to a plan B months ago.

They announced it was 2024 only a couple months ago, long after they had access to 2024. Remember they made some of the default aircraft, and they've already released one native 2024 aircraft.

So it probably has nothing to do with the SDK.

Edited December 18, 20241 yr by Tuskin38

1 minute ago, Tuskin38 said:

No they weren't. There's zero evidence of this, and inibuilds have said otherwise.

Ini would never publicly say that lol.

 

1 minute ago, ryanbatc said:

Ini would never publicly say that lol.

 

They already have.

And microsoft has zero control over where they release their products.

Stop spewing conspiracy theory nonsense.

Edited December 18, 20241 yr by Tuskin38

24 minutes ago, Aviator_2024 said:

Another prove that 2024 is in its alpha/beta stage. It’s not ready for developer planes because the corse sim is broken and massive stuttering after last patch. I have RTX 4090 I9 14900k

I have a similar system with no stutters whatsoever.  very frustrating for some!

this is great. I never uninstalled 2020 and am still having a blast with it. I also have never purchased Say Intentions or BATC so I feel if I did one of those I could easily get another year out of 2020 before getting itchy again for something new in FS2024. Im glad I held out for now because I was really looking forward to the A350.

 

Also isnt their A220 with Synaptic which will probably never come only being developed for FS2020? 🤭

Edited December 18, 20241 yr by environmental_ice

Just now, ryanbatc said:

Ini would never publicly say that lol.

 

I’m sorry but it really does not make a lot of sense.
 

Ini is a contractor, they’re not a 1st party developer of Microsoft and thus not beholden to any of their requirements outside of contractual obligations.
 

Microsoft can’t strong arm ini into what ini does with its OWN products. It’s been shown with how ini approaches its contract work compared to its own products with regards to updates, customer support, etc etc

 

Anyway onto the main topic, this is good news to those who are still with 2020, though I imagine in due time there will slowly be some apparent differences between the two versions. Curious to see how it all evolves!

34 minutes ago, ryanbatc said:

I'm saying I firmly believe they had a lot of pressure from MS to move forward with 2024 only.  With the rough release month the end user has spoken... users are leaving 2024.  Recent spikes are the previous two patch releases.

The reality is much less sensational IMO. If a large enough of a majority of users switched over to 2024 exclusively then it made business sense for ini to only release it for 2024. Current market reality is that a sizeable number of users are on 2020 so ini is releasing it for both (given that it also has the 2020 codebase for the aircraft)

Ini (like PMDG for their 777F) assumed it would be the former in the above two possibilities, now they are adapting to the current market reality.

Obviously for their payware aircraft ini will do what's best for them, and MS has no say in the matter (and these claims that MS was/is exerting pressure on ini to only release for 2024 is completely unfounded.. no different from claims that MS intentionally made problems happen in 2020 in order to make 2024 look better)

Edited December 18, 20241 yr by lwt1971

Good news! I only have to wait until its release, instead of waiting for 2024 to improve.

It really is too bad, 2024 had promise, but even I who uninstalled 2020 and came into 2024 with excitement am now planning on reinstalling 2020 and moving back to that as my primary platform. Too many poor design choices -- like the forced back-on-track feature -- just keep me from really enjoying 2020, not to mention all my content locked up on the Marketplace because they did not actually check and test compatibility before launch; I have no plans to ever purchase there anymore. They must have gone back to a much earlier build and forked off development of 2024 as it is true many of the early 2020 issues are back. I expected challenges and issues and bugs and for it to take time to really flush out, but I did not expect this level of issues.

Anyway, I like many others are going back or just remaining on 2020 so for many developers this will be a dilemma, release on 2024 only and have less sales or slower sales over a much longer period of time as people gradually come to 2024 over the next couple of years, or release on both platforms and have to support both.

4 minutes ago, lwt1971 said:

The reality is much less sensational IMO. If a large enough of a majority of users switched over to 2024 exclusively then it made business sense for ini to only release it for 2024. Current market reality is that a sizeable number of users are on 2020 so ini is releasing it for both (given that it also has the 2020 codebase for the aircraft)

Indeed, 2024 release has been not great. Even at its current state, 2024 performs like word not allowed while 2020 performs miles better, so I am staying on 2020 and will get the 350 once is released