Camera tools show as all white on v2.5
70 Replies
Here are the possible variables:
1. Steam Version or Meta/Oculus Store version?
2. Connecting via Link? Airlink? Steam Link? Virtual Desktop?
3. Your system OpenXR backend can be either Meta or Steam
4. Which headset? (so far all reports of issues are Quest 2)
5. Which Open Brush version (I'm assuming non-beta v2.5)
From @Kevin W. Tharp
The students who cannot see anything but white in the monitors for multi-camera video and camera paths are using Meta Quest 2, connected to SteamVR, using Open Brush version 2.5.0.@Kevin W. Tharp how are they connecting the Quest 2 to the PC? (i.e. variable 2 above) - I've tried Virtual Desktop. Now going to try Link over USB.
Okay, let me throw out some notes here:
1. I was able to replicate the issue on the Meta 2. Here are the variables:
Open Brush Versions: Both the Open Brush Versions connected to SteamVR (link cable) version 2.5.0, and Meta Quest Version 2.5.0 have the problem with the video feed into the in game camera monitors, and recording.
Here is a video I was able to capture that demonstrates it in the standalone version of Open Brush 2.5 on the Meta 2 without Questlink or SteamVR: https://www.facebook.com/121203185/videos/2686511724846109/
I tested it on a Meta 2 that had not updated and was still on Version 2.4 Quest Version. Here is a video that shows that the camera paths video is working in that version. https://www.facebook.com/121203185/videos/943415800354994/
Symptoms:
Monitors that should be showing video are white. This is happening in the Multi-camera video and snapshot modes, and it is happening in the Camera Paths tool in path monitor and menu monitor. Recording Camera Path when connected to SteamVR and running version 2.5 on Steam via link (cable) records white screen.
Isolating this down to where it is not working:
Successfully able to view video in
Camera Monitors (Multi-camera video and snapshot) and in
Camera Paths monitors (both the monitor in the Camera paths Menu and in the in path moving monitor
on the following systems/configurations:
Valve Index connected to Steam VR running Open Brush 2.5.0 - All working
HTC Vive and XR Elite connected to Steam via cable, running Open Brush 2.5.0
*Meta 3 Standalone version 2.5.0 - Working in stand alone version only
Unsuccessful in viewing video in
Camera Monitors (Multi-camera video and snapshot) and in
Camera Paths monitors
on the following systems/configurations:
Meta 2 running Open Brush 2.5 standalone, and connected to SteamVR via cable quest link
*Meta 3 running Open Brush 2.5 when connected to Steam VR via cable quest link
Open Brush 2.5 Meta 2 on device, not Steam VR. Video Camera monitor...
Open Brush 2.5 Meta 2 on device, not Steam VR. Video Camera monitors not working in Camera Paths or Multi-camera video
Open Brush 2.4 camera paths working, no steam VR | By KevinFacebook
Open Brush 2.4 camera paths working, no steam VR
OK. I'm seeing that on Quest 3 now
And it's nothing to do with PC vs native. I'm running standalone.
@mikesky Just tested on v2.4.28 and getting the same issue. 2.4.20 was fine
v2.4.24 is fine
v2.4.26 is fine
(i have a horrible feeling v2.4.28 will be fine when i retest) testing v2.4.27
so does it require an upgrade of VR headset from quest2 to quest3 to work?
Thank you all for your help!
v2.4.27 was fine
Nope! It is v2.4.28
This commit: https://github.com/icosa-foundation/open-brush/commit/bd1bb0d7af29499ac2d95252980b7f018ce5fc0d
GitHub
Branding Refresh (#662) · icosa-foundation/open-brush@bd1bb0d
* Update logos
* Update readme logo
* macOS backgrounds
Co-authored-by: Andy Baker
Which makes absolutely no sense...
@mikeage anything change about the build pipeline between v2.4.27 and v2.4.28 ?
anything that might not show up in a commit?
I am able to get it to work in Meta 3, standalone, Version 2.5. https://www.facebook.com/121203185/videos/780185994067007/
Meta 3 stand alone working | By KevinFacebook
Meta 3 stand alone working
in which case - it's not deterministic because i just tried that
to be clear - i'm only testing Quest 3 standalone at the moment
Nothing that I can think of. I'll check the full logs in a few to see if there's something in the image level perhaps, but there shouldn't be
I tried it on old sketches and on new and was able to make it work on both.
My testing is simple.
1. Reinstall
2. Launch
3. Select the camera tool
I'm not even loading sketches. Just those 3 steps each time
i wonder if doing more stuff might be making it work in some cases and not others?
i did all those steps yesterday & it still not working for me on quest 2 with link cable. it was working perfectly fine before monday
I just went back into Meta 3, standalone version. It is working, but the version is now 2.6.0.
Quest Link Via cable and SteamVR, version is still 2.5, and it is not working.
Quest Link Via cable and SteamVR, version is still 2.5, and it is not working.
Quest 3 standalone 2.6 - not working.
There is another variable I've not thought of.
🤔
Are you doing anything when you test? Can you try Quest 3 v2.6.0 and just follow the steps I do? Open App then open the camera tool
I have a whole bunch of systems available to me if we need to look at variables: Meta 2, Meta 3, Valve Index, HTC XR elite.
No - it's important for now to stick to Quest 3 standalone and v2.6.0 - the fact it works in one case and not others is the key
we just need to figure out why - adding in more systems might just confuse things
that would be fantastic to know each
it really won't help
it's working on one headset and not on another with exactly the same config (in theory)
@Kevin W. Tharp would be great to know just if i need to purchase the quest 3 for it to work
it's not that! it's a software bug
Rebooted machine, went into open brush 2.6 standalone Meta 3, opened camera tool, and I can see video in monitor for snapshot (no video in standalone version). Then opened the camera paths tool, and was able to see video in monitors.
it will be fixed once we can figure out the cause - nothing to do with your choice of hardware
yeah - so why is my v.2.6.0 not working. I really hope this isn't related to Quest firmware versions
because that will be really hard to test!
ah - there's a reason to test on PC - at least I can compare SteamVR versions more easily than Quest firmware versions
gonna reboot the quest. if i can get it to work on mine i'll have a clue
ive been working with the quest2 as a monitor and running everything through steamVR , i dont understand why it worked fine and then suddenly one day stops working and shows white screen
neither do we! 🙂
@Kevin W. Tharp said it worked fine with the quest3 its just the quest 2 not working
that turned out not to be the case
FYI, there was a quest link update it forced out. I just came back to my lab after 15 days away.
@Carrie Able - try v2.4.27: https://github.com/icosa-foundation/open-brush/releases/tag/2.4.27
GitHub
Release 2.4.27 · icosa-foundation/open-brush
🐛 Fixes
Reset default environment. Passthrough only for Zapbox (PR #660 by @mikeskydev)
can you clarify for me, was quest3 also not working
that worked for me.
just download that and you'll be fine
Right now, they are trying to figure it out. Quest 3 not working as it was earlier. We need to let them trouble shoot this. That is why i am testing all my systems. They are working through it now.
OK. Got to walk the dog. That's usually where I get my good ideas so fingers crossed.
do i deinstall openbrush before downloading the link you sent?
lol sounds good i need to eat lunch
I see zero differences in the build environments. Check both Windows OpenXR and Quest 2+ for 2.4.27 and 2.4.28
This may not be relevant, but it may be a clue. The camera tool shows for the auto .gif and five second .gif, but not for the video and snapshot tools in the multi-camera.
Hey, I found something. I was in the Meta 2, Standalone version 2.6.0. It was showing white. I went into the camera settings, and I turned off the watermark, and that made the video start working.
ah ha!
dammit
that's making sense. lol
thank you kevin!
Stupid Unity question -- the png watermarks did change there, but the meta ones didn't... is it possible that something was cached or something and therefore didn't import or get included properly?
just checking that now.
shouldn't matter - the .meta files should be unchanged
i'm wondering if there's a difference in the alpha channel or something?
they are both RGB 8bits per channel
On a rather superficial level, they seem the same
found a difference!
and if the texture is set to repeat edges that will do it
bloody invisible pixels
Tested this in both Meta 2 standalone and cable version of Open Brush, toggling that setting fixes and breaks in both environments.
yeah. makes sense.
just got to remember how to get photoshop to let me access the alpha channel directly
if i magic wand it then i might create nasty edges.
In the words of the Beatles, "I hope we passed the audition".
i might easily have floundered around for hours without you discovering that!
i'd looked at that commit and thought "it's just a few logo updates. can't be anything to do with that"
time to pull out the big guns:
it's probably 20 years since i've had to use this dialog box!
@mikeage gonna just revert two watermarks for now. Will fix properly tomorrow
Maybe tag @mikesky for that, not me 🙂
no - i really meant you
ok to merge to beta once the tests have passed? Can you do the release? I'd have to look up the instructions!
i want to test a build and then just get this live
I don't want to talk about 2.7 without First-Mike, even though it probably merits a new release. Now that we have a scenario, it's probably a really quick test cycle
isn't this the classic "main is broken - push a hotfix quick" scenario?
if the commit is those two image files, it's (highly) unlikely to make anything worse
WOW!!!
Are we going to push 2.8 tomorrow with the new branding?
it's broken, but it's also a specific feature. That's my concern. If it'll be more than, say, 24 hours, then my thought might be different
thank you so much!! do you have a screenshot of what this menu looks like?
Pretty sure it's only affecting the branding on the camera watermarks. and it's only the spacing between the words "open" and "brush"
@Kevin W. Tharp @andybak do i still need to download that github link? or just turning off the watermark should work?
that's also true. The default is that the watermark is on, right?
yep. that makes sense
watermark setting will fix it. Long press on camera button
bit of a shame we can't do releases without using up nice version numbers. i'm going to miss 2.8 - it has a nice ring to it
talking of numerology. My hotfix is PR 667... 😯
Oh man, that’s so dumb
Thanks for the bug finding everyone 🙂
Yeah we’ll put out another hotfix, who knew images would break things!
How long will it take to get the new branding PNGs that work, now that it can be easily tested?
Can we just do 2.7 and avoid 2.8?
Yeah I reckon so, I’m not bothered if people turn off the watermark really
Well, we don't really have an easy way to inform them, so we can't really leave it broken too long. Maybe we can rethink the watermark in general, but that's probably not a question for here/now
Just release I reckon. The logo is barely noticeable and I'm done for the day
Oh, I was proposing we have Mike fix it properly, not you 🙂
In any case, good night, and good work to both you and Kevin!
@Kevin W. Tharp thank you so much !!!! that fixed it!! how can i ever thank you!!
Appreciate you @Kevin W. Tharp @andybak !!!
I have students that have an assignment due tonight that required them recording with the camera paths tool. That's how I found out about the issue and came in here looking to see if it had been reported. I'm glad we figured it out, and a half hour before class began even.
Apologies for the inconvenience! I thought changing logos would be fairly innocuous 😅
This is just part of teaching near the edge. I appreciate what you all are doing with Open Brush.
appreciate the open brush team also!🎸👾💜