PlumCrazy

Similarly, I find when I shutdown MSFS on my PC (and after I shut down my PC altogether), the GPU and CPU temperatures seem to go down. Shocking, right?!

I see plenty of aircraft contrails in FS2024. Is this issue specific to BATC?

I want it because my beloved FFX Citation X has issues in SU4 beta that cannot be corrected until the full SU4 release.

I skipped through portions of the video, so forgive me if it was answered. Does anyone know if you can turn off the annoying yellow ribbon markers guiding you through the course? Obviously, they may be helpful when just starting out and learning a course, but if they can't be disabled, I will not bother running the Red Bull Air Races even one time.

Isn't that why we have countless graphics settings though? - so people with higher end systems can have a more graphically detailed sim while those with lower end systems can adjust to gain performance. I don't think my 9800X3D, 5080, 64GB system is going to be brought to its knees because a few AI aircraft's landing gear are rendered... It's unfortunate when design decisions result in regressions to the sim, regardless of the hardware on which it is played. I guess this is what Asobo refers to as "optimization"...

If they have to fix each AI model individually, wouldn't it make more sense to just fix the sim itself to work with the way all models were created previously. I didn't have disappearing landing gear in MSFS2020. Now using the same models, the landing gear only displays when very close to the AI aircraft. This doesn't hit me as a problem that needs fixed in the models. This smacks me in the face as a MSFS2024 regression that should be fixed.

I can't think of a single reason to keep flying MSFS 2020 with 2024 available - assuming you have decent hardware specs. 2024 certainly has had its growing pains, but it is at a very usable state now. SU4 (which should go live any day) brings some substantial improvements to the sim as well (many of us running MSFS2024 are using the beta SU4 branch of the sim already).

Performance seems good for me in the latest beta. I fly in VR (Reverb G2, 9800X3D, 5080). I'd be fine if this latest build was the official SU4 release. One regression I have noticed in the past 2 beta updates: AI aircraft sounds now cut in suddenly when the aircraft becomes within maybe 1/2 mile of you and cut out suddenly when the aircraft flies/drives out of that range. Previously you could hear AI aircraft from much farther away, and the engine sound would not cut in/out so drastically. This is noticeable for me only when I am standing outside my aircraft, so not a huge issue (as I tend to be in the cockpit 99% of the time 😉 )

I have no clue about this "streamer" you are talking about. If you were active on the official forums, you would have seen hundreds of complaints about this particular issue within an hour or so of the beta release. It is well over a thousand now. Pretty sure these people weren't there because of a video streamer LOL.

If a company releases code that works on their in-house systems, yet doesn't work for 100% of the users who use it in the real world, their test methodology deserves criticism and should be fixed. If you consider this particular bug to be insignificant enough to not hold back the beta, I simply will agree to disagree (and the huge number of complaints and bug reports seem to support my feelings). I fly in VR and would absolutely revert to SU3 without the user community "fix" for this bug that is now available. The bug text is plenty annoying in 2D, but it is pretty much game breaking in VR. This bug would prevent anyone flying in VR from participating in the SU4 beta. That is a significant bug by my definition.

If the change was merged after "whatever set of test they run before releasing..." then it supports the theory no testing was done in the released code in-house. You seem to think that is fine. I will continue to say that is sloppy software development practice (yes, even for released beta builds). If the released code was tested, yet in-house "testers" didn't notice this bug, I am at a loss for words. As a VR user of the sim (I guess I should say game at this point), if the bug was noted in-house and deemed not significant, then I am at an equal loss for words. We shall agree to disagree...

How can this particular bug happen when checked? It's not like the bug is present under a certain specific scenario or for users with specific hardware or settings enabled. This bug is present for every single person who enters a flight - in a flight simulator. Either the specific beta build was run/tested by zero people in-house before release or it was noted and deemed not significant enough to stop the release. Neither scenario is a good look for Asobo...

Did you really just imply this bug would only be noticed in-house if they did a full set of comprehensive regression testing? We all expect a certain amount of instability and/or bugs in a beta release. I wouldn't expect a bug that hits 100% of the user base in the face the instant they start a flight to even make it into an alpha build. I have to assume the development team did their beta compile and sent the new release on its way without even running the new build once in-house.

We all understand it's a beta. Bugs are to be expected. But I 100% disagree with you if you think bugs that effect EVERYONE and are obvious the second EVERYONE starts a flight (so would be impossible to miss with even rudimentary in-house testing) should be expected - even in a beta.

I have been having quite a few issues with flightsim.to not responding to mouse clicks lately. I usually just refresh the web page and retry until it works...

Is it any less disconcerting though that this was an actual bug? How much confidence can you have in a software development team, when a bug that is immediately apparent to 100% of the user base upon initiating any flight is released to the general public?

OMG I can only hope this not a new "feature" added by Asobo. Nobody can REALLY think this a good idea. I am sometimes in the cockpit stopped (doing pre-flight and startup procedures) for 15+ minutes before rolling. I fly in VR and can't think of anything more immersion breaking than having to see this ridiculous message plastered on the screen the entire time... I'm not sure what is a more scary thought: That Asobo thinks we all want to see "[Shift+[C] Exit Aircraft" any time our aircraft is stationary... or it's a bug that effects 100% of users the second they start a flight, yet was somehow missed in testing before this beta was released to the masses.

I am using the 2020 version in SU4 beta and it works very well. One issue I have is the night panel lighting seems to not work correctly. It is possible I do not know how to properly configure the panel lights (though I believe I have tried every combination possible with the light dials), but I can only get backlit panel lights on the lower mid section of the cockpit console. I have to have flood lights enabled to see the left, right and upper panels areas of the cockpit panels. Can someone confirm if you are seeing the same?

I am on version 0.4.5.7-test3 and running MSFS2024 SU4 beta. I still get the URL error when the app tries to auto-update to 0.4.5.8-test1. Not a big deal, as I can apparently just user 0.4.5.7 with the latest beta release.

And VR helps exponentially more than that 55" pancake screen. 😉

When you see REGRESSIONS like the mouse curser leaving a never-ending trail as you move through menus in VR (which affected EVERY VR user in the SU4 beta), I find it hard to believe that was "intentional" on Asobo's part. No reason a bug like that should be present on any release version - beta or not - and is absolutely evidence of poor in-house QC. Unless of course your argument is valid and Asobo decided to intentionally break the sim (albeit in a beta release) for all VR users LOL. There are countless other examples of poor QC over the life of MSFS and MSFS2024...

I assume you don't use default ATC or have any AI aircraft enabled. Otherwise, you would HAVE to see the glaring issues in those areas.

Yes, there is an Oasis driver that works in Win11 with the G2. Not trying to be rude, but how can you not know that?

There are a number of problems in the sim where I could criticize Asobo for poor quality control. Specific airports or instances where ground imagery isn't perfect (when the entire world is modeled in the sim) are not on my list.

I copied the 2020 version of the Citation X into my 2024 Community folder and it loads up in the sim as expected, but the screens are still black. UPDATE: The 2020 version of the Citation X does indeed work! I had to disable the 2024 version and enable the 2020 version. Thanks for the tip!