multiple Android clients (via Artemis/Moonlight), aiming to create 2 independent virtual displays

[Owlock]

👋 Hi everyone, just jumping in to support this discussion:

I’m also trying to use Apollo/Sunshine on Windows 11 with multiple Android clients (via Artemis/Moonlight), aiming to create 2 independent virtual displays — one for each device.

Despite configuring separate instances (ports, state files, etc.), the virtual display created by Apollo only works for one client, or gets duplicated/replaced when another client connects.

🔧 I've tested:

Custom .conf files and port separation

Independent sunshine_name and log_path entries

Fresh Windows 11 installs with SudoVDA only

Apollo-Fleet-Launcher & scripts from drajabr

And still... only one virtual display appears at a time, even if both clients are connected. Windows only recognizes one extra monitor.

💡 Feature request:
Please consider supporting multiple virtual displays from a single Apollo instance, or provide an official method to run multiple isolated instances, each bound to a persistent, separate virtual display (and client).

Even SpaceDesk and Deskreen allow extending the desktop to multiple clients — Apollo has the architecture to surpass them but needs native support for multi-display workflows.

🙏 This feature would benefit remote workers, productivity users, developers, and streamers — not just gamers. If there's any experimental branch or workaround, I’d love to help test it or provide logs.

Thanks for your hard work — this would be a game changer!

[ClassicOldSong]

I want, but the messy code written by Sunshine blocks me from implementing this.

It'll take a substantial amount of time to clear out the all messed up logic they have written so please bear with launching multiple instances for now...

[Owlock]

Hi @ClassicOldSong,

Thank you for your candid explanation about the challenges with the messy Sunshine codebase. I understand that implementing native multi-display support will take substantial time on your end.

Regarding your suggestion to "bear with launching multiple instances for now...", I wanted to provide more specific feedback on a tool designed for this purpose: the Apollo Fleet Launcher by drajabr.

I tried extensively to use Apollo Fleet Launcher (which is meant to manage multiple Apollo instances), but I encountered significant compatibility issues:

"Error: Invalid index."
"Please Upgrade to latest Apollo Version" (even after trying various recent Apollo releases from your repo and SudoMaker's site)
"Apps.json file doesn't include Desktop app, please clean install Apollo"
These errors persisted, preventing me from using the launcher to manage my multiple Apollo instances for extended virtual displays. It seems the launcher is extremely sensitive to the specific Apollo version it expects, making it unusable for current Apollo releases.

Given that Apollo Fleet Launcher aims to simplify managing multiple instances (which you suggested we "bear with" manually), would it be possible for you to communicate with drajabr (the developer of Apollo Fleet Launcher)? Perhaps a collaborative effort could:

Identify the exact Apollo version Apollo Fleet Launcher is designed for.
Or, update Apollo Fleet Launcher to be compatible with your current official Apollo releases.
Or, integrate a more robust multi-instance management feature directly into Apollo itself, bypassing the need for external launchers.
Solving this compatibility would significantly ease the burden of manual multi-instance setup for users like me who are trying to achieve multi-monitor extended desktops with Apollo.

Thanks again for your continuous support.

[ClassicOldSong]

You can open an issue to the Fleet Manager' repo.