Urgh ok, so xml read by 3ds max did not work out great the position data was correct that was coming in but the visual output was not right even with switching XY or YZ or XZ around and making sure the scene scale was correct, so i tried it the other way with camera data and target (look at ) data from 3ds max, I guess this(file: "cameraposXML")
is too much keyframe data. I created a file exactly as you are supposed to with the xml file i saved out from enscape to use as a guide.
Why can't enscape just give an fbx output of the camera path this is so frustrating. I am going to try it with less data points, because clearly enscape can't cope.It played something at one point then just froze on this screen. Nothing previews now it is just stuck on this
i can't seem to post xmls so i guess save it to your computers and change the end file type from txt to xml.
the "camerapostoxml" you can change as well to .py . it takes the positions from 3ds max the camerapos and target files i created using maxscript.