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

Windows: Builder's 3-D view is black until a structure is loaded; MSI install takes ~80 s

Open
#356 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
c

Research direction

Start by reproducing the black Builder 3-D view on Windows 10 and compare its first paint with Linux and macOS. The issue names no source files or tests, so locate the Builder viewer entry point and inspect the MSI installation logs with msiexec /l*v timestamps to establish where time is spent. Done means the viewer has its expected background before a structure is loaded and the installation delay has been investigated; the issue leaves the fix and performance target open.

Written by the indexing model from the issue text.

Description

Seen 2026-10-16 recording the install video on a fresh Windows 10 account (9.2.0 MSI):

  • Black view. Tools › Builder opens with a black 3-D view, which stays black for about 25 s, through Add Structure from File, until water.xyz is drawn. The background is white on Linux and macOS. Expected: the viewer's background from the first paint.
  • Slow install. The MSI's "Please wait while Windows configures ECCE" phase takes about 80 s. The MSI holds about 160 MB in many small files (bundled Python, Perl, wxPython), and Windows Defender scans each one. Options: fewer files (Python stdlib in a zip, pruning unused packages), or measure where the time goes with msiexec /l*v timestamps first.
    Not release-critical.
Dominant language
C
Stars
10
Forks
8
Avg merge
21m
Merged PRs (30d)
1

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 FriendsofECCE/ECCE

All issues in FriendsofECCE/ECCE

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.