Make it possible to create LuxCore nodes in Cycles node trees

Open
#362 1 comment 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
blender, python
Domain
computer-graphics

Research direction

Start by inspecting LuxCoreNode.poll(), the existing Cycles node reader, the node export procedure, and the Cycles shader node-tree add-node menu. Determine how Cycles nodes can produce LuxCore properties and how mixed LuxCore/Cycles trees are exported. Done means compatible Cycles nodes, LuxCore categories, and a Cycles category are available together, with node groups tested where possible.

Written by the indexing model from the issue text.

Description

enhancement

Benefits:

  • We can use Cycles' color ramp nodes
  • We can use Cycles' curve nodes (in the future, once LuxCore has this feature)
  • It's a workaround to issue #167
  • Node groups? Needs testing

This requires the following:

  • Modify LuxCoreNode.poll()
  • Cycles nodes will have to be exported by functions that take the node as input and produce LuxCore properties, much like the existing Cycles node reader (which we can probably repurpose for this)
  • The node export procedure will have to be changed to allow a mix of Cycles and LuxCore nodes
  • The "add node" menu of the Cycles shader node tree will have to be modified. If possible, it would be good to have all the existing LuxCore categories in the top level, and on the bottom an entry "Cycles" which contains all Cycles categories, however I don't know yet if this is possible

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

Dominant language
Python
Stars
877
Forks
108
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from LuxCoreRender/BlendLuxCore

All issues in LuxCoreRender/BlendLuxCore

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.