v1.17 for builds at or above 45110 Tweet

[kubo]

THE best render engine and the best modelling tool
They need each other so much..

I totally agree, I own a 3dmax integrated plugin license, it works great... the only downside is that now I'm hooked to blender and try to stay as far away from max as possible ;P so I would love to see an integrated plugin working inside blender.... so if anyone needs a non-technical help (you need someone to make the sandwiches or bring the beers) drop me a note! I'll be glad to help!

[Morichalion]

Works for 2.63 release candidate.

You rock, Yoyoz.

[vipvip]

congrats and many thanks Lionnel
for your constant and excellent help with the blender plugin !

[ROUBAL]

Hello, I encounter big troubles with Blender 2.63 official (r45996 with Bmesh) and The Plug-in v1.17 :

I have to export a scene with 26 characters with many materials and textures. As I encountered troubles, I tried to export only one cube with 6 materials (simple colors). The export with the cube works.

With the characters, the problem is that instead of generating valid obj and mtl files, the plugin creates an obj.temp file and an empty mtl.temp file.

If I try to remove the temp extension, all objects share the same material which seems to be the first material in alphabetical order.

I tried with only one character with same result.

After trying to export only some specific characters, I noticed that Blender displayed shortly when exporting a message saying that something goes wrong with a texture slot.

After some more trials, I found that if one texture that you don't want to export is disabled in the textures panel, the exports fails and generates defective obj.temp and mtl.temp. It is annoying, because you have to actually remove these textures from the stack, even if you need them inside Blender. So you have to save a different version if you render some parts in Blender and other parts in Octane.

Please, would it be possible to ignore disabled textures slots when exporting ? It would avoid this bad behaviour. I don't mean missing textures for what a warning is welcome, but only disabled textures.

Thanks in advance !

[matej]

@Roubal, check the console output for a more detailed description of what went wrong (probably some issues with texture path names). The exporter first writes the .obj to a temporary file, so if something goes wrong the original is not overwritten.

[ROUBAL]

@matej : The problem is only that the exporter tries to export some textures that I don't want to export and which are willingly disabled !

[MattRM]

Hi all,

I got this problem with Blender 2.63a and export script 1.17 :

The console log here :

Code: Select all

Octane plug-in v1.17 on 2.63.0 : Rendering still image
Octane plug-in v1.17 on 2.63.0 : Call to render without options
Octane plug-in v1.17 on 2.63.0 : Output ocs: "Z:\PROJECTS\OCTANE\test_CAM2.ocs.o
cs"
Octane plug-in v1.17 on 2.63.0 : Output obj: "Z:\PROJECTS\OCTANE\test_CAM2.ocs.o
bj"
Octane plug-in v1.17 on 2.63.0 : Output mtl: "Z:\PROJECTS\OCTANE\test_CAM2.ocs.m
tl"
Octane plug-in v1.17 on 2.63.0 : Unit Factor (rescaling): 1.0000
Octane plug-in v1.17 on 2.63.0 : Exporting frame #1
Octane plug-in v1.17 on 2.63.0 : Begin OBJ/MTL export
Octane plug-in v1.17 on 2.63.0 : OBJ file: "Z:\PROJECTS\OCTANE\test_CAM2.ocs.obj
.temp"
Octane plug-in v1.17 on 2.63.0 : Processed <Plane> in 0.000 secs
Octane plug-in v1.17 on 2.63.0 : Processed <Monkey> in 0.650 secs
Octane plug-in v1.17 on 2.63.0 : OBJ export time: 0.653 secs
Octane plug-in v1.17 on 2.63.0 : MTL file: "Z:\PROJECTS\OCTANE\test_CAM2.ocs.mtl
.temp"
Octane plug-in v1.17 on 2.63.0 : Processing <Material>
Octane plug-in v1.17 on 2.63.0 : Processing <Material.001>
Octane plug-in v1.17 on 2.63.0 : MTL export time: 0.003s
Octane plug-in v1.17 on 2.63.0 : Using camera : <Camera.Camera>
Octane plug-in v1.17 on 2.63.0 : Using Depth of Field from : Camera
Octane plug-in v1.17 on 2.63.0 : Using DoF from blender camera: 0.000000 * unitS
ize
Octane plug-in v1.17 on 2.63.0 : Camera position: x 12.894371 y 6.987521 z 11.31
1346
Octane plug-in v1.17 on 2.63.0 : Camera target: x 12.239509 y 6.542276 z 10.7006
80
Octane plug-in v1.17 on 2.63.0 : Camera up: x -0.317370 y 0.895343 z -0.312469
Octane plug-in v1.17 on 2.63.0 : Resolution set to 1920 x 1080 at 50%
Octane plug-in v1.17 on 2.63.0 : Samples per image: 64000
Octane plug-in v1.17 on 2.63.0 : Launching Octane: ['D:\\PROGRAMME_INSTALLED\\Refractive_Software\\OctaneRender\\octane.exe', '-m', 'test_CAM2.ocs.obj', '--cam-lensshift-right', '0.000000', '--cam-lensshift-up', '0.000000', '--cam-fov', '49.134342', '--cam-pos-x', '12.894371', '--cam-pos-y', '6.987521', '--cam-pos-z','11.311346', '--cam-target-x', '12.239509', '--cam-target-y', '6.542276', '--cam-target-z', '10.700680', '--cam-up-x', '-0.317370', '--cam-up-y', '0.895343', '--cam-up-z', '-0.312469', '--film-width', '960', '--film-height', '540', '-s', '6cxdf4000', '-r', 'Z:\\PROJECTS\\OCTANE\\test_CAM2.ocs.obj', 'Z:\\PROJECTS\\OCTANE\\test_CAM2.ocs.ocs']
Octane plug-in v1.17 on 2.63.0 : Status set to Info: Completed in 0h0m0.75
Info: Completed in 0h0m0.75


Any Ideas ?

Thanks

ps : working if I uncheck "export camera from scene" in Blender

MY BAD... Old Octane.exe still in my computer

[ROUBAL]

When attempting to render an animation with 26 characters, I get this on the console and the render stops after one single frame. On other tests, I sometimes rendered two frames before the render stopped with same message.



I rendered successfully 7 frames with only 4 characters exported. As they are almost all similar in structure, what could cause the trouble ? I checked and only mesh objects and the exported camera (named Camera) are present and selected in the scene in Blender (no empties). The characters are all selected and the 3 Context boxes are enabled : Selection Only, Remove Hidden, Remove Invisible.

Characters are boneless and animated by Shapekeys.

At a moment, it seemed that both selecting the camera and checking the export camera box caused the trouble, so I tried again with the camera unselected and the Camera export box enabled... without success.

As I can get the animation work with some characters, I think that some others have a problem, but as they are very similar in the principle, I can't find what is going wrong. Any clue ?

With 26 characters, it is very hard to find the culprits. I tried to export them by adding one character at each export, but when troubles happen, I don't see any difference with other characters that work.

[big_jimmy]

Hi all,

First post here so excuse me if this is a potentially daft question

Am using the latest exporter script 1.17 from Blender 2.63a. Opening my simple scene in Octane initially looks OK - but it seems as soon as any material is reassigned the cube and cone exhibit these strange artifacts. After this no matter what I assign to them they still look the same.



I've tried exporting with and without "Write materials into OCS file" - without this ticked I see



any ideas what I'm doing wrong here?

A huge thankyou in advance.

[big_jimmy]

Ok - I have figured out what is causing the above, it's the "smooth" property



If I set this off, the objects are rendered as you'd expect. The only problem is that when assigning any material, the "smooth" flag seems to be switched back on again. Any idea what is going on here?