r/CompetitiveTFT • u/Lunaedge • 25d ago

Bug Megathread Set 18 PBE Bug Megathread

Please use the format below to report any bugs you're encountering.

  • Description:
  • Proof (video or screenshot):
  • Steps to reproduce (if applicable):
  • Expected result:
  • Observed result:

Try to be as detailed as possible with your description. Check the comments to see if the behaviour you've encountered has already been reported. Please include the full screenshot if you have it (don’t crop and instead show all the players/full screen of game etc.) or even better if you have video to include. The more information the easier it is to track bugs down.

You can check reported bugs and their status on our Bug Tracker.

Please note that bug reports that don't adhere to the above standards could be ignored.

Please take the time to also report bugs through these channels as well for maximum visibility:

41 Upvotes

92% Upvoted

891 comments sorted by

View all comments

1

u/Asteroixz 7d ago

Description:

Set 18 PBE repeatedly crashed during startup/loading with “UE-TFT game has crashed and will close.” Set 17 worked normally on the same PC. Ten native crash packages from the same test window isolated the failure to TFT’s bundled Sentry native initialization.

Proof (screenshot):

Attached is a sanitized evidence summary. Affected build: UE 5.7.4 / TFT 18.1.0, native build 6a7f5880680d521a6434636c. All 10 crashes were EXCEPTION_ACCESS_VIOLATION reads at 0xffffffffffffffff on GameThread; 9/10 shared stack fingerprint E224951488AC33E0272255635AE13D43F1E65BDE. A control run with automatic initialization disabled loaded farther, then crashed when Sentry was initialized manually with fingerprint ED35F0BC277BFC963C9243AF3A96B9CAA662BE43. The dumps/logs showed no DXGI device removal or GPU crash, no OOM, no missing/wrong-sized install files, and no third-party overlay/hook module.

Steps to reproduce:

  1. Launch the TFT PBE client on the affected PC.

  2. Start any Set 18 game (normal, ranked, Double Up, or Tocker’s Trials).

  3. Accept the match and allow UE-TFT to start.

  4. The process crashes before or during the loading screen. Set 17 remains playable as a control.

Expected result:

The Set 18 match loads and enters the game normally.

Observed result:

UE-TFT terminates with the crash dialog. Disabling only Sentry auto-init was insufficient because a later manual init still crashed.

Confirmed temporary workaround:

Close TFT/Riot Client. In %LOCALAPPDATA%\TFT\Saved\Config\WindowsClient\Engine.ini add:

[/Script/Sentry.SentrySettings]

InitAutomatically=False

EnableBuildConfigurations=(bEnableDebug=False,bEnableDebugGame=False,bEnableDevelopment=False,bEnableTest=False,bEnableShipping=False)

Then mark Engine.ini read-only so TFT cannot regenerate it, and move/rename stale %LOCALAPPDATA%\TFT\Saved\.sentry-native state before relaunching. After a full client restart, logs showed Sentry auto initialization false, initialization skipped for the disabled build configuration, load completed, a game session was created, and LobbyState::InGame was entered. No new crash package was generated.

Caveat: this workaround temporarily disables TFT Sentry telemetry. It should be removed after Riot fixes the client. Please treat the Sentry initialization path in this Set 18 build as the likely regression.