FSR 2.0 "shimmering/ghosting" (no issues using FSR 1.0 instead)

[Marii Wukruk]

https://steamcommunity.com/sharedfiles/filedetails/?id=2873101125 not sure if it's AMD drivers being AMD drivers or Windows being Windows, or if it's simply as indicated, and just that, an experimental feature, meaning it is yet to be finished, or finalised, if you will, so, thought I'd share.

Driver Version 21.50.21.11-220428a-379219C-AMD-
AMD Windows Driver Version 30.0.15021.11005
Windows 10 Home (64 bit), Windows ver. 21H2. Up to date, no updates pending, no optional updates pending, etc.

If it matters, AMD Software: Adrenalin Edition Version 22.5.1 released: 28/04/2022.

[The Exile]

Originally posted by Wukruk:

https://steamcommunity.com/sharedfiles/filedetails/?id=2873101125 not sure if it's AMD drivers being AMD drivers or Windows being Windows, or if it's simply as indicated, and just that, an experimental feature, meaning it is yet to be finished, or finalised, if you will, so, thought I'd share.

Driver Version 21.50.21.11-220428a-379219C-AMD-
AMD Windows Driver Version 30.0.15021.11005
Windows 10 Home (64 bit), Windows ver. 21H2. Up to date, no updates pending, no optional updates pending, etc.

If it matters, AMD Software: Adrenalin Edition Version 22.5.1 released: 28/04/2022.

I am assuming you are using Windows.

If you aren't using Windows, let me know, because the following won't help you if you are on a linux distro and there are alternative methods to gather the required information to start troubleshooting.

Information Collection Guide
--------------------------------

In order to help you figure out what's wrong and troubleshoot your issue you need to provide information about your system. There are a few ways to do this...

1. Dxdiag
----------

Use DxDiag, a Microsoft Windows Application, to get information about your system that can be used to troubleshoot issues on your system.

Click open the search menu.
Search for "DxDiag".
Run DxDiag.
Save the results to a text file.
Use PasteBin to post the results recorded in that text file.
Pastebin's website - https://pastebin.com/index.php
Make sure the pastebin expires after a few days.
Provide the pastebin link here in the forum And we can go from there.


2. Alternative Option ( PowerShell )
------------------------------------

First, you will need Windows PowerShell installed to gather the information needed to troubleshoot your issue and the version installed needs to be fairly recent. Windows 10 comes with version 5.1. So, if you have Windows 10, you can skip the next step here (Getting PowerShell).


Getting PowerShell
----------------------
By default you should already have Windows PowerShell installed if you are using any version of Windows, however, sometimes the version installed is out of date and isn't able to grab information needed. To get around this, you can install the most modern version of Windows PowerShell via Microsoft's website.

You can download the latest version of that here...

Windows PowerShell 7.2.6+ Winget or MSI Packages
https://docs.microsoft.com/en-us/powershell/scripting/install/installing-powershell-on-windows?view=powershell-7.2

When installing this software, make sure you tick the "Add to right click context menu". This will make it so that whenever you right click, you will have an option to run whatever you are highlighting through Windows PowerShell 7.2+.

Why do I need PowerShell?
You don't really need it but, you need it in our case to gather the troubleshooting information using a script I am providing to you as an alternative to a DXdiag. I highly recommend the DXDiag over this method but, this PowerShell Script Method also works just fine. You can also uninstall PowerShell after you are done gathering the info, if you installed PowerShell 7.2.6+, the version that came with your version of Windows is part of the operating system and while there are ways you can remove it, I highly recommend not removing portions of the Operating system willy nilly. The information provided is important in figuring out where the issues may lie and gives us a base line to help you get your problem resolved.

If you aren't willing to do it, I understand. Some people get scared when they are met with stuff they don't understand and well, good luck. No one can really help you without some sort of solid base line info to help you start troubleshooting. There is no way to really figure out what could be wrong without knowing what you are using in the first place.



Get the Script
-----------------

The following pastebin link will link you to the Windows PowerShell Script you are going to use to gather the info needed.

PowerShell Info Gather Script
https://pastebin.com/B9KBQWB2

Visit that link.
Copy the text in the pastebin link provided above.
Open a Windows Notepad and paste the stuff from the pastebin link into the Notepad.
Next hit file, Save as, and name the Notepad PSInfo.ps1.

Remember where you saved it. Example, C:\User\(Your User name)\Downloads or wherever you saved it.



Using the Script
-------------------

Once you have the script ready...
Navigate to the script location and right click, run with Windows PowerShell.

You will need admin rights for the script to run properly. So be aware of that.
If your account isn't admin, you need to start an admin Windows PowerShell window and navigate to the location of the script to run it. If you need help with that, let me know. There are also instructions within the script's comments to help get scripts running as most of the time scripts are disabled by default by Windows and you have to make changes on a per user basis to allow the running of said scripts. Again, instructions on how to do that and the commands required are inside the script itself, just open the script with notepad and start reading, it should be somewhere at the top of the script.

Wait for the script to gather the info.
Once done it will prompt you with...
"Press Enter to exit"

Hit Enter. It exits the script.
Open Windows File Explorer and go into the folder labeled C:\PSDiag, the script creates this folder to place a text file with the info collected by the script. Once you copy and paste all that info into a paste Bin link and post here on the forums you can then just delete the folder and the text file inside.
Inside the folder will be a text file, PSDiag.txt.
This text file will have a lot of the information needed to help start troubleshooting.
With the info in the PSDiag.txt Text file copied...
Create a temporary Pastebin post and provide the link to said post here on the forum.
Pastebin's website - https://pastebin.com/index.php

We can go from there.

Good Luck

[Chibbity]

It's a known issue with FSR 2.0 in DRG, I've heard FSR 2.1 fixes it; so use 1.0 till it gets updated.

I believe it's an unwanted/unintended complication with Temporal Anti Aliasing which FSR requires.