Multiple Moonlight instances (to pair with Multiple Apollo instances) #325
Replies: 4 comments 30 replies
-
|
Do not copy over the state file, instead you should remove one of them and let them auto recreate. The state file contains the server identity which is generated only once per instance, copying them makes them identical to the clients. |
Beta Was this translation helpful? Give feedback.
-
|
Hi all, first thanks also from my side to @ClassicOldSong for initiating Apollo which makes the sunshine/moonlight experience even better by introducing VDA! At least for Windows VMs this makes my dream of using multiple displays without tools like parsec or RustDesk come more true :) Ultimately Linux support would be a mind blower! What I am trying to achieve is a dual display Apollo <> Moonlight solution. My test setup: Host:
Client:
A single desktop or virtual desktop connection worked seamlessly. Unfortunately I wasn't able to get a second instance of Apollo up and running.
No problems here I would say. Only admin rights needed and created
In "sunshine.conf" I only find a one liner:
--> I added your entries below the existing line
I elevated my rights according to this video and tried a Then I had a closer look at the instructions of @drajabr and was a bit overwhelmed by his AHK script. So I decided to include his steps about the .json files first and see if I get it manually running
Since I read @ClassicOldSong's answer on @AokiMarcel-dev's initial question I made the mistake and deleted the Then I decided to stick more to @drajabr's instructions:
Already done
Did this
Cloned the repo to my downloads folder and unzipped it
Why do the config files from @drajabr contain additional parameters? Are they documented somewhere? --> Added the content of @drajabr's sunshine_1.conf to my
This was already done
Where should I look for filenames and paths? Not sure where to adjust @drajabr's file names to mine ...
Did this > no additional Apollo icon appeared in the taskbar. Also Moonlight doesn't show me additional connectivity options.
Would love to do so :P Sorry for my long question, but I'd really like to proceed here - thanks! |
Beta Was this translation helpful? Give feedback.
-
|
I'm working on a simple GUI-based tool to do particularly this, currently its basic functionality but more features coming soon (very soon) You can check it at: https://github.com/drajabr/Apollo-Fleet-Launcher |
Beta Was this translation helpful? Give feedback.
-
|
Hi there, will this solution (or apollo fleet manager) can manage two separate virtual display SudoVDA ? or do i need to install a second virtual display tool ? many thanksk |
Beta Was this translation helpful? Give feedback.

Uh oh!
There was an error while loading. Please reload this page.
-
Hi, wanted to start thanking you for all the work you've put into this fork! The project is amazing. Loved using Moonlight+Sunshine, and Apollo makes this combo even better, with the virtual displays and auto resolution/refresh. Now I'm able to easily use my Legion Go as an additional display.
Now for my suggestion (not sure if it's already out there / work around in place, couldn't find it yet): An extension to your solution for multiple Apollo instances (as written in your wiki, and also in @drajabr's repo you link on the same wiki). Which is multiple moonlight instances, each containing a different connection to the separate Apollo instances.
Background why: I have the Legion go + portable monitor that I'd like to both be connected to the same gaming PC host. When I created the multiple Apollo instances, one for the Legion go screen and one for the portable monitor (following both guides above), I was able to connect 2 different instances of moonlight to each. Issue is that since it's the same host, with the same IP (but different ports and sunshine_name in their respective sunshine_x.conf) for some reason moonlight replaces one connection with the other (and they're not automatically found through the moonlight scan, only one of the instances shows up). The only work around i found was to open moonlight twice, connect to Apollo Instance #1, then go to second moonlight, and manually add the PC with the Apollo Instance #2 port. This then replaces the first connection and now I have both connections.
So every time I want to reproduce this setup, I need to manually add the other connection that got replaced (which I believe happens since it's the same IP). Would be nice to have different connections appearing for each port. And possibly have a way to manually create more virtual displays and project them to the additional monitors, using one single Artemis (once that's available on other platforms) and one single Apollo client. I read on other posts you have something like that planned, just don't have the time to do it.
Beta Was this translation helpful? Give feedback.
All reactions