Commit Graph
3 Commits
Author SHA1 Message Date
spoopyghosty0 f0eb7850fb Lint: wrap lines over 120 characters and sort an import (from the merged fix branches) 2026-10-17 02:43:52 -04:00
spoopyghosty0 277dd99645 Cpp2IL crashes aren't "code not found"; triage orders replayed logcat lines by date (#293)
- il2cpp._run: a non-zero exit or no .cs file under DiffableCs is an unreadable game. The release Cpp2IL dies on
  BattleTalent (Unity 2021.3.45f2, exit 134, IndexOutOfRangeException in CsFileUtils.GetTypeName) after making the
  folder tree; every class was recorded "missing" and cached.
- find_methods: any release failure gets one try with the development build (it reads BattleTalent), not only an
  unsupported metadata version; never with a caller's Cpp2IL or FRAMEPORT_CPP2IL. Errors are cached as errors,
  never as missing classes; cache entries with no class found and every wanted class missing are run again.
- Il2cppReturnPatch: Cpp2IL failures become the same WARN check as "code not found" but with Cpp2IL's error line;
  the method list in the WARN has no duplicates.
- triage: logcat times include the date (logcat replays kernel lines dated days earlier ahead of the game's; by time
  of day the "past midnight" guess gave a healthy run frames-stopped 83261 s). Year wrap handled.
2026-10-17 01:52:47 -04:00
spoopyghosty0 b8d5b3badc Cpp2IL: Unity 6.5 games use the development build (metadata v107)
No Cpp2IL release reads Unity 6.5's metadata yet ("We support 23-106, got 107"), so the text-field and MSAA
fixes were skipped for Wander 0.3570 (#198). When the release reports an unsupported metadata version, the
development branch's CI build (nightly.link, as Cpp2IL's README links it) is fetched into tools/cpp2il-nightly/
and used; cached errors of that kind get one retry with it. Checked with Wander 0.3570: it reads the v107
metadata and writes TMP_InputField, OVRDisplay and OculusLoader.
2026-10-12 18:07:00 -04:00