Material Node Editor
Moderators: ChrisHekman, aoktar
- LOVEXMEDIA
- Posts: 36
- Joined: Wed Jun 07, 2017 1:19 am
Getting straight to it, the Material Editor Node system needs a rework in the UI. It is kind of clunky and is difficult to navigate when working with multiple nodes. After using Substance Designer I feel spoiled by the seamless interface and how clean it looks! I will do some designs to show what I think could improve the look to update the vibe! I love Octane and I look forward to the many new features to come!
LoveyDov3
https://www.instagram.com/lvydov3/
i9-10940x [Custom Loop] • 96GB RAM • 2× NVLinkRTX 3090 FE
https://www.instagram.com/lvydov3/
i9-10940x [Custom Loop] • 96GB RAM • 2× NVLinkRTX 3090 FE
- LOVEXMEDIA
- Posts: 36
- Joined: Wed Jun 07, 2017 1:19 am
Here is a quick rendition of what I have done just to give a visual aid as to what I believe could help clean up the Node Editors look and vibe.
Last edited by LOVEXMEDIA on Wed Jul 31, 2019 10:58 pm, edited 1 time in total.
LoveyDov3
https://www.instagram.com/lvydov3/
i9-10940x [Custom Loop] • 96GB RAM • 2× NVLinkRTX 3090 FE
https://www.instagram.com/lvydov3/
i9-10940x [Custom Loop] • 96GB RAM • 2× NVLinkRTX 3090 FE
Thanks for your advice!
Octane For Cinema 4D developer / 3d generalist
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
- LOVEXMEDIA
- Posts: 36
- Joined: Wed Jun 07, 2017 1:19 am
I appreciate you and your work!!aoktar wrote:Thanks for your advice!
Here is a revised version of the Materials as of 2019.1 RC2.
LoveyDov3
https://www.instagram.com/lvydov3/
i9-10940x [Custom Loop] • 96GB RAM • 2× NVLinkRTX 3090 FE
https://www.instagram.com/lvydov3/
i9-10940x [Custom Loop] • 96GB RAM • 2× NVLinkRTX 3090 FE
Your revision looks completely unappealing. I don't see how those thick lines are of any help. Also, there is a reason why every single app that uses nodes moved away from those kinds of lines they are all but easy to read. The node interface in Octane looks good already I would focus instead on UX rather than UI. Adding more options like group nodes, shortcuts, a node finder, etc.
Plus if we are in for a change in the look why not go all out and integrate the new C4D system.
Plus if we are in for a change in the look why not go all out and integrate the new C4D system.
- LOVEXMEDIA
- Posts: 36
- Joined: Wed Jun 07, 2017 1:19 am
I agree that my first mock up was pretty rough but the second image is more true to my vision. I am doing a write that goes into more detail about why I think the way I do. I think you are right in that there definitely could be more done in the UX area of C4D's Octane plugin.Terryvfx wrote:Your revision looks completely unappealing. I don't see how those thick lines are of any help. Also, there is a reason why every single app that uses nodes moved away from those kinds of lines they are all but easy to read. The node interface in Octane looks good already I would focus instead on UX rather than UI. Adding more options like group nodes, shortcuts, a node finder, etc.
Plus if we are in for a change in the look why not go all out and integrate the new C4D system.
What I would enjoy would be look at how the main materials (OctDiffuse, OctGlossy etc.) could be more of a folder system. One that would collapse all connected nodes upon minimizing it and auto arrange them so upon maximizing that MAT node it would be organized for ease of use. There could even be a on/off for that feature so as to keep it as is and allow users to maintain using Toggle to Snap instead as a means to clean up their nodes.
I wouldn't begin to know what would be more efficient in the long run for OTOY, integration or their own system like they have currently but either way I would love to see some polish in the node editor.
LoveyDov3
https://www.instagram.com/lvydov3/
i9-10940x [Custom Loop] • 96GB RAM • 2× NVLinkRTX 3090 FE
https://www.instagram.com/lvydov3/
i9-10940x [Custom Loop] • 96GB RAM • 2× NVLinkRTX 3090 FE
Actually our node editor system is not a really new system. It's using native containers of C4D by same way you do with material manager. Just putting a graphics interface between user and C4D core. Because of this implementing the groups are hard. I tried that to implement but it's not straightforward to do without issues.
My next step will be to improve the UX for our node editor. And also I'll try to use new node editor of R21. But will keep the our NE
My next step will be to improve the UX for our node editor. And also I'll try to use new node editor of R21. But will keep the our NE
Octane For Cinema 4D developer / 3d generalist
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
- LOVEXMEDIA
- Posts: 36
- Joined: Wed Jun 07, 2017 1:19 am
I am excited for all the new innovation coming from you all in R21! Thanks for all the replys!aoktar wrote:Actually our node editor system is not a really new system. It's using native containers of C4D by same way you do with material manager. Just putting a graphics interface between user and C4D core. Because of this implementing the groups are hard. I tried that to implement but it's not straightforward to do without issues.
My next step will be to improve the UX for our node editor. And also I'll try to use new node editor of R21. But will keep the our NE
LoveyDov3
https://www.instagram.com/lvydov3/
i9-10940x [Custom Loop] • 96GB RAM • 2× NVLinkRTX 3090 FE
https://www.instagram.com/lvydov3/
i9-10940x [Custom Loop] • 96GB RAM • 2× NVLinkRTX 3090 FE
- connartist
- Posts: 20
- Joined: Sun Nov 17, 2013 5:11 am
I'm trying to decide if its worth it to upgrade or just stick with R20 for as long as possible and then eventually upgrade. Is porting Octane over to the R21 node system a low priority that could likely take a year? If its right around the corner it could weigh my decision to upgrade before my MSA is up, thanks!