Ohmsquare

A few interesting ones I've flown recently: [AIRLINER] LTBS (Dalaman, Turkey) RNP 19 [AIRLINER] LDDU (Dubrovnik, Croatia) RNP 29 [GA] LJZA (Slovenia), Microsoft handcrafted, any RWY [GA/AIRLINER] ENLK (Leknes, Norway), any RWY [GA] ENRA (Norway), Microsoft handcrafted, any RWY [AIRLINER] EGNS (Isle of Man, UK), any RWY [AIRLINER] EGNM (Leeds, UK), any RWY [AIRLINER] CYCG (West Kootenay Regional Airport, Canada), Microsoft handcrafted, any RWY [AIRLINER] LPHR (Azores, Portugal), any RWY [AIRLINER] LESO (San Sebastian, Spain), RNP A RWY 04 [AIRLINER] LFKC (Calvi, France), Circling/visual approach for RWY 36 (airlines tailor made charts can be found online)

This is an excellent update, thanks a lot!

2024 runs great with SU4 (still in beta).

IIRC, Freelook speed setting in Camera options.

I don't think I've ever experienced such good performance in MSFS 2024 as I have now with SU4 beta. The difference compared to SU3 and previous update versions, or even MSFS 2020 for that matter, is clearly striking. Fenix, FSHud with generous amount of AI traffic, payware airports (either MSFS 24 native or just compatible), TLOD at 250 and it's just smooth, no blurry textures, no stutters whatsoever. I'm just a little afraid that this won't last forever and something will go wrong again.

Interesting, I didn't know there were multiple options. I think I'll stick with option No. 1 for now, at least until the option No. 3 is fixed and then maybe I will try that one. Thanks.

No need to use FSLTL/AIG injectors with FSHud, because it injects the traffic itself.

Double post

Are you aware that Asobo constantly tweaks the LOD curve and the last major change happened only few days before final SU3 release? That's actually very frustrating for developers.

In terms of time spent: Fenix DA40 (COWS) DC-6 (PMDG)

BFU, after first quick flight: noticeably better performance (MSFS 2024) hand flying feels so great now ground behaviour, incl. T/O and LND, much much better the sounds!

Dynamic settings: it does change TLOD and OLOD down to 50% of its original value (might be less, not sure here) when FPS drops down to its pre-set target. The reduction occurs gradually. As soon as the FPS improves, TLOD and OLOD will return - again gradually - to the original limit. This can be easily seen in the MSFS built-in FPS indicator, where you can see current TLOD and OLOD values (labeled "Terrain/Objects LOD factor"). If someone has blurry textures with dynamic settings ON too often, it usually means that either a) their frame rate target in dynamic settings is set too high relative to available performance; or b) their TLOD values are set too high; or, a combination of both. As I wrote in a previous post, frame rate target in dynamic settings should not be a target you want to reach, but rather a limit you don't usually want to go below. For example, I have the frame rate target in dynamic settings set to about 85% of my normally expected performance, i.e. if I had the FPS locked at 60 I would set dynamic settings frame rate target to 50 FPS. If the FPS oscillates between 60 FPS and 50 FPS, I don't mind such a performance drop and dynamic settings remain inactive. A drop in FPS below 50 might already be undesirable for me, so in that case the dynamic settings will kick in, which will cause TLOD and OLOD gradual degradation to keep the frame rate at least at the 50 FPS threshold. If the simulator evaluates that there is available power again, it will start to gradually increase the TLOD and OLOD values up to the original value. AutoFPS: AutoFPS can achieve the same and much more, allowing the user complete control if they choose to go this route. It's a really powerful and fantastic tool. Personally, I prefer the dynamic setting over AutoFPS because I like how it adapts better to the current performance load, resulting in a smoother overall experience.

I my case it is pre-FG. *** I have nothing but positive experience with Dynamic settings and use it instead of AutoFPS now. The key is to set the FPS value correctly, it should not be a target you want to reach, but rather a limit you don't usually want to go below. However, it is still recommended to set a reasonable TLOD value in the first place.

This is not correct. You described the keyboard shortcuts for custom views which function differently from the default cockpit view. Also, but I am not sure here, the default keyboard shortcuts in MSFS 2024 for custom views are different now, they use Shift command exclusively (Shift F5 - F8 to save the camera, Shift F1 - F4 to recall it). For a customized default cockpit view (usually 'VFR Pilot') you save the camera with the 'VFR Pilot View Save' command - by default it should be Ctrl+F10. And Shift+F10 resets this particular cockpit view to the default settings made by the aircraft developer. That is the default view you get back to when you use 'Camera Reset' or 'Reset Cockpit View' commands. You can also use Ctrl+F9 for 'IFR Pilot' and Ctrl+F11 for 'Landing view'. You can switch between these views using the 'Next Pilot Position' or 'Previous Pilot Position' commands. These default camera views as well as the custom views are stored in a separate camera.cfg for each aircraft.

I have found that FSHud + AIG work pretty well, it is probably the best option for ATC and AI traffic currently (MSFS2024).