Page 14 of 16

Re: Version 3.07-R2 (Stable) update on 01.11.2017

PostPosted: Fri Dec 01, 2017 12:10 pm
by Ron
albaglib wrote:for me I finish my last work with octane and after it is Redshift all the time ... bye bye octane ...


What is the reasons to quit Octane?

What does Redshift better?

Would be great if you share your experience with us.

Ron

Re: Version 3.07-R2 (Stable) update on 01.11.2017

PostPosted: Sat Dec 02, 2017 12:27 am
by divasoft
Ron wrote:
albaglib wrote:for me I finish my last work with octane and after it is Redshift all the time ... bye bye octane ...


What is the reasons to quit Octane?

What does Redshift better?

Would be great if you share your experience with us.

Ron

Endless bugs and empty promises of developers.

Re: Version 3.07-R2 (Latest stable) update on 01.11.2017

PostPosted: Mon Dec 04, 2017 11:53 am
by KeeWe
I experienced the following problem:

Rendering to the picture viewer and working at the same time may cause a crash by using CTRL+Z. I think it only happend when working on File A while rendeinrg File B. How can I upload the last Octane related crash report?

Matte Material Shadow Bright gray

PostPosted: Thu Dec 07, 2017 5:13 pm
by Refracty
Hello,
I have a problem with my Matte Shadows.
The diffuse Material has "Matte" aktive and is black.
The shadow looks fine in the Render Viewer but when I start the batch rendering but the PNGs with alpha are grayish. The BG Color is baked in the shadow.
Alpha interpretaion in AE makes no difference.
How can I avoid the grayish shadow? I don't need a Background at all. How can I suppress the BG completely? So that I have the same image like in the Octane Live Render View?
Thank you.

Re: Version 3.07-R2 (Latest stable) update on 01.11.2017

PostPosted: Mon Dec 11, 2017 5:57 pm
by lancemoody
Just as an addendum to my earlier reports. Since changing by DelayTimeout to 60 seconds, I have had only one Octane failure (and it was a well-behaved simple failure--just stopped rendering).

Lance

Re: Version 3.07-R2 (Stable) update on 01.11.2017

PostPosted: Thu Jan 11, 2018 3:09 pm
by DanielPaul
bepeg4d wrote:Hi DanielPaul,
do you mind to try to roll back to 383.13, or even 382.33 with a clean installation?
ciao beppe


hey Beppe,

we have problems with new drivers above 383 or 384. Im not shure.
Looks like all gpus are used for raytracing, even when the displaycard is disabled for rendering.
There is no load on the display card, but the interface and viewport is laggy.

Is there any reason, why the newer drivers could cause this problems?
I need to know, we are in talk with nvidia to find the bug.
Also other programs in our pipeline have the same issues.

Thank you

Re: Version 3.07-R2 (Latest stable) update on 01.11.2017

PostPosted: Thu Jan 11, 2018 5:25 pm
by bepeg4d
Unless you have purchased a newer GPU, better to stay with old stable drivers. In my opinion, new drivers are interesting only for gamers.
I’m using 382.33 and 383.13 on two different multi gpu machines, and are very stable drivers.
Most important thing is to perform a clean installation without old parts of drivers in your system, and avoid the Windows auto update.
ciao beppe

Re: Version 3.07-R2 (Latest stable) update on 01.11.2017

PostPosted: Fri Jan 12, 2018 10:45 am
by DanielPaul
Alright. So if im right, the developing of octane is still on older drivers?

Maybe it would be useful to put the recommended driver versions on the release posts :)

cheers
Daniel

Re: Version 3.07-R2 (Latest stable) update on 01.11.2017

PostPosted: Mon Feb 19, 2018 4:41 pm
by renderingz
Does instance colour by image only work on grid array clones? Can't get it working on hexagonal grids or cloning onto a plane.

Re: Version 3.07-R2 (Latest stable) update on 01.11.2017

PostPosted: Sat Feb 24, 2018 4:15 pm
by 14bmwc780nike
Version 3.07-R2 bugs:

MoGraph clones don't always show up in the final render when using multiple objects for cloning but are present in the octane live viewer. Possible geometry limitation? Lowering parametric surface subdivisions seems to get objects to show up, but ends up looking horrible. Leverage camera culling in a future release?

Bitmap materials consistently default to UV projections regardless of the projection type chosen in the Octance material. Must override via the Cinema 4D projection tag and assign project there which is usually Cubic.

The live viewer doesn't update or detect changes consistently.

Normal maps need to be inverted.

Every texture in a file gets sent to render even when it's not assigned to an object. Can a more efficient solution be created?

Crashing has been far less frequent.