SayAgain

To be blunt, I don't care whether you have "a problem or it doesn't bother you" as that is irrelevant and doesn't change the facts there is a culling issue reported by myself and MANY others. You don't like weather depiction in MSFS, fine, do you see my trying to telling you otherwise? In fact, I agree that weather depiction is hit and miss. It's as if the only things that matter to you are of significance. So it's some sort of contest now? So your motive here seems to be one of YOUR priority on what you want "changed". A discussion I have ZERO interest in and will not derail you because it's important to you. If you have problems with weather, then do what I and others have done, post screenshots/videos demonstrating the problem and STOP trying derail other legitimate issues because they don't "bother you". You posted a video to show there was "no problem" but the fell flat because it showed there was a problem with culling. Congratulations you've contradicted yourself in a single post. Is this from your official survey? I don't recall saying "acting for the community" ... please do show me where I said that or is this just more slinging of false information so as to sway support? Hate to break it to you, based on the likes in this thread, you're not getting much support. I'm updating my ignore list.

You mean "a problem" since I'm not the ONLY person who has reported the issue (311 posts about this problem in the MSFS 2024 official forum). And there ya go, you've demonstrated "defensive" rather than objective. Even though from your OWN video, it was pointed out all the aircraft without wheels that you apparently don't see or notice? So why are you interested in commenting on this problem? So if you don't have a problem with missing wheels and other small objects, then can we assume you also would NOT have a problem with those same objects being visible? You see where I'm going with this? Again, what's you real motive here?

To add further clarification from PDX about 450 ft away: Hope this helps, pretty sure we're all on the same team here for a better experience.

Ok, at least you've acknowledge there is a problem ... that's a start. And again, as per my PDX reference earlier in this thread (distance is about 500 ft well within a normal person's visual line of sight): and move closer ... it's magic ... my FPS suddenly drop from 1000 FPS to 500 FPS ... oh the horror! I honestly have no idea why some of you are so defensive in regards to this problem ... what's your motive? I mean fixing it benefits everyone so I don't get your responses?

Winner winner chicken dinner, that latest exe worked! Looking good (except the culling of wheels): On another unrelated issue with PSXT and RealTraffic ... I followed Dr. Balthasar's process to get a new API token for RT and placed that token in my RT license info in the RT app and all went well. However, when I start PSXT I got the following error indicating I have two different RT Licenses?? So I removed the RT license file from root of PSXT folder which seems to have resolved this issue (it automatically create a new .lic file on PSXT restart) ... just an FYI. Thank you for getting this resolved ... if only Asobo were as responsive as you (a freeware developer) 🙂 Cheers, Rob.

Same issue with livery scan unfortunately ... new logs: https://drive.google.com/file/d/1-Dm3JuNU7yWLnPoRpYcxm5QaWRhYHoI3/view?usp=sharing

No, my typo, you're correct no double parked in this video.

Yes, you’ve confirmed you have the problem also … very easy to spot when you stop zooming in 😉

Well if you folks don’t want to provide your graphics setting nor post a video then we’re in a game of he said she said. I’ve posted numerous videos and my graphics setting. Something Asobo asked for … because … drum roll … some rando dude on the internet needs to show and tell not just tell 🙂

Sometimes and other times it’s completely wrong weather being depicted. Like the other day it was clear and 91F here in PDX and XP12 showed heavy cloud cover … after about 20 minutes it thinned out a little but didn’t match real world weather at all (clear sky all day). It’s definitely hit or miss on how the live weather is depicted … sometimes it’s very close and sometimes it way off. I do use HiFi weather also, but not enable in this case.

Hit the record button (or hot key sequence for nVidia or AMD) and post on YouTube so we can see what you see.

Would be good to list your graphics settings (resolution, DLSS, etc.), monitor size, distance to monitor, add-ons, zoom value, etc. so we can determine the difference. On my 4K 42” OLED is noticeable, on my 4K 77” OLED it’s VERY noticeable (as you would expect since the distance between my head and the OLED screen is the same … hence why % screen size should NOT be used for culling calculations).

You might want to find out why your post repeated 4 times. Yeah, I’d give them a call as it’s not normal. I’m assuming you bought this computer and it’s not on some rental plan? If you purchased it then you need to be setup as the owner/admin so don’t have these restrictions. Windows 11 now does require a Microsoft account (can create one for free), BUT, there are ways to work around that and vary based on Home vs. Pro edition. For some this is a significant deal, for others it doesn’t matter … not sure how you feel about it, but it’s easier to just go with the flow that big brother Microsoft want from you especially when it comes to using MSFS 2024.

“Your organization”? Is this on a work computer? Where were you trying to copy the files/folder to?

So you have fix priority (assume that’s what this is really about). At least you get to see the weather, culling prevents users from seeing the object (or just parts of an object) that should be visible. Code changes to MSFS weather system are far more involved than a code changes needed to provide a graphics slider to adjust culling (% screen size). Weather system changes would be a multi-month project. Culling slider would be a 1-2 day project. I personally don’t know how you can’t laugh hysterically at AI aircraft that in many case may show the main landing gear (when closer) but not the nose landing gear. When I got my wife to try MSFS 2024, her first comment was “what’s wrong with that airplane” (pointing out the missing landing gear) as she taxi out to the runway … she made ZERO mentions of the weather or cloud depiction.

Same goes for MSFS 2024, I’m not sure why you are surprised? You could apply your own surprise to the issues you have with XP as being relatively minor and others wouldn’t understand. But, whether you understand or I understand or anyone else, not really relevant … the problem exists, it’s real, it’s been demonstrated numerous times, it’s ultimately a bad design decision to improving FPS and reducing VRAM usage … or more accurately a design decision that should have come with a graphic settings slider. And the solution is relatively simple fix not some major overhaul. And the issues isn’t just landing gear in the distance, it’s a long list of smaller objects and swapping of LODs on relatively close objects transforming them into what sometimes seems like a entirely different object or different carrier (push back tugs for example). Using % of screen is simply NOT the correct approach to culling … sure it’s “by design” but a graphics engineer would know it’s NOT a good solution but is a simple approach to reducing VRAM usage and increasing FPS … it’s a sledge hammer approach.

Many users do wipe and re-install to resolve problems … it’s not ideal because you don’t really discover what the problem was and how to avoid it in the future. It’s pretty common for folks to run into the same issues later on down the line after a wipe and re-install … time and add-ons and updates can do that. And this method of re-install isn’t specific to MSFS, all platforms seem benefit from this, but sadly it doesn’t really isolate the issue that caused the problem in the first place. I’m running into similar issues regarding my MSFS 2024 start times, it went from less than 1 minute to 5 minutes or so … it was likely one thing I installed that triggered it but trying to discover which add-on caused it is time consuming and mostly trial and error. I’m not aware of any diagnostics mode that would log in detail durations of specific tasks during the sim start or even entering a flight. I’m sure it exists in a development environment, but doesn’t seem to be available in dev mode … but maybe I missed something?

It was not aa 3rd party or contracted 3rd party by MS/Asobo (you’ll to select one of the “generic” ones provided by default in MSFS 2024) … I’ll go thru my notes tonight and post a video if I have time. It’s the same issue as any other small object and not restricted to Jetways wheels … any “default” airport with jetways will demonstrate the issue. I want to say default PDX was one of them (really need to check my notes), but I was able to replicate on just about any default MSFS 2024 airport that wasn’t 3rd party. Graphics settings: Everything on Ultra Blurr OFF No DLSS/FG Resolution 3840 x 2160 I estimated distance from object around 400-500 ft. Looks like I had started some documentation on PDX: I’m in the office right now, but like I said, you should be able to determine on any default airport.

Video of PSXT ... as you can see before I start PSXT there are NO static aircraft at PDX. at 3:06 min mark, parked aircraft will disappear making way for aircraft that just landed and taxi in. at 4:19 min mark, another aircraft taxi's into occupied spot then proceeds to takeoff thru the terminal. this is coming from Real Traffic as you can see in the PSXT window. I was able to reproduce the doubling up of aircraft on taxi-ways this time, but it does happen.

Same ... here are the 4 log files in a zip: https://drive.google.com/file/d/1A0lOk61OCuCYRxflUG-Nf-Hw2R7JcXVi/view?usp=sharing Yes absolute sure no static, will get you a screenshot before and after

I’ve been meandering between sim platforms for a long time … all that really changes is how much time I spend in each one relative to the other. But I must admit, it’s time consuming keeping 4 platforms going … my focus will be XP12 for this month, maybe P3D next month (still much to learn in FSLabs Concorde). They all have their issues … I’d certainly like to have “just one” platform, but I doubt that will ever happen … but diversity is good.

I’ve provided demonstrations of the several culling issues via video and screenshots numerous times in official and here. I even tried to post on that thread I linked above but got some error saying I don’t have permissions?? I’m in their dev program so no idea what that was about and didn’t follow up … I guess they just had enough of my complaining 😉 I have no idea why they use % of screen size, the variability in end user hardware is probably why we see such variance in user perception. If it really is such a basic calculation, all the easier to make it a graphic settings we can adjust to our liking … maybe 1 hour coding work, 1-2 days testing work, release.

MS Store: %LOCALAPPDATA%\Packages\Microsoft.Limitless_8wekyb3d8bbwe\LocalState\WASM Steam: %APPDATA%\Microsoft Flight Simulator 2024\WASM Rob.

I already covered this with video and screenshots (earlier in this long thread) that default MSFS AI model and other models (jetways) all present the exact same issue as in AIG and other AI traffic products. This IS a Asobo/Micorsoft "by design" choice.

No (more than that, much more) ... https://devsupport.flightsimulator.com/t/sim-culls-model-parts-and-ignores-lods-of-the-model/17174/13 A very IMPORTANT thread and has gone from "by design" to "under review". Everyone in that above thread has requested a graphics setting option. The problem comes from a rather simple formula based on % of screen size which IMHO makes no sense (someone on a 77" 4K screen within a few feet will be able to notice the problem easily). As pointed out, that lower resolution screens 1080p will exhibit lesser of a culling problem than higher resolution screens (aka 4K). It does NOT make sense to use % of screen size as reference and even less sense trying to factor in all the end user other settings that could be at play. The problem is present on all native MSFS 2024 objects with all their defined LODs. I get that more than one LOD is needed, but that's NOT the problem as demonstrated in that thread. Given the variability in end user resolutions, scaling, and other factors it would make more sense to provide a graphics settings option rather than to just assume everyone is at 1080p and use some value that works best for that resolution and only that resolution. Which brings us back to XBOX which can do 4K but is typically using dynamic resolution scaling from 1080p or 1440p because it can't really do 4K at 60Hz and certainly not at 120Hz.