It has, but not necessarily in a well documented way.
Dynamo has a LOT that goes into it, and there are WAAAAAAAY more pressures on it than almost any of us know.
- It aims to be open source wherever possible to simplify deployment.
- It cannot use open source software which requires all derivative work to also become open source.
- It has to run in a .NET environment.
- Visualization has to work across a broad range of operating systems and hardware.
- It has to support components are often used in other ways which aren’t readily known, such as using a Watch3D node for secondary views or even output to new tools (see Dynamo for Forma)
- It needs to enable user interaction within the viewport (start a new graph and while still in automatic run mode: place a point, switch to your 3D geometry view, and try to select and move the point).
- The display has to be able to be quickly created from the geometry produced by the ASM engine (the proprietary geometry engine which Dynamo runs on)
- The tool has to be supported in a robust and capable community so we don’t have a major security vulnerability sitting in everyone’s desktop environment.
Of the remaining tools, HelixToolkit was the clear winner at the time, and has served Dynamo well. As a framework it seems great, and there are a bunch of examples of what it can do which are absolutely worth checking out. However it also means that the Autodesk developers who are best suited to tackle a complex model display environment aren’t able to jump in and implement features they’ve built before as it’s not the framework they use daily.
Dynamo also has to balance a TON of feature requests - viewer is on the list but when/how that gets done is tricky. The display of content in context (i.e. the Revit geometry preview) also reduces the immediate need. My hope is that some of the new tools we’re seeing (Dynamo as a Service, Dynamo for Design Automation, etc.) means we’ll get a better model viewer in the near future.