Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Add wireframe and transparent preview modes for 3D model inspection

Closed
#47 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
52/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
react, threejs, typescript

Research direction

Start by locating the existing 3D preview and its controls, then trace how the preview renders generated geometry without affecting export. The work is complete when users can switch between shaded, transparent, wireframe, and optional overlay modes while STL/3MF output remains unchanged.

Written by the indexing model from the issue text.

Description

enhancement

Kromacut could add extra view modes in the 3D preview to make generated models easier to inspect.

This would be useful for development, debugging, and advanced users who want to better understand the generated geometry before exporting or printing.

Useful view modes could include:

  • Normal shaded view.
  • Transparent/x-ray view.
  • Wireframe view.
  • Optional wireframe overlay on top of the normal model.

The goal is to make it easier to inspect model shape, layer structure, edges, and possible geometry issues without changing the actual export.

This could live as a small view-mode control inside 3D mode, near the existing preview controls. It should be clearly treated as a preview/inspection option, not a print setting.

Desired outcome:
Users and developers can quickly switch the 3D preview into a wireframe or transparent mode to inspect the generated model more clearly, while STL/3MF export behavior remains unchanged.

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

  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 vycdev/Kromacut

All issues in vycdev/Kromacut

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.