Skip to content

Games running on SudoVDA Virtual Display dont expose resolution of the Virtual Display as an Option. #1453

Description

@Tyfui90

Goal:

  • Use Apollo with Moonlight to stream a Windows 11 Virtual Display of 2560x1600 90Hz to Steam Deck and run Red Dead Redemption 2 at that resolution.

Description:

  • Apollo creates a Windows Virtual display set at 2560x1600 90Hz by the moonlight client, Windows has this Virtual Display as the main display, and Windows disconnects the 4k tv HDMI screen automatically too.
  • RDR2 does not show the correct resolution options for any fullscreen, windows borderless, or borderless. They all only have the same options of 1920x1080, 1600x900, (1366x768 cant remember this one exactly) at 60Hz.
  • Technically I can use Apollo/Moonlight to stream the 4k 60hz TV output (No Virtual Display). This means that If I want a lower resolution & higher refresh rate to match the Steam Deck I need to lower the resolution manually I cannot increase the refresh rate due to 60hz being the TVs limit. Then I need to undo this change when I use the 4k tv directly again.

Desired behaviour:

  • I turn on my pc, (which is connected to my 4k TV over HDMI, The TV is off and stays off.)
  • The PC starts up, and Steam Starts automatically and enters into Steam Big Picture mode. (Windows does not yet have a connected display that is turned on, nor a Virtual Display.)
  • I open moonlight on my steam deck. (Moonlight is configured to start a 2560x1600 90Hz Virtual Display. Apollo is configured to open Steam Big Picture, to Always use Virtual Display, and shows SudoVDA is Ready.)
  • Moonlight starts and I am in windows looking at Steam big picture running on the Virtual Display. (Windows is correctly using the moonlight configured 2560x1600 90Hz Virtual Display, and the HDMI TV display automatically disconnects as windows has 'Only show on 2' automaitcally set when the Virtual Display connects.)
  • Open RDR2 & check display options.
  • See the Option to use RDR2 at 2560x1600 90Hz in any of fullscreen, windows borderless, or borderless.

Actual behaviour:

  • I turn on my pc, (which is connected to my 4k TV over HDMI, The TV is off and stays off.)
  • The PC starts up, and Steam Starts automatically and enters into Steam Big Picture mode. (Windows does not yet have a connected display that is turned on, nor a Virtual Display.)
  • I open moonlight on my steam deck. (Moonlight is configured to start a 2560x1600 90Hz Virtual Display. Apollo is configured to open Steam Big Picture, to Always use Virtual Display, and shows SudoVDA is Ready.)
  • Moonlight starts and I am in windows looking at Steam big picture running on the Virtual Display. (Windows is correctly using the moonlight configured 2560x1600 90Hz Virtual Display, and the HDMI TV display automatically disconnects as windows has 'Only show on 2' automaitcally set when the Virtual Display connects.)
  • Open RDR2 & check display options.
  • In RDR2, for fullscreen, windows borderless, and borderless in RDR2 they all only have the same options. of 1920x1080, 1600x900, (1366x768 cant remember this one exactly) at 60Hz.

Additional Information:

  • I have also tried this with Oblivion Remastered and No Mans Sky, and have the same issue with the Virtual Displays resolution not being available.
  • I had this issue with my 3080, and still have it after switching to a 7900XTX. So doesn't seem to relate to gpu drivers.
  • Setting Moonlight to 1280x800 60Hz, creates the Virtual Display correctly in windows, but games still do not expose this resolution option.
  • Steam autostarts while connected over HDMI to a 4k TV, that stays turned off, before Virtual Display exists/ is connected. Maybe this propagates resolution issues to games launched via steam big picture?
  • Apollo is also configured to open steam big picture when it is launched. Maybe this causing a conflicts since steam big picture is already running?
  • In Moonlight client there are the options for fullscreen, windows borderless, and borderless, do these have an impact on the Virtual Display that is created by Apollo?

Given the Virtual Display is always created with the set resolution & refresh rate, I assume its unrelated to Moonlight and maybe not Apollo either. It feels like a windows issue where windows is passing the null/blank resolution information from the disconnected TV over to games rather than the information of the created Virtual Display.

I would like to know if there is any insight or direction to take my troubleshooting from here. Or if there is a known workaround or fix for this or an issue similar to this.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions