It would be extremely helpful if enscape saved coordinates, elevation and field of view in the meta data of rendered images!
Hi @tomsull , and thank you for your input. Just in case you haven’t yet, please feel free to forward this as a feature request via our Chaos Enscape Ideas Portal as detailed here.
If you have any other wishes alongside you can of course file them as well for our product management team to see and review.
likewise, can we please get (the option to export) a sidecar file* for video exports please, that capture:
- run datetime
- machine (name should suffice, spec would be nice)
- username
- source (file)
- version (source & enscape)
- render completion time
- preset (if any used)
- output settings (resolution, quality, etc)
*I’d be happy with a .csv, but happier to see an option for others types suppoted, like .xmp, .xml, .json etc)
- to add, short/in the absence of an Enscape-benchmarking tool (something for a next request post perhaps) it would be great to have render runtime added to the list above (not sure how I missed it out before)
why?
Well, I’ve had a simple 5min dolly shot rendering (albeit at ultra w/ DOF at maximum 120fps on a fairly pissy 12GB 3060) for the last 2+ hours and I’m not even past the 50% mark… purely for stress-testing (loads* of assets & lights) to validate/argue BIG SPENDING on some beefier GPUs in the near-future - but the point/reason (for wanting render-run metrics) still stands, is, imo, a very valid one for folk (like me) that deal with the ROI & VFM of IT sensibilities.
So please please (copy pasta this request into the suggestion-machine ad infinitum)
*ooo that’s another add, let’s get some scene metrics in this output report/sidecar whilst we’re at it!!!