I have a two monitor setup for my Zwift room, and would love to use the smaller monitor I have situated below the main display for the ZC.
The companion app runs just fine in the emalator and signs on correctly.
What is missing is the “GAME” option from the menu.
I suspect that the emulator is “Double-natting” the connection to the internet, and thus does not appear on the same network and the Zwift game. I have tried different emulators with the same results.
Is there a special way to maybe bridge these connections or somehow open up a port (no idea) to allow the two programs to communicate?
When I use ZC on my android phone its works great, as they are on the same network (192.168.1.0 network) and not natted to a different IP schemea.
Any ideas out there?
I have not done this, but I think it really depends on the capabilities of the emulator to enable bridging, or possibly bind it to a second network interface that’s on the same network so the discovery process will work. For example if the emulator supports connecting to physical USB devices, you could try using a USB Ethernet adapter and stick it on the same network. Probably best to talk to the community of people who use the emulator.
1 Like
I’ve used Bluestacks before and had no issues.
What Android emulator are you using?
edit - I see you’re also using bluestacks.
When I was doing it, I don’t think I had set anything in particular network wise.
Was it on the exact same PC as the GAME?
Yes it was running on the same computer that was running Zwift as well.
I had to stop using it at some point though a little while back, bluestacks decided my CPU all of the sudden didn’t have the requirements to operate? Or something happened.. I don’t recall.
With the changes to iOS coming soon though I’ll have to look back into trying it again.
Wish it weren’t such a resource hog though.
1 Like
Thanks for the quick reply! Are you on a MAC?
Windows 10.
I’ll try getting it back up and running again tonight if I can remember and see if I can find anything.
But I genuinely don’t recall doing anything strange on the setup, I’m fairly certain I just used the default which should be going through virtual ethernet.
1 Like
Follow up, got it reinstalled and with an instance using Android 13 Beta… same issue.
After loading it up and playing around I’ve noticed they’ve removed some of the network settings and just have you set it up via cellular service.
I’ll have to keep digging into it, but so far, same issue; the older version of bluestacks did not have this problem.
Okay so the vEthernet appeared this boot, and I noticed it had a strange IP, so I tried two things, DHCP, and also a fun one, stealing the IP of the phone I use for Companion (immediately after it was connected to Zwift and loading the map I did a IP swap)
Nothing.
So, I’m now under the assumption there’s something wonky going on with the network connection and how Bluestacks does it now, I can almost guarantee this is all that’s going wrong.
I think there are some APKs you can install or other things to really change the android settings since Bluestacks now uses a silly settings for android babies menu; something to give back full settings control.
The digging continues!
Really appreciate your tenacity on this one. I had given up. Good to see we have come up with the same hypothesis as to where the block is. I wonder if there is an archive for the older versions of BlueStack?
