OTOY Forums

@acc24ex
Shadow pass shows all direct light shadows that calculated on the first bounce.
This includes sun light, but excludes sky light or texture environment if importance sampling is disabled or the texture environment doesn't consist of an image.
The reason for this limitation is that those light source are not included in the direct light calculation and Octane doesn't shoot an explicit shadow ray and with that can't calculate a shadow.
The shadows are weighted by the contribution of the light source casting the shadow.

thanks for the reply paride.. I'll keep in mind..

BTW this version seems buggy: imager / response doesn't seem to work on some scenes.. reloaded pc and all, it's still non reactive, along with post processin - I'm using 980ti and 580gtx for this.. anyone else getting this..

..and some weird stuff like changes in lighting/lag/flickery thing - when changing glossy level on some metal.. got it once or twice now

Paride - the xref material is not the problem. The problem is for objects in my local scene, which have local materials. These local objects/material get broken (grey) if the file has any xrefs turned on.

Hi acc24ex,
I'm not experiencing these issues, could you kindly share a scene where these issues happen to you?
Regards
paride

Been using v2 until a stable build of 3 came out, so thought I would try it today.

Seemed to install fine, but under the 'devices' tab there are no GPU's are showing. If I attempt to open octane window it says 'evaluating, no gpu's detected'. Rebooted and still no GPU's in octane. Uninstalled back down to V2 and my GPU's instantly appear again both there (2x 980tis).

Any advice? (Max 2014 build here)

darkline wrote:Been using v2 until a stable build of 3 came out, so thought I would try it today.

Seemed to install fine, but under the 'devices' tab there are no GPU's are showing. If I attempt to open octane window it says 'evaluating, no gpu's detected'. Rebooted and still no GPU's in octane. Uninstalled back down to V2 and my GPU's instantly appear again both there (2x 980tis).

Any advice? (Max 2014 build here)

Update your GPU driver Octane 3 now uses CUDA 8.

thanks will try that now

[quote="paride4331"]@acc24ex

Do not forget to add an infinite plane. We really need

works pretty well so far. But I'll know more in the next week.

Two odd thing I've come across :
1) One scene I opened from V2, suddenly the opacity of the material was 0 with v3. So I thought my object has dissappeared from the render. Turned out I needed to change the opacity in the material back to 1
2)unticking the motion blur checkbox with the octane window open brought my pc to a grinding halt. I had to wait about 2.5 minute for the viewport to update and remove the motion blur from my objects (was much faster in v2)

that's it so far

paride4331 wrote:Hi acc24ex,
I'm not experiencing these issues, could you kindly share a scene where these issues happen to you?
Regards
paride

OK, this was my fault - I forgot I was running octane camera, and kept on changing the settings on the Render window .. what now reminds me - can you do something to syncronise the camera settings to the render window..
- we can now access all the render window parameters? - if so, I could do it in maxscript when I catch some time - (did anyone try and do some octane properties for maxscript manual)