0.4.5.6-test17, available here or via auto update with + Tests enabled, should now work with SU4 1.6.5.0. 

Thank you!

I'm trying to catch-up after 10 days off my PC Sim.

6 hours ago, Konderbt said:

I moved everything and choosed it right but MSFS 24 didnt want to accept it but now i got it. Now i want to add Auto Start as before. But if i wanted to do this via the Installer it says "Failed to add Auto-Start".

That's usually because of a permissions issue. The simplest solution is to just edit the EXE.xml file in your MSFS 2024 root user folder, or create one if it doesn't exist, and manually add the AutoFPS auto start, replacing <username> with your Windows username. eg.

<?xml version="1.0" encoding="windows-1252"?>
<SimBase.Document Type="Launch" version="1,0">
  <Descr>Launch</Descr>
  <Filename>EXE.xml</Filename>
  <Disabled>False</Disabled>
  <Launch.ManualLoad>False</Launch.ManualLoad>
  <Launch.Addon>
    <Disabled>False</Disabled>
    <ManualLoad>False</ManualLoad>
    <Name>MSFS_AutoFPS</Name>
    <Path>C:\Users\<username>\AppData\Roaming\MSFS_AutoFPS\bin\MSFS_AutoFPS.exe</Path>
  </Launch.Addon>
 </SimBase.Document>

 

When the DTLOD decreases in poor conditions in the autofps app, is this a reflection of the dynamic settings decrease, or autofps LOD decrease?

21 minutes ago, agent00729 said:

When the DTLOD decreases in poor conditions in the autofps app, is this a reflection of the dynamic settings decrease, or autofps LOD decrease?

It is an AutoFPS decrease. At this time I am unable to detect the dynamic settings LOD reduction, because it is a MSFS internal response not an actual fixed setting that the app can monitor and/or change like it usually does. I am still looking for it memory, but so far no banana. You can monitor it yourself in the FPS view of developer mode, which is how I worked out what it is actually doing.

Hi

I reinstalled SU4 and can no longer use frame generation with AMD 3 on my RTX 3090. All three screens are flickering. 
If I turn it off, the flickering goes away. Is this a known issue?

Kind Regards Ramon

21 minutes ago, Metall4You said:

Hi

I reinstalled SU4 and can no longer use frame generation with AMD 3 on my RTX 3090. All three screens are flickering. 
If I turn it off, the flickering goes away. Is this a known issue?

Kind Regards Ramon

https://forums.flightsimulator.com/t/regression-1-6-3-0-fsr3-broken-severe-screen-flickering-makes-it-unusable/737468

Right on. Look forward to testing this hopefully today.

What do you guys recommend I set for settings? 
 

 What I currently do is “40” FPS under max frame rate, then I do Frame Generation ”X3”. This is because I set my FPS to match my refresh rate of 120HZ which is what my PC can accomplish. It’s smooth and my PC can meet those settings. Under Dynamic Settings I have it at “30” FPS. Is that reasonable, or should I match “40” FPS under dynamic settings? 

 

 

Thanks, everyone. 

15 minutes ago, spearmint_flyer said:

What do you guys recommend I set for settings? 
 

 What I currently do is “40” FPS under max frame rate, then I do Frame Generation ”X3”. This is because I set my FPS to match my refresh rate of 120HZ which is what my PC can accomplish. It’s smooth and my PC can meet those settings. Under Dynamic Settings I have it at “30” FPS. Is that reasonable, or should I match “40” FPS under dynamic settings? 

 

 

Thanks, everyone. 

I am still trying to quantify the effect of the dynamic settings target frame rate for the various graphics modes, and can't actually test MFG as I don't have a 5000 series card, so you might be able to tell me what target frame rate works best. 

I have been matching it to my AutoFPS target FPS, so 120 in your case, but TBH I am not sure whether dynamic settings target frame rate works off native or actual frame rate, so 40 could just as well be what should be set. The best way to tell is to turn on developer settings FPS view in MSFS and observe what the Terrain and Object LOD factor readings show. If at 120 FPS for the dynamic settings target frame rate they are permanently reading 0.5, even when your system is easily achieving 120 FPS, then the setting just may well be native frame rate. There's only one way to find out and when you do let me know!

12 minutes ago, Reset XPDR said:

I am still trying to quantify the effect of the dynamic settings target frame rate for the various graphics modes, and can't actually test MFG as I don't have a 5000 series card, so you might be able to tell me what target frame rate works best. 

I have been matching it to my AutoFPS target FPS, so 120 in your case, but TBH I am not sure whether dynamic settings target frame rate works off native or actual frame rate, so 40 could just as well be what should be set. The best way to tell is to turn on developer settings FPS view in MSFS and observe what the Terrain and Object LOD factor readings show. If at 120 FPS for the dynamic settings target frame rate they are permanently reading 0.5, even when your system is easily achieving 120 FPS, then the setting just may well be native frame rate. There's only one way to find out and when you do let me know!

Okay, I will test it. I did notice that when I went into settings after turning on AutoFPS it set it to 110 which is what AUTOFPS is set automatically too as well. 

10 minutes ago, spearmint_flyer said:

Okay, I will test it. I did notice that when I went into settings after turning on AutoFPS it set it to 110 which is what AUTOFPS is set automatically too as well. 

I gather you are using non-expert mode? In the latest test version, I have auto-enabled dynamic settings and it will set it to as close to your AutoFPS target FPS as possible. On reading a bit more today about what type of frame rate dynamic settings uses, and from my own quick experimentation just now, it seems to be the native, not the frame generated, frame rate, so I will likely have to alter the code to use the native frame rate.

30 minutes ago, Reset XPDR said:

I gather you are using non-expert mode? In the latest test version, I have auto-enabled dynamic settings and it will set it to as close to your AutoFPS target FPS as possible. On reading a bit more today about what type of frame rate dynamic settings uses, and from my own quick experimentation just now, it seems to be the native, not the frame generated, frame rate, so I will likely have to alter the code to use the native frame rate.

Yes, I believe it is the native frame rate. In the past anytime I've set it to a target rate higher then native I get excessive blurring of the terrain. 

4 minutes ago, spearmint_flyer said:

Yes, I believe it is the native frame rate. In the past anytime I've set it to a target rate higher then native I get excessive blurring of the terrain. 

I will change it to native frame rate in a test update to be released shortly. 

FYI, 0.4.5.6-test19 has just been released with the following change:
- Revised auto-enabling of dynamic settings in non-expert mode to use the native (pre-frame generation) AutoFPS target frame rate when deriving the dynamic settings target, matching what the MSFS engine actually uses.

Also, a note for anyone trying dynamic settings in expert mode, make sure you are setting the dynamic settings target frame rate to be the native (pre-frame generation) frame rate you desire, not the frame generated one, as this is what the MSFS engine actually uses.