Skip to content

A fast 2D and 3D game engine — TypeScript SDK, C++/WebAssembly core, visual editor. Ship one project to web, desktop, WeChat MiniGames, playable ads, and native Android / iOS.

fix(gates): both package launchers pin the scale, and the playthrough cleans up

yhhc86fc8a8b61c
diff --git a/.gitignore b/.gitignore
index b752cd5ed..1e11e7671 100644
--- a/.gitignore
+++ b/.gitignore
@@ -152,6 +152,8 @@ native/ios/app.generated.yml
# verify-golden's package scratch (exports it launches and throws away)
/.golden/
+# verify-playthrough's, on the same terms
+/.playthrough/
# The export pipeline bundles through a scratch dir inside its own tree (node
# resolution), and a crashed run leaves one behind for the source gates to judge.
diff --git a/desktop/scripts/launch-minigame.mjs b/desktop/scripts/launch-minigame.mjs
index fa06f9eb4..7f4f5e7d2 100644
--- a/desktop/scripts/launch-minigame.mjs
+++ b/desktop/scripts/launch-minigame.mjs
@@ -30,6 +30,10 @@ import { inputScript } from './inputScript.mjs';
// Headless / GPU-less (CI) WebGL2 falls back to SwiftShader; harmless with a GPU.
app.commandLine.appendSwitch('enable-unsafe-swiftshader');
app.commandLine.appendSwitch('force-color-profile', 'srgb');
+// Both of the above pin a machine's answer to the code's; so does this. A capture
+// is in DEVICE pixels, so a scaled display returns a frame the editor's own
+// capture cannot be compared against. Its twin launcher pins it for the same reason.
+app.commandLine.appendSwitch('force-device-scale-factor', '1');
const argv = process.argv.slice(2);
const flag = (n, d) => {