Farpoint PC VR v0.7.5 - Haptics and Gamma Fixes

Farpoint PC VR v0.7.5

This experimental PC VR release uses shadPS4 baseline 06e813ff8c8e2a6d81b02cabfcc9543c3debf78e with the Farpoint OpenXR port.

Changes in v0.7.5

• Restores controller haptics by forwarding game vibration requests to OpenXR. Haptics were confirmed working in local headset testing.
• Changes tone-mapper gamma from 2.0 to 1.2. Live comparisons confirmed that this control affects headset brightness, and 1.2 was preferred in the tested scene. Existing v0.7.0 profiles regenerate the gamma override on first launch.
• Corrects the save-transfer instructions below.

Retained from v0.7.0

• Raises the game graphics-memory pool to 3,072 MiB. Diagnostics found fragmentation preventing a 4 MiB allocation in the previous 2,400 MiB pool. A local session exceeded the old budget without that crash; this is a mitigation, not a guarantee of stability.
• Limits single-pixel GPU readbacks to the actual pixel rather than copying unwritten row padding into guest memory. Green textures and overly bright lighting remain under investigation; this fix needs further gameplay validation.
• Applies a tone-mapper gamma override of 1.2 to darken the image. This is a visual adjustment, not a correction for every lighting artifact.
• Left thumbstick click toggles 3x movement speed; click again for normal speed. Both stick clicks still recenter and clear the toggle. Controller/focus loss also clears it.
• Adjusts the right-hand Aim pose downward by 20 degrees and forward by approximately 7 inches.
• Allows headset rendering to proceed when a desktop mirror frame is unavailable, reduces presentation-log noise, and retains full-refresh pacing. Performance improvement is not guaranteed.
• Adds direct fault-context files and a bounded history of the latest 4,096 memory-allocation events for supported crash paths, plus GPU-wait timing summaries. Texture-source capture is disabled by the launcher. The developer's external Python pool monitor is not included or required.
• Retains stack protection, spatial-audio corrections, Virtual Desktop compatibility, SteamVR/OpenXR support, and resolution choices through 3072 x 3456 per eye.

Game-specific configuration and sprint overrides are generated locally from the supported game during first setup. The ZIP contains no game assets, generated game profiles, saves, personal logs, or diagnostic captures.

First-time installation

1. Download Farpoint-PC-VR-v0.7.5-First-Install.zip and extract it to a new writable folder.
2. Put your own Farpoint CUSA04508 version 1.00 package in that root folder, beside Play Farpoint.bat, and name it Farpoint.pkg. Do not put it inside pc-vr.
3. Connect your headset using your OpenXR runtime, such as SteamVR or Virtual Desktop VDXR.
4. Open Play Farpoint.bat, choose your settings and start. First launch extracts the compatible zero-passcode package, restores metadata and generates resolution profiles. Keep the console open until setup finishes.

You may instead browse to the supported eboot.bin in a complete extracted game. The executable SHA-256 must be 92A21FF9E309CE5DD58B058C4B12329463697BB27FDA98B5DA353E0A73BD9C0F. Other game versions are not verified.

Requires 64-bit Windows, a Vulkan-capable GPU, an OpenXR headset/runtime and the Microsoft Visual C++ x64 runtime. The ZIP includes the emulator, launcher, extraction/setup tools, configuration and licenses. No game files, generated game profiles, saves or personal logs are included.

Controls

Right A/B: Cross/Square; left X/Y: Circle/Triangle. Left stick moves; right stick turns. Triggers: L2/R2; grips: L1/R1; left menu: Options. Left stick click toggles 3x sprint. Both stick clicks recenter. The right controller supplies the Aim pose. Complete the game's calibration.

Existing installations

Close the game and extract to a new folder. Select your existing complete extracted game's eboot.bin in the launcher, or supply Farpoint.pkg as described above. To retain progress, copy your existing pc-vr/user/home/1000/savedata/CUSA04508 folder into the new pc-vr/user/home/1000/savedata folder before starting. Setup regenerates the sprint and memory/gamma overrides beside that game's original pak files. Back up any custom overrides before using the same game directory.

Report a crash

After a crash, right-click pc-vr/collect-crash-report.ps1 and choose Run with PowerShell. Attach the resulting ZIP under pc-vr/reports to an issue at https://github.com/evertec82/Farpoint/issues. Include the level/action, headset/runtime, GPU/driver and chosen resolution. Review reports before sharing; logs can contain local paths. Some abnormal exits still do not produce a fault-context file.

Validation and known issues

The emulator builds successfully. Launcher syntax, generated memory/gamma and sprint pack parity with the local candidates, and package integrity were checked. The haptics correction and gamma response were confirmed locally. The single-pixel readback change is not yet confirmed to eliminate the texture issues. Green/purple textures, excessive brightness, stretched geometry, performance limitations, and additional crashes may remain. This release remains a prerelease for testing and reports.

Source is on farpoint-upstream-preview; see BUILD.txt in the download for the exact source and executable identity and BUILD-FARPOINT.md in the repository for build instructions.

Farpoint PC VR v0.7.0 - Memory, Rendering and Controls

Farpoint PC VR v0.7.0

This experimental PC VR release uses shadPS4 baseline 06e813ff8c8e2a6d81b02cabfcc9543c3debf78e with the Farpoint OpenXR port.

Changes

• Raises the game graphics-memory pool to 3,072 MiB. Diagnostics found fragmentation preventing a 4 MiB allocation in the previous 2,400 MiB pool. A local session exceeded the old budget without that crash; this is a mitigation, not a guarantee of stability.
• Limits single-pixel GPU readbacks to the actual pixel rather than copying unwritten row padding into guest memory. Green textures and overly bright lighting remain under investigation; this fix needs further gameplay validation.
• Applies a tone-mapper gamma override of 2.0 to darken the image. This is a visual adjustment, not a correction for every lighting artifact.
• Left thumbstick click toggles 3x movement speed; click again for normal speed. Both stick clicks still recenter and clear the toggle. Controller/focus loss also clears it.
• Adjusts the right-hand Aim pose downward by 20 degrees and forward by approximately 7 inches.
• Allows headset rendering to proceed when a desktop mirror frame is unavailable, reduces presentation-log noise, and retains full-refresh pacing. Performance improvement is not guaranteed.
• Adds direct fault-context files and a bounded history of the latest 4,096 memory-allocation events for supported crash paths, plus GPU-wait timing summaries. Texture-source capture is disabled by the launcher. The developer's external Python pool monitor is not included or required.
• Retains stack protection, spatial-audio corrections, Virtual Desktop compatibility, SteamVR/OpenXR support, and resolution choices through 3072 x 3456 per eye.

Game-specific configuration and sprint overrides are generated locally from the supported game during first setup. The ZIP contains no game assets, generated game profiles, saves, personal logs, or diagnostic captures.

First-time installation

1. Download Farpoint-PC-VR-v0.7.0-First-Install.zip and extract it to a new writable folder.
2. Put your own Farpoint CUSA04508 version 1.00 package in that root folder, beside Play Farpoint.bat, and name it Farpoint.pkg. Do not put it inside pc-vr.
3. Connect your headset using your OpenXR runtime, such as SteamVR or Virtual Desktop VDXR.
4. Open Play Farpoint.bat, choose your settings and start. First launch extracts the compatible zero-passcode package, restores metadata and generates resolution profiles. Keep the console open until setup finishes.

You may instead browse to the supported eboot.bin in a complete extracted game. The executable SHA-256 must be 92A21FF9E309CE5DD58B058C4B12329463697BB27FDA98B5DA353E0A73BD9C0F. Other game versions are not verified.

Requires 64-bit Windows, a Vulkan-capable GPU, an OpenXR headset/runtime and the Microsoft Visual C++ x64 runtime. The ZIP includes the emulator, launcher, extraction/setup tools, configuration and licenses. No game files, generated game profiles, saves or personal logs are included.

Controls

Right A/B: Cross/Square; left X/Y: Circle/Triangle. Left stick moves; right stick turns. Triggers: L2/R2; grips: L1/R1; left menu: Options. Left stick click toggles 3x sprint. Both stick clicks recenter. The right controller supplies the Aim pose. Complete the game's calibration.

Existing installations

Close the game and extract to a new folder. Select your existing complete extracted game's eboot.bin in the launcher, or supply Farpoint.pkg as described above. To retain progress, copy your existing pc-vr/user/savedata folder into the new pc-vr/user folder before starting. Setup regenerates the sprint and memory/gamma overrides beside that game's original pak files. Back up any custom overrides before using the same game directory.

Report a crash

After a crash, right-click pc-vr/collect-crash-report.ps1 and choose Run with PowerShell. Attach the resulting ZIP under pc-vr/reports to an issue at https://github.com/evertec82/Farpoint/issues. Include the level/action, headset/runtime, GPU/driver and chosen resolution. Review reports before sharing; logs can contain local paths. Some abnormal exits still do not produce a fault-context file.

Validation and known issues

The emulator builds successfully. Launcher syntax, generated memory/gamma and sprint pack parity with the local candidates, and package integrity were checked. The latest gamma and single-pixel readback changes have not yet been confirmed in headset gameplay. Green/purple textures, excessive brightness, stretched geometry, performance limitations, and additional crashes may remain. This release remains a prerelease for testing and reports.

Source is on farpoint-upstream-preview; see BUILD.txt in the download for the exact source and executable identity and BUILD-FARPOINT.md in the repository for build instructions.

Farpoint PC VR v0.6.5 - Enable Stack Protection

Farpoint PC VR v0.6.5 - Enable Stack Protection

Fixes a launcher configuration gap: existing profiles could leave General.redzone_patches disabled even though the emulator includes the stack-protection changes. The launcher now enables it before starting Farpoint, including when the setting is missing. A submitted v0.6.0 crash report reproduced the original render-thread failure with this setting disabled.

The emulator executable is unchanged from the v0.6.0 full-refresh package. This release retains its full-refresh pacing and Network-settings corrections. It does not include the local experimental gun offsets, mirror changes or additional timing diagnostics.

Existing v0.6.0 users: Close Farpoint and replace pc-vr/launch-farpoint.ps1 with the copy in this ZIP. Keep your saves and settings. Launch through Play Farpoint.bat so the correction is applied.

Validation: Launcher syntax and migration of missing, disabled and enabled settings passed. Package integrity and the unchanged executable hash were verified. Gameplay crash prevention still needs confirmation; this is not a fix for every reported crash.

This experimental build uses shadPS4 baseline 06e813ff8c8e2a6d81b02cabfcc9543c3debf78e with the Farpoint OpenXR port. Install in a separate folder for comparison with the earlier build.

Retained changes from v0.6.0

• Replaces v0.5.0's overbroad frame-pointer protection with control-flow-aware stack offsets, so ordinary allocated locals do not consume protective patch space. The real-module startup check no longer exhausted patch space; unrelocatable instructions fell from 2,619,026 to 292 in that comparison.

• Restores the earlier spatial-audio implementation and corrects position, gain and reset attribute numbers in both audio backends. The previous mapping could interpret position data as volume.

• Adds sparse audio-mix signal diagnostics, reduces repeated zero-length batch log noise, and enables fatal-level log flushing.

• Retains the Virtual Desktop exception fix, expanded crash reports, launcher and resolution options.

Gameplay verification is still pending. Compilation, a production-analysis probe on the complete crashing routine, and an isolated startup check passed. The audio trace confirms gain values are interpreted correctly, but audible gameplay and the original crash scene have not been verified. Remaining unrelocatable instructions, rendering artifacts and crashes are still under investigation.

Included

• OpenXR headset rendering, tracked Aim controls and the resolution launcher, through 3072 x 3456 per eye.

• Virtual Desktop exception fix: normal first-chance C++ exceptions can reach their native handlers instead of prematurely shutting down the emulator.

• Defensive validation of invalid time-query output addresses.

• Expanded fatal crash reports: CPU registers, stack/red-zone contents, code bytes, memory mappings, frame-chain candidates and host-module backtraces.

• Per-session executable hashes, automatic preservation of the previous log, and a crash-report ZIP collector.

• Guest red-zone protection and the newer renderer's precise readback configuration enabled for this comparison.

First-time installation

1. Download Farpoint-PC-VR-v0.6.5-First-Install.zip and extract it to a new writable folder.

2. Put your own Farpoint CUSA04508 version 1.00 package in that root folder, beside Play Farpoint.bat, and name it Farpoint.pkg. Do not put it inside pc-vr.

3. Connect your headset using your OpenXR runtime, such as SteamVR or Virtual Desktop VDXR.

4. Open Play Farpoint.bat, choose your settings and start. First launch extracts the compatible zero-passcode package, restores metadata and generates resolution profiles. Keep the console open until setup finishes.

You may instead browse to the supported eboot.bin in a complete extracted game. The executable SHA-256 must be 92A21FF9E309CE5DD58B058C4B12329463697BB27FDA98B5DA353E0A73BD9C0F. Other game versions are not verified.

Requires 64-bit Windows, a Vulkan-capable GPU, an OpenXR headset/runtime and the Microsoft Visual C++ x64 runtime. The ZIP includes the emulator, launcher, extraction/setup tools, configuration and licenses. No game files, generated game profiles, saves or personal logs are included.

Controls

Right A/B: Cross/Square; left X/Y: Circle/Triangle. Left stick moves; right stick turns. Triggers: L2/R2; grips: L1/R1; left menu: Options. Both stick clicks recenter. The right controller supplies the Aim pose. Complete the game's calibration.

Report a crash

After a crash, right-click pc-vr/collect-crash-report.ps1 and select Run with PowerShell. Attach the ZIP created under pc-vr/reports to an issue. Include the level/action, headset/runtime, GPU/driver and whether the older build also crashes. Review the report before sharing because logs/settings can contain local paths. No continuous image capture or hardware watchpoints are enabled.

Testing limitations

Both compilation and executable/launcher smoke checks passed. Headset gameplay, campaign stability and rendering correctness have not been established for this new baseline. Its renderer/readback implementation differs from the earlier port; not all old title-specific rendering workarounds were carried over, so lighting or geometry may regress. Existing stretched geometry, texture artifacts and render-thread crashes are not claimed fixed. This prerelease is for comparison and collecting actionable crash reports.

The source for this candidate is on the farpoint-upstream-preview branch. See BUILD.txt for the exact source and executable identity, and BUILD-FARPOINT.md in the source for build instructions.

Version history

• v0.1.0: First-time installation / metadata fix.

• v0.2.0: Stability improvements.

• v0.3.0: Crash reporting and time-query guard.

• v0.4.0: Newer shadPS4 comparison, Virtual Desktop fix and expanded diagnostics.

• v0.5.0: Frame-pointer stack protection and single-attribute audio submission candidate fixes.

• v0.6.0: Narrower stack protection, restored spatial audio and corrected audio attribute mapping.

• v0.6.5: Enable stack protection for existing profiles at launch.

Release source: commit bcacf8a7.

Farpoint PC VR v0.6.0 - Revised Stack Protection and Spatial Audio

Farpoint PC VR v0.6.0 - Revised Stack Protection and Spatial Audio

Full-refresh correction (version remains v0.6.0): Restores the launcher's VR pacing setting, which the newer emulator port had ignored. This removes the unintended half-refresh pacing limit. The runtime/compositor may still reproject when rendering cannot meet the headset's refresh rate. Compilation and package checks passed; headset frame-rate verification is pending. Source: commit 3c355798.

Launcher correction included: Supports the newer Network settings section and older profiles, fixing the connected_to_network property error. Existing v0.6.0 installations need both pc-vr/shadps4.exe and pc-vr/launch-farpoint.ps1 from this ZIP. Close the emulator before replacing them and keep your existing saves and settings.

This experimental build uses shadPS4 baseline 06e813ff8c8e2a6d81b02cabfcc9543c3debf78e with the Farpoint OpenXR port. Install in a separate folder for comparison with the earlier build.

Changes in v0.6.0

• Replaces v0.5.0's overbroad frame-pointer protection with control-flow-aware stack offsets, so ordinary allocated locals do not consume protective patch space. The real-module startup check no longer exhausted patch space; unrelocatable instructions fell from 2,619,026 to 292 in that comparison.

• Restores the earlier spatial-audio implementation and corrects position, gain and reset attribute numbers in both audio backends. The previous mapping could interpret position data as volume.

• Adds sparse audio-mix signal diagnostics, reduces repeated zero-length batch log noise, and enables fatal-level log flushing.

• Retains the Virtual Desktop exception fix, expanded crash reports, launcher and resolution options.

Gameplay verification is still pending. Compilation, a production-analysis probe on the complete crashing routine, and an isolated startup check passed. The audio trace confirms gain values are interpreted correctly, but audible gameplay and the original crash scene have not been verified. Remaining unrelocatable instructions, rendering artifacts and crashes are still under investigation.

Included

• OpenXR headset rendering, tracked Aim controls and the resolution launcher, through 3072 x 3456 per eye.

• Virtual Desktop exception fix: normal first-chance C++ exceptions can reach their native handlers instead of prematurely shutting down the emulator.

• Defensive validation of invalid time-query output addresses.

• Expanded fatal crash reports: CPU registers, stack/red-zone contents, code bytes, memory mappings, frame-chain candidates and host-module backtraces.

• Per-session executable hashes, automatic preservation of the previous log, and a crash-report ZIP collector.

• Guest red-zone protection and the newer renderer's precise readback configuration enabled for this comparison.

First-time installation

1. Download Farpoint-PC-VR-v0.6.0-First-Install.zip and extract it to a new writable folder.

2. Put your own Farpoint CUSA04508 version 1.00 package in that root folder, beside Play Farpoint.bat, and name it Farpoint.pkg. Do not put it inside pc-vr.

3. Connect your headset using your OpenXR runtime, such as SteamVR or Virtual Desktop VDXR.

4. Open Play Farpoint.bat, choose your settings and start. First launch extracts the compatible zero-passcode package, restores metadata and generates resolution profiles. Keep the console open until setup finishes.

You may instead browse to the supported eboot.bin in a complete extracted game. The executable SHA-256 must be 92A21FF9E309CE5DD58B058C4B12329463697BB27FDA98B5DA353E0A73BD9C0F. Other game versions are not verified.

Requires 64-bit Windows, a Vulkan-capable GPU, an OpenXR headset/runtime and the Microsoft Visual C++ x64 runtime. The ZIP includes the emulator, launcher, extraction/setup tools, configuration and licenses. No game files, generated game profiles, saves or personal logs are included.

Controls

Right A/B: Cross/Square; left X/Y: Circle/Triangle. Left stick moves; right stick turns. Triggers: L2/R2; grips: L1/R1; left menu: Options. Both stick clicks recenter. The right controller supplies the Aim pose. Complete the game's calibration.

Report a crash

After a crash, right-click pc-vr/collect-crash-report.ps1 and select Run with PowerShell. Attach the ZIP created under pc-vr/reports to an issue. Include the level/action, headset/runtime, GPU/driver and whether the older build also crashes. Review the report before sharing because logs/settings can contain local paths. No continuous image capture or hardware watchpoints are enabled.

Testing limitations

Both compilation and executable/launcher smoke checks passed. Headset gameplay, campaign stability and rendering correctness have not been established for this new baseline. Its renderer/readback implementation differs from the earlier port; not all old title-specific rendering workarounds were carried over, so lighting or geometry may regress. Existing stretched geometry, texture artifacts and render-thread crashes are not claimed fixed. This prerelease is for comparison and collecting actionable crash reports.

The source for this candidate is on the farpoint-upstream-preview branch. See BUILD.txt for the exact source and executable identity, and BUILD-FARPOINT.md in the source for build instructions.

Version history

• v0.1.0: First-time installation / metadata fix.

• v0.2.0: Stability improvements.

• v0.3.0: Crash reporting and time-query guard.

• v0.4.0: Newer shadPS4 comparison, Virtual Desktop fix and expanded diagnostics.

• v0.5.0: Frame-pointer stack protection and single-attribute audio submission candidate fixes.

• v0.6.0: Narrower stack protection, restored spatial audio and corrected audio attribute mapping.

The launcher and full-refresh corrections retain v0.6.0 and its existing release URL.

Farpoint PC VR v0.5.0 - Stack Protection and Audio

Farpoint PC VR v0.5.0 - Stack Protection and Audio Prerelease

This experimental build uses shadPS4 baseline 06e813ff8c8e2a6d81b02cabfcc9543c3debf78e with the Farpoint OpenXR port. Install in a separate folder for comparison with the earlier build.

Changes in v0.5.0

• Extends Windows guest stack protection to temporary data addressed through the frame pointer. This addresses a coverage gap affecting the stack slot seen corrupted in repeated render-thread crashes.
• Queues audio samples submitted through the single-attribute 3D-audio API, matching the batch API. Previously that path stored the descriptor without submitting the samples for playback.
• Adds pointer/count details to invalid audio-batch reports.
• Retains the Virtual Desktop exception fix, expanded crash reporting, launcher and resolution options from v0.4.0.

These are candidate fixes, not confirmed gameplay fixes. The Windows build, executable smoke check and focused production-decoder probe passed. Replaying the failing scene and verifying audio are still required. Broader stack protection may increase startup time and runtime overhead, and some instructions remain unrelocatable. Existing rendering issues remain under investigation.

Included

• OpenXR headset rendering, tracked Aim controls and the resolution launcher, through 3072 × 3456 per eye.
• Virtual Desktop exception fix: normal first-chance C++ exceptions can reach their native handlers instead of prematurely shutting down the emulator.
• Defensive validation of invalid time-query output addresses.
• Expanded fatal crash reports: CPU registers, stack/red-zone contents, code bytes, memory mappings, frame-chain candidates and host-module backtraces.
• Per-session executable hashes, automatic preservation of the previous log, and a crash-report ZIP collector.
• Guest red-zone protection and the newer renderer's precise readback configuration enabled for this comparison.

First-time installation

1. Download Farpoint-PC-VR-v0.5.0-First-Install.zip and extract it to a new writable folder.
2. Put your own Farpoint CUSA04508 version 1.00 package in that root folder, beside Play Farpoint.bat, and name it Farpoint.pkg. Do not put it inside pc-vr.
3. Connect your headset using your OpenXR runtime, such as SteamVR or Virtual Desktop VDXR.
4. Open Play Farpoint.bat, choose your settings and start. First launch extracts the compatible zero-passcode package, restores metadata and generates resolution profiles. Keep the console open until setup finishes.

You may instead browse to the supported eboot.bin in a complete extracted game. The executable SHA-256 must be 92A21FF9E309CE5DD58B058C4B12329463697BB27FDA98B5DA353E0A73BD9C0F. Other game versions are not verified.

Requires 64-bit Windows, a Vulkan-capable GPU, an OpenXR headset/runtime and the Microsoft Visual C++ x64 runtime. The ZIP includes the emulator, launcher, extraction/setup tools, configuration and licenses. No game files, generated game profiles, saves or personal logs are included.

Controls

Right A/B: Cross/Square; left X/Y: Circle/Triangle. Left stick moves; right stick turns. Triggers: L2/R2; grips: L1/R1; left menu: Options. Both stick clicks recenter. The right controller supplies the Aim pose. Complete the game's calibration.

Report a crash

After a crash, right-click pc-vr/collect-crash-report.ps1 and select Run with PowerShell. Attach the ZIP created under pc-vr/reports to an issue. Include the level/action, headset/runtime, GPU/driver and whether the older build also crashes. Review the report before sharing because logs/settings can contain local paths. No continuous image capture or hardware watchpoints are enabled.

Testing limitations

Both compilation and executable/launcher smoke checks passed. Headset gameplay, campaign stability and rendering correctness have not been established for this new baseline. Its renderer/readback implementation differs from the earlier port; not all old title-specific rendering workarounds were carried over, so lighting or geometry may regress. Existing stretched geometry, texture artifacts and render-thread crashes are not claimed fixed. This prerelease is for comparison and collecting actionable crash reports.

The source for this candidate is on the farpoint-upstream-preview branch. See BUILD.txt for the exact source and executable identity, and BUILD-FARPOINT.md in the source for build instructions.

Version history

• v0.1.0: First-time installation / metadata fix.
• v0.2.0: Stability improvements.
• v0.3.0: Crash reporting and time-query guard.
• v0.4.0: Newer shadPS4 comparison, Virtual Desktop fix and expanded diagnostics.
• v0.5.0: Frame-pointer stack protection and single-attribute audio submission candidate fixes.

Versions increase with each published revision. Existing release URLs are retained.

Farpoint PC VR v0.4.0 - Newer shadPS4 and Crash Diagnostics

Farpoint PC VR v0.4.0 — Newer shadPS4 Comparison Prerelease

This experimental build uses shadPS4 baseline 06e813ff8c8e2a6d81b02cabfcc9543c3debf78e with the Farpoint OpenXR port. Install in a separate folder for comparison with the earlier build.

Included

• OpenXR headset rendering, tracked Aim controls and the resolution launcher, through 3072 × 3456 per eye.
• Virtual Desktop exception fix: normal first-chance C++ exceptions can reach their native handlers instead of prematurely shutting down the emulator.
• Defensive validation of invalid time-query output addresses.
• Expanded fatal crash reports: CPU registers, stack/red-zone contents, code bytes, memory mappings, frame-chain candidates and host-module backtraces.
• Per-session executable hashes, automatic preservation of the previous log, and a crash-report ZIP collector.
• Guest red-zone protection and the newer renderer's precise readback configuration enabled for this comparison.

First-time installation

1. Download Farpoint-PC-VR-v0.4.0-First-Install.zip and extract it to a new writable folder.
2. Put your own Farpoint CUSA04508 version 1.00 package in that root folder, beside Play Farpoint.bat, and name it Farpoint.pkg. Do not put it inside pc-vr.
3. Connect your headset using your OpenXR runtime, such as SteamVR or Virtual Desktop VDXR.
4. Open Play Farpoint.bat, choose your settings and start. First launch extracts the compatible zero-passcode package, restores metadata and generates resolution profiles. Keep the console open until setup finishes.

You may instead browse to the supported eboot.bin in a complete extracted game. The executable SHA-256 must be 92A21FF9E309CE5DD58B058C4B12329463697BB27FDA98B5DA353E0A73BD9C0F. Other game versions are not verified.

Requires 64-bit Windows, a Vulkan-capable GPU, an OpenXR headset/runtime and the Microsoft Visual C++ x64 runtime. The ZIP includes the emulator, launcher, extraction/setup tools, configuration and licenses. No game files, generated game profiles, saves or personal logs are included.

Controls

Right A/B: Cross/Square; left X/Y: Circle/Triangle. Left stick moves; right stick turns. Triggers: L2/R2; grips: L1/R1; left menu: Options. Both stick clicks recenter. The right controller supplies the Aim pose. Complete the game's calibration.

Report a crash

After a crash, right-click pc-vr/collect-crash-report.ps1 and select Run with PowerShell. Attach the ZIP created under pc-vr/reports to an issue. Include the level/action, headset/runtime, GPU/driver and whether the older build also crashes. Review the report before sharing because logs/settings can contain local paths. No continuous image capture or hardware watchpoints are enabled.

Testing limitations

Both compilation and executable/launcher smoke checks passed. Headset gameplay, campaign stability and rendering correctness have not been established for this new baseline. Its renderer/readback implementation differs from the earlier port; not all old title-specific rendering workarounds were carried over, so lighting or geometry may regress. Existing stretched geometry, texture artifacts and render-thread crashes are not claimed fixed. This prerelease is for comparison and collecting actionable crash reports.

The source for this candidate is on the farpoint-upstream-preview branch. See BUILD.txt for the exact source and executable identity, and BUILD-FARPOINT.md in the source for build instructions.

Version history

• v0.1.0: First-time installation / metadata fix.
• v0.2.0: Stability improvements.
• v0.3.0: Crash reporting and time-query guard.
• v0.4.0: Newer shadPS4 comparison, Virtual Desktop fix and expanded diagnostics.

Versions increase with each published revision. Existing release URLs are retained.

Farpoint PC VR v0.2.0 - Stability Improvements

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

Stability improvements

• Deferred GPU callbacks now own their captured data rather than retaining references to expired local objects.
• Nested GPU waits no longer execute the same queued callback twice.
• GPU readbacks now copy the correct source bytes across memory-segment boundaries.
• GPU capture triggers and live shader diagnostic controls are removed from this build. No diagnostic dumps or game files are included.

These correct reproducible bugs; they do not establish that all crashes are fixed. Intermittent crashes, stretched geometry and some texture artifacts remain under investigation. Full campaign compatibility is not yet verified.

First-time installation

1. Download Farpoint-PC-VR-First-Install.zip and extract it into a writable folder, such as D:\Farpoint.
2. Put your own Farpoint CUSA04508 version 1.00 package beside Play Farpoint.bat, named Farpoint.pkg (not inside pc-vr).
3. Connect your headset and select its OpenXR runtime.
4. Open Play Farpoint.bat, select your settings and click Start Farpoint. Initial setup extracts the package, validates metadata and creates the resolution profiles locally. Keep the console open during setup.

The ZIP includes the emulator, graphical launcher, setup scripts, default configuration, package extraction tools, documentation and licenses. All seven resolution profiles are generated from your game. 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.

For an existing installation, close the emulator and extract the ZIP over its program folder; retain your game and pc-vr/user folder. The package contains no user settings or saves to overwrite.

Validation: Windows build; callback ownership, nested queue execution, segmented memory-copy, compatibility and protected-page read tests passed. The old callback/segmented-copy implementations fail their targeted regression checks.

Farpoint PC VR v0.1.0 - First-Time Installation

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

First-time installation

1. Download Farpoint-PC-VR-First-Install.zip below and extract it into a writable folder, such as D:\Farpoint.
2. Put your own Farpoint CUSA04508 version 1.00 game package in that folder, rename it Farpoint.pkg, and place it beside Play Farpoint.bat, not inside pc-vr.
3. Connect your headset and select its OpenXR runtime.
4. Open Play Farpoint.bat, choose your settings, leave the default game path selected, and click Start Farpoint. The first launch extracts the package and creates the settings and resolution profiles automatically. Keep the console open while it works.

D:\Farpoint\
  Farpoint.pkg       <-- place your game here
  Play Farpoint.bat  <-- open this
  pc-vr\

Already extracted your game? Place the complete game folder at games/CUSA04508/files/uroot/, with eboot.bin inside it, or use Browse to select your extracted executable elsewhere. The full game content is required, not only the executable.

Included

The ZIP contains the Windows emulator, graphical launcher, first-launch setup, default configuration, package extraction tools, documentation and licenses. All seven resolution profiles are generated locally from your game; no additional profile download is needed. Game files are not included.

Requires 64-bit Windows, a Vulkan-capable GPU, an OpenXR runtime/headset and the Microsoft Visual C++ x64 runtime. Package extraction supports compatible zero-passcode packages. Other game regions or versions are not supported.

Features

• Corrected OpenXR stereo presentation and SteamVR support.
• VR controller and experimental tracked Aim support, plus gamepad mode.
• Lighting, reflection-texture and campaign-loading fixes.
• Full-refresh game pacing, with desktop mirror limits controlled separately.
• Seven resolutions from 960 � 1080 through 3072 � 3456 per eye, with additional guest memory for higher resolutions.
• Buffer-cache and readback stability improvements under evaluation.

This is a development release. Rainbow textures on distant objects, stretched geometry and intermittent crashes remain under investigation. Full campaign compatibility is not yet verified.

Startup metadata repair

Setup now extracts and validates sce_sys/param.sfo and associated package metadata, preventing the observed Failed to get TITLE_ID startup crash. For an installation missing this file, place the original Farpoint.pkg beside the launcher and run it again. Existing extracted game content does not need to be extracted again. The supported executable and CUSA04508 1.00 checks remain in place; this fix does not establish compatibility with other executables or editions.

Farpoint PC VR v0.3.0 - Crash Reporting and Time-Query Guard

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.