Page 3 of 4
Re: OctaneRender® for 3ds max® v4.04 - 6.17
Posted: Wed May 01, 2019 7:12 am
by paride4331
senorpablo wrote:paride4331 wrote:senorpablo wrote:There's a massive bug with Octane lights/emissive geo and shadow catchers. The scene is a daylight with HDRI for lighting, plus another daylight set to visible with a float texture for backplate at dark grey. Shadow catcher plane under objects of interest.
Adding an Octane light to the scene breaks the shadow catcher. The light seems to be casting shadows which are much, much darker than they should be(like 1000x). A little tiny LED size light like you might find on electronics to let you know the power is on, casts massive shadows on objects which are receiving no illumination. The result is that the entire shadow catcher turns dark and becomes clearly visible in the scene.
Octane shadow catcher broken.jpg
Hi senorpablo,
this issue seems to be because of the way shadows are calculated.
The strength of a shadow is calculated from the ratio of obstructed incoming
light to incoming light from all sources. So basically in this
particular case, the strength of the light sources themselves are
cancelled out. The effect could be better if you use a daylight
environment (the shadows are much softer with lower power).
So, there's not much we can do for now, at least nothing on the 3dsmax
To avoid this issue you should use render layers instead of shadow catcher.
Regards
Paride
I am using a daylight environment with texture HDRI. The power is at 2.
I'm rendering dozens of shots and don't have time to use a render layers/compositing workflow.
Between this case, and the one Coilbook has discovered, can Octane really promote itself as "unbiased"?
Hi senorpablo,
precisely because shadow catcher is a trick and DL AO is a plus.
Compositing is the correct unbiased workflow and unbiased engine is PMC or PT.
Regards
Paride
Re: OctaneRender® for 3ds max® v4.04 - 6.17
Posted: Wed May 01, 2019 9:25 pm
by senorpablo
paride4331 wrote:
Hi senorpablo,
precisely because shadow catcher is a trick and DL AO is a plus.
Compositing is the correct unbiased workflow and unbiased engine is PMC or PT.
Regards
Paride
DL AO is the default for Octane. So by Otoy's own choice, Octane is not unbiased by default.
Everything in rendering is a "trick." Every single aspect of CGI is an approximation or estimation. The shadow catcher is poorly implemented. I'm curious if Mental Ray, Iray, Vray, Redshift or Arnold have the same issue. My hunch is no.
Re: OctaneRender® for 3ds max® v4.04 - 6.17
Posted: Thu May 02, 2019 11:04 am
by ThaRaven
Hey,
so there is no RTX Hardware support planned for V4 ?
Re: OctaneRender® for 3ds max® v4.04 - 6.17
Posted: Thu May 02, 2019 11:53 am
by paride4331
ThaRaven wrote:Hey,
so there is no RTX Hardware support planned for V4 ?
viewtopic.php?f=27&t=71351#p362399
Re: OctaneRender® for 3ds max® v4.04 - 6.17
Posted: Fri May 10, 2019 11:01 am
by Elden
In my setup 3ds Max 2019, win7 X64, a very problematic bug seems to have sneeked into this build. The live viewer has become unreliable and doesn't always update properly. For instance - I just had an object set to non-renderable in the Max properties, and set to movable proxy in the Octane properties. Switching it to renderable in the Max properties - still invisible in the live viewer. Closing the live viewer and opening it again - still no sign if the object in question. The only way is to exit and restart max. I've had other occasions when ojects wouldn't update properly in the live viewer. Needless to say, this hampers the workflow. Anybody else have a similar experience?
Re: OctaneRender® for 3ds max® v4.04 - 6.17
Posted: Fri May 10, 2019 12:16 pm
by Elden
And adding to that. If I isolate an object with the live viewer open, and then bring back the whole scene - it still only renders the previously isolated object. Again, the only solution for me when Octane is in that mood - is to restart Max. Crazy...
Re: OctaneRender® for 3ds max® v4.04 - 6.17
Posted: Sun May 12, 2019 4:13 pm
by merid888
error with the version 6.17. i see the map in the view of 3ds max but i can't see into octanerender viewport
someone can help me ?
thank you octanrender team
Re: OctaneRender® for 3ds max® v4.04 - 6.17
Posted: Mon May 13, 2019 9:25 am
by paride4331
Elden wrote:And adding to that. If I isolate an object with the live viewer open, and then bring back the whole scene - it still only renders the previously isolated object. Again, the only solution for me when Octane is in that mood - is to restart Max. Crazy...
Hi Elden,
I tested your issue and sent to developers.
Regards
Paride
Re: OctaneRender® for 3ds max® v4.04 - 6.17
Posted: Mon May 13, 2019 9:28 am
by paride4331
merid888 wrote:error with the version 6.17. i see the map im the view of 3ds max but i can't see into octanerender viewport
someone can help me ?
thank you octanrender team
Hi merid888,
it's difficult to say off the top of my head.
could you share that material making a 3dsmax archive?
Regards
Paride
Re: OctaneRender® for 3ds max® v4.04 - 6.17
Posted: Thu May 16, 2019 1:51 am
by coilbook
Hi Paride,
what does this error mean?
Camera 1 rendered sequence fine this is another camera angle and after rendering frame 1, octane processes frame to and then render fails right before frame two is about to render.
out of core is not unloading properly?
Thanks
UPDATE: restart fixed it but I noticed if a frame one uses almost all of the vram and frame two needs to use out of core because phoenix is added or a larger animated texture, octane crashes with no memory error instead of using CPU ram. Hopefully they can fix it.