FrankPooleFloating wrote:Well that sucks. I just fired up SA (use LW 99.99% of time) and yeah, I see what you are talking about. And I could have sworn that SA had alembic export. Hmm.. I believe the plugs (and Unity) are going to be able to import ORBX in 3.1, which should be damn soon... should be...
..the hell is that thing?....
Because of some missing pieces in the alembic camera system (e.g. pano camera), ORBX packages saved from SA use the ocs XML unless the .abc was exported extnerall into an ORBX package.
What we have done in Unity+3.07 is allow you to load an ORBX file as a bounding proxy volume in the root Unity scene, which just uses the geometry outpit in the primary RT. Youcan then inspect the cameras, environment and other valeus in the ORBX file and copy/paste these vales into host scene camera/env if you wish. The other feature we've enabled in Unity (but useful template for other 3.07+ plug-ins with SA UX) is you can select an imported ORBX rendertarget and load that directly, edit with the full SA UX etc., which gives you the same exact workflow as SA, within the host DCC app.
There still may be a bug, if the .ocs camera values in an ORBX package don't work when loaded into the host DCC app camera settings.