Resolution change bug (with Virtual Display)

[edel79]

Hello,

I have a bug when I want to change the resolution of my remote pc, on which I don't have any screen connected to, so I use the famous Virtual Display Driver by MTT.

At first, after the installation of your script, it is working, the initial screen resolution change is working... but not totally.
In fact during the resoultion change, the script is hanging at a point I don't understand. It seems related to the refresh rate, indeed here is the end of the initial run (the full one is attached to this tkcket) :

DÉBOGUER : Function Assert-ResolutionChange called with Width: 1920, Height: 1200, Refresh: 60
...
DÉBOGUER : Attempt number: 12
DÉBOGUER : Function Get-HostResolution called
DÉBOGUER : devMode.dmSize: 220
DÉBOGUER : Current modeNum: -1
DÉBOGUER : Current devMode.dmPelsWidth: 1920
DÉBOGUER : Current devMode.dmPelsHeight: 1200
DÉBOGUER : Current devMode.dmDisplayFrequency: 60
DÉBOGUER : Current host resolution: 1920 x 1200 x 60
DÉBOGUER : Refresh difference: 0

And just above that :

DÉBOGUER : Match found. Attempting to change resolution.
Resolution changed successfully.

As stated, this is the 12th and last attempt to change the resolution (already done), after that litteraly nothing occurs, the script is hanging, preventing every further action until this one is closed manually through the task manager.

Until that, the next attemps ends up with :

Exiting: Another instance of the script is currently running.

the previous one.

Here are the virtual screen resolution definitions I use :

_<global>
	<!--These are global refreshrates, any you add in here, will be replicated to all resolutions-->
	<g_refresh_rate>60</g_refresh_rate>
	<g_refresh_rate>90</g_refresh_rate>
	<g_refresh_rate>120</g_refresh_rate>
	<g_refresh_rate>144</g_refresh_rate>
	<g_refresh_rate>165</g_refresh_rate>
	<g_refresh_rate>244</g_refresh_rate>
</global>

    <resolution>
        <width>1920</width>
        <height>1080</height>
        <refresh_rate>30</refresh_rate>
    </resolution>
    <resolution>
        <width>1920</width>
        <height>1200</height>
        <refresh_rate>30</refresh_rate>
    </resolution>_

With that on the Windows display settings I can see these two resolutions among others, and all the refresh rates from 30 to 244.

Can you telle me what's wrong ?

log_1740161580.txt

[Nonary]

I don't see any bugs in the log, it changes the resolution and double checks to see if it applied up to 12 times. The script won't change the resolution again until you have fully closed out the stream in Moonlight, or you have stopped streaming and the grace period got triggered (configured in settings.json)

Try streaming your desktop and let me know if it changes fine there

[edel79]

OK so the initial execution is OK. But what's not is that on my case the script doens't detect the end of the streaming session.
When I close the session and open a new one, the previous execution of the script is still alive (I can see it on the task manager and the fact the previous log file is still on the edit mode), so the new one can't operate and I get the Exiting: Another instance of the script is currently running message, at least until the grace period has not ended.

Running only with the desktop produces the same effect : the end of the streaming session is not detected. I close it via the standard key combination : Ctrl+Alt+Shift+Q

How to find out this session ending bug on the logs ?

[Nonary]

How are you closing the session? In moonlight you need to exit and then go back into the host and then click on the X to end stream.

Simply minimizing client or control shift Q does NOT end the stream, it only suspends it

[edel79]

That's the point, the official Moonlight wiki states :
Ctrl+Alt+Shift+Q - Quit the streaming session (leaving the game running on the host PC)
So this shortcut should be treated as session closing as anyway at the this point it is not displayed anymore.

I don't understand how to do
go back into the host and then click on the X to end stream
how to do that outside of a Moonlight session ?
You mean on the Moonlight client running locally from where the session was launched ? but in this case this is not the host. And even, I don't have the X to end stream on the Moonlight client (I'm running the Mac version).

I need more explaination I guess :)

[Nonary]

If you can't figure out how to close the session, change the grace period in settings.json to like 4 seconds instead.

On Mac I think you have to right click the app with the play button icon to end stream, can't remember exactly.