Lol I barely did anything to get this working XD Just added shaders to the right paths and everythin
Lol I barely did anything to get this working XD Just added shaders to the right paths and everything fell into place
OYeah I noticed that as well :/ I think also the way that the thumbnails are staying loaded ends up costing too many resources (on the quest at least). Haven't looked too far into that
AI found the async bits tricky but I've done very little async in C#
AGLTFast was async only - how did you work round that?
OLmao I just used your code from your first go
OTried giving it a fresh look and couldn't really think of a different enough way of doing it
Aha! glad it was useful. I expected you to rip it out and start again.
AMaybe just a button to "unload all thumbnails"?
OI started to, but ended up having to balance my dev time between trying to get this working and getting some sort of workable app using the Open Brush API for a teaching session soon
ARemind me what you're doing with the API and teaching?
A(Ah. Loading a scene with imported models fails after restarting the app. Probably because the models aren't initialized properly if the thumbs aren't loaded?)
OI'm wondering if this would be any better? IDK if y'all are already using it. If that's the case, sorry for the redundancy. https://docs.unity3d.com/ScriptReference/AssetPreview.html
Oyeah currently it looks like clicking the asset to load the thumbnail will create the object. And I think clicking the thumbnail again just duplicates it into the scene
ALoading the scene twice works. So first time is correctly initing the thumbs but not the scene models.
OHuh interesting
AProbably related to async completion.
AAssetPreview looks like it's Editor-only
OFor context: currently in med school. I'm working with the anatomy dept to create interactive VR learning modules. Currently, they use this thing, but it has a lot of limitations: https://www.medicalholodeck.com/en/
DICOM Viewer, human anatomy lab and 3D anatomy models for teamwork in virtual reality (VR) .
AAh yes. I remember now.
ADid you do some stuff with displaying volumetric textures as well?
OThe goal is to use Open Brush's more robust drawing tools to be able to highlight structures (arteries, nerves, surgical landmarks) and then compare what the student draws with an answer key drawing
AWe've added point cloud import recently. Adding DICOM support would be a nice addition too.
AImport ALL the things!
A(had the urge to add MagicaVoxel support the other day too...)
OI did not, but it looks like gltfast has an extension that adds support for it
AGitHub
Volume rendering, implemented in Unity3D. Want to support my project? Donate some money to Red Cross and send me a screenshot/message/issue, and I'll be greatly motivated! :) Any amount is ...
OLmao the dept chair has already suggested I do this next
OAFor any importer that doesn't insist on async it's pretty trivial to add support. I think point cloud import took me half a day.
AI want to replace the obj importer too so it works on the Quest.
A(Parsing obj files is pretty damn simple. I got a basic one done from scratch for my generative models branch)
AOf course - re-exporting is tricker if the result isn't a normal mesh
OIt's funny how Unity is supposed to be this amazing cross-platform engine, but then there's so many things that don't work with VR cuz of the quest being Android
OStill trying to find a (FOSS) webview solution :)
MLet me know when you do 
OSo sad that they're all like $150
AA webview is such a huge blob of code, it would be better if each platform exposed it as part of their API
Abut then there would always be a few platforms that didn't so we could never rely on it 100%. Which means I guess we'd probably go back to wanting an embedded solution
AGitHub
Functional web browser for Unity without any issues or hassle. - GitHub - Voltstro-Studios/UnityWebBrowser: Functional web browser for Unity without any issues or hassle.
Ano android. damn
AGitHub
What platform are you experiencing this issue on? Other What architecture is your platform? Other What version of UWB are you using? Git Repo What Unity version are you running? n/a Describe what t...
Are: Layers. I decided to go ahead and implement "Objects remember what layer they came from and return there when deselected"
Abut because I'm lazy and it was tricky - I actually implemented "A selection remembers the layer that the last object added to the selection came from"
AWhich is interesting because it means that in simple cases things work as expected.
ABut if the user does this:
- Select some stuff from Layer 1
- Switches to Layer 2 and selects some more stuff
- Deselects everything
Athen the stuff from Layer 1 moves to Layer 2. Hey presto - a way to move stuff to a different layer without needing a specific button.
AIt's a bit of an "easter egg" feature but I wonder if it's a rare enough use case and rare enough to do my accident that we can leave it in?
A@bootleg @ancientworlds waddya think?
Bto me personally it sounds like it can easily go wrong for specific types of artists
BI often struggle to keep up with layers in traditional drawing applications and finding out later that layer magic messed up my work is immensely annoying
Bconsidering that layer UI is even less visible in Open Brush, I'm concerned that this might end up messy