Contents in .obj while exporting

#1

Hi all, I am pretty new in Nuke and I was using WriteGeo to export the CameraTrackerPointCloud I did in format of .obj and I am trying to revamp the script a little…

I can’t really remember where I got the .obj file by using this video/script (http://www.creativecrash.com/maya/tutorials/import-export/c/using-nuke-6-x-3d-tracking-data-inside-of-maya) as my guide.

So basically the contents in the .obj file (supposedly if this is the correct one), it is as follows:

v -0.6110637188 0.0093309134 8.1327419281
 
 vn -0.2112581345 -0.7280599689 -0.6521492792
 
 v 0.7267020941 0.0233836491 8.6937112808
 
 vn -0.0528684395 -0.1126191291 -0.9922307493
 
 v 0.9012823105 -0.5180503130 7.7685375214
 ...
 ...

However, when I tried to do WriteGeo (seeing that the nuke version I use and the one in the video is pretty different), the contents in the .obj file is pretty different

## OBJ file generated by Nuke ##
 
 
 
 # vertex list - offset=0
 
 v -0.091236 0.098044 -0.792965
 
 v -0.019980 0.030144 -0.840554
 
 v -0.129045 0.001008 -0.870259
 ...
 ...
 # end of file

Any ideas why it differs so? Is it just because the difference in nuke versions?

#2

this is probaly from a different/custom obj writer?

i dont know the OBJ specs, but i think the “v” stands for vertex and “vn” for vertex normal.

if your points dont have a normal then you can export them.

is you exported pointcloud not loading in maya or why do you ask?

#3

As mentioned, I am trying to use the scripts for my stuff and it is not working. When I tried to load in the exported point cloud from nuke (in obj format), into this script, it fails to recognize it

If I am doing it in the ‘supposedly’ right method, I realized that my obj contents starts off with ## OBJ file generated by Nuke ## whereas in the script, it is interpreted that the contents in the obj file should starts off with v in this case.

And hence, I am asking. Not sure if this is a case of me doing it wrong or is it something to do with the difference in Nuke versions or what

#4

What program are you trying to load the point cloud into?

#5

Hi beaker, I am trying to load in the point cloud (exported from Nuke) into the plugin / script (Maya, in this case) in the link that I have posted in my thread

If you check out the video in the link, I am assuming that as the person who exports the point cloud info, it is generating in the layout of the first code I posted (once again, please refer to my first post), rather than the latter (the one that I generated), based on my knowledge on how I think the code works…

Adding on, as mentioned, I am not so sure if the difference in the code format is due to the different Nuke versions, seeing that the writeGeo that I used in the latest version of Nuke is pretty different from the ones in the video

#6

Just export fbx or alembic of both the camera and a point cloud from Nuke(plug the write geo out of the scene node). Maya can read everything in that way. This plugin for maya is from back in the day when there wasn’t a native way to move data between the two.