Improve Cycles OSL nodes interface #89741
Labels
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
5 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#89741
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
I have found that the interface of the OSL nodes has certain limitations. I think some of them could have a relatively easy solution. For example, change how vectors are displayed in the node. This simple change will improve the appearance of the larger nodes. Another aspect to improve is the interface for image files. Using a 'string' field allow to introducing typographical errors by the user. I think a PointerProperty to bpy.types.Image would be more convenient.
I hope these proposals make sense.
Main task list:
Sub tasks:
Added subscriber: @povmaniac
Added subscriber: @CreatorSiSo
I think the first step to improve how some options are drawn in the interface is to add a suitable definition for each option within the OSL code.
For example, for Booleans.
Without this definition, it is quite difficult to deduce when an option is a Boolean or an integer.
Added subscriber: @brecht
Thanks for your tips, Brecht.
Vector input: the idea is save vertical space in the node, but yes, in the 'normal' node sizes the horizontal space maybe is not enough. But the user can extend the node size easily.
Image datablock: currently I use the typicall 'template_ID' image file interface for my nodes, that is not perfect but is very clossely to the used in the Blender texture node.
{F10231931, width=100%}
After some testing, I have verified that the definition of each property added in the .osl file is processed and added in metadata format inside the .oso file
This generates the following metadata:
The next step is to add the property definition in some cases like booleans or image files.
Later, we can advise users to do the same when using their own OSL code.
I have created a first patch for review by the Blender developers. https://developer.blender.org/D12074
@brecht I applied all the required changes and I added the blender_shader.cpp part that I think is necessary modify. https://developer.blender.org/D12074?id=40152
Thanks..
This issue was referenced by
e6bbbd965a
Something I noticed is that I ran into an assert, there's a bitmask on the amount of input plugs to a max of uint64_t (64 plugs) in Cycles.
Yes I have made an OSL node that uses just under 100 plugs and yes they are all needed... :)