You can do a github cloud build. That works for me (takes a bit longer)
You can do a github cloud build. That works for me (takes a bit longer)
NThanks, but I want to build it on my local machine in order to be able to change something in code. I'm currently studying different existing libraries for oculus. This is one of libraries I want to study and maybe integrate somehow in my project
NBtw, is there any other exitsting games or projects that is built on top of open brush?
AThanks, but I want to build it on my local machine in order to be able to change something in code.Yes - the workflow is: 1. fork our repo 2. Turn on Github actions on your fork 3. Push a change with "[CI BUILD]" in the commit message. Then Github automatically does a build for every platform
ABtw, is there any other exitsting games or projects that is built on top of open brush?Well there's all the stuff mentioned in the docs: https://docs.openbrush.app/alternate-and-experimental-builds/
ABut there's probably more. I always keep an eye on the Github network graph: https://github.com/icosa-gallery/open-brush/network
GitHub
Open Source Fork of Tilt Brush. Contribute to icosa-gallery/open-brush development by creating an account on GitHub.
ABut that doesn't catch stuff that isn't public, isn't a direct fork - or stuff on Gitlab etc.
NThanks!
Myou mean like taking the functionality/brushes of open brush and using it in a different app?
NYes, right
Mokay, that's two for the list of libopenbrush 
Mthe current codebase is very intertwined, but in the future we want to make the core of it a module that anyone can use, with a nice API
Mby the way, if you just want to display things that are created in open brush, there's a separate toolkit for that
NThat would be great!
AIt might be possible to build something on top of Open Brush. What's tricky is extracting smaller parts of it. Have you looked at the API stuff? That is a good guide to how to activate specific bits of functionality outside of the main UI
NNot yet, but I'm going to look at API once I fix my environment
AThat stuff is hopefully going to be merged to main fairly soon: https://github.com/icosa-gallery/open-brush/pull/198
GitHub
Insominx: Added "tags" to brushes and filtering based on them: #154
Andybak: Features/http api: #155
Andybak: Features/snapping: #186
Andybak: Features/color jitter: #187
Andybak: Features/http api: #155
Andybak: Features/snapping: #186
Andybak: Features/color jitter: #187
Nwow...
C@andybak I just started playing with the "save selected strokes" & media library tools.
The unity scene that results when brought in via GLB doesn't contain the referenced models (they're just empty).
And the files that it spits out into the Media Library folder are .usd, which, I'm not sure if it's supported by the toolkit.
Let me know if you think this should work in theory, or if i'm barking up the wrong tree.
I'm going to see if there's a USD plugin I need in order to pull in the models first
The unity scene that results when brought in via GLB doesn't contain the referenced models (they're just empty).
And the files that it spits out into the Media Library folder are .usd, which, I'm not sure if it's supported by the toolkit.
Let me know if you think this should work in theory, or if i'm barking up the wrong tree.
I'm going to see if there's a USD plugin I need in order to pull in the models first
Ahmmm. good point.
Mtiny nitpick (cc @nike61 ): it's
[CI BUILD]
Adoh! i knew something felt wrong as i typed that
CThe tools, if they were to work would be SO handy
Ai think nobody thought of using those two features at the same time
Apersonally - i would like to replace the "save selected strokes" with a more flexible approach. at the moment the strokes become non-editable (coz they are .usd files)
AI'd rather get scene merging/additive loading working
Aand that is actually nearly done (but might have subtle bugs)
Cyeah that'd be ideal
CIn the meantime I can export each of my models as GLB and recombine it in unity using the Nulls as transform guides
Ai keep meaning to get back to the scene merging. if i'm lucky i might even have a build today. assuming my last fix worked
A(so - now I've jinxed it obviously!)
CMaybe scene merging will skyrocket the scene complexity as well though?
CIt sounds cool, I would use it today if I could
AOne of the things I'm stuck on is updating the tilt meter correctly
Abut there's also a note in the code from ages back saying "additive loading is buggy as it duplicates existing strokes" - i can't seem to see any evidence of that but i haven't tried too hard
Ai think even with bugs it's quite appealing. it might be "bearably buggy" and we can hide it behind a settings flag so normal users don't get tripped up by it
CI love reading all the little notes, it's like "this'd be a really cool feature if I ever got around to it"
Ayeah. check out the comments in the .tilt file loader. it's practically a history of development quirks and decisions
CIt's tricky that there's no way to tell if it was fixed and then that note wasn't deleted
AI tried a couple of ways to detect the extra strokes - but couldn't.
Athey weren't there on export, didn't seem to be in the unity scene. but i might have done something dumb
ACheck out this page: https://blog.google/products/google-ar-vr/paint-friends-tilt-brushs-latest-prototype-creations/
kinda makes you sad to think this code existed at some point but we won't ever get to see it
kinda makes you sad to think this code existed at some point but we won't ever get to see it
Google
Tilt Brush is better with friends. Our multiplayer prototype lets you share ideas, draw, and create with others.
CIt's not a huge problem, as long as the merged thing has a unique parent in the hierarchy from the original
AI'd pay good money for a chance to look through the internal Google repo branches!
CGrouping and the breaking by colour tools in toolkit have been saving my life
CI just need something which breaks apart by individual strokes.
And one which resets the pivot of the group to the centroid, or the centroid + minimum bounds on the Y
And one which resets the pivot of the group to the centroid, or the centroid + minimum bounds on the Y
Ai think someone did that once - i had a go at it and it didn't seem that hard
A(the split by strokes bit)
Athere's one place in the code where it decides how to split meshes on export
CYe I was playing with that, didn't get around to split strokes though, if it exists I'll take it!
Ado the exported meshes use submeshes? i guess not