OctoPrint / OctoPrint/OctoPrint
[Request] Just-in-time gcode preview
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 9.1k
- Forks
- 1.7k
- Avg merge
- 2d 5h
- Merged PRs (30d)
- 4
Description
Is your feature request related to a problem? Please describe.
GCode Viewer is unusable on large models. The volume of data overloads the browser and makes the tab crash and/or slow to a crawl.
Describe the solution you'd like
Rather than loading and analyzing the entire gcode file, only index the start of each layer at load time. Then, using that index, load, analyze, and render a particular layer only when navidating to it. Cache up to (a configurable?) N recent layers for quicker navigation and for showing previous/next layer if selected.
Describe alternatives you've considered
The only alternatives seem to be not using Octoprint for gcode preview or only using it from a very-high-end computer (and especially not mobile device).
Additional context
No response
Contributor guide
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 by locating the GCode Viewer and tracing how a large file is currently loaded, analyzed, and rendered. Done means large models no longer overwhelm the browser, while layer navigation loads only the selected layer and supports the requested recent-layer caching behavior.
Written by the indexing model from the issue text.
Assessment
- Domain
- frontend, performance
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100