got-feedBack/feedBack-desktop
1
0
Fork 0
mirror of https://github.com/got-feedBack/feedBack-desktop.git synced 2026-08-11 03:09:56 +00:00
Code Issues Actions 1 Packages Projects Releases Wiki Activity

Force high-performance GPU on Windows to stabilize 3D Highway resolution (#53)

Browse Source 
On hybrid-GPU Windows laptops (Intel iGPU + NVIDIA/AMD dGPU), Chromium's
GPU-process adapter selection is non-deterministic across launches. When
it binds the iGPU, the 3D Highway's per-frame WebGL cost blows the draw
budget and the load-adaptive resolution scaler (feedBack#654) silently
drops the canvas to as low as quarter-res — so the highway renders
pixelated even with Quality pinned at HD, varying launch to launch. The
renderer's `powerPreference: 'high-performance'` WebGL hint is only
advisory and doesn't reliably override the OS/Chromium adapter choice.

Append the Chromium `force_high_performance_gpu` switch on win32 (before
app.whenReady, so it's read during Chromium init) so the discrete adapter
is selected consistently and the scaler rarely engages. Single-GPU
machines are unaffected; on dual-GPU desktops it likewise picks discrete.

Fixes #52

Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This commit is contained in:
Byron Gamatos
2026-06-30 20:18:34 +02:00
committed by GitHub
co-authored by Claude Opus 4.8
parent 92a78b4c9a
commit 3eefa3646a
1 changed files with 20 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
src/main/main.ts
+20
View File
@@ -210,6 +210,26 @@ if (process.platform === 'linux') {
}
}
if (process.platform === 'win32') {
// Pin the WebGL/GPU process to the discrete (high-performance) adapter on
// hybrid-GPU machines. On Windows laptops with an Intel iGPU + NVIDIA/AMD
// dGPU, Chromium's GPU-process adapter selection is non-deterministic across
// launches — one run binds the iGPU, the next the dGPU. When it lands on the
// iGPU the 3D Highway's per-frame WebGL cost blows the draw budget and the
// load-adaptive resolution scaler (feedBack#654, static/highway.js
// _adaptRenderScale) silently drops the canvas to as low as quarter-res to
// hold the frame rate — so the highway renders pixelated even with the
// Quality selector pinned at HD, and which way it goes varies launch to
// launch. The renderer's `powerPreference: 'high-performance'` WebGL hint
// (plugins/highway_3d) is only advisory and does not reliably override the
// OS/Chromium adapter choice. This switch forces the high-performance GPU at
// the Chromium level so the fast path is consistent and the scaler rarely
// engages. Set before app.whenReady() so it's read during Chromium init.
// Desktop machines with a single GPU are unaffected (there's nothing to
// pick); on dual-GPU desktops it likewise selects the discrete card.
app.commandLine.appendSwitch('force_high_performance_gpu');
}
// Prevent error dialogs from showing when the Python subprocess has issues.
// Both handlers log and swallow — don't let a stray rejection in one of the
// subsystems tear the whole app down.