Roadmap 0.11, Discord, last sweep before 0.9 (2026-11-05)

FX.42 Input lag since 0.8.1 in Studio on Windows and in the browser, with no CPU or GPU load

  • Fix
  • Planned
  • CadCraft
  • Studio

Reported 2026-11-04 by one reporter: drawing, panning and clicking respond late since 0.8.1, in Studio (the process uses about 6 MB in Task Manager, which is the shell, not the web view) and in Chrome. Not reproduced and not measured. Do: compare 0.8 and 0.8.1 for new pointer, wheel or timer work (hardware probe, input devices UI, problems store, live presence), measure input latency on ws11a with a real GPU, and ask which app and file. Do not claim a cause before measuring.

studio-fix-09 2026-11-05: NO CAUSE FOUND in the page. The apps' own files are byte-identical between 0.8 and 0.8.1 (only BimCraft's workspace/engine.js and release.json differ); the shared shell loads live from the site. tools/shell-test/input-latency.mjs (pointer, wheel, click to next frame, idle frame time, long tasks, Event Timing) run on ws11a (real GPU, Windows Chrome) for CadCraft, BimCraft, ModelCraft, PartCraft in 0.8, 0.8.1 and the a Discord member build: no difference between the builds: idle frame 10 ms with no long task in all 12 runs; pointer to next frame p50 7 / p95 9.5 ms and wheel p50 15-16 / p95 18-19 ms in 0.8, 0.8.1 and a Discord member alike (workstation11a, RTX 5070, empty app, a 100 Hz frame clock); results in the log. Not measured: Studio's own WebView2 window, the reporter's machine, a big drawing, a 4K or high-refresh display. Still need: which app, drawing size, graphics card. Looked at 2026-11-07: 0.8 and 0.8.1 differ only in release.json, so the app code is the same; headless Chromium on the server shows the same 60 fps, 0.3 ms per pointer move and no long tasks while drawing or panning in 0.8, 0.8.1 and /lab. Not found, not fixed. Needs the reporter: a Chrome performance trace of a a Discord member, whether a controller, 3D mouse, pen or touch screen is connected, the file size, and whether it also lags at /use/cadcraft/0.8. A real-GPU check would run on workstation11a.

Waits on: the reporter's machine, app and file; a Studio (WebView2) measurement on Windows

Add a comment

Community comments

No comments yet

Add detail as we go: how you would use it, files or steps that show the problem, what other programs do. The team reads every comment.

Sign in or create a free account to add a comment.