On 1/11/2025 at 3:51 PM, abrams_tank said:

They are doing a public open beta for SU1. Jorg said it in the Twitch Q&A. You can search for it if you want.

About time; the more people testing the more infos / feedback coming back.

On 1/11/2025 at 10:32 PM, KERNEL32 said:

 

Thank you to Kernel32 for listing the source.

"Flighting" in Jorg's terminology means a public open beta. So now we all have the source. 

Edited January 13, 20251 yr by abrams_tank

On 1/11/2025 at 10:02 PM, Sonosusto said:

Yeah, I can't find it either.

I wish when people post stuff like "you can search for it ..." etc would instead provide a source.

I'm on vacation and I don'f have my PC with me. Using my phone to find the source is extremely cumbersome and slow. I can't be bothered to do the OP's work, especially when I am in transit.

The worst part is, so many people in this thread were asking for the source and liked your comment that there is no source. Kernel32 did the work of finding the source.  And yet when Kernel32 posted the source on Saturday, not a single person acknowledged or liked their comment until I did.

Edited January 13, 20251 yr by abrams_tank

9 hours ago, Krakin said:

You can't expect every single update to go through public testing, especially this early on when there are so many issues to get through. I mean you and others keep talking like the issues are infinite so if Asobo had to wait on the public to comb through everything, we'd get nowhere. As far as I can tell, this hotfix did it's job but people see that as a reason to complain. Jorg promised a public beta for SU1 so be sure to participate and report any bugs it introduces when the time comes 👍🏾

I never said they needed a public test for these patches, they just needed their own internal QA team to do a word not allowed job for ONCE!

On 1/12/2025 at 7:04 PM, abrams_tank said:

I'm on vacation and I don'f have my PC with me. Using my phone to find the source is extremely cumbersome and slow. I can't be bothered to do the OP's work, especially when I am in transit.

The worst part is, so many people in this thread were asking for the source and liked your comment that there is no source. Kernel32 did the work of finding the source.  And yet when Kernel32 posted the source on Saturday, not a single person acknowledged or liked their comment until I did.

Well that's all unfortunate and I didn't realize any of this. Just noticed this, the kerfuffle that ensued, and the lack of proof. Can't say I dont believe you because I do.

No worries. Its the internet and everything gets lost in translation 

We don’t have time for public betas tests at this early stage imo. 2024 has regressed so much from 2020 in some areas that Asobo need to get the sim back to that standard asap - and public testing shouldn’t be required as they can just port over 2020 code hopefully.

there are a few caveats with that but several hot fixes is the way to go for now, get that enormous bug list down to a manageable levels then concentrate on the big SU

3 hours ago, Sonosusto said:

Can't say I dont believe you because I do.

No worries. Its the internet and everything gets lost in translation 

Well, just click on Kernel32’s video. Jorg clearly says they are returning to “flighting” in early 2025, meaning SU1.

I replied to the OP and gave the OP a huge hint on where to find the source. I specifically mentioned Jorg and I even said the last Twitch Q&A. The hint was so anybody who wanted to dig for the source had a place to start and it was narrowed to within the last Twitch Q&A.

In the end, I’m glad that I didn’t waste time looking for the source. Few people acknowledged or thanked Kernel32 for providing the source.  It just makes everyone in this thread who clamored for a source, then Kernel32 provided the source, look ungrateful for Kernel32’s work.

Things with MSFS2024 are pretty much where I expected them to be at this point in time. As mentioned, they simply can't have a beta large enough to cover all of the possible combinations of hardware as well as variations in network speeds from user to user. Telemetry will play a large part in fixing things. 2024 does not run well (most of the time - occasionally it does) on my machine unless I turn everything down to low and 50/50 on OLOD and TLOD, in which case it runs great. I can't get performance and visuals on par with what I get in 2020 to save my life. Not even close. (well... I've had a half dozen or so that were better than 2020, but I can't consistently get that type of performance)

That being said, I still try it every other day or so so that MS/Asobo can get the telemetry data that will help them fix it.

Some users are using it with no problems. Others, including me, are not. I left 2020 installed for that very reason. I expected everything that we are seeing right now. It'll get better soon. Just like 2020 did. Some people would have been better off waiting until the word on Avsim was that it was good to go before they bought it. That's what I did with 2020.

Edited January 14, 20251 yr by MDFlier

54 minutes ago, MDFlier said:

Things with MSFS2024 are pretty much where I expected them to be at this point in time. As mentioned, they simply can't have a beta large enough to cover all of the possible combinations of hardware as well as variations in network speeds from user to user. Telemetry will play a large part in fixing things. 2024 does not run well (most of the time - occasionally it does) on my machine unless I turn everything down to low and 50/50 on OLOD and TLOD, in which case it runs great. I can't get performance and visuals on par with what I get in 2020 to save my life. Not even close. 

That being said, I still try it every other day or so so that MS/Asobo can get the telemetry data that will help them fix it.

Some users are using it with no problems. Others, including me, are not. I left 2020 installed for that very reason. I expected everything that we are seeing right now. It'll get better soon. Just like 2020 did. Some people would have been better off waiting until the word on Avsim was that it was good to go before they bought it. That's what I did with 2020.

Make sure you turn off that Dynamic thingy, and then tune from there, maybe that is the reason. That thing gave me headaches for a few days trying to figure out what the h… was going on, until I finally had sense to turn it off and then tune my settings. Not saying this is your issue, but it could be…

Edited January 14, 20251 yr by Kaboki

46 minutes ago, Kaboki said:

Make sure you turn off that Dynamic thingy, and the tune from there, maybe that is the reason. That thing gave me headaches for a few days trying to figure out what the h… was going on, until I finally had sense to turn it off and then tune my settings. Not saying this is your issue, but it could be…

Asobo should really leave it off by default.

5 minutes ago, Krakin said:

Asobo should really leave it off by default.

Yeah, totally agree!! It almost turned me into certain negative people on this forum, had bad performance, blurry ground textures and was on the verge to ditch 2024 and go on rampant rage campain in the forums, swearing and cursing Asobo. Luckily I just tried turning it off and voila, sim was fixed, lol… Think it could have saved them a few bad reviews by not having it on by default:p

Edited January 14, 20251 yr by Kaboki

15 minutes ago, Kaboki said:

Yeah, totally agree!! It almost turned me into certain negative people on this forum, had bad performance, blurry ground textures and was on the verge to ditch 2024 and go on rampant rage campain in the forums, swearing and cursing Asobo. Luckily I just tried turning it off and voila, sim was fixed, lol… Think it could have saved them a few bad reviews by not having it on by default:p

This and Raytraced Shadows. Another fps killer are trees on high - but I love the tree shadows too much to go to medium. So I decided to use DLSS "Balanced" instead of "Quality". Since my hardware is very similar to yours and 8 GB of VRAM are the main problem, I now can mostly use high settings and a Terrain LOD between 120 and 150 and still get 30 to 40 fps.

18 minutes ago, crimplene said:

This and Raytraced Shadows. Another fps killer are trees on high - but I love the tree shadows too much to go to medium. So I decided to use DLSS "Balanced" instead of "Quality". Since my hardware is very similar to yours and 8 GB of VRAM are the main problem, I now can mostly use high settings and a Terrain LOD between 120 and 150 and still get 30 to 40 fps.

Not sure how you can see my specs:p, but i have RTX 3080ti 12 gb VRAM and 12th gen intel. 
 

May I ask how you turned off raytracing? Its grayed out in my settings and I cant turn it off..

FS2024 needs time and lots of it. I'm glad I didn't secrume to MS marketing bait.

3 hours ago, Kaboki said:

Yeah, totally agree!! It almost turned me into certain negative people on this forum, had bad performance, blurry ground textures and was on the verge to ditch 2024 and go on rampant rage campain in the forums, swearing and cursing Asobo. Luckily I just tried turning it off and voila, sim was fixed, lol… Think it could have saved them a few bad reviews by not having it on by default:p

Same here. I had blurry textures first day, saw this unknown, new option and switched it off. Solved.

I can’t understand why they did not deactivate this immediately after release when the first issues were reported.

The team must be really stunned at the moment dealing within issues at all fronts.