11 minutes ago, bobcat999 said:

I haven't tried the very latest beta update (.12) with DX12 yet, but there was no mention of a fix in that change log, or any previous ones actually.  I will get around to testing it with DX12 again soon.

I think I’ve just been lucky Bob, haven’t seen anything about the bug either, in any of the beta release notes. It could be that AutoFPS has some sort of favorable effect…

If multithreading continues to be improved (not really sure what’s changed since DX12 became available back in Aug ‘22), I will be extremely pleased with MSFS performance. 

12 minutes ago, Cpt_Piett said:

I think I’ve just been lucky Bob, haven’t seen anything about the bug either, in any of the beta release notes. It could be that AutoFPS has some sort of favorable effect…

If multithreading continues to be improved (not really sure what’s changed since DX12 became available back in Aug ‘22), I will be extremely pleased with MSFS performance. 

Yes, performance is good.  It is just aesthetics (like the tiles issue) and a few handling issues for me. 

Of course, as you say, anything that continues to help CPU's (better multi-threading etc.), is very welcome,as it is this that is my limiting factor now rather than GPU issues. 
And I think the 'main thread' limitations apply to most people, if not all, so I am not being selfish I don't think  

Any improvements to VRAM usage in DX12 folks are experiencing?

1 hour ago, CaptKornDog said:

Any improvements to VRAM usage in DX12 folks are experiencing?

Not that I've seen.

Just did a couple of quick performance tests.

Settings:

• Fenix V2 | iniBuild's EGLL | Orbx London | | GSX | AutoFPS with TLOD Min 50 OLOD 1000
• 4K HDR | DLSS 3.7 + DLAA | DX12+FG | Ultra w/ shadows 6K | PG on
• FPS RTSS-locked at 65 in front edge sync
• Latest Nvidia driver 552.12
• Hyperthreading on in BIOS (24 threads)
• Fenix, FSLTL assigned to the 8 E-cores in Process Lasso
• Resizable BAR on
• Shader cache recently cleared

ILS27L approach via Lambourne, no AI traffic (sadly AIG TC crashed without me realizing):

Taxi to runway 27 and take-off to 3000ft w/ FSLTL (max 30 IFR, max 30 parked):

Conclusion: 

Absolutely stellar performance, even with AI traffic. I find that FPS locked to 65 is a sweet spot with my hardware. Without the FPS lock, things will not be as smooth (i.e. FTV is worse). 

Remark:

Notice the sensor data:

• Avg CPU load around 20%
• CPU max thread load around 50%

=> ample CPU headroom. 

Edited April 12, 20242 yr by Cpt_Piett

5 hours ago, Cpt_Piett said:

Just did a couple of quick performance tests.

Settings:

• Fenix V2 | iniBuild's EGLL | Orbx London | | GSX | AutoFPS with TLOD Min 50 OLOD 1000
• 4K HDR | DLSS 3.7 + DLAA | DX12+FG | Ultra w/ shadows 6K | PG on
• FPS RTSS-locked at 65 in front edge sync
• Latest Nvidia driver 552.12
• Hyperthreading on in BIOS (24 threads)
• Fenix, FSLTL assigned to the 8 E-cores in Process Lasso
• Resizable BAR on
• Shader cache recently cleared

ILS27L approach via Lambourne, no AI traffic (sadly AIG TC crashed without me realizing):

Taxi to runway 27 and take-off to 3000ft w/ FSLTL (max 30 IFR, max 30 parked):

Conclusion: 

Absolutely stellar performance, even with AI traffic. I find that FPS locked to 65 is a sweet spot with my hardware. Without the FPS lock, things will not be as smooth (i.e. FTV is worse). 

Remark:

Notice the sensor data:

• Avg CPU load around 20%
• CPU max thread load around 50%

=> ample CPU headroom. 

 

Nice study!

I have +/- the system RIG as you have, will test later tonight.

 

You lock FPS at 65 in SIM? So 130 with FG?

Can you please share autoFPS configurations print?

 

Regards!

6 hours ago, Cpt_Piett said:

Just did a couple of quick performance tests.

Settings:

• Fenix V2 | iniBuild's EGLL | Orbx London | | GSX | AutoFPS with TLOD Min 50 OLOD 1000
• 4K HDR | DLSS 3.7 + DLAA | DX12+FG | Ultra w/ shadows 6K | PG on
• FPS RTSS-locked at 65 in front edge sync
• Latest Nvidia driver 552.12
• Hyperthreading on in BIOS (24 threads)
• Fenix, FSLTL assigned to the 8 E-cores in Process Lasso
• Resizable BAR on
• Shader cache recently cleared

ILS27L approach via Lambourne, no AI traffic (sadly AIG TC crashed without me realizing):

Taxi to runway 27 and take-off to 3000ft w/ FSLTL (max 30 IFR, max 30 parked):

Conclusion: 

Absolutely stellar performance, even with AI traffic. I find that FPS locked to 65 is a sweet spot with my hardware. Without the FPS lock, things will not be as smooth (i.e. FTV is worse). 

Remark:

Notice the sensor data:

• Avg CPU load around 20%
• CPU max thread load around 50%

=> ample CPU headroom. 

I'm curious what would be the result with TLOD100/200, OLOD1000, without AutoFPS...

1 hour ago, NoobX said:

You lock FPS at 65 in SIM? So 130 with FG?

Can you please share autoFPS configurations print?

65 FPS with FG. I don't get much higher than that at places like EGLL. 

17 minutes ago, Bond said:

I'm curious what would be the result with TLOD100/200, OLOD1000, without AutoFPS...

Without AutoFPS the result would be exactly the same with the same TLOD and OLOD. But at higher altitude TLOD 50-100 is quite low. 

Edited April 12, 20242 yr by Cpt_Piett
Posted the wrong AutoFPS screenshot

1 hour ago, Cpt_Piett said:

65 FPS with FG. I don't get much higher than that at places like EGLL. 

Without AutoFPS the result would be exactly the same with the same TLOD and OLOD. But at higher altitude TLOD 50-100 is quite low. 

The same? How about under 1000feet? With TLOD at 100/200 under 1000 feet I bet you'll struggle, no? Or else you wouldn't need that option on AutoFPS?

Hmmm...

Do people not know how to quote someone without including these massive images? 

41 minutes ago, Bond said:

The same? How about under 1000feet? With TLOD at 100/200 under 1000 feet I bet you'll struggle, no? Or else you wouldn't need that option on AutoFPS?

Hmmm...

One of the huge advantages of AutoFPS is the ability to set TLOD Min at 1000ft to ensure it doesn't bottleneck everything when flying into major hubs. I've got it set to 50 (with the + checked i.e. it can go up to 100 if there's headroom for it). 

With TLOD at 200 I would definitely struggle into EGLL, KJFK, EHAM, KLAX etc. 

EDIT: Not sure if I understand your comment. What I meant was that at the same TLOD and OLOD, the result would be the same whether you set it in MSFS menu or AutoFPS. 

Edited April 12, 20242 yr by Cpt_Piett

I assume you mean that you would struggle with performance into the very large airports with hundreds of AI planes enabled? I have TLOD at 250 and OLOD at 200 on my PC, and I do not struggle into any airports (including IniBuilds EGLL London Heathrow and FlyTampa EHAM Amsterdam Schiphol) with AI disabled. Admittedly I have everything set to HIGH rather than ULTRA, but I am still amazed by how much detail my i5 7600k can shift at decent framerates.

Edited April 12, 20242 yr by Christopher Low

54 minutes ago, Christopher Low said:

I assume you mean that you would struggle with performance into the very large airports with hundreds of AI planes enabled? I have TLOD at 250 and OLOD at 200 on my PC, and I do not struggle into any airports (including IniBuilds EGLL London Heathrow and FlyTampa EHAM Amsterdam Schiphol) with AI disabled. Admittedly I have everything set to HIGH rather than ULTRA, but I am still amazed by how much detail my i5 7600k can shift at decent framerates.

I don't have hundreds of AI (where did you get that from?) - max 30 in the air and 30 parked. With AI off, performance is excellent even into EGLL and EHAM (both payware). I have to say that performance is not bad at all with AI (FSLTL) at my current settings. As can be seen in my CapFrameX screenshots - the difference in performance is in fact minor. 

My assumption was because I could not understand why you would struggle with performance from a PC that is so much more powerful than mine. I appreciate that you run at a higher resolution, but even so I would have thought that your PC would never have a problem at a TLOD of 200.

1 hour ago, Christopher Low said:

My assumption was because I could not understand why you would struggle with performance from a PC that is so much more powerful than mine. I appreciate that you run at a higher resolution, but even so I would have thought that your PC would never have a problem at a TLOD of 200.

I don't think I mentioned that I struggle with performance - I'm extremely happy with the performance. But I run at TLOD 50-100 into major hubs to prevent being bottlenecked by the CPU. Having said that - I don't think I could manage TLOD 200 into Heathrow at 65 FPS. 

I'm currently over NZ South Island in Black Square's Caravan and getting 100 FPS with TLOD 920. 

Edited April 12, 20242 yr by Cpt_Piett