Repository navigation
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Game: Rustler - Grand Theft Horse (Epic), Rustler.exe and UnityCrashHandler64.exe. Thread: 1571482272253747222. Proton 9 ARM64EC with FEXCore 2603 and 2605 reproduces black startup. Latest report: 473 c000001d exceptions in UnityCrashHandler64.exe, first native frames libarm64ecfex.dll+0x171BFC, +0x17B31C, +0x17C520; guest frame UnityCrashHandler64.exe+0x5C5A0. Rustler loads UnityPlayer and later becomes idle. FEX stderr enabled: module logs in Rustler, no helper startup/assertion detail. Existing exception DFmt runs only with thread state and Logging::Init runs after LoadConfig, so repeating that capture cannot diagnose pre-logger failure. Diagnostic round 1 adds executable-scoped allocation-free bounded Wine stage output, temporary error/assert handlers after CRT through config loading, and native illegal-instruction PC plus FEX base before the thread-state guard. Normal logging and exception behavior remain unchanged. Preserve Proton 9 and ARM64EC; no game patch or graphics changes. Expected next evidence: FEX-STARTUP last completed stage and early assertion or native PC; compare helper and main-process progress independently. Diff check passed; compile/package validation through CI.