evertec82/Farpoint farpoint-pc-vr-crash-reporting-20261008

Farpoint PC VR - Crash Reporting and Time-Query Guard

on GitHub

Farpoint PC VR for Windows, with OpenXR support for SteamVR and Virtual Desktop.

Crash reporting and defensive fix

• Rejects impossible time-query output addresses instead of writing through them. This addresses the specific invalid write found in a submitted crash log; it does not repair the underlying corrupt pointer or prevent every crash.
• Expands fatal crash reports with the remaining CPU registers and temporary stack storage needed to investigate recurring render-thread failures.
• Includes the previous callback-lifetime, nested callback execution and segmented GPU readback fixes.
• Enhanced reports run only on a fatal error. No per-frame image, shader or geometry captures are enabled.

Recurring render-thread and GPU callback crashes remain under investigation. Stretched geometry and texture artifacts are also unresolved. This prerelease is intended to help collect useful reports, not to claim those problems are fixed.

First-time installation

1. Download Farpoint-PC-VR-First-Install.zip and extract it into a writable folder, such as D:\Farpoint.
2. Place your own Farpoint CUSA04508 version 1.00 package next to Play Farpoint.bat, named Farpoint.pkg. Put it in the extracted root folder, not inside pc-vr.
3. Connect your headset and select its OpenXR runtime.
4. Open Play Farpoint.bat, select your settings and start the game. Initial setup extracts the package, validates metadata and generates resolution profiles. Keep the console open during setup.

The ZIP contains the emulator, graphical launcher, setup scripts, default configuration, extraction tools, documentation and licenses. No game files, saves or personal configuration are included. Compatible zero-passcode packages are supported; other executables/versions are not verified.

Requires 64-bit Windows, a Vulkan-capable GPU, an OpenXR headset/runtime and the Microsoft Visual C++ x64 runtime.

Help investigate crashes

After a crash, copy pc-vr/user/log/shad_log.txt before launching again. Open an issue and attach that saved log, along with:

• Release tag and BUILD.txt contents.
• Game title ID, version and region.
• GPU/driver, headset and OpenXR runtime.
• Resolution and frame-rate selections.
• Level, action immediately before the crash, whether it repeats, and any launcher exit code.

Review logs for local paths and machine details before posting publicly. Do not upload game files or memory dumps. See CRASH-REPORTING.md in the ZIP for details. No special scene or headset positioning is required.

Validation: Windows build and targeted time-query tests passed, including the reported invalid address, normal/null outputs, range overflow and avoiding partial output changes on a rejected address. Gameplay stability has not yet been established. The ZIP was checked for integrity and completeness; BUILD.txt records the exact executable hash and source revision.