Othanks!
OToggle Grouping for Selection
ā
Combines the currently selected strokes into a single group. They will move and scale as one. You can ungroup them easily by clicking again.
ā
Combines the currently selected strokes into a single group. They will move and scale as one. You can ungroup them easily by clicking again.
Oohhh ive done this, did not imagine it would stay glued together after the export
Oi dont think it does personally
Obut not sure ive 'toggled'
Owill try it out
Othank you!
O(im not currently working on this btw have sort of resigned self to not splitting the mesh but will be so cool if i can work out how to :D)
ANo - I wasn't sure it did. I was asking.
ABut it would probably be a good feature to implement.
Oit would be so awesome!!!!!!
Owow
O
1I believe groups export as different pieces
1If they don't, it would be a nice feature
CHas anyone else had a problem building for quest 2 where when they export the APK using the guide on the openbrush GitHub for quest 2 that the build is a folder rather than an APK file?
Does anyone know how to make the APK from the folder?
I tried installing Android studio.
I was wondering if maybe it's because I didn't approve the connection request inside the headset before building?
Generally I've not had a problem with making Android builds the regulsr way
Does anyone know how to make the APK from the folder?
I tried installing Android studio.
I was wondering if maybe it's because I didn't approve the connection request inside the headset before building?
Generally I've not had a problem with making Android builds the regulsr way
MThe build should have an APK inside it... what do you see there?
CI'm seeing basically what looks like an unzipped APK
MYou build via the GUI Tilt->Build (or something like that)? And the output was in
../builds/Release_OpenBrush_FromGui or something (i forgot the exact details but it should be something similar)?CYep
CSorry I didn't see any documentation for this part
Mthat is... strange. It'd take me 2 hours to reproduce because I recently wiped my local Library folder, but it should have some JSONs (unneeded) and an APK. Are the files you're seeing in the root, or a subdirectory? Can you paste a screenshot or directory listing?
CYeah don't worry about reproducing it, I'll be back in an hour and I'll share add much as I can
Mok, great! We'll continue later.
This is the only documentation we really have https://github.com/icosa-gallery/open-brush#building-your-app-for-oculus-quest
What do you mean by "export the APK using the guide"? What's the export?
This is the only documentation we really have https://github.com/icosa-gallery/open-brush#building-your-app-for-oculus-quest
What do you mean by "export the APK using the guide"? What's the export?
CThat's the one, yeah sorry I just meant do a build rather than export
CFollowing those exact steps there
C
Athat's weird
CI'll try again with the quest set up properly
Mok... it looks like you actually opened the APK! I don't know enough about windows to know if that's standard or something you installed... but if you go up one directory, is com.Icosa.OpenBrush.apk actually a directory or is it a file that you can open like a directory? Maybe from the command line... what does a simple
dir show?Cyeah sorry it's just showing up as a folder
CBut I'm also getting some build errors mainly relating to google drive, which I got stuck in the process of setting up
C
Cah google is telling me I can just zip it up and rename it to an apk
MI have to admit, I haven't seen this failure.... I wonder if the build was interrupted before the end? Happy to hear how it works after the zip.
Cyeah it's likely, could've failed because it has an error and then doesn't package it as the final step
Mthat seems likely. Let's see if it gets better once the other errors are fixed.
CYeah the apk doesn't run, it must've aborted during build
CAny chance I can just disable the online componants?
MProbably, although I'm not positive that's your only issue. Our official builds come with keys for sketchfab and google, but when we test PRs and forks, they're not there (straight stock from git) and those compilations are also working, so I think there might be something else as well. That said, I'm not sure what it is -- I'm not really an expert in Unity. Maybe we should move this from #archived-support-and-bugs to #archived-dev-getting-started (although honestly, we mostly have the same people everywhere 
)
Andy, any ideas?
)Andy, any ideas?
Cah yeah that could be it, I think I forked an official version rather than the github repo
M
CCWould you recommend just pulling the from https://github.com/icosa-gallery/open-brush instead?
I was hoping to just get a quest app running with my custom brush shaders, maybe a few nicities from the experimental versions
I was hoping to just get a quest app running with my custom brush shaders, maybe a few nicities from the experimental versions
MYes, just start from there, get it compiled, and then start your work
Cthe documentation gets very vague, or potentially outdated at this point
https://github.com/icosa-gallery/open-brush#creating-an-oauth-credential
There's no mention of what the package name is or the sha fingerprint, and there's no option for other
https://github.com/icosa-gallery/open-brush#creating-an-oauth-credential
There's no mention of what the package name is or the sha fingerprint, and there's no option for other
Mskip it. Not needed for a basic build
CI think it's the last error preventing the build though?
Abtw that PR is currently buggy. I pushed a fix this morning that broke scene merging completely. will fix tomorrow