When I see this:
it’s pretty much like seeing this:
That’s not my world, it feels incomprehensible and I just close the window.
After reading your post I’m realizing that maybe this is something I can install and test by myself. So I’ll give it a try.
BTW, when I say ‘like in Modo’ I mean all I have to do is hit this tab, one mouse-click:
I’m curios why you don’t include this functionality in Rhino WIP, without having to install anything?
The Rhino WIP is already a terrible representative group of users of the real world user base of Rhino. Making functionality like this part of the GitHub underground seems like just more nerd echo-chambering. I don’t get it.
I get why this makes sense for developers, but I’d argue that an expensive plugin to just make a viewport VR-ready is absolutely irrelevant. We have zero interest on more plugins, more licenses, more exporting and obsoleting files, more disjointed experiences, more little companies with no business model, more troubles. Especially when companies like Enscape, Mindesk, etc most likely end up selling to Autodesk or Dassault or some other VR VCs/Private Equity (if they are not already hostages of VCs). I won’t spend a penny or a second on a 3rd party product for this basic functionality.
If McNeel’s argument is that this is not basic functionality, then fine, change me $300-500 extra for a McNeel developed, supported, and Rhino-Teams-licensed plugin. I trust that, and happy to invest money and time on something that has long term viability.
We need two things:
- Working more in VR in Rhino (and Grasshopper). With one-click.
- Export to Unreal. (a bridge from Grasshopper to Unreal is something we would pay for, for sure)
I hope this helps,