MrRoper

Its expected behaviour due to their culling system: Sim "culls" Model-parts and ignores LODs of the Model - [MSFS 2024] Bug Reports / Aircraft - MSFS DevSupport My only hope now is that AIG / FSLTL implement a workaround (invisible objects etc) as I dont see MS changing this behaviour.

Photogrammetry can only be streamed. Its possible that it is stored in the rolling cache, so you might be better of with a huge cache file instead.

I was using FSLTL.

Unfortunately, its still not fixed, the low draw distance of gears is still present

Of course, as soon as I posted this it started working 😄

Not working here im afraid. UK based.

The lvar to map is S_FC_CAPT_TILLER_PEDAL_DISCONNECT

I think you would have to use Spad.next or similar software to set the appropriate LVAR for it. I dont think there is an actual mapping for it

Some great real world videos of flights here : (12) Approach and Departure Videos - YouTube I believe this is Eurowings and they disconnect the auto throttle on most approaches.

This used to work with frame generation (albeit with a lot of latency introduced) until the nvidia driver that fixed vsync for DLSS3. I used to use the exact same technique to lock at 40 fps in RTSS but get 80 fps in game. the affects were similar to what Noel is showing with a massive reduction in frame time variance.

A lot of the usage will be the AA settings that are being used, Try running with No AA or SS and see what the usage is, I would be surprised if its anywhere near 3gb

Unfortunately LM doesn't have the Entertainments License, which might put people off developing / buying it. Dont get me wrong I want it to succeed but its not there yet :(

you do understand that even P3D Will OOM eventually? its still a 32bit app and until that changes pushing it with large amounts of scenery and memory intensive add ons will cause it to run out of VAS. Updates in Hardware cannot overcome the 4GB VAS limit, only X-Plane has that going for it at the moment. Considering how hard we are pushing FSX I think its doing rather well, there is some life left in the old girl yet!

Hi Lucass MY advise would be to use the Internal FSX limiter and use the FIBER_FRAME_TIME _FRACTION config entry to gain back some of the FPS lost. As i said this loss of FPS isn't a bug, its Time being given to the Rendering loop to render Textures. Im not sure if the cfg entry is case sensitive, however mine are [bUFFERPOOLS] and Usepools

Tushka, Set your Scanning schedule to a time when you are not using FSX and also exclude the FSX directory from the Real-Time scanning.