OctaneRender® 1.0 beta2.52 >>> download here <<< [OBSOLETE]

[romrom74]

Hi refracty,
I have same troubles with 2.52 ...computer reboots, 5 to 15 secs after render is running, in dl, pmc or pt. I run it on an 1200watt HPZ800, with 2 gtxs580 3gb, 2 xeons 3.46 ghz and 48 gb of ram...this machine is the most stable and powerfull (and most expensive)I ever have,however when I try to do some renderings with octane, computer reboots like if there's some kind of protection mechansim. If you look at the windows event log, you'll see a critical kernel-power event (41), which is a very low level error.
I don't have any trouble with this gear when doing some really heavy realtime rendering in opengl or directx at all.
So I think it's a driver/cuda problem on windows7 64 bit with cuda,because all the hardware (the 2gtx, th psu and so on , have been tested separatly on on another machine without any problem at all)+ I don't have this behavior with pre cuda 4.0 build of octane.
so you 're not alone...

[roeland]

Normalmapping doesn't work if the texture is piped through a texture input pin into the material macro. The texture must be inside the macro, for normalmapping to work:

It is a more general problem, the node graph is not updated correctly after connecting a node to an input pin of a macro node. We will fix that problem in the next release.

--
Roeland

[matej]

Thanks, Roeland. I thought it was somehow related to this problem.

[Refracty]

Hi romrom74,

I am still investigating the issue that i have run to.
Here is a short update:

I updated the driver to the most recent - No much difference. The problem still existed. I tried differnt GPU combinations and it worked with all combis except 'all GPUs'.
Then I remeasured the power.
The interesting thing is that the pathtracing kernel sucks more Watts then the PMC kernel. It is not so visible with one gpu but with multiple NF110 chips I see a difference of 100 Watts at full load. So this could lead to a power issue (at least in my case) especially with PT.
I have now pluged one of the GPU power cords into a different rail (PSU) to see if the voltage is just too unevenly spreaded.
I did this today so I will test more and let you know. For now it is working.

I am not sure if your problem is about the same thing but the activity in the kernel could lead to more energy consumption.
Can you choose other slots in your PSU for the Graphics Card energy supply?

[telemmaite]

Refracty exactly same experience here. My whole PC is almost frozen when i render with PT it loads my GPU 30% more than PMC!

[matej]

A small annoyance: if you reconnect an input pin inside a macro, the value of the pin that has been set previously gets lost and the pin is set to default.

[Refracty]

Here is a final update. I hope this issue will not repeat and might help other useres experiencing a 'full' crash / reboot when working with Octane (especially PT kernel).

A few days ago I have pluged in one 'Graphic Card Power Cable' into a different plug of my PSU.
Before my PSU crashed often especially with Pathtracing wich pulls more Power compared to PMC.
Now since I did this small change in the power configuration it works fine.
It seems that there was one 'Power Rail' with Voltage problems so that it shut of when it has hit the 1350 Watts mark.
Now all runs smooth so far. Not even one crash.

[nildoe]

thx refracty for getting back to us with that feedback, im sure it will be very useful for me and others when(if) we run into that issue.

[matej]

I'm not sure if I'm missing something here, but how do I use a texture for emission since the introduction of IES? If I set the texture to the distribution pin of the texture emitter node, I get the emission alright, but the coordinates of the emission don't correspond with the UV coordinates. Open the attached scene and move around the plane a little and you'll see what I mean (the texture emission coordinates change with the camera).

tex-emiss.jpg

EDIT: lol, nevermind, the texture should be plugged into 'efficiency', not distribution

[8Eggar8]

My render window completely freezes after only turning a minute bit

Any Ideas?


BTW - I am using the most current driver 285.58, and I have checked the original Beta of Octane and all works fine on that version

Thank You for any help you can give on this matter

just freezes and sticks there for a long while, may move a frame or two after 1min. or so...

Doing some testing now.... it seems maybe when I include my 460se card into the picture, all starts to go wrong.. more soon...

oooo... wow, looks like that's the bug... one of my 460 cards is a zotac 460se and whenever that one is included the scene 'Locks' up...
neither of the 460 cards are hooked up to my displays (only my 260 is)....
anything heard about the 460se cards producing problems?

hmm... Zotac's HomePage says a driver specified for xp64 is version 280.26.... is one allowed to mount an earlier driver version on top of the more recent version just to satisfy one of the cards?