@cnoellert @AdamArcher
What is mocha doing to solve the distortion?
Is it using the track that it does or does it need the lens grid?
We are now relying almost entirely on 3DE camera solves from outside vendors. Hence my frustration and limited ability to change the delivery.
Having a better understanding of the lens grid tool and the 3DE node in Nuke hasn’t changed the fact that Flame has to jump hoops 
to protect all of the pixels.
I’ll check my OFX plug-in as this says it is only available in the standalone to export a stmap. Though you could possibly undistort in one Mocha Pro node then redistort in another but not sure if you can resize the image so you don’t drop off the undistorted bits as I have not tested it.
Watch the video on my link above. Mocha has a lens menu and you can either auto calculate it or draw lines.
As mentioned earlier, I’ve never used it myself as I’ve had Nuke available and know how to do it in that but this looks usable or worth testing at the very least.
I also believe Syntheyes can create stmaps as well. I don’t have that myself right now but it would be a very cost effective solution if it works.
Syntheyes can indeed calculate distortion and write out STMaps
I still think Flame should be able to do this natively.
100% agree there!
I threw together a quick archive of your lens grid undistorted in Mocha, output the STMAPS and setup a batch with all three as inputs. Mocha has these two STMAP output types, minimum and equal. I’ve used minimum in the past but I included both in the batch and showed where equal fails. Had I been doing this for real I might have spent a little more time carefully choosing my lines for the calibration but I kinda just blazed through. I included the mocha file for you to dissect as well.
All of that can be found here →
https://www.dropbox.com/s/sfm6t5068c61obz/lensDistortMocha.zip?dl=0
Terrific. Thank you, Chris.
So, you can undistort and redistort via the plugin’s various render mode outputs but, it’s internally using the equivalent of the “equal size” STMAP output that will crop the input image so it’s a non-starter. Better to go through stand-alone and use the “minimum size” STMAP output and avoid heartache.
Yep, this is the way.
Late to the party, but ST maps and DasGrain are the two main reasons we have to go into Nuke during comp. Someone has done a feature request for ST maps, I’d encourage everyone to give it an upvote on the Autodesk website
upvoted!
Upvoted