Icosa does naturally, and it’s there for others if they need it, we also have a template repo if it’s just a stanalone thing, I’ve used it on hic et nunc for example
My problem is that I want people to be able to use the stuff I make (here wearables) on other platforms. So far it looks nothing can really be exported out of open brush..
Everything can be exported, it’s just so special that no one has really tried to support it before, I’d say we’re the first ones putting this code out there
GLTF is going to be the format for that for sure. Open brush will probably need some form of extension for it’s more special brushes for sure, but you can make that ridiculously easy for platform implementers, lemme get an example
Hey Hubs team long time no see! I'd like to get support for something we've been working on in OMI working in Hubs. This PR adds support for the OMI_audio_emitter extension, a dra...
SDK built once, only a few lines of code to add (and this is having to jump through hub’s much more complicated system so the base case is even easier)
That sort of support will rely on the closed platforms being happy about accepting open standards, and users pushing for it. For example VR chat has to be processed in unity and uploaded as unity’s proprietary format. It does happen to support the tilt brush toolkit though. No GLTF runtime support at all. If you’re interested in wearables then the platforms should be considering VRM avatars, which again is implemented as a GLTF extension.
New to discord, having an issue I can't solve with OB. This first screenshot is from the apps camera that I used in this painting a year or so ago. The foreground and background strokes are blurred, but there is no blurred vignette. I have since gone back into the same painting and tried to take photos, but there is no blurring effect at all. Was this in an update to the app?
Kind of a circular problem. Once the tools are built, and a community starts to really take shape, art blitz them on twitter. Going to have a hard time pushing for integration until there's something fully defined that they can look at and go, ya, worth doing
"A year or so ago" would have been before Open Brush was released. So - did you take this screenshot in Tilt Brush? Our first release was in January this year.
If it was Tilt Brush, then it's a bunch of stuff was changed by Google to make it possible to release as open source and it's hard to track down all those differences. If you just mean "I used an earlier version of Open Brush" then I might be able to dig a bit deeper to see what changed.
It was 100% open brush as my painting is still in there, and I've taken screenshots within the OB app since and they don't look similar, everything is in focus.
I'm a bit stumped. We've never had a depth of field effect. The 1.0 release didn't have bloom but it was then fixed. Multibrush had more effects but you're certain it was Open Brush... The only effects I'm aware that we've ever had is Bloom and Vignetting. I guess bloom could be mistaken for a depth of field blur - but it responds to brightness - not distance between the brush-stroke and the camera.
In the experimental build, I see that the pictures taken do have a depth of field like effect. @annahoo. is this the kind of blur you are talking about?
Definitely not vignette because I customized the config file specifically to get rid of that (and have been able to toggle it back on and check to make sure it's not the effect I'm looking for). I haven't downloaded multibrush either. That might be the effect, I'm not sure, I've got another photo take in app of the same painting, different angle that might also show the effect better