11-02-2021, 10:27 PM
I'm loading a Model3D via Task.Run (it's very large) and then freezing it so I can use it in the main UI thread where I manually add it to a ModelVisual3D. That works great, no problems. I am also allowing the user to toggle visibility of the ModelVisual3D (I also have wireframe and other display options that can still be visible) and to do this I'm removing/adding it to viewport children list.
Here's where the (maybe) bug comes in: if the model is frozen the first add works, the remove works and then when the model is re-added, I get no visual of the model. If I clone the model in the main UI thread (so it's not frozen) that same exact code works fine.
So, it appears that once a frozen model is removed from the viewport children list it cannot be added back in and get visuals.
Since I'm now just cloning the Model3D after load, it's no concern to me but I thought you might want to look at it.
Here's where the (maybe) bug comes in: if the model is frozen the first add works, the remove works and then when the model is re-added, I get no visual of the model. If I clone the model in the main UI thread (so it's not frozen) that same exact code works fine.
So, it appears that once a frozen model is removed from the viewport children list it cannot be added back in and get visuals.
Since I'm now just cloning the Model3D after load, it's no concern to me but I thought you might want to look at it.