Moderator: Paul Tuersley
Sorry for the tease, stay tuned! If anyone really needs it I can throw the Max version up now - it works perfectly. I have no intention of ever charging for these scripts.
mishagogo wrote:Thought I'd share this version which I modified to support Maya 2015
Hi,,you ve been very helpful,,i ve been using your script from AE to maya,, with maya 2014 I have no problems at all. but since i upgrade AEcc and maya 2015 when importing a video to maya, there is a problem creating a shadow plane(use background), "mental ray abort"
It works fine importing image but not importing video
I'm running into a problem however. I used your script to export the camera tracking data just fine (apparently) but then in 3ds Max I open a new file and try to run the generated script it tells me "-- Cannot assign to read-only variable: camera". For reference, I'm following the tutorial here --> https://cgi.tutsplus.com/tutorials/3d-c ... -cms-27249
Does anyone have any suggestions on what could be going wrong?
Google Earth Studio outputs "real world" scale, so the units used in the export are in the thousands of kilometer range, and most 3D programs have problems with scene scales operating at that level.
The camera path in LightWave shows major "stair-stepping" and the results are unusable for matchmoving.
The camera path in Maya shows the same stair-stepping but for some reason, the motion of the camera in Maya seems smoother (even though the same values are being used).
I tried using a different script to export the AE 3D camera to Blender and got the same results. Jagged stair-stepping motion paths.
From what I can gather, the Google Earth scene scale is so large that when the scenes are brought into most 3D apps, they end up rounding the last 2 or 3 digits, which at this scale, means that you're rounding meters, not millimeters or even centimeters. And that means the camera is jumping all over the place, which again makes the track useless.
So in terms of this script, it's doing its job perfectly (although I will note that tracking markers didn't have their proper locations in the Maya file but they were there in the LightWave file). However if you're hoping to use this script to help comp 3D objects into your Google Earth Studio scenes, you may need to look elsewhere.
Have you managed to get it working with the export from Google Earth Studio yet?
A year later and I'm trying the same workflow as you, by exporting it from Google Earth Studio to After Effects and then from AE to 3ds Max using this script. But I also get the error "-- Cannot assign to read-only variable: camera".
Google Earth Studio now has the option on the render advanced settings to export the camera using local coordinates centred on an assigned tracking node. I was hoping this will have fixed this issue but I still get the error.
I've also tried setting up my 3ds Max file's system units in different scales such as kilometres, meters, cm's, etc but that doesn't have an affect.
I've run out of ideas what the problem is now...