35 minutes ago, St Mawgan said:

Sorry to hear that. It's pretty much back to pre SU4 for me now - very nearly an instant transition. 

It can vary saint.  Aircraft with steam gauges seem to come off worse, and as I saw you said before, it can vary dependent on where you fly and how complex the scenery is.  I suppose when the scenery is heavy it culls more, when it is light it maybe doesn't have to, but not really that much difference for me.  Although this is for slow cockpit rendering.  For traffic without wheels, it seems to happen everywhere.  And with the pop-in objects at close range (even with high LOD set such as 400), I am not technical enough to know if it is a LOD issue or culling, or both.  I am not bothered really as long as they can make it better.  All I know is I never had anything like this in SU3, and I still had scintillating performance, smooth as silk then.

Edited May 4May 4 by bobcat999

1 hour ago, SayAgain said:

Agree, and it’s not restricted to just AI traffic landing gear, the wheels on Jetways don’t render when one is about 300ft away (and this is at max LOD) either so we have floating jetways.

We have service vehicles that transition to terrible LOD (making it look like the vehicle switch to another carrier or even different type of vehicle) and this happens as little as 100 ft away.

I’m asking Asobo to provide PC users with a culling parameter.  

There also seems to be an issue with night lighting at some airports. Gary Summons (UK2000 developer) told me this when I noticed delayed apron lighting activation during beta testing of the just released KCON Concord Municipal after loading my aircraft. I noticed that some of the apron lights were not on, so I moved forward to see if they would activate when I got a bit closer. They did.....but then I noticed that if I did this at all of the aprons, I could then move far away from the airport, and all of the apron lighting remained active.

I have not done much night flying in MSFS 2024 (and to be honest, it has reminded me that I need to remember to test the night lighting during beta testing of new airports), so it is something that has evaded radar detection since I upgraded. However, I do recall noting delayed activation of apron lighting when beta testing previous UK2000 airports in MSFS 2020, but at the time I thought it was the standard "close range culling issue" that affects numerous things in the Asobo simulators. However, there seems to be something else going on with respect to the lighting.

how can so many still be having issues? Most AVSIMMERS are experienced and do not have problems like the Facebook crowd. I have NEVER had an issue from FS2020 ONWARD why??? just a good clean gaming laptop, comes built married with the proper components from day 1. No home made pc not done right or perhaps anyone with issues has MS OFFICE OR MCCAFFEE loaded...both known evil destroyers of pc performance. 

 

this video is not for most, just those whom continue to have disasters it is really very basic obvious stuff but... perhaps someone will beneift .

 

 

18 minutes ago, JETPETER300 said:

how can so many still be having issues? Most AVSIMMERS are experienced and do not have problems like the Facebook crowd. I have NEVER had an issue from FS2020 ONWARD why??? 

Never had an issue since 2020?  Not even the multitude of issues even MS / Asobo admitted to have been an issue and have put right in various sim updates and ultra long patch notes, probably thousands of fixes? 
I can't take this seriously if this is the case, as this must either be a joke or you are blind to them.

PS.  I had to stop watching your video when you said not to have MS Office installed on the same PC as MS2024.  Absolute rubbish.  

Edited May 4May 4 by bobcat999

1 hour ago, Christopher Low said:

Gary Summons (UK2000 developer) told me this when I noticed delayed apron lighting activation during beta testing

Yep, I’ve noticed the same … I recall the P3D days when dynamic lighting had a restriction of the number of lights that could be rendered (250 or 500) in order to maintain performance … it was frankly silly, as you taxi along on large airports you’d see the lights go off and come on within a few hundred feet of your POV.  It was janky then just as it is today in MSFS 2024.  So developers would reduce the number of lights at an airport or narrow their radius.  How some things never change.

Edited May 4May 4 by SayAgain

11 minutes ago, JETPETER300 said:

I have NEVER had an issue from FS2020 ONWARD why???

 

If you want some constructive criticism, that's a bizarre statement.  i guess there's no need for an SU6, 7, 8 etc?  2020 had 16 SUs.  What about the issues specifically mentioned in the patch notes?  

I watched part of your video, but had to turn it off.  Blaming antivirus?  That's one of the biggest IT myths out there.  Granted, I'm all for dumping bloated, outdated AV products and using MS Defender out of the box, but blaming software issues on AV is comical.

For the record I'm nearing 30 years in IT.  Every vendor out there will tell you to turn off AV with any problem, and it almost never fixes it.  The amount of actual problems I've seen caused by AV are extemely small, and almost always something like quarantining an EXE file.  We disable AV and test just to make them happy.  It works almost 0% of the time.  

In complex software, problems happen.  Changes can impact a random thing that nobody ever thought would impact each other (and therefore nobody thought to test).  

Story time - back in 2020, one of the SUs rolled out and I started getting CTDs out of nowhere.  People blamed everything to faulty memory, other hardware issues, AV, and just about every other cause.  They were trying to be helpful, but it was not the voltage on my RAM that was suddenly off.  The CTDs started after an SU, and guess what fixed them?  A future SU.  After this new SU, I never had a CTD again.  

That said, there's lots of people asking AI to "tweak" their system and doing all sorts of awful things.  However to dismiss every single possible issue with both sims is not helpful at all.  

12 minutes ago, bobcat999 said:

Never had an issue since 2020?  Not even the multitude of issues even MS / Asobo admitted to have been an issue and have put right in various sim updates and ultra long patch notes, probably thousands of fixes? 
I can't take this seriously if this is the case, as this must either be a joke or you are blind to them.

PS.  I had to stop watching your video when you said not to have MS Office installed on the same PC as MS2024.  Absolute rubbish.  

Sorry, Rob, but me, too. I didn't switch to FS2024 for the first few months, so I can't speak to that. I have not been satisfied with most of the default aircraft and so stick to payware for the most part. I have no clue why I haven't had problems, but run MSFS as clean as possible with the minimum number of Community add-ons, and only a few bits of support software.

My system was purchased in 2022 and wasn't at the cutting edge back then. I do have to limit stuff like traffic and run at moderate graphics settings between medium and high. I run at 2K, capped at 30 fps, and in HDR, but it all fits in the 8K of VRAM. I don't have any third party airports because I learned years ago that this can cause all sorts of problems, but have not had performance issues with Fenix, PMDG, etc.

Most all of the problems I have had along the way have been due to user error on my part. This is hugely complex software that works very well if used with a bit of discretion. 

The best part of using AI to fix things is that it reads crappy forums posts and uses them as gospel - no wonder people have problems 😂

To solve all problems with MSFS, simply press ALT+F4.

And now we wait...

38 minutes ago, JETPETER300 said:

how can so many still be having issues? Most AVSIMMERS are experienced and do not have problems like the Facebook crowd. I have NEVER had an issue from FS2020 ONWARD why??? just a good clean gaming laptop, comes built married with the proper components from day 1. No home made pc not done right or perhaps anyone with issues has MS OFFICE OR MCCAFFEE loaded...both known evil destroyers of pc performance. 

 

this video is not for most, just those whom continue to have disasters it is really very basic obvious stuff but... perhaps someone will beneift .

Video removed

While i do agree that having a system built with quality components correctly and thoroughly optimized (Bios & Operating System) is going to deliver best performance. You telling me that you haven't had any issues from 2020 isn't lending credibility to the argument. 

There will always be issues thrown up that have to be worked through whether it comes from a platform update (Hardware driver or Operating System update) or the running software (Sim) over time. There may be even external factors that require a little more in depth knowledge in order to fix an issue (Example a bad DNS config that slows the data stream down even though you have gigabit internet). For you to say that you have not had any issues from 2020 onwards tells me either your platform has been stuck in time with no further updates or that you willfully neglect or fail to observe and adjust for any changes or performance regressions made to the sim as it gets developed over time.

And with that i cannot take your argument very seriously.    Then again .. you may have been struck with serendipity. 

 

Edited May 4May 4 by Maxis

Just to clarify:

1. The object culling issue was created by Asobo and they identified it as “by design”.  

2. Asobo also proceeded to suggest the issue was 3rd party AI traffic models at fault, I (and others) have provided visual evidence this is NOT the case.

3.  Asobo proceeded to suggest that 3rd party scenery was not created correctly and only had 1 LOD and not 3-5 LOD for every model.  This was again proven incorrect (again with visual evidence) showing default airport buildings, signs, etc. appearing and disappearing within a relatively short distance from POV.

These are all related to Asobo design decisions not “bugs”.  It’s would be an amazing simple change to allow users to set the culling via some slider in the graphics settings (limit it to just PCs if they like) … seriously, this could be accomplished in a hour or less of coding.  All I’m asking for is an option.  For those loving high FPS, they don’t need to touch the culling slider (if one existed).  I’m not requesting we exclude anyone, just ask for an option.

11 minutes ago, SayAgain said:

Just to clarify:

1. The object culling issue was created by Asobo and they identified it as “by design”.  

2. Asobo also proceeded to suggest the issue was 3rd party AI traffic models at fault, I (and others) have provided visual evidence this is NOT the case.

3.  Asobo proceeded to suggest that 3rd party scenery was not created correctly and only had 1 LOD and not 3-5 LOD for every model.  This was again proven incorrect (again with visual evidence) showing default airport buildings, signs, etc. appearing and disappearing within a relatively short distance from POV.

These are all related to Asobo design decisions not “bugs”.  It’s would be an amazing simple change to allow users to set the culling via some slider in the graphics settings (limit it to just PCs if they like) … seriously, this could be accomplished in a hour or less of coding.  All I’m asking for is an option.  For those loving high FPS, they don’t need to touch the culling slider (if one existed).  I’m not requesting we exclude anyone, just ask for an option.

I haven't frequented this place since this time last year. This was one of the main reasons I quit using MSFS2024. I was screaming black and blue about it upon release. The Asobo enablers in this forum assured me it was a non-issue because 2024 was glorious and had pebbles. I see they still didn't give the end user an option to override it. Good luck in getting it accomplished. I really hope you or others can. 

As a side note, I just reinstalled MSFS2024 to see how it's come along. Seems pretty good performance wise now, however, the clouds are looking a bit pixelated sometimes. Other than that, it does seem to be in a way better place than the frustrating mess it was at launch. 

Hello Ian!🫡

11 minutes ago, Ianrivaldosmith said:

No he frecuentado este lugar desde este momento el año pasado. Esta fue una de las principales razones por las que dejé de usar MSFS2024. Estaba gritando negro y azul al respecto al soltarlo. Los habilitadores de Asobo en este foro me aseguraron que no era un problema porque 2024 era glorioso y tenía guijarros. Veo que todavía no le dieron al usuario final una opción para anularlo. Buena suerte para lograrlo. Realmente espero que usted o otros puedan.

Como nota al margen, acabo de reinstalar MSFS2024 para ver cómo ha llegado. Parece bastante bueno rendimiento ahora, sin embargo, las nubes se ven un poco pixeladas a veces. Aparte de eso, parece ser en un lugar mejor que el desastre frustrante que estaba en el lanzamiento.

Most of the people around here who think everything will be fine in 2024 are the same ones who thought everything was fine on launch day; they’re also the same ones trying to convince us that Inibuilds’ aircraft are problem-free and on par with PMDG or Fénix. I suspect these people have ulterior motives because while they say one thing, the notes for each patch tell a very different story.
 

 

 

The other important thing about 2020 and 2024 is that things behave differently for different people, even if those poeple do similar things.  In troubleshooting, you'd assume if user 1 does X, Y, Z and user 2 does the exact same things in the exact same order, results should be the same.  For some reason, especially starting with 2020, it was common for people to see wildly different resuts.  It can be easy to say "well, user 2 must have done something wrong if they see something differently".  While that's possible, it isn't always the case.

I mentioned my 2020 CTDs after an SU.  I found a few people with the exact same issue as me, but the vast majority of the community was fine.  Had 2020 been crashing on everyone, it would have been all over the internet.  Something impacted a small subset of us (FWIW, it seemed to track back to a specific video card).  To this day I still don't know what caused it.  

I have very few issues with 2024 overall, fewer than most it seems, but I never, ever talk down to anyone who is, because I've been on the wrong end of those conversations enough times to know it isn't useful or helpful.  

Edited May 4May 4 by kerosene31