LuxCoreRender / LuxCoreRender/BlendLuxCore
Expose "opencl.task.count" as an advanced parameter to fine tune memory usage by threads
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 877
- Forks
- 108
- PR merge metrics
- No merged PRs in 30d
Description
Expose "opencl.task.count" as an advanced parameter to fine tune memory usage by threads.
This has been proposed and talked here:
https://forums.luxcorerender.org/viewtopic.php?f=4&t=3560&sid=4536371c9ba3391d31b6f44638279e0c
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked LuxCoreRender forum discussion to understand the proposed behavior, then locate how advanced parameters are exposed in the Blender integration. Done means exposing opencl.task.count as an advanced parameter so users can tune memory usage by threads; the issue names no files or tests to run.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- blender, python
- Domain
- computer-graphics
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100