Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Always get "connection timeout" in server #118

Open
reckter opened this issue Jul 25, 2024 · 3 comments
Open

Always get "connection timeout" in server #118

reckter opened this issue Jul 25, 2024 · 3 comments

Comments

@reckter
Copy link

reckter commented Jul 25, 2024

I cant get passed "Could not initiate connection for Apple-Vision-Pro.local.: connection timed out".
The App on the vision pro crashed after some time.
The few times I can click on "connect" in the APV, it shows a wireframe of my surrounding but never drops me into the steam VR room.

I`m on beta 3 vision os 2.
Tried woth both the public release (20.7.1) and the nightly version from the testflight.
Varous server versions none worked.

Any ideas?

@gekkehenkie11
Copy link

Same thing, used to work before

@ifokeev
Copy link

ifokeev commented Oct 27, 2024

I'm experiencing this due to different settings in the ALVR server. It could be the microphone settings or something else. It doesn't show any errors, just timeouts.

@bo3b
Copy link

bo3b commented Oct 30, 2024

I think I was forced into this box after a forced App update from the App Store. What was previously completely stable has been just auto-exiting after maybe 30 seconds. I'm not sure how the App store works, but if it's possible, I would like to kindly request that we be allowed to run at least one prior version to avoid being dead in the water after an update.

ALVR on PC does not seem to have any problems, but the log does say the client timed out. But that seems consistent with the AVP app crashing. I don't know how to find any logs or any diagnostic info on the AVP app. There is definitely some bug here that crashes the App on AVP, but I don't know how to narrow it down.


It's possible this is settings related, because after the update, I was forced to also move to the ALVR 20 protocol and am using v20.11.1. This also reset all my ALVR settings. I also updated the AVP to OS v2.1. Earlier ALVR builds do not help, and the nightly build is v21 and incompatible with AVP app.

In playing with settings- I'm seem to have a more stable setup by changing some defaults. Not sure, but Virtual Desktop is running OK for about 5 minutes now. Settings that I altered:

  • Presets:
  1. Preferred Framerate: 90 because lower settings are not supported in AVP app.
  2. Headset speaker: Disabled.
  3. Hand tracking interaction: Disabled.
  • Video:
  1. Bitrate: 340 Mbps. The default 30 is unusably bad. More than 340 seems unncessary, and is about all my router will accept.
  2. Maximum Buffering: 3.50 frames. I'm not sure but I think this one is critical.
  • Audio:
  1. Headset speaker: Off I don't know if this is supposed to work, but it never does for me.
  2. Headset microphone: Off
  • Headset:
  1. Controllers: On Probably On by default.
  2. Tracked: Off It's too confusing leaving these on while trying to use SteamVR.
  3. Handtracking interaction: Off It's currently too janky to be usable, even to simply close SteamVR dashboard. BTW- in SteamVR dashboard, go to settings and Advanced, and VR Dashboard on SystemButton to Off, to avoid having it block you at launch.

Edit: These settings lenthened the time to crashing, but I still get crashes that I can't fix. For something simple like VirtualDesktop streaming, it seemed OK and would not crash. But running a game or anything demanding still crashes in a few minutes.

i7-9600K at 3.6GHz, RTX2080, 32Gb, Samsung SSD. But of course crashes happen in Apple Vision Pro side.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants