Yeah, but there's gotta be a way...
I understand that it's proprietary, but it's also a human readable, text format that is well organized. I could create an exporter very easily if there was a document outlining its structure or list of possible objects and properties. Attached is a screenshot of an action file. It's very clear and readable.
To further the point that this is possible, there are other applications that write out .action files for subsequent import into Flame. Shotgun is one application I believe that can do this. There are others, but this is the most recognizable example.
Since Flame does allow the saving of actions to an .action file, and the file isn't encrypted, there must be a way to figure out the spec.
What follows is opinion...
It would also work to Autodesk's benefit to make this format open so that pipeline developers can create automation tools. This is a constant frustration when working with Flame and trying to integrate it into a larger studio pipeline. If the software were more open it would be much easier to work with.
Thank you so much for your time.
