OTOY Forums

hi thanks for your follwing, aLeXXtoR & pixelrush...
pixelrush: the problem is very simple: as you export a blender scene with 2.61 version ( all builds ) & choosing 'export cameras', as aLeXXtoR says, instead of giving the right position of the camera, it place it at pos. 0 ( inside the 0,0,0 object ) whatever the export you do ( anim or not )...

to lionnel: i noticed a bug for D.O.F tracking objects with camera ( blender 2.60 and before of course as 2.61 export-camera doesn't work ).
It would be very nice to correct it too... ( for the 2.61 of course... )

Havent found it yet, much more used to old 2.49 python.
42734 was ok but it was broken before 42883.
Might be related to mathutils vector changes.
Nothing obvious to me anyway atm.
Probably needs Lionel to sort it out since he is used to his code.

ok
thanks anyway

I just posted v1.13 that should do the trick (just swapping matrix world coordinates, so I don't know if there're any side effects).

Thanks Lionel
Just to clarify for people, v1.12 is the one you want for the official Blender 2.61 release (42608).
If you are using a graphicall.org or other build after 42734 you need v1.13
Changes in Blender code broke the script

Super Lionel
merci beaucoup !!

Thank you, Lionel!

I haven't tested id yet, but I noticed some more issues with exporter 1.12 and B2.61:

• materials: Diffuse-Glossy switch doesn't take any effect (material exports as Glossy until it edited in Octane;
• materials: Roughness (for float texture) doesn't affects Octane's paremeterl;
• camera: picking object for Depth of Field calculations doesn't give proper results (camera "focuses" far behind the desired object).

I hope that you'll find some time to review it.
Anyway, thank you very much for your work!

Alexander.

@Vincent: avec plaisir

@Alexander:
- diffuse/roughness: materials are almost always exported to glossy with only diffuse color properly set, except if you use the 'write to ocs' feature which is now deprecated. Unless I can make Blender use nodes 'a la cycles' and map them to Octane nodes, I'm afraid all material pipeline is to be done in Octane (that's a shame for those who want to animate materials). At the moment Octane only takes materials from the crap mtl format.

- camera focus: I made some quick test and I don't think there's something broken there. What you must remember is that the exporter (and blender) takes in account the distance from camera to the origin of the object, not to the closest surface. You may be disappointed if you made large translations while in edit mode... In the exemple below, the camera will focus behind the 'real' object. You can fix that back in edit mode, select the relevant vertices/faces and then force center of object to geometry.

Hi Lionel

i have to try the dof but i can't tell you when because very busy actually and will tell you ( usually i used parented empty objects to track for dof, so that there is no confusion for obj distance)... )
thanks again
Vincent

Thank you, Lionel, for reply!

I just found a solution: my problem was that target Empty object was "multiuser" object... %) I have currently no idea how could that happen, but maybe I'll find it out someday. ))


Thanks!