OCTANE DEVELOPERS READ THIS THREAD TO SEE OCTANES ISSUES Tweet

[manalokos]

Hi Mojave,

Yes I know, but we are constantly going back and forth between DL. Info, and Pathtracing on the menu on the right, as we are debugging other parts of the graph, so when we go back to Pathtracing we loose all our settings for that node.
Another thing:
The graph node gets also too cluttered to manage it efficiently, it would be great to have an "Up" or "Back" button to move out of nodes and sub-nodes, just like navigating in folders and subfolders in a standard windows folder.
I have to regularly close all the tabs in the graph editor because they are packed so tight they are impossible to read.

Hi Filipe,

There's a way you can already save your preferred kernel settings by saving the node as a preset into your local DB.

[coilbook]

lately your new updates gave us tons of failed slaved with lots of cuda errors
Also when rendering for animation slave fails we have no idea it did. Please add a pop up message slave failed or something like this.

[mojave]

Yes I know, but we are constantly going back and forth between DL. Info, and Pathtracing on the menu on the right, as we are debugging other parts of the graph, so when we go back to Pathtracing we loose all our settings for that node.

As an option, instead of switching your kernel node type you could have different kernel nodes and change the one connected to your render target. In that way your settings will not be lost.

[manalokos]

Yes, we know that... but if we are using DL it is because we are inspecting another part of the nodegraph, which is already difficult to navigate, it is not really an option to use kernel nodes in the nodegraph there are already too many nodes.
So much that I sometimes wish there was an option for global materials and more stuff.
And trust me, I am already working with the Octane Standalone since 2011, and working on very complex setups, everyday ever since.

As an option, instead of switching your kernel node type you could have different kernel nodes and change the one connected to your render target. In that way your settings will not be lost.

Kind regards
Filipe

[FrankPooleFloating]

3.07 is nearly out. 3.08 is internally being tested...

Hey G, can you elaborate a wee bit on nearly? 3.07 kinda seems like a moving target...

[Goldorak]

3.07 is nearly out. 3.08 is internally being tested...

Hey G, can you elaborate a wee bit on nearly? 3.07 kinda seems like a moving target...

3.07 sdk is going out to plugin devs this week for initial testing and integration.

[Tag12345]

3.07 is nearly out. 3.08 is internally being tested...

Hey G, can you elaborate a wee bit on nearly? 3.07 kinda seems like a moving target...

3.07 sdk is going out to plugin devs this week for initial testing and integration.

is this update going to give faster render times against noise?

[Draydin_r]

Supposedly it will have the post processing denoiser built into it.

[mojave]

Supposedly it will have the post processing denoiser built into it.

The Octane AI denoiser is still in a experimental phase. It will come in a later date, but it hasn't been announced for 3.07.

[Tag12345]

Supposedly it will have the post processing denoiser built into it.

The Octane AI denoiser is still in a experimental phase. It will come in a later date, but it hasn't been announced for 3.07.

Well, i guess that makes sense since a denoiser would be a larger leap than 3.XX --> 3.XY (more like a 3.1 update or 3.2 instead)


though honestly, how long must we wait? Any dates at all, even estimates? And if 3.07 or 3.08 dont include major updates what will they have -- bugfixes?

It just feels like we keep waiting and waiting -- but being already 2-3 months or more, we aernt getting anywhere closer. Although i made this thread and we seem to be communicating with you devs abit more often (which is awesome), it still feels like you guys also seem unsure or wary to put of info about even estimated dates for progress,etc.


You have to understand, we are getting no relief in being told that big things are coming, then wait a few months, then told again the same thing, then waiting longer, then getting confirmation that things are being finalized, and that the update/features we were hoping for, are still being worked on and wont be in the next updates to come -- mind you -- without giving dates on this stuff too.

Can we honestly get a Long sticky thread about everything? I feel its time. Otherwise whats the point in talking with us if you guys cant take in account how we are feeling about all of this. Help us out, and lets push through this together without leaving us in the dark.


@gold @mojave @stratified @aokar @abstrax


Hell, add me to the team and ill do it haha (joke) but honestly. Communication is key. And rn, if you scroll through all of the forum posts and more, even the Facebook Oage showing the timeline for Octane 4 & brigade, the community as a whole is asking wheres the updates, wheres the communication, wheres the stuff people were promised a year or so ago when 3.X launched.

its been almost a whole year. You have many of these people looking into using other renderers during this time as they wait on Octane to develop more (since that 600$ investment doesnt come easy).


Least yall can do is Sticky thread with an update with as much info as you can about Updates - Delays - Better Communication here forward


No hate to the devs, yall know we love you all -- the work you guys do, and you guys are the reason we get to make the incredible stuff we do. Lets start again on a better footing though!