carl-anders / slimevr-wrangler Goto Github PK

My computer has issues connecting the joycons through bluetooth although its 4.2 bluetooth. But my phone connects flawlessly and it would be cool if there was an app for slimewrangler for android or even just have it implemented onto owotrack’s app.

in #21, I broke out the serialization description into its own crate. I would love if we could transfer this crate into the main SlimeVR rust monorepo as I think that its generally useful in projects wishing to communicate with the SlimeVR server as trackers, such as the firmware me and @ImUrX are writing

Would be really good if this code could be relicensed under more permissive licenses

Maybe implemented as a command line switch.

For Linux this would allow disabling the use of hidraw that apparently can cause instability in some cases. It also allows using Joycons for purposes other than use with slimevr-wrangler (ie. Joycons in single mode get used by the wrangler, while Joycons in combined mode are not)

I'm building some rust firmware for SlimeVR and I'd like to use the code that describes the packet formats. I think this code is generally useful and can probably be refactored into its own crate, possibly even hosted under the SlimeVR-Rust monorepo.

I'll submit a PR to do this refactoring at some point, if no one else beats me to it :)

Is PS4/PS4 Wireless Controller support possible?

• Should it use the factory or user calibration?

I have 6 Joycons here I am attempting to use for FBT. I was attempting to put all 6 on the wrangler at the same time, however it seems I can only connect 3 of them at time max. The only correlation I can put to this is that all the controllers that seem to connect are on the same side, left or right controllers. I can switch between connecting all of each type, but I can never connect both at once. I have already attempted to connect them in alternation, Attempted to connect them all to windows before launching the wrangler, attempted to connect them by the pairs they were bought in, everything. I know it's in alpha, but I have gotten 5 controllers connected off of a fluke when I freshly downloaded the software, so I have no idea why it's not connecting.

I wanted to make sure I put in this as an issue so it could be looked at for viability. The Joycons are more than capable of doing it, but I am unsure how it would get the haptic data via OSC. Apologies if this is out of scope for this project.

The default SlimeVR server can only take up to 2 rotational inputs from each IP. One from the packet type 1 and packet type 16. Since this seems to only use packet type 1 it sends all the rotational data to one tracker. Adding an option for every pair of joycons to have a different IP could allow for redirecting the packets from another device like a phone.

Mostly my joycons would only rotate, but not following the motion. Don't know if my joycons have a problem or not, any advice?

the newly steam joycon support kinda screw up the software on detecting the joycon
when i have my steam opened the joycon are automaticly connect to steam and unable to search
as trackers with slimevr wrangler,need some solution on that (maybe disable joycon connected as steam controller)
the only way to pair controller as tracker is when the steam is closed

I am unsure of what is causing this "lag" in particular as each time I open the software my computer freezes in a pattern even when I try to pair my joy con. the one time I got it to not do this was starting up the sever and pairing a joy con ( which now isn't even connecting to my PC for some reason ). and I don't know if this has anything to do with it but after setting them up I went to pair them in slimevr and a controller had turned off. I reconnected it but it and another controller just disconnected after and as I said I have tried twice after that to reconnect them but they aren't connecting via bluetooth.

The pro controller can defo connect via bluetooth but I also think it has the same IMU's as joycons as I do remember being able to physically turn the controller in mario kart to steer?

(I'm not demanding you add this right away, its just a suggestion and I think what you're working on is really cool and will help bring slime VR to alot more people)

If I open the executable, it will open and close a command prompt window. It does nothing else. I reinstalled windows and still have the problem. It opened fine the first time I installed windows on my laptop before installing any drivers for the laptop.

So when I connect a single joycon it will work perfectly for a few minutes and then it's roll, pitch and yaw slow down to an absolute crawl after the Status says "Laggy IMU" for a split seccond and then goes back to "Healthy", or it will happen when two are connected, one connects right after the other. it's a very weird issue that keeps appearing and makes using node wrangler unusable.

I've tried it with the reg and blue joycons from my launch switch and a brand new pair of green and pink ones and the issues persists. I event tested versions 0.8 and 0.9 and the issue appears.

I mannaged to record of gif of one work and one not working, I am moving both joycon the exact same amount at the same time for this entire gif:

the status is "healthy" when connecting to just one joycon,but when connects to 2 or more,the status gets unstable,switching from healthy to laggy frenquently

says "disconnected. trying to connect to 127.0.0.1:6969"
how do I fix this

Title is self explanatory

so i have all my joycons and pro controller connected via windows but wrangler doesnt read all of them

I had recently factory reset my computer and I had installed VRchat and steam vr. But for some reason the program keeps crashing and won't let me launch it. Any Ideas of what may be causing this.

i am trying to use a pro controller and two joy-cons with this program and can not get more than two of the three to show up in slimevr wrangler, no matter how much time i spend dis- and reconnecting the controllers. every controller is connecting fine to my computer and even with all three connected simultaneously they are all fully functional and usable. in fact, i've tested a fourth controller and noticed not even the slightest drop in functionality for any single one of them. this is immensely irritating, especially with it being the only tool of its kind and no functional solutions around.

i would like to reiterate: my setup is completely functional. the aforementioned issues i am experiencing are exclusively on the program's end.

All the devices on my pc disconnect then the joy cons are just saying "Paired"

i was wondering how many joycons you needed

My left Joycon drifts at a constant rate on the Yaw axis. I was wondering if there's a way to implement a way to compensate any drift by doing a calibration.
Simply asking the user to lay their Joycons flat for a few seconds, detecting the drifts in degrees/second, and sending compensated gyro data to SlimeVR. Or simply having a manual calibration tool where users can at least input the compensation themselves.

Here's a video that demonstrates the effect (doesn't happen on the right Joycon so it's not a Wrangler issue) : https://www.youtube.com/shorts/cyWSeClkVUs

Would it be possible to add support for Wiimotes that have Wii Motion Plus? They have a gyroscope, although I don't know how you'd implement their support in Rust as the current input interpreters are only in C, Java, Python... (maybe with a C -> Rust thing?). I'm no programmer so I'm not qualified to know if it's doable, but I'd love to see this feature as I have 2 Wiimotes almost begging me to be used for Full Body Tracking.

Wiimote libraries : http://www.wiibrew.org/wiki/Wiimote/Library
Wiimote motion analysis (only for the accelerometer tho) : http://www.wiibrew.org/wiki/Wiimote/Motion_analysis

Thanks in advance!

(I can even provide contact info if you need to test the program with actual hardware)

The error outputed in the console is as follows:

Last login: Wed May 17 19:39:57 on ttys002
/Users/---/Desktop/slimevr-wrangler ; exit;
---@macbook-pro ~ % /Users/---/Desktop/slimevr-wrangler ; exit;
thread 'main' panicked at 'wgpu error: Validation Error

Caused by:
In Device::create_render_pipeline
note: label = iced_wgpu::triangle::gradient pipeline
Internal error in VERTEX | FRAGMENT | VERTEX_FRAGMENT shader: new_render_pipeline_state: "Compiler encountered an internal error"

', /Users/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/wgpu-0.14.2/src/backend/direct.rs:2403:5
note: run with RUST_BACKTRACE=1 environment variable to display a backtrace

Saving session...
...saving history...truncating history files...
...completed.
Deleting expired sessions...none found.

[Process completed]

When I try to launch the .exe, I get a blue loading circle next to my pointer for a moment, and then nothing happens.

thread 'main' panicked at 'WaylandSurface failed: ERROR_OUT_OF_HOST_MEMORY', /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/wgpu-hal-0.14.1/src/vulkan/instance.rs:373:69
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
warning: queue 0x564c5de0d5b0 destroyed while proxies still attached:
  xdg_wm_base@20 still attached
  wl_output@14 still attached
  wl_output@13 still attached
  zwp_text_input_manager_v3@12 still attached
  xdg_activation_v1@11 still attached
  wl_subcompositor@10 still attached
  zwp_relative_pointer_manager_v1@9 still attached
  zwp_pointer_constraints_v1@8 still attached
  wl_seat@7 still attached
  wl_shm@6 still attached
  zxdg_decoration_manager_v1@5 still attached
  wl_compositor@4 still attached
  wl_registry@2 still attached

This is the command line output when trying to run the application with provided instructions.