Preserve generated 3D model when switching between 2D and 3D modes
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 58/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- react, threejs, typescript
- Domain
- computer-graphics, frontend
Research direction
Reproduce the issue by generating a 3D model, switching to 2D, and returning to 3D; then trace the mode-switching and model-generation entry points. Done means the existing model remains available when only the view changes, while changes to image or model-affecting settings still require regeneration.
Written by the indexing model from the issue text.
Description
After generating a 3D model, switching from 3D mode back to 2D mode and then returning to 3D mode discards the generated model and requires it to be regenerated.
Expected behavior:
The generated 3D model should remain available when moving between 2D and 3D modes, as long as the underlying image/settings that affect the model have not changed.
Actual behavior:
Returning to 3D mode requires regenerating the model, even if the user only switched views.
Why this matters:
Regenerating the model can take time, especially for larger or more complex images. Losing the preview during normal navigation makes the workflow feel slower and can interrupt comparison between the 2D image and the generated 3D result.
Desired outcome:
Users should be able to move between 2D and 3D mode without losing the current generated model unless they make a change that actually requires regeneration.
- Dominant language
- TypeScript
- Stars
- 290
- Forks
- 32
- Avg merge
- 6h 2m
- Merged PRs (30d)
- 7
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from vycdev/Kromacut
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 48/100
-
Experimental WebAssembly acceleration for compute-heavy algorithmsMay be free again @vycdev claimed this 82 days ago, and no pull request is open. Openenhancement
-
enhancement good first issue help wanted
Difficulty 5/5 Over a week Newbie friendliness 55/100
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 42/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
QuantumNous/new-api#7839 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 1 day
-
bug p2 triaged
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
getpaseo/paseo#7071 · 1 comment ·
Maintainers usually reply within 1 day
-
test: make the #3408 Claude OAuth token fixture obviously fake so secret scanners stop flagging itOpen
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
code-yeongyu/senpi#3436 ·
Maintainers usually reply within 1 day
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 78/100
lingdojo/kana-dojo#32505 · 1 comment · 5 reactions ·
Maintainers usually reply within 1 day