-
Notifications
You must be signed in to change notification settings - Fork 50
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
Pico 4 Ultra Controllers #269
Comments
Hrm. That definitely sounds like they're intercepting the HTTP request and returning their own internal assets. Which I'm not exactly a fan of, but I guess could work out in some limited cases assuming that the assets that they deliver are actually well formatted and aligned. It's unfortunate that they don't seem to have taken the time to validate that here. (Also, this approach won't work for any sites not using that specific CDN.) @song-fangzhen has contributed assets to this repo in the past on behalf of @picoxr. Perhaps they know who to direct this to? Unfortunately there's nothing that can be done on our side aside from ask that these devices be contributed to the public assets and used normally? Thanks for the analysis, though. It's helpful to know that these kind of strategies are being employed by the hardware manufacturers. |
You're welcome. It looks like @song-fangzhen's last commit in GitHub was October 2023, so I may do some digging to see if I can find a point of contact if they don't respond in the near future |
@kalegd Do you know if this happens on any other WebXR website? It would definitely help to know the PICO device OS + Browser version. Feel free to send me an email and I can help dig into this issue. I do see the issue with Sliceofmusic.com but it falls back on the Neo3 controller because there isn't a PICO4U profile available as expected. Odd that the user loads up the PICO4 Ultra controller. Did they perhaps add in the controller themselves? Danny from PICO |
Hi Danny, |
Profile id
N/A
Describe the bug
Users have reported to me that their Pico 4 Ultra controllers are not oriented correctly. I'm using the latest version of the input profiles, but the weird thing is that pico 4 ultra isn't even an option, but somehow their controller model is getting loaded? I'm a little confused on how to proceed and rectify this issue
What I know
pico-4
,pico-g2
,pico-neo2
, andpico-neo3
pico-merline
andpico-phoenix
(`pico-4' is removed)oculus-touch-v2/profile.json
, but the profile-id comes in aspico-sparrow
oculus-touch-v2/left.glb
, but the model loaded is actually a pico 4 ultra controllerI'm guessing their browser does some weird overwriting thing?
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Generic fallback controller used, or the Pico 4 ultra controller is oriented correctly
Screenshots
Video curtesy of Akumelion from the Pico discord as I don't own this headset (I did verify this strange behavior with the emulator as well)
ScreenRecording_2024.11.11-19.11.45.mp4
3D engine (please complete the following information):
Additional context
Requesting advice on how to best proceed, if anyone has any contacts from the Pico browser/headset teams, or if there are any recommended alternative solutions I could pursue?
The text was updated successfully, but these errors were encountered: