3 hours ago, GSalden said:

It is correct that only the main screen can make use of FG. 
 

From NVIDIA Team:

This is not a limitation of the GPU itself as it is an internal scaling filter, using AI tensors, but each game applies it differently.
There are games that apply it natively and the graphics engine uses it for all aspects of the game, so in situations with multiple screens it is complete. But there are games that use it at the internal level of textures, resolution, or graphic pixels and it only applies in real time to the game’s main rendering, and other secondary aspects are adjusted by effects of Motion Blur, Filtering, or the same graphics engine, modifying textures and resolution that are not in the field of vision.

In the case of MFS, they use DLSS 3 at the level of the main camera, like VRRR Shading, and since their main monitor is the main camera for the game, it only applies in that visual field and the other visual gamut remains in the normal rendering of the graphics engine.
There are more games that use this type of use such as Red Dead Redemption 2, Elder Scrolls Online, or Forza 5.

This is because the implementation is designed for the graphics engine first and for the main camera, so setups with 2 or 3 monitors are not taken into account, since it is extra performance and very rarely used, to optimize in these types of configurations.

Therefore, it depends on each game and developer how they implement it and it is not necessary to return your GPU if it is something that does not matter too much to you in this case since we cannot control the way or implementation of DLSS 2, 3 or Ray Tracing and each developer adjusts it based on their desires, optimization or performance for the general public.

Hi,

My point was that I am not using FG.

FG is disabled.

But still the app thinks FG is enabled and detects incorrect (double) FPS on center screen.

It would seem the app does not work in multi-screen setups.

 

1 hour ago, LGKR said:

But still the app thinks FG is enabled

As I have said before, to which you haven't responded specifically, the app thinks FG is enabled because your usercfg.opt file indicates DX12 is in use and the known MSFS active memory location for FG status is set on. The only way for this app to incorrectly determine your FG status is that you have had both an MS Store and Steam version of MSFS installed at some stage and the app is reading the config file from your old one or you actually do have FG enabled and don't realise it or there is a bug in the code. In the latter case, out of thousands of users you are the only one to report this incorrect positive detection, no matter how many monitors MSFS is spread over, so it is far more likely one of the first two is the case.

 

Edited March 2, 20242 yr by Reset XPDR

1 hour ago, Reset XPDR said:

As I have said before, to which you haven't responded specifically, the app thinks FG is enabled because your usercfg.opt file indicates DX12 is in use and the known MSFS active memory location for FG status is set on. The only way for this app to incorrectly determine your FG status is that you have had both an MS Store and Steam version of MSFS installed at some stage and the app is reading the config file from your old one or you actually do have FG enabled and don't realise it or there is a bug in the code. In the latter case, out of thousands of users you are the only one to report this incorrect positive detection, no matter how many monitors MSFS is spread over, so it is far more likely one of the first two is the case.

 

I can confirm that DX12 is enabled.

I have the MSFS Store version, and I have never had the Steam version.

The userCfg.opt has no line where FG is mentioned at all.

FG option is not active in settings - in fact, it cannot be activated - it is greyed out.

Very strange indeed

11 minutes ago, LGKR said:

I can confirm that DX12 is enabled.

I have the MSFS Store version, and I have never had the Steam version.

The userCfg.opt has no line where FG is mentioned at all.

FG option is not active in settings - in fact, it cannot be activated - it is greyed out.

Very strange indeed

Have you ever had FG enabled in the past? If so, do you now have HAGS disabled, hence the greying out of FG in MSFS?

BTW, usercfg.opt does have a line in it for FG but it is just not called that (DLSSG IIRC). Regardless, I don't use this line to detect FG as the user could change it while in the MSFS settins menu whereas DX version is fixed until the next time you run MSFS, even if you change it in game.

Edited March 2, 20242 yr by Reset XPDR

22 minutes ago, Reset XPDR said:

Have you ever had FG enabled in the past? If so, do you now have HAGS disabled, hence the greying out of FG in MSFS?

BTW, usercfg.opt does have a line in it for FG but it is just not called that (DLSSG IIRC). Regardless, I don't use this line to detect FG as the user could change it while in the MSFS settins menu whereas DX version is fixed until the next time you run MSFS, even if you change it in game.

Yes I have tried FG, but as it only works on one sceeen, I turned it off. And HAGS is also disabled.

I do not have DLSSG IIRC in the UserCfg.opt.

I do have

DLSSG 1 and

DLSSGVR 0

if this is of any relevance.

Does this mean I should make a full reinstall of MSFS to rule out any FG- enabled-bug in the code?

 

58 minutes ago, Reset XPDR said:

 

It would be great if someone who uses more than one screen in MSFS - multi-screen setup - try the following:

1. Have Auto FPS App on "Stay on top", so the app window is visible when in MSFS.

2. Press mouse pointer (left click) on center screen (main screen). Check FPS counter on Auto FPS App.

3. Press mouse pointer (left click) on side screen. Check FPS counter on Auto FPS App.

4. Press mouse pointer on other side screen (if you have 3 screens) and check FPS count in app.

Are the detected FPS values in the Auto FPS app the same for all screens?

I am getting different readings on main screen and side screens, which makes the app not work as it should.

Greetings All,

So much impressed with the AutoTLOD app; I thought I'd give this a try.  However, no luck so far.  I have an AMD Radeon RXT6700XT with FG enabled.  Trying both DX11 and DX12 in the sim; the app does not recognize that FG is enabled and only with "Target PC Mode". 

Should this app work with AMD cards with FG enabled?

Thanks

@LGKR
Wish I could help but all I can add is the following peripheral data points, neither one of which is probably directly useful to you:

- Frame generation only working on the center monitor in multi-monitor setups (when frame generation has been enabled of course), is a known issue in multiple games, so appears to be a driver limitation.  Maybe something about this fact is related to why his app seems to think you have it working on the center monitor, even though you believe that not to be the case.

- I run a triple screen setup but could not get adequate performance with the true multi-monitor option in MSFS. So instead I used NvidiaSurround to create one big screen, and I use an MSFS window spread across half of the left monitor, the center monitor, and half of the right monitor. In this situation, with Surround enabled, frame generation does indeed work correctly on all three screens -- because the driver sees them as one big screen.

But it seems the bottom line is that this app only has one way of detecting frame generation and for whatever reason it seems that maybe with multi-monitor setups this indication may be erroneous in MSFS.

Edited March 2, 20242 yr by GregP

11 hours ago, SkylanePilot said:

Do you have any idea what may be going on here or even give me a place to start looking?

Did you resolve this by looking for AutoFPS in the taskbar/system tray? If the icon is there, double-click to open window. To hide, right click systray icon and select hide.

OK. I cannot be the only one having trouble keeping up with much of this.  HAGS. AutoFPS vs Dynamic LOD?   I am on RTX 3080 and at one time had the FG hack in place.  I could not get it to work well with either of these two apps.  Likely due to fact that for RTX 3080 FG is a hack.  So I have systematically removed all aspects of the 3000 series FG.  So now comes HAGS as a potential issue.  I currently have HAGS on.  Perhaps a remnant I missed removing of the FG hack?  So with these two apps which is it?  HAGS On?  Or HAGS Off.  Is that different for one vs the other app?

Sorry, but this is now an historic 21 page topic.  My wife chuckles at it, describing it like the wash cycle of her washing machine.  You know, where the garmets are tossed one way and then the other over and over ....  (that is in jest) 😁

Edited March 2, 20242 yr by fppilot

Been watching the display in this app, and realized that when flying in  overcast skies really has an affect on FPS.  I also just discovered that my FPS with the PMDG 737 is about 10 FPS higher than with the Fenix B2. 

Edited March 2, 20242 yr by Bobsk8

When using it in VR is there a way to see the utility so you can monitor what its doing , your frames etc?  cant seem to get it to overlay in side the cockpit?  Probably an easy option i have not switched on  but any help appreciated.

 

Cheers

 

cheers

 

 

3 hours ago, Cpt_Piett said:

Did you resolve this by looking for AutoFPS in the taskbar/system tray? If the icon is there, double-click to open window. To hide, right click systray icon and select hide.

I restarted the computer. I moved the installer program window to my my main monitor where FG is set to on.
I used the installer to delete the program.
After the installer reported that the program had been successfully removed, I reinstalled and ran it.

When the window appeared, I clicked the option for it to remain "on top." The window did not disapper and It remained on top.
I checked the system tray and the icon was visible.
Then, I started MSFS and the window remained on top.
It remained on top all the way to the MSFS welcome screen.
Then I checked the system tray and the icon was still present. 
Then, I returned to the AutoFPS window and I clicked to turn on Expert Mode. The instant I did that, the "on top" window disappeared AND the icon in the system tray was gone as well.  (I did note that in the system tray, there was now a blank icon between two other icons but the blank one did not respond to either left or right click. 

The log file looked like this:

2024-03-01 22:51:13.828 [INF] ----------------------------------------------------------------------- 
2024-03-01 22:51:13.857 [INF] [ App:InitLog                      ] MSFS2020_AutoFPS v0.4.1 started! Log Level: Debug Log File: ..\log\MSFS2020_AutoFPS.log 
2024-03-01 22:51:13.863 [INF] [ App:InitSystray                  ] Creating SysTray Icon ... 
2024-03-01 22:51:14.035 [INF] [ ServiceController:Run            ] Service starting ... 
2024-03-01 22:51:14.038 [INF] [ IPCManager:WaitForSimulator      ] Simulator started 
2024-03-01 22:51:14.077 [INF] [ MobiSimConnect:Connect           ] SimConnect Connection open 
2024-03-01 22:51:14.077 [INF] [ IPCManager:WaitForConnection     ] Connection not established - waiting 30s between Retries 
2024-03-01 22:52:25.438 [INF] [ MobiSimConnect:SimConnect_OnOpen ] SimConnect OnOpen received 

In Task Manager,
-on the Processes page, there was no entry for the MSFS2020_AutoFPS process.
-on the Details page I found the following:
       Name                                                                          PID            Status          CPU   Memory    
       MSFS2020_AutoFPS.exe                                           39604        Suspended     00   40 K  
       MSFS2020_AutoFPS installer v.0.4.1.exe                  16224        Suspended     00   32 K
Neither process could be killed. Received "Access is denied" error.

HAGS, Variable Refresh Rate, and Optimization for windowed games settings have no effect.

Uninstalling nVidia’s new app has no effect.

Runnng nVidia game ready driver 551.61  

Disconnected 2nd monitor and restarted.

With only one monitor active, the following steps are 100% repeatable on my system. 
1. restart computer
2. start AutoFPS app
3. if app window opens with expert options not displaying, click expert options and the window will expand to show expert options. 
4. If I then click to deselect expert options OR click to activate OLOD, program will crash and the system tray icon will disappear leaving a process suspended which can’t be killed.  
5. if app window opens with expert options displaying, and repeat step 4 and program will crash. 

What is interesting is that if the program crashes because  I select OLOD, on the next restart, the program window will open with expert options showing AND OLOD SELECTED!

Marty

Edited March 2, 20242 yr by SkylanePilot
Further testing

59 minutes ago, SkylanePilot said:

I restarted the computer. I moved the installer program window to my my main monitor where FG is set to on.
I used the installer to delete the program.
After the installer reported that the program had been successfully removed, I reinstalled and ran it.

When the window appeared, I clicked the option for it to remain "on top." The window did not disapper and It remained on top.
I checked the system tray and the icon was visible.
Then, I started MSFS and the window remained on top.
It remained on top all the way to the MSFS welcome screen.
Then I checked the system tray and the icon was still present. 
Then, I returned to the AutoFPS window and I clicked to turn on Expert Mode. The instant I did that, the "on top" window disappeared AND the icon in the system tray was gone as well.  (I did note that in the system tray, there was now a blank icon between two other icons but the blank one did not respond to either left or right click. 

The log file looked like this:

2024-03-01 22:51:13.828 [INF] ----------------------------------------------------------------------- 
2024-03-01 22:51:13.857 [INF] [ App:InitLog                      ] MSFS2020_AutoFPS v0.4.1 started! Log Level: Debug Log File: ..\log\MSFS2020_AutoFPS.log 
2024-03-01 22:51:13.863 [INF] [ App:InitSystray                  ] Creating SysTray Icon ... 
2024-03-01 22:51:14.035 [INF] [ ServiceController:Run            ] Service starting ... 
2024-03-01 22:51:14.038 [INF] [ IPCManager:WaitForSimulator      ] Simulator started 
2024-03-01 22:51:14.077 [INF] [ MobiSimConnect:Connect           ] SimConnect Connection open 
2024-03-01 22:51:14.077 [INF] [ IPCManager:WaitForConnection     ] Connection not established - waiting 30s between Retries 
2024-03-01 22:52:25.438 [INF] [ MobiSimConnect:SimConnect_OnOpen ] SimConnect OnOpen received 

In Task Manager,
-on the Processes page, there was no entry for the MSFS2020_AutoFPS process.
-on the Details page I found the following:
       Name                                                                          PID            Status          CPU   Memory    
       MSFS2020_AutoFPS.exe                                           39604        Suspended     00   40 K  
       MSFS2020_AutoFPS installer v.0.4.1.exe                  16224        Suspended     00   32 K
Neither process could be killed. Received "Access is denied" error.

HAGS is ON.
Variable Refresh Rate is ON.
Optimization for windowed games is ON.

So, I am back where I started. This has me stumped.

Marty

Is there anything in Windows event viewer under Windows logs Application for the moment the app and icon disappears? If so can you message me any associated error codes and log text for this app. Thanks

1 hour ago, Bozdog said:

When using it in VR is there a way to see the utility so you can monitor what its doing , your frames etc?  cant seem to get it to overlay in side the cockpit?  Probably an easy option i have not switched on  but any help appreciated.

 

Cheers

 

cheers

 

 

It doesn't display inside VR, which I primarily fly too. I am not really planning to do so as it is intended as a set-and-forget tool and IMO such info all the time is counter productive to immersion.