Thanks for the prompt response @teocomi - it’s not a total deal breaker as pulling in the latest and greatest data from a stream is probably OK as long as I test it first – it’s the graphical limitations of the Hololens 2 really that I am slightly worried about.
On a slightly different thread - I was looking at the Revit / Rhino / Unity tutorial this morning and noticed that the start commit / end commit links don’t seem to be linked to anything yet, is there a repo for this tutorial that I can look at?
that could definitely work! Would love to get my first commit into the speckle-verse
There are some lingering comments and thoughts that should be addressed before doing a pr to a test branch. The main issues that I’d like to address is how the Dispatcher could work within the editor. The logic that helps with thread protection held in a coroutine and that seems to be the culprit for blocking the editor from achieving dopeness.
Not sure what graphic components you’re exactly worried about, but if it’s anything around model / mesh rendering you could instance a prefab of any loaded mesh into your editor during runtime and throw that into a test .apk. I did this when poking at the Quest2 performance
Hi @haitheredavid
Interesting - I have tried this by dragging the loaded mesh into a folder in assets but the prefab was missing all of the mesh objects - ie empty mesh filters? Am I missing something super obvious?
@NigeDemo Huh well it work with the speckle 1 in unity! Sorry for the mistaken info, I just tested it with speckle 2 and I was wrong with saying that process would work. Not sure what would cause the change in that since both connectors are in version 2020.
I’ll make some time to dig into this and follow up with any info
(lil mental note!) Just took a quick peek into this and it seems like the way meshes are assigned to the filter is causing the meshes from being saved. Seems to be a straightforward change! I’ll test it in my branch and if it works push it along in my next commit.
Gotta get those discourse flare ya know! I’ve set aside some time today to work through the dispatcher, we could touch base on it tomorrow at the standup? It seems like unity has a somewhat stable package for editor coroutines that we can rely on for this fix.
@teocomi Was able to get some good juju going tonight with using the Editor Coroutine Package with the Dispatcher! I thought it was freezing and crashing but few seconds later some nice lil’ meshes appeared in the scene. I’ll have to play around with this a bit more to get the editor from locking up. I also noticed a few errors getting thrown for the mesh creation, something to do with mesh leaking… not sure what that is but I’ve got my fingers crossed that it will be something related to the instancing of loaded meshes conversation above
Hey @haitheredavid quick update on this, I’ve been through your code and it seems the dispatcher is not needed for receiving in Editor mode
I’m cleaning some things up and will then push some updates this week!
@teocomi ah that’s terrific! Looking forward to seeing the updates I’ve been migrating away from the dispatcher and utilizing the c# Job system instead. Still a wip, gotta get myself moved down to mexico in t-minus 13 hours
Side note- Since our last chat about the VD, I’ve been chugging along with migrating from speckle v1 to v2. It’s been helpful to see how the Kits and Converters actually get implemented
I did this when poking at the Quest2 performance 
Not sure what would cause the change in that since both connectors are in version 2020.
I’ve been migrating away from the dispatcher and utilizing the c# Job system instead. Still a wip, gotta get myself moved down to mexico in t-minus 13 hours 
