Skip to content

1.1.0-rc3

Pre-release
Pre-release

Choose a tag to compare

@Str8UpWHITE64 Str8UpWHITE64 released this 19 Jun 16:52
· 15 commits to master since this release

Librarian-AP v1.1.0-rc3

Third release candidate for 1.1.0. Drop-in install — see INSTALL.txt in the zip. Server host: use the
updated librarian.apworld.

New in rc3 — the crash fix

  • The intermittent native crash should be fixed. Every rc2 report pointed at the same root cause:
    the mod was updating book/bookcase state on a background thread, racing the game's renderer into a
    crash — especially right after a series/shelf unlock. rc3 funnels all of that work through a single,
    serialized, on-the-game-thread "pump," so it can no longer race the renderer. This is the headline
    fix we need you to validate
    — play through connects and series/shelf unlocks and tell us if it stays
    stable.

Carried over

  • The rc2 crash mitigation (proactive redraw sweep off) stays.
  • Row-completion fix, no level inflation on reload, and the large cleanup from rc1/rc2.

Known issues

  • "Invisible when held" book (rare, random). Workaround: throw it out of bounds (it comes back
    visible), or reload. It's below the mod's reach — see known_bugs.txt.
  • Return-to-menu freeze (rare). rc3 prevents the crash there, but a heavy warding pass right before
    going to the menu can still cause a multi-minute freeze on the Menu→Continue path. Separate follow-up.

If you crash or freeze — PLEASE send logs (this is the whole point of rc3)

Send the crash-report folder, especially:

  • Mods/Librarian-AP/crash_trace.log — the breadcrumb ledger; its last lines name what we were doing
  • …/Binaries/Win64/UE4SS.log — the last ~200 lines
  • one line on what you were doing (connecting, a series unlock, returning to menu, …)

Please confirm your title screen shows v1.1.0-rc3 first — older builds don't help. Optional A/B if
you do crash: set BOOK_ACTOR_GAMETHREAD=false (or CASE_WARD_GAMETHREAD=false) in
Scripts/diag_flags.lua to route that layer back to the old off-thread path, and report whether it returns.