OTOY Forums

Hello everyone,

I recently got my hands on octane and think it´s a great tool but I encountered a strange error message saying "Narcissic camera ... stop looking at yourself!", when I wanted to render a still image from within blender. I´m using blender 2.57.1 and the unofficial exporter 1.1.0.

Has someone any idea what the console is trying to tell me? I found nothing via google considering this error message. I´m quiet certain it´s my own mistake , but I simply don´t know what´s wrong. In the blender internal everything works fine, octane also works great running on it´s own (tested with the scenes from the demo suite).

My system configuration:
- AMD Phenom II X6 1100T
- 8 GB RAM
- one GeForce GTX 550Ti (for display)
- two Geforce GTX 580 (for rendering)
- Nvidia driver version 270.61
- Win 7 Pro 64 bit

Thanks in advance for your help.

Kind regards, Kai

haha lol, yoyoz...

I'm not sure (you are the first with this problem), probably something wrong with your camera - some extreme parameter values maybe? Or there is no camera?

Post a screen of the console or a bare scene that is still giving the problem, I want to see this output message

Yay, first ... in something!

there is a camera in the scene tracking an empty (both animated via keyframes). They are moving from one location key to the next including a little rotation of the target within 250 frames. Camera settings are 55 millimeters focal length, perspective mode, size 0.5 on display.

Yersterday evening I got it to work exporting to octane, but only when I uncheck "export camera from scene".

PS.: Only thing I changed was to remove the GTX 550ti from my system, but that was just because I realized that the two 580s run on pci express 8x mode when there are three cards on my board. So I put the two 580s in onther pci express slots and got rid of the 550ti. Performance is a bit better now with two cards running in 16x mode instead of three on 8x mode plus lower temperatures on the gpus. I think that has nothing to do with my current problem, but it was the only thing I changed execpt unchecking the option mentioned above.

Kind regards, Kai

OMG ... now I saw it in the camera settings!
DAMN! I´m such an idiot!

The camera had IT SELF as depth of field target object ... now it works fine.

Good, the enigma is solved.

Programmer's sense of humor is awesome...

Indeed, it might as well could have sayed: "Get it right, you dumb f..."
Thanks for your reply anyway

I couldn't resist putting this error message and I apologize if it made you lose some time

Nice you finally figured out what happened anyway!

Cheers,
Yoyoz

No no, it´s ok. I found it quiet funny too.

But I have another question concerning rendering performance, particularly gpu load. Should I create a new topic for this, or is it ok when I ask you right here?

Kind regards, Kai

Questions about Octane itself don't fit in this sub-forum, but post it anyway, it's probably already been answered / debated, so spawning new threads would be a waste.

Ok,

as I already mentioned I changed my system configuration to just two 580s instead of adding an extra 550ti for display, to get the two 580s running in pci express 16x mode. Initally I did that because I never got octane to use more than 50% gpu load on any card. Now it seems a bit better, but still the gpu load does not exceed 56% on one and 49% on the other 580.

Is there something I did wrong in the octane preferences? I left everything on default except that I put both 580s in the "active" panel in the cuda devices.

PS.: For testing purposes I tried cycles and it uses up to 96% gpu load. Of course only on one 580, since cycles doesn´t support multiple gpus, I think.