abstrax wrote:marco75 wrote:i use this version but it is not so stable, when i export from c4d r12 sometime with some scenes octane after voxelization (at the beginning of the rendering) it close.
the same scene loaded directly as mesh in octane and not directly by c4d as obj file made by the exporter of c4d have no problem.
why????
i have this problem often...
c4d 64 bit R12
12 Gb ram
geforce GTX590 1,5Gb x 2
Hi Marco,
Could you please send me an example scene, that shows this behaviour?
Thanks,
Marcus
Have the exact same problem, everything exports, then octane shuts down, now I imported the .obj inside 3dmax, everything loads up perfect inside max, and then into octane again, and shuts it down.. Obviously it's a octane thing.. is it still the file/object naming issues .. ?
BTW 3dmax octane exporter is like 5 times slower than c4d's is, and the c4d plugin is so much nicely implemented, but still, the same problem arises, loads up voxelizes, and octane shuts down with no error messages..
What exact specs are we supposed to follow, I've been debugging this for an hour now, will try an object by object import until I find out which one causes the prob.. it doesn't seem it is related to the octane plugin as much, or let's try the 3dmax forum part
EDIT: Found one solution, and it was stupid/easy..
Make sure you select "Specify GPU devices to use" inside the octane plugin exporter and select a device
The same problem/solution works in both c4d and 3dmax exporter.. I know you don't always need to select it, but maybe it's a multi-gpu thing.. anyway try that
Re-edit: it's a multi GPU thing in my case, crashes octane when I select all the GPUs.. ?
it's octane 2.46b, seems to work only on 1 GPU today..
it's because of my 4th gpu card 8800 gtx, when I take it off runs ok.. well.. that's that sorted