Multiple Moonlight instances (to pair with Multiple Apollo instances)

[AokiMarcel-dev]

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.

[ClassicOldSong]

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.

[AokiMarcel-dev]

Awesome, that worked! thanks a lot. You're a machine man, such fast replies, most of the issues/discussions recognize that and I'm impressed as well!

I think the

"3. Add json state files: create as many empty .json files to be used as state file, like sunshine_1.josn, sunshine_3.josn, and sunshine_3.josn. You can copy the first sunshinbe_state.json so the 3 instances will use same username/pass combination."

part of the Drajabr's tutorial misled me to this.

Thanks again, it's perfect now! Hope I get a chance to support your patreon eventually =)

[drajabr]

Thanks @AokiMarcel-dev for your feedback, I already updated it.

I agree with you on that @ClassicOldSong Is a real machine 😜

And btw nice setup : )

[AokiMarcel-dev]

Lol, sorry, the misled was harsh hahah, didn't find a better word for it. I used your guide for hours yesterday, it's awesome (as I mentioned in the issue I opened on your repo =] ). The USB for Android portion awesome, great idea! Will try to implement here as well. And the PowerShell is fantastic too, without the need for any additional applications.

[drajabr]

Its okay, please let me know if there's something else is unclear/misleading about the rest of setup, tbh I believe I rewrite is needed, my english sucked, and probably someone can compile the same guide with far less words/sentences than I used.

[ClassicOldSong]

Your English is good enough to me, I'm not a native speaker as well and I can totally understand what you're saying