hansschmucker / NVStreamer1080

Utility to automatically detect NVidia GameStream activity and set a fitting resolution or switch to a second screen.
Apache License 2.0
112 stars 8 forks source link

Not returning resolution #10

Open Gareth-Power opened 2 years ago

Gareth-Power commented 2 years ago

Im switching between from 25601440 to 1280800 perfectly, but its not changing back. I have a single monitor. Its logging that the session is ended and its attempting to reset, but no change.

hansschmucker commented 2 years ago

Hi @gurrier , could you please post a screenshot, especially with the log scrolled down to the selected part if it exists: image

Gareth-Power commented 2 years ago

Hi, see attached, definately not returning the resolution currently. I cant make the window larger to see the rest of the log Screenshot 2022-10-25 213744

hansschmucker commented 2 years ago

Thanks.... hmmm... my best guess is that the API somehow won't accept 144... or maybe it's not actually 144 but a fraction. I've done some digging into better ways to set a non-integer refresh rate, but sadly haven't found a solution yet.

hansschmucker commented 2 years ago

BTW the new version has an override feature for custom resolutions and refresh rates. Maybe try setting a custom return resolution like 1920x1080x60 ... if that works we at least know that it's an issue with that specific resolution and refresh rate.

juzta commented 2 years ago

I have the same issue as above. Going from 3440x1440@144 to 3840x2160@60 works but at application exit it doesn't switch back. I also tried your suggestion above but also to that resolution it doesn't switch. The log screen is displaying "Restoring resolution 1920x1080@60".

Also tried the following with no results: 1280x1024@60 to see if aspect ratio maybe

What works though is going from 3440x1440/144 to 1920x1080/60 and back to 3440x1440/144 3440x1440/144 to 1280x1024/60 and back to 3440x1440/144

It seems switching back from 3840x2160 to something else is the problem here.

Using an 3060 Ti with driver release 522.25.

Update 3: What also works is going from 3440x1440/144 to 1920x1080/60 and to 3840x2160/60

But then trying again with same settings (so the monitor is in 3840x2160/60) to 1920x1080 it doesn't switch to 1920 and stays in 3840x2160.

Hopefully this helps you in some sort of direction!

hansschmucker commented 2 years ago

Thanks @juzta that actually helps a lot because it means that switching back to specific resolutions is the issue... Not sure when I'll get around to doing it, but next build I'll include a few debug switches so you can try different ways of restoring the resolution.... hopefully we'll find something that works.

hansschmucker commented 2 years ago

Uh wait... it shouldn't say Restoring resolution 1920x1080@60 ... urgh... that's probably a bug on my part.

juzta commented 2 years ago

Oke, tried some more resolutions. I do not see a direct link.

Works with 2560x1440@60 > 1920x1200@60 > 2560x1440@60 Works with 2560x1440@60 > 3840x2160@60 > 2560x1440@60

Doesnt work with 2560x1440@60 > 1920x1080@60 > 2560x1440@60 Doesnt work with 2560x1440@60 > 1920x1080@60 > 1280x1024@60 Doesnt work with 2560x1440@60 > 1920x1080@60 > 1680x1050@60 Doesnt work with 1920x1200@60 > 3840x2160@60 > 1920x1200@60 Doesnt work with 1920x1080@60 > 3840x2160@60 > 1920x1080@60 Doesnt work with 3840x2160@60 > 3840x2160@60 > 1920x1200@60 Doesnt work with 3840x2160@60 > 3840x2160@60 > 3440x1440@60 Doesnt work with 3840x2160@60 > 3840x2160@60 > 3440x1440@144 Doesnt work with 3440x1440@144 > 3840x2160@60 > 3440x1440@144 Doesnt work with 800x600@60 > 1280x960@60 > 800x600@60

The log keeps saying its "Stream end detected" and restoring to that specific resolution even though it is not.

Pe4CeFu11 commented 1 year ago

just wanted to bump this as im also having the same issue as everyone else here. going from 3840x1440p 144hz > 1920x1080p 60hz. and i can not return to original resolution. Logs show that it should of worked but did not

Konrad25W commented 1 year ago

I just wanted to bump it, unfortunately, this issue still exists.