Posts by anam-ate

here is the pdf guide i wrote:forum.enscape3d.com/wcf/index.php?attachment/42991/

Hey Emilio,

I don't use Enscape much because i don't really like it , but our office uses it all the time, so I made this tool that converts camera paths from 3DS Max and generates an XML file for Enscape to read.

see attached:

the dropbox link in this doesn't work anymore so i've attached the scripts and below is a walk through what i did in MAX and enscape

https://anam-ation.com/3dsmax-camera-path-to-enscape-tool/

hope this helps

A

You should be able to get the position data for your PFTrack camera using my script in MAX without drawing a spline, i haven't tested it , but i guess it works the same, it's just taking the position of your camera for each frame and saving it out.

Let me know if you have any issues

http://anam-ation.com/3dsmax-camera-path-to-enscape-tool/

code is in the dropbox link

I managed to export a camera path animation from 3DS max and save it as an XML file that is read by Enscape in rhino.

I've got a basic target camera attached to a spline that you can export the camera positions and the target positions.

I have a python file that reads the data and converts it to XML , i did post production in After effects then with the moving people from Max with an object Id and composited it with the enscape render

I will be posting the code and solution this weekend on my website anam-ation.com

solved it, Enscape "lookAt" is relative to the camera position where as in 3ds Max it is the absolute position. Really Enscape should just write an fbx exporter

A

well it is moving now made some errors in the python script

but it isn't moving in the right place or orientation, so i think i need to work out the units better

no that didn't do it even though this looks completely correct

Any help from the developers would be much appreciated?

ah crap i think i need to record the timestampSeconds = ""

as well that is why it is not moving

i think i need to get the timestamp data in there as well

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.

cameraposXML.txttarget.txt

camerapostoxml.txtcamerapos.txttarget.txt

Edited 3 times, last by anam-ate (12 minutes ago). — This post has previous versions that are saved.

Urgh ok, so xml read by 3ds max did not work out, 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.

cameraposXML.txttarget.txt

camerapostoxml.txtcamerapos.txttarget.txt

ah excellent thank you will give this a go

Hi,

so I've done some researcher another user(Macker) on the forum had it so they could import the camera path from Enscape's xml file exporter to 3dsMax but they never posted the solution.

I wrote a script in 3dsMax that takes a camera and morphs it between multiple positions and targets. This script works but when it brings in the XML positions and targets(lookat) it does not create a camera path like the one in Enscape. I know that the morph camera is going through all of the correct points in 3dsmax that correlate with the xml file as it prints the data correctly but the visual output is not the same. I had to flip the y/z coordinates and scaled my scene by 1000 which seemed to get somewhat of a similar camera orientation but generally it was not correct.

I know that several people have asked about this, could there be a bug in the xml exporter? Also the other user who did this mentioned FOV i don't have those settings saved in the XML export file. Any help would be much appreciated. In the mean time I will try to generate an XML from 3ds Max and feed that into enscape.

Thanks

+1

please please give us an API

+1