C4D node editor now has FULL 3rd party SDK

[HTK421]

C4D’s new native node editor is truly the best node interface of all 3D applications. It is Gorgeous !
However, nobody uses it because we are all addicted to 3rd party GPU renderers like Octane.
Ahmet, this would be a fantastic opportunity to integrate octane to use the c4D node editor, to make C4DOctane the best and most integrated “plugin” of all.

See the announcement from Maxon

[aoktar]

Don't you love our node editor?

[HTK421]

Hi Ahmet

Im detecting that I cannot convince you to develop that integration
So instead, here are a few issues that I've noticed in the current octane node editor.

This is meant to be a constructive and positive review (helping to report issues), it is not meant to criticize in any way
Thanks

[HTK421]

.... ironic timing
Today Maxon announced Redshift is now integrated with the C4D node editor.
So one of your major rendering competitors is now using that fantastic node editor.

Im only mentioning this to highlight that a lot of octane customers who are already frustrated by the stability issues are very tempted by Redshift,... and now that Redshift uses the C4D node editor it will become a very compelling alternative.

[aoktar]

OK what do you wish to hear from me? I'll switch to RS asap

[KeeWe]

Ahmet, would't you benefit from migrating to the C4D node editor? As far as I understand it, you could overtake features and let maxon do the work on certain things so to speak. Beside, no hard feelings, but the node editor from maxon looks and feels better than octanes. Don't get me wrong, I think you do an amazing job and I can certainly very well with Octane's node editor, but in terms of UI and UX, the native one would be my choice.

[aoktar]

Ahmet, would't you benefit from migrating to the C4D node editor? As far as I understand it, you could overtake features and let maxon do the work on certain things so to speak. Beside, no hard feelings, but the node editor from maxon looks and feels better than octanes. Don't get me wrong, I think you do an amazing job and I can certainly very well with Octane's node editor, but in terms of UI and UX, the native one would be my choice.

I don't avoid that may look better but I put a lot of effort to write this editor. Also our still have advantages over it, R20 and older versions have not node editor and I bring that.
Anyway I'm negative to integrate for new node editor but it's a hard task and no time to do it now. Also it will cause to maintenance the ours and c4d's same time.

[KeeWe]

I don't avoid that may look better but I put a lot of effort to write this editor.

There is no doubt about it an I hope you know how much the c4d community appreciates your excellent and quick work. I think theres no doubt that you are a huge part of Octane's success, not only in c4d.
And I know how hard it is to abandon something one put so much effort and hard work in it... but I hope this won't stand in the way of objective improvements.

R20 and older versions have not node editor and I bring that.

Good point, I didn't think of that.

Anyway I'm negative to integrate for new node editor but it's a hard task and no time to do it now.

Sure. I just think we should keep and eye on it, on the long run it would be very nice to have the native node support.

And again: I'm I wrong that you would benefit from stuff maxon brings to the node editor. Example grouping... wouldn't that be something maxon has to do and you could simply use it for Octane as well?

[frankmci]

The problem is that Ahmet is only one guy, and there's only so much he can do. Octane currently supports C4D versions all the way back to R15, so if that pattern persists, it means about five or six years worth of Double Development Hell for Octane to have both its own node editor, as well as be integrated with Cinema's. That's a nightmare of development and support I wouldn't wish on anybody!

I think the practical thing to do is cut Octane support for older versions of Cinema in the relatively near future. Limiting it to two or three years backward compatibility is perfectly reasonable. The current seven version backward compatibility is pretty crazy. With Redshift now owned and integrated by Maxon, the market pressure for the renderer to be fully integrated is going to be very high. Ultimately, I suspect Octane will have to be fully integrated to survive as a viable C4D option, but I'm glad I'm not the one having to make those tough development decisions.

[aoktar]

CORRECTION for a typo, hope you notified that written by mistake

Anyway I'm NOT negative to integrate for new node editor but it's a hard task and no time to do it now.