Ultimaker / Ultimaker/CuraEngine
scenegraph for scene management
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 1.9k
- Forks
- 933
- Avg merge
- 3d 9h
- Merged PRs (30d)
- 10
Description
Hello folks,
Is there any online for this API to disscuss some relevant issues? I did not see any , therefore I am posting it here. How do you manage a large scene that has to fit inside the printing region ? In other words, If there are several copies of the same model, do you save and send all the coordinates of each model to slicer,, or you manage the scene using the scenegraph data-structure first , then slice it and eventually generate gcode for each of the copies of the model ?
Thanks
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
No file, test, or entry point is named. Start by locating the existing scene-management and slicing entry points in CuraEngine, then compare how repeated models are represented before G-code generation. The intended scenegraph design and completion criteria need clarification before implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- computer-graphics
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100