4 hours ago, JonathanC said:

Is the inibuilds freeze on flight end bug fixed? They say they can’t repro since December .. I haven’t tried in ages and am away from computer. Is it working for you guys? 

It still happens anytime if you have flown the aircraft i.e. taken off and landed, and have used SimBrief integration. 

If you just spawn in an IniBuilds aircraft and then exit, it does not happen. 

I suspect Asobo only checked the latter case and not the former.

That's it they can get to word not allowed, VR fixes now "planned"for SU2 is absolutely appalling, no other way to describe it, word not allowed 'em.

1 hour ago, ndts said:

At least letting people beta test updates for free will be an improvement, since Asobo charged people $60-200 to beta test FS2024.

I do find it entertaining that one of the reasons Asobo gave for "everything has to be streamed" was "we can push patches faster", when at least a couple of the aircraft (the Albatross and C-17) have had fixes waiting to be pushed since some time before Christmas.

A paid beta test would be fine, this is an alpha. Beta generally means feature complete with a few bugs and some polishing needed. 

Looking through the official forums, the root cause of the inibuilds CTD issue is apparently an SDK issue that has been identified and should be fixed in SU1. Probably a disconnect between the support people who put together these updates and the devs who are actually aware of what is causing issues. As they said in the update, the SU's will include way more fixes than what is upvoted. We probably won't know more about fixes until the beta is available.

As for timing, I'm not sure what people expected... it's not like Asobo can just snap their fingers to fix things. They are rolling these fixes into the SU's so they can be tested with other fixes. We've all seen one fix that breaks something else in the process, and rolling everything into an SU helps test against this.

And as for some things that are "under investigation" like the LOD issue, it's a lot harder to track something down when it doesn't affect everyone and could even be something networking related that is outside of Asobo's control. I know it doesn't mean much to those who have the issue, but after flying for 5 hours in the PC-12 tonight, sometimes pushing my luck with an x16 simrate, the only time I saw blurry ground textures was when high-res satellite imagery didn't exist in the area I was flying.

Speaking of the PC-12, since the pressurization issue won't be fixed until SU2, I'll assume that Asobo/Carenado are actually doing the right thing and modeling the pressurization system instead of just applying a bandaid fix to PC-12 missions. I would rather have an actual fix than a bandaid hotfix released outside of the regular patch schedule.

2 minutes ago, Funky D said:

Looking through the official forums, the root cause of the inibuilds CTD issue is apparently an SDK issue that has been identified and should be fixed in SU1. Probably a disconnect between the support people who put together these updates and the devs who are actually aware of what is causing issues. As they said in the update, the SU's will include way more fixes than what is upvoted. We probably won't know more about fixes until the beta is available.

 

It looks like a lot of the top 20 upvotes issues won’t be fixed by SU1, which is disappointing, IMO.

 But yeah, I think there will be a big list of fixes for SU1, but it may not be some of the top 20 upvoted issues.

I can totally understand the VRAM issue may take until SU2 to fix. That probably requires an entire recode and a lot of time for testing, so that’s why it’s been set for SU2.

 

3 hours ago, MrFuzzy said:

LOL, AVSim is known for its negativity but the users' reactions to this dev blog are so tame in comparison with the censored official forum outrage:

https://forums.flightsimulator.com/t/january-16-2025-development-update-blog-discussion/698449

MSFS Forum : "My favorite sim activity/plane does not work!! Fix this **#@?now!"

AVSIM Forum :"I've spent xxx hours in the sim and I've found an activity /plane that works PERFECTLY. It's now my favorite activity/plane and I love this sim. No going back!" 

Proof that there are usually 2 sides to every story 🤔

I'm glad there's nothing affecting me since I only fly the FENIX 320, with BATC + FSLTL.

No hangs, no performance problems, and provided I keep flying **only** the FENIX, I can live with the limitations of the weather effects (at least helped by ASFS and RealTurb v2) and of the physics modeling.

But it's really strange, I would say - worrying - to see such a slower than 2020 development pace, or at least communication with the user community. 

MS FLIGHT always comes to my mind when this sort of stuff happens 😕

5 hours ago, Aviator_2024 said:

Main problems like VRAM Performance problems are planned for SU2 which is god know when

Take a breath!  With four years of updates to 2020 it isn't rocket science to have a clue to the timeframe.

5 hours ago, Aviator_2024 said:

It will take awhile for 2024 to be flyable

What ignorance is this?  I, like many, have been successfully using 2024 since a week after release.

3 hours ago, ndts said:

since Asobo charged people $60-200 to beta test FS2024.

Seriously?

More or less every game I have gets multiple bug fixes and updates throughout it lifetime.  Why should 2024 be any different? Have you really forgotten the number of updates 2020 had?

I get up in the morning and have breakfast. Didn't occur to me how many get up and have a negativity injection.

Edited January 17, 20251 yr by MrBitstFlyer

My plan has been to wait for SU2 before moving on to 2024 (25) and my plan stands firm after listening to this development update.

2 hours ago, Funky D said:

Looking through the official forums, the root cause of the inibuilds CTD issue is apparently an SDK issue that has been identified and should be fixed in SU1. Probably a disconnect between the support people who put together these updates and the devs who are actually aware of what is causing issues. As they said in the update, the SU's will include way more fixes than what is upvoted. We probably won't know more about fixes until the beta is available.

As for timing, I'm not sure what people expected... it's not like Asobo can just snap their fingers to fix things. They are rolling these fixes into the SU's so they can be tested with other fixes. We've all seen one fix that breaks something else in the process, and rolling everything into an SU helps test against this.

And as for some things that are "under investigation" like the LOD issue, it's a lot harder to track something down when it doesn't affect everyone and could even be something networking related that is outside of Asobo's control. I know it doesn't mean much to those who have the issue, but after flying for 5 hours in the PC-12 tonight, sometimes pushing my luck with an x16 simrate, the only time I saw blurry ground textures was when high-res satellite imagery didn't exist in the area I was flying.

Speaking of the PC-12, since the pressurization issue won't be fixed until SU2, I'll assume that Asobo/Carenado are actually doing the right thing and modeling the pressurization system instead of just applying a bandaid fix to PC-12 missions. I would rather have an actual fix than a bandaid hotfix released outside of the regular patch schedule.

I generally agree with that, but one glaring issue really can't be explained like this. The EFB in VR. How can an issue with a new core feature make it into the release build when it can be reproduced with a 100% rate in about 5 minutes, including the launch of the sim? I really blame the management here, since this should have been delayed at least until February. Launching the sim in this state right before the holidays was a total failure. 

9 hours ago, fppilot said:

Holiday vacations?

True, but in still as an end user it’s disappointing…

4 hours ago, MarcG said:

That's it they can get to word not allowed, VR fixes now "planned"for SU2 is absolutely appalling, no other way to describe it, word not allowed 'em.

They're just joking with us right now. Eight months to solve VR when Martial said they're already working on fixes and would be out soon.

It's disgraceful.

I don't see any mention of resolving issues related to saving settings for flight controls and other configurations. There are plenty of videos on YouTube about these menus and malfunctioning items. VRAM and this flight control issue should be the first priority. Something is wrong here.