hmmm. i thought i'd documented all the shortcut keys in the developer notes.
hmmm. i thought i'd documented all the shortcut keys in the developer notes.
Aah - it's linked from the dev notes: https://docs.google.com/spreadsheets/d/1D7vIerfSz1vtyDS_dPdvHiANluEr60VFrxhzE7ZbfAU/edit#gid=1073965238
A"CycleCanvas"
DI'll try it when I get the chance. Shift + C
AIt's pretty broken - but the code should be a useful place to start digging
AI do wonder if there's a fair amount of code-rot for this feature. I've seen other places in the code that definitely assume there's only the main canvas and the selection canvas
DThere Definitely is some... The SceneScript assumes only a MainCanvas and Selcection Canvas. I'll probably have to rewrite it for muliple canvases
DThen the main app script needs a ref to a scene script lol
Awhy do you need more than one SceneScript?
Z@andybak I tried yesterday for the reg and beta and Google blocks the app from having access to your Google account now. For security.
ABy "reg" do you mean the normal release - the non-beta?
ZYes
ZTried both same error
Aok. so that's a completely different issue. @mikesky ?
MYeah that's the one i was mentioning in our chat, not entirely sure what's going on but it's google related. interestingly it works fine on quest builds! @Zandy have already reproduced that, I think I need to take it up with google support. If you DM me your google account email I might be able to add you as a 'test' account which might unlock it
AOK. So this is a new issue with every release (presumably because something has changed with our API account). Does it effect everyone?
MProbably all desktop builds yeah :/
Mit's weird since I believe they're exactly the same credentials and the same app ID
MYeah they are, i'm not sure what's going on. probably some sort of 'ew desktop app, insecure' rubbish on google's part
Mmaybe it's revenge for open brush being cooler than tilt brush 
DI don't but it assumes only a MainCanvas
ANot sure I follow. SceneScript has got layers and m_ActiveCanvas. Doesn't "MainCanvas" mean simply "the initial canvas"?
DNvm i got it to work
Chey, have the latest build of open brush but there is no camera preview. Same issue with the steam version
AWhich "latest build"? ;)
ALatest main release? Latest beta? Latest experimental mode? (Deep breath) or latest beta experimental mode?
A(yeah, we need to streamline this stuff!)
C@andybak lol tried them all! Lets stick with latest main release.
COpenBrush_Desktop_0.4.21
A@mikesky I'm too full of food to reach for my headset. Is this a known bug? I remember intermittent issues with this
MAh, if you have ‘post effects on capture’ set to false in your config this happens @chromasnare
C@mikesky Oh hey! So I set it to true and it worked. Thanks!
MGitHub
Steps to reproduce: Edit your Open Brush.cfg config file to disable PostEffectsOnCapture. Example: { "User": { }, "Video": { }, "Flags": { &...
JHey! So I just downloaded open brush and I'm having a problem. I get into the app but everything is black. I can only see the open brush controllers, I can move them around but pressing any buttons doesn't do anything. I've tried updating my video drivers but that didn't seem to fix it. Any ideas of what's going on? I'm using the steam version of the app and playing on the oculus rift s
MI can't say I've heard of that before. You can try downloading the rift specific version directly from oculus (rather than Steam) if you'd like, but for more debugging help, we might need someone with a PCVR setup (I'm Quest only)
https://www.oculus.com/experiences/rift/5227489953989768/
https://www.oculus.com/experiences/rift/5227489953989768/
Oculus
A Tilt Brush derivative for free on Oculus! Enjoy making awesome art in VR.
MTo be clear, this is the regular steam build? Not the "pre-release" channel or the "experimental" channel, right?
Jyes, and I just tried the version on the oculus store and it had the same problem
MInteresting. I know people are using the steam version (the rift specific build is a bit niche), but I'm afraid I can't offer any specific advice for you here.
AI remember one other person reporting a similar issue and I can’t remember if they solved it. You haven’t got dual monitors or anything else out of the ordinary, have you?
JNot at the moment, no
MThere's this icosa-gallery-chat which is vaguely similar but jot really the same root cause, it'd appear
MJI think I remember actually having this problem before with tiltbrush, the way I fixed it was by using the previous build option in the steam beta options.
Jthing is I don't know what the difference between the two versions was so Idk if theres a way to use that to help fix the problem with openbrush
AThat sounds to me like there was a problem introduced in an older version of Tilt Brush that affects you (and very few other people unless we are just not hearing about it). The odds are that issue will be in all newer versions which would include every version of Open Brush.
ASo - unless we can figure out why this is affecting you, or some way to reproduce it on other computers then it's pretty tricky to resolve.
JHmm, when open tilt brush become open source, did its history also become available to the public? Maybe its possible to figure out what changed between the updated version and the build that works for me?
MUnfortunately, we don't have any history of TB
JDang
AIs it possible that the mode didn't change in the build?
I get that issue if I don't switch the tab from console to game in unity.
My memory is a bit hazy, might also happen if I exit the game from inside rather than unity, or close steam and leave oculus open, would have to check.
Not sure if being in monoscopic or something similar would have the same effect?
Anyhow, potentially a sequencing error where it's not switching states properly?
I get that issue if I don't switch the tab from console to game in unity.
My memory is a bit hazy, might also happen if I exit the game from inside rather than unity, or close steam and leave oculus open, would have to check.
Not sure if being in monoscopic or something similar would have the same effect?
Anyhow, potentially a sequencing error where it's not switching states properly?
ZIs it possible to get the camera showing with post effects capture on false? One thing I miss with TB is the ability to capture clear videos without post effects.