ALVR Dashboard won't open

[Furby667]

Description

I downloaded ALVR to try out some PCVR titles but I can't open ALVR dashboard. I upgrade to the latest versions of Windows 10 and it still won't open ALVR Dashboard.

General Troubleshooting

• [x] I carefully followed the instructions in the README and successfully completed the setup wizard
• [x] I read the ALVR Wikis here and here

Environment

Hardware

Note: for Linux, an upload to the hw-probe database is preferred: hw-probe -all -upload

CPU: Intel Core i3 2350M

GPU: Intel HD Graphics 3000

GPU Driver Version: 9.17.10.2849

Audio: Intel Display Audio

Installation

ALVR Version: ALVR v21.0.0-dev00+nightly.2023.09.30

ALVR Settings File: N/A

SteamVR Version: 1.27.5

Install Type:

• [x] Packaged (exe, deb, rpm, etc)
• [ ] Portable (zip)
• [ ] Source

OS Name and Version (winver on Windows or grep PRETTY_NAME /etc/os-release on most Linux distributions): Windows 10 22H2 (19045.2006)

[zmerp]

Can you try the debug build of ALVR nightly? Open cmd and launch ALVR (so the terminal doesn't immediately close), then copy here the terminal output.

[Furby667]

This is what it gave me.

"[22:00:29.583960700 DEBUG eframe] Using the glow renderer [22:00:29.612007600 DEBUG eframe::native::run] Entering the winit event loop (run_return)… [22:00:29.631349800 DEBUG eframe::native::run::glow_integration] trying to create glutin Display with config: ConfigTemplateBuilder { template: ConfigTemplate { color_buffer_type: Rgb { r_size: 8, g_size: 8, b_size: 8 }, alpha_size: 8, depth_size: 0, stencil_size: 0, num_samples: None, min_swap_interval: None, max_swap_interval: None, config_surface_types: WINDOW, api: None, transparency: false, single_buffering: false, stereoscopy: None, float_pixels: false, max_pbuffer_width: None, hardware_accelerated: None, max_pbuffer_height: None, native_window: None } } [22:00:29.792208200 DEBUG eframe::native::run::glow_integration] using the first config from config picker closure. config: Wgl(Config { inner: Config { hdc: 453054384, pixel_format_index: 2 } }) [22:00:29.793100700 DEBUG eframe::native::run::glow_integration] successfully created GL Display with version: WGL and supported features: FLOAT_PIXEL_FORMAT | SWAP_CONTROL | MULTISAMPLING_PIXEL_FORMATS | SRGB_FRAMEBUFFERS [22:00:29.799773400 DEBUG eframe::native::run::glow_integration] creating gl context using raw window handle: Some(Win32(Win32WindowHandle { hwnd: 0x8040a, hinstance: 0x7ff7f94c0000 })) [22:00:29.806087800 WARN eframe::native::run::glow_integration] failed to create context using default context attributes ContextAttributes { release_behavior: Flush, debug: false, robustness: NotRobust, profile: None, api: None, shared_context: None, raw_window_handle: Some(Win32(Win32WindowHandle { hwnd: 0x8040a, hinstance: 0x7ff7f94c0000 })) } due to error: [ffffffffc0072095] OS Error -1073274731 (FormatMessageW() returned error 317) (os error -1073274731) [22:00:29.806868800 DEBUG eframe::native::run::glow_integration] retrying with fallback context attributes: ContextAttributes { release_behavior: Flush, debug: false, robustness: NotRobust, profile: None, api: Some(Gles(None)), shared_context: None, raw_window_handle: Some(Win32(Win32WindowHandle { hwnd: 0x8040a, hinstance: 0x7ff7f94c0000 })) } [22:00:29.810219500 ERROR eframe::native::run] Exiting because of error: Glutin(Error { raw_code: None, raw_os_message: None, kind: NotSupported("extension to create ES context with wgl is not present") }) on event Resumed [22:00:29.812412900 DEBUG eframe::native::run] Asking to exit event loop… [22:00:29.828398000 DEBUG eframe::native::run] Received Event::LoopDestroyed - saving app state… [22:00:29.829054300 DEBUG eframe::native::run] eframe window closed thread 'main' panicked at 'called Result::unwrap() on an Err value: Glutin(Error { raw_code: None, raw_os_message: None, kind: NotSupported("extension to create ES context with wgl is not present") })', alvr\dashboard\src\main.rs:107:6 note: run with RUST_BACKTRACE=1 environment variable to display a backtrace"

[zmerp]

Unfortunately this unactionable because the error is in a third party library. On another note, your Intel HD Graphics 3000 will never be able to run VR games properly.

[github-actions[bot]]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.