MindeK

Check your other mods or addons, this mod does not have any impact on ram.

Just copy new dll files on top of old ones. No registry changes needed.

Yes!

Try this : For those that have MSFS crashing or freezing while using this mod : I've set in NVCP Max Frame rates to 60 and now my simulation runs stable without any crashes. It still a bit stuttery while panning really fast, but that can be solved by lowering your camera movement speed. One interesting think I noticed that by capping frame rates at 60 fps, MSFS developer option fps display shows that MSFS is only generating 30 fps, but Steam overlay shows 60 fps and motion and game feels really smooth. So it seems that other 30 fps are generated by FG. Leaving max frame rates off or 120 in NVCP makes MSFS crash with directx12 error or just complete freeze. Any ideas why fps setting may have this effect? (using latest nvidia game drivers)

MSFS game settings in NVCP. Global settings remain unchanged on my setup (all default).

For those that have MSFS crashing or freezing while using this mod : I've set in NVCP Max Frame rates to 60 and now my simulation runs stable without any crashes. It still a bit stuttery while panning really fast, but that can be solved by lowering your camera movement speed. One interesting think I noticed that by capping frame rates at 60 fps, MSFS developer option fps display shows that MSFS is only generating 30 fps, but Steam overlay shows 60 fps and motion and game feels really smooth. So it seems that other 30 fps are generated by FG. Leaving max frame rates off or 120 in NVCP makes MSFS crash with directx12 error or just complete freeze. Any ideas why fps setting may have this effect? (using latest nvidia game drivers)

35 is very low. I've got impression that fg is working as it should when initial frame counts is at least 50 fps.

also, how many frames do you get in this particular situation without fg? it might be just that you initial frame rates are too low, so you get like 50% real frames and %50 generated, which might have that ghosting effect. Try maybe setting everything to 60 if you monitor support that.

One thing I would like to note, maybe it would be helpful for someone. Following instructions I've enabled fg in msfs and disabled v-sync. In nvcp set v-sync for msfs. My monitor refresh rate is 60hz. By doing that I've got fg but it was somewhat lagy, althought steam fps counter was showing 60fps. Later just trying various settings I've set in nvcp max frame rates to 60 and wow it changed a lot. Msfs feel became so smooth and it feels that this is how real fg should work and feel. tldr : set in nvcp max frame rates to your monitor current hz rate.

This is completely unrelated to our situation. We are using NOT Nvidia Frame Generation but AMD, which is freeware software based solution. Only thing that MSFS does not support that (probably will be implemented some time latter), thus additional hack is used to trick MSFS to think that Nvidia Frame generation is used, instead of AMD.

You should use same refresh rate for your monitor as set in game/nvcp. Meaning that, if you set 60 fps in game, you should set the same for your monitor. If gsync is used, game v-sync should be disabled, and in nvcp you should set variable refresh rate, so that you montors g-sync would support any fps game is producing, thus removing any issues that would be visible without v-sync. Natively, nvidia frame generation does not support v-sync. Only way to enable it is to use g-sync or free-sync comapatible monitors and set them up accordingly.

0.70 version is out - https://github.com/Nukem9/dlssg-to-fsr3 Also, thanks for rising a ticket regarding random crashes while using fg - https://github.com/Nukem9/dlssg-to-fsr3/issues/190

Tool does not change any files or file system in MSFS.

Has anyone noticed that after decent LOD value does not decrease to the minimum set (0:0.5 in my setup) and stays at 1 when taxing at airport. Although during take off LOD values are changing as configured.