I get the sense that you guys are mulling over the future of your geometry/mesh file formats right about now. It looks like OpenSubdiv didn’t make the 4.20 release which makes sense since UE currently doesn’t support any mesh file format to support it. [EDIT: OpenSubDiv DID IN FACT MAKE IT INTO 4.20]
I’m wondering, what’s the big picture here? One of your Trellos implies you have some of your big foreheads sweating over this. Good! The timing is perfect. To me is seems that an issue is that OpenSubdiv seduces you into using the USD/USDZ file format (which is great in itself) but then suddenly you’re awkwardly side-by-side with Hydra in some strange incestuous relationship. This might be OK for Apple / Adobe / Autodesk but seems to be dancing a little close to the fire for a company like Epic.
It’s probably not as bad as I’m making it out to be, but in a strategic sense adopting USD could be ceding really large swaths of future technical control to Disney (aka Pixar) if you just wholly adopt the format as the UE file format going forward. But I know you guys are smart enough not to fall into that trap, at least not directly.
I’m hoping you guys are planning on fully supporting this stuff yet sub-classing it in a way so that you can support other technologies (formats) as well. Personally, for dynamic environments I’m a big fan of more procedural approaches like the Grasshopper subsystem incorporated into Rhinoceros3D. To me that just seems like a perfect fit for UE. But in any case, externally-controlled file format support would be a really tricky beast, it might be problematic to support a plug-in approach due to legacy future support… I don’t know…
Hopefully we can kick off a healthy community discussion between people who are far smarter than I who can help inform developers where things are going while getting some early feedback. I have the feeling this is a big issue that might be rather important in the future.
cc: [USER=“35”]Tim Sweeney[/USER] just for grins