Jittery image in game, can't get rid of it even if LS is not running

[Kaktuszfüge]

I bought LS a few days and wanted to test it on MH: Rise, I was mainly interested in trying the scaling options.

After adding the game exe and clicking a few options (can't tell which because since then I reverted back everything to default) I immediately noticed that the game is super jittery in Windowed or Borderless with Vsync on. I realized I may have messed a setting up or something, so just to confirm the culprit I closed the game, reverted back everything to default in LS and closed. To my surprise the jitter remained.

I'm not even sure how that is even related to LS, but nothing else has been installed, etc just LS. Since then I reinstalled the game, uninstalled LS completely, deleted the games shaders, reset driver shaders, no change.

Any idea what's causing the issue and how to fix it?

Issue in action:
https://cdn.steamusercontent.com/ugc/47956727089208193/8911F8F25B1AF6BDDFD1CE51F74DCECCE82DC0C1/

[Gizzmoe]

It's not related to LS, so the MH forum is the right place to ask to help.

[Kaktuszfüge]

The issue came up since the usage and purchase of LS, MH has not been modified in any way (patch,mods, settings) for weeks from my side. The only variable is LS, so I'd assume it is related.

Especially since the last time I saw 'jittering' like this it was also related to game capture, which is something that LS does (if my surface level understanding of it is correct).

Edit: Also, what makes you say that it is not related to LS?

[Gizzmoe]

Originally posted by Kaktuszfüge:

Edit: Also, what makes you say that it is not related to LS?

LS doesn't modify anything on the system. And the problem is even there when LS is not running.

[Kaktuszfüge]

Originally posted by Gizzmoe:

LS doesn't modify anything on the system.

I'm not saying it does. But what *does* it modify other than its own files? Shaders?

Originally posted by Gizzmoe:

And the problem is even there when LS is not running.

You are right! That does imply the issue is elsewhere. All the other clues point to LS though. The main one is that the game's behavior *only* changed after trying LS, so it must have tangled with something. It is also possible that is an undiscovered bug.

[the$silver]

Originally posted by Kaktuszfüge:

Originally posted by Gizzmoe:

LS doesn't modify anything on the system.

I'm not saying it does. But what *does* it modify other than its own files? Shaders?

Originally posted by Gizzmoe:

And the problem is even there when LS is not running.

You are right! That does imply the issue is elsewhere. All the other clues point to LS though. The main one is that the game's behavior *only* changed after trying LS, so it must have tangled with something. It is also possible that is an undiscovered bug.

Lossless scaling DOES NOT modify any of the files of the game, in fact it doesn't even read those files, it is just an overlay that shows generated frames between the real ones. It doesn't inject anything at all and it doesn't access any other file other than itself.

It works by capturing the real frames with the windows APIS like dxgi and wgc (like a screen capture software) and then process them to generate the needed frames. that's why compared to in-game frame generation, LS has more artifacting.

[Kaktuszfüge]

Originally posted by the$silver:

Originally posted by Kaktuszfüge:

I'm not saying it does. But what *does* it modify other than its own files? Shaders?



You are right! That does imply the issue is elsewhere. All the other clues point to LS though. The main one is that the game's behavior *only* changed after trying LS, so it must have tangled with something. It is also possible that is an undiscovered bug.

Lossless scaling DOES NOT modify any of the files of the game, in fact it doesn't even read those files, it is just an overlay that shows generated frames between the real ones. It doesn't inject anything at all and it doesn't access any other file other than itself.

It works by capturing the real frames with the windows APIS like dxgi and wgc (like a screen capture software) and then process them to generate the needed frames. that's why compared to in-game frame generation, LS has more artifacting.

Thanks for the info!

I'm trying to figure out why this issue happened exactly when I started to use LS, why the issue looks similar to one I've had years ago (which was related to game capture by OBS; on a different rig alltogether) and if it isn't related to LS, what the heck could it be?

[the$silver]

probably a driver setting changed, or maybe a setting in the game that changed. I will suggest to re-install your graphics drivers. maybe do a clean install with DDU (display driver uninstaller).-

[Kaktuszfüge]

Originally posted by the$silver:

probably a driver setting changed, or maybe a setting in the game that changed. I will suggest to re-install your graphics drivers. maybe do a clean install with DDU (display driver uninstaller).-

Good tips. Game settings have been ruled out. Driver has been rolled back, factory reset, etc, issue still present. I do plan to fully uninstall the driver with DDU, so that's the next step.

[the$silver]

hope this fixes it...

[Fallingferret]

does it still happen if you restart the game and just leave it in borderless windowed throughout? cause that issue looks awful familiar, and the last time i played rise was loooong before i ever started using LS

[Kaktuszfüge]

Originally posted by Fallingferret:

does it still happen if you restart the game and just leave it in borderless windowed throughout? cause that issue looks awful familiar, and the last time i played rise was loooong before i ever started using LS

Yep, the issue was consistent and persistent. The only way to workaround was to use Fullscreen or have Vsync off.

Turns out it was indeed an AMD driver issue. There was a driver update on the same day I started using LS, but I somehow forgot or didn't notice. But I also ruled out driver issue as an option since I rolled back to a much earlier driver and the issue was still there.

Cleaning the driver completely with DDU and using one before the latest driver did fix the issue.

Appreciate the help guys!