Cpt_Piett

Yes, I have stuttering with GSX ground crew and vehicles. MSFS 2024. Its always been like this. I also notice stutters with BATC injected aircraft (after you pointed this out). For some reason, I’m not extremely bothered by DLSS ghosting on glass panels, or FG artifacts in general. Or low resolution clouds with apparent «grid-like» voxels. I use DLSS quality and everything seems quite good. I might not have the «pristine ultra-sharp amazing «image stability» as you claim. But in general, the sim (2024), looks fine to me. Bottom line: I do have the GSX «jerky» movement as you do. But based on all your recent posts - I think your more susceptible than the rest of us to these «artifacts».

Indeed! As things are so polarized (much as in the real world), I can't be bothered to make a video praising 2024 - I'd rather just delete the source material and watch season 6 of Better call Saul (I had nearly finished the video editing). I'll leave it up to "professional video creators" (insert your favourite flightsim youtube channel here) to promote FS2024. IMO I don't care what sim people are using. I honestly really can't be bothered.

Nevermind - I don't want to add fuel to the fire...

We don't actually know that it's a minority - but based on my experience, following most threads here on Avsim since 2024 released on Nov19, I think the drama and negative comments have settled down a bit. I just made a video (not sure if I'm going to release it yet), using several payware and freeware GA aircraft at various locations in 2024. Mostly a very nice experience, very few bugs (I did encounter a few - I would call them "non game breaking") - but with some considerable improvements in the ground detail, flight model (it differs depending on the aircraft addon), lighting model, shadows, clouds, weather, mountain cliffs etc.

I'm still not on SU2. Based on what I've read so far, I'm apprehensive. I don't want to risk not being able to change the controller settings - or loose them entirely. In terms of performance, it seems that there are conflicting reports (as usual). Some are saying performance is considerably better, whilst some are having an opposite experience. At this stage, I think I'll just stay on the fence. I'm happy with how the sim works in SU1.

Well, as this thread is now 7 pages, I think that @Greazer is happy! Probably not a lot of new arguments - but from my perspective it's alright comparing the sims. One thing is for sure - there's always a bit of drama, which can be entertaining 🍿🍿🍿

I’ve not seen much difference on/off with this setting. Except that enabling/disabling on the ground can cause mesh issues that doesn’t disappear until the flight is reloaded.

You can limit FPS in nvidia control panel or RTSS.

Cool video. Or useful I should say. Lately I’ve reduced settings from ultra as the difference with some settings is not that big, visually. Some settings impact performance more than others - ray traced shadows and trees in particular. The latest version of AutoFPS has a new feature where various settings can be reduced when performance is tight - I’ve found this very useful when flying airliners into the largest airports with ATC addons and AI traffic.

You don’t mention AIG, but if that’s what you’re using, download the latest version of AI manager https://github.com/Kaiii3/AIGTech-AIManager-beta/releases/latest

Unfortunately this is not an option with BATC, as far as I know.

Elevated taxiway lights, displaced runway markers, object popping - and probably a lot more that I can't remember right now. At some airports I get visual glitches like shimmering on fences and other structures. The object popping is significantly better if I set OLOD to 1000 (it doesn't affect performance that much). As for objects, I try to disable as much as possible e.g. with the iniBuilds airports. E.g. with parked cars I don't see the point of having these when they "suddenly" pop into view as I'm taxing past or on final approach.

I got it a few months back as I realized I would be using BATC more and more. Sadly FSHud development seems to have come to a halt. Here's the changelog for 1.6.46.Experimental as an example of continued development:

Sometimes BATC gives me "step" altitudes, other times I'm told to "descend on the STAR". It's getting better though - another large update to the experimental branch this week (can't remember if it was reported in this thread or another).

Good question! I would descend to 5000ft at the final waypoint of PUBBB and follow the altitude and speed restrictions on the STAR. I don’t think there’s a valid transition between TEMBRS3 and ILS 10L, so I suppose BATC will give vectors to the localizer at some stage. I’m interested to hear how others interpret this though.