Cannot run StardustXR server
I get the error, when running
cargo run
:
``rust
āÆ cargo run
Finished dev [unoptimized + debuginfo] target(s) in 0.11s
Running
target/debug/stardust-xr-server`...Can't Seem to Launch Any Applications
This is my first time attempting to run Stardust. I have a Quest 3 and I'm able to connect to the headset and run the Stardust server. It's all black but I can see 2 cones for my controllers.
However, from here I'm unable to launch any applications. flatland appears to run when it's invoked from the command line but there is no output nor anything to be seen in the headset. While flatland is running, I attempted to run some applications with gravity, but nothing seems to appear.
If I'm being honest I'm not sure I'm running flatland or gravity correctly. For flatland I just run
cargo run
. Should I see anything after running flatland?...Can not run wayland applications under stardust
I built stardust-xr-server on Arch, started it with its own XDG_RUNTIME_DIR (otherwise my desktop becomes unusable), and tried to connect weston-terminal to it with ...
WAYLAND_SOCKET=/tmp/stardust-xr-0/wayland-0 weston-terminal
. Weston-terminal only outputs this:
failed to connect to Wayland display: Success
failed to create display: Success
failed to connect to Wayland display: Success
failed to create display: Success
How to connect Meta Quest?
I've just install the server successfully. Now I want to run it with my Meta Quest 3 but I don't know from where should I start š
GL_INVALID_FRAMEBUFFER_OPERATION
just have built stardust and it shows the error right after run:
...
ERROR main smithay::backend::renderer::gles: 486: [GL] GL_INVALID_FRAMEBUFFER_OPERATION in glDrawElementsInstanced
ERROR main smithay::backend::renderer::gles: 486: [GL] GL_INVALID_FRAMEBUFFER_OPERATION in glClear(incomplete framebuffer)
ERROR main smithay::backend::renderer::gles: 486: [GL] GL_INVALID_FRAMEBUFFER_OPERATION in glDrawElementsInstanced
ERROR main smithay::backend::renderer::gles: 486: [GL] GL_INVALID_FRAMEBUFFER_OPERATION in glClear(incomplete framebuffer)
keyboard & mouse input issues
@Nova I followed up a bit this morning on some of the issues we were looking at earlier. IDK how many of these issues are known but hopefully this is useful
Observations with
-f
(and nothing in ~/.cargo/bin
š ) so far, using QT_QPA_PLATFORM=wayland WAYLAND_DISPLAY=wayland-0 DISPLAY= kate
as my test application:
What works: right click to drag, left click to click without dragging...stardust server build errors on fresh Arch install
All, hoping to get some insight, hitting the attached error while trying to build server on a fresh Arch install. Thanks in advance!
error when starting stardust server (bad egl parameter)
when trying to start the server i get this error about egl
```
2023-07-04T14:40:45.265535Z ERROR main smithay::backend::egl::ffi: 64: [EGL] 0x300c (BAD_PARAMETER) eglQueryDmaBufModifiersEXT: EGL_BAD_PARAMETER error: In eglQueryDmaBufModifiersEXT: Invalid format
...
WiVRn 'filters must be initialized before linking'
*attached neofetch screen snip for my system info + wivrn log
i ran into this issue on my last stardust attempt and downgrading ffmpeg worked~ but turned out to be too unstable after the initial shine wore off https://github.com/Meumeu/WiVRn/issues/1
ive now updated my system and switched to ffmpeg-git and integrated graphics to try and narrow down the issue without any luck......
cargo build error while compiling smithay
The exact issue is with rust 1.69
error[E0277]: the trait bound `Boottime: ClockSource` is not satisfied
error[E0277]: the trait bound `Boottime: ClockSource` is not satisfied
protostar - tests failing
```
Finished test [unoptimized + debuginfo] target(s) in 0.07s
Running unittests src/lib.rs (target/debug/deps/protostar-e14b68abae2a9f7f)
running 4 tests...
molecules - tests failing
```
Finished test [unoptimized + debuginfo] target(s) in 0.04s
Running unittests src/lib.rs (target/debug/deps/stardust_xr_molecules-c0b6ff7264407201)
running 2 tests...
compile error - server
``error[E0277]:
PanelItem doesn't implement
std::fmt::Debug`
--> src/wayland/xdg_shell.rs:209:2
|
205 | #[derive(Debug)]
| ----- in this derive macro expansion...`comet` 6DoF
Comet is starting me way below where the pen is, using North Star + Monado.
- Tried restarting
monado-service
, stardust-xr-server
, and comet
with headset on.
Here is my North Star config for Monado: https://gist.github.com/sambilbow/91e1f794a6c757aa368c17ee8e01a20e...`./xr-terminal.sh` behaviour
Running
./xr-terminal.sh
opens alacritty
on my main monitor. Despite a monado-service
running connected to my North Star. Stardust XR does seem to be connecting to the service and showing my hands on the headset though.What is the list of nessacry packages on ubuntu to install stardust?
```
silverdev2482@silverdev2482-Standard-PC-Q35-ICH9-2009:~/stardust-xr-server$ cargo build
Compiling proc-macro2 v1.0.53
Compiling quote v1.0.26
Compiling libc v0.2.140...
North Star + StardustXR
Hello! I have
monado-git
and openxr-git
installed from the AUR. I'm running kwin wayland. I have a North Star plugged in via USB/DP and stardust-xr-server
installed via the documentation instructions.
When I run cargo run
I get the server window on my main monitor. Ideally I want it on the headset, how do I make Stardust talk to Monado and do the things ā¢ļø ? New to most of this as coming from Unity development, so be gentoo with me š
Perhaps this is a bit more of a Monado question, as I dont think I have things running properly with that yet. I don't mind not running in direct mode, which is apparently not possible with wayland anyway. Any pointers from North Star running devs here?...Error while compiling stardust-xr-server on gentoo
error: could not find native static library
StereoKitC, perhaps an -L flag is missing?
error: could not compile
stereokit-sys` due to previous error
Caused by:...XDG variable error
thread 'event_loop' panicked at 'Unable to find a free stardust socket path', src/main.rs:238:40 any fixes for this ?