From 065428c81f92b4419dab5f5281a00fdbe6ad77e5 Mon Sep 17 00:00:00 2001 From: Valiantsin Dzerakh Date: Sun, 1 Nov 2026 02:51:19 +0300 Subject: [PATCH] Name the 1.4.3 contact-setup crash under the real-time step's floor Issues #29 and #92 (0.1.1, 240 Hz monitors, fps_limit = display) crash in main+0x1292560 reading a Havok body's shape. Forced steps between 1/252 and 1/230 s reproduce it in that call chain on the Depths load 3 of 3 times; steps of 1/240 s and longer, or the same jitter through the floor, play. The comment now records it next to the #241 abort. Co-Authored-By: Claude Opus 5.5 --- runtime/frame_rate.c | 9 +++++++-- 1 file changed, 7 insertions(+), 2 deletions(-) diff --git a/runtime/frame_rate.c b/runtime/frame_rate.c index c2527475..08b5343c 100644 --- a/runtime/frame_rate.c +++ b/runtime/frame_rate.c @@ -18,8 +18,13 @@ // 280 Hz monitor): Havok's hkDefaultMemoryImpl reports "Out of memory" for the buffer the physics pre-solve (profiler // scope "TtPreSolve") resizes in main+0x1261630. Forced steps on the Depths save: 1/240 s plays, 1/244 s and shorter // abort; the field, sky island and fight saves play at 1/280 s, the town save aborts after about 800 frames. The -// frame limit stops at 240 too (LIMIT_MAX_HZ), so the floor only catches the average dipping under 1/240 s at that -// limit, and no limit makes the game run slower than the clock. +// same short steps also crash a physics worker reading that buffer's contacts: an access violation in main+0x1292560 +// or its caller main+0x1286870 (narrowphase contact setup, reached from the grid task main+0x12f1ea0), reading a +// Havok body's shape at body+0x78 as null or garbage (issues #29 and #92, 240 Hz monitors with fps_limit = display). +// Steps drawn from 1/252..1/230 s crash the Depths load there in seconds; 1/240..1/230 s plays. The frame limit +// stops at 240 too (LIMIT_MAX_HZ), so the floor only catches the average dipping under 1/240 s at that limit: a +// present late by less than a period keeps the pacer's phase (nvn_api_obj.c, pace), so the next display interval is +// shorter than the period. No limit makes the game run slower than the clock. // // The sample is the display time the pacer gives each present (nvnQueuePresentTexture), so the step follows the // frames as shown, pacing waits included. With the step on, the pacer ignores the game's interval and holds a frame