search

UE4SS-RE / RE-UE4SS

Injectable LUA scripting system, SDK generator, live property editor and other dumping utilities for UE4/5 games
http://docs.ue4ss.com/
MIT License
1.28k stars 166 forks source link

[BUG - Release] Game (Nightingale) crashes on startup #403

Open noooooooooooooooooooooa opened 7 months ago

noooooooooooooooooooooa commented 7 months ago

Branch or Release 3.0.1

Game and Engine Version Nightingale - 5.3.2

Describe the bug UE4SS is crashing on startup

Mods directory Only default mods

To Reproduce Steps to reproduce the behavior:

  1. Launch game
  2. Crash

Expected behavior UE4SS crash after starting game, it show a message telling that it saved the crash dump.

Screenshots and UE4SS Log UE4SS.log Crash Dump

Desktop (please complete the following information):

UE4SS commented 7 months ago

@localcc You mentioned here that the game exe shouldn't be required for debugging crash dumps but this doesn't seem to always be true, including with the crash dump supplied in this issue. Any idea why this might be the case ? It found UE4SS.dll and the symbols loaded successfully but as you can see in the screenshot, the callstack isn't visible.

2024-02-21_08-42_crashdmp_missing_frames

localcc commented 7 months ago

As far as I know the exe shouldn't be required, the crash here could've occurred inside of the game binary and ue4ss was possibly not in the callstack when it occurred

mikey-wotton commented 7 months ago

Getting the same issue, same specs. Error message in a dmp file if that helps.

Capture
mikey-wotton commented 7 months ago

I tried bypassing UE4SS and using UnrealMappingsDumper directly (which I understand UE4SS uses under the hood). It seems to succeed but only outputs an empty .usmap file. I suspect UE4SS might be expecting some output from UnrealMappingsDumper but is instead receiving a garbled .usmap?

Egaliterrier commented 7 months ago

Experiencing the same issue. Maybe there could be some clues to the issue in these working dumps: https://github.com/zanzo420/Nightingale-SDK Also, just to note, the game actually continues to work as normal after the crash message pops up during launch. The game only properly closes/crashes when you click ok on the crash popup, at least on my end.

Egaliterrier commented 6 months ago

Anything I can provide to help shed light on this issue? Full memory dump, game executable?

Egaliterrier commented 3 weeks ago

Same issue with the new Nightingale update, using UE4SS experimental 3.0.1-173. Can't figure out why this happens, regardless of settings used. Would love a second, perhaps wiser, pair of eyes to take a look. I've tried disabling all mods (including keybinds), all hooks, tried with and without every relevant, and probably irrelevant, setting - same crash, regardless.

Here's a link containing the game's .pdb/.exe, a ue4ss full memory crash dump, uecc crash dump (for which I had ue4ss' crash dumps disabled), game log, ue4ss log, dumper7 sdk, aswell as the ue4ss settings used. https://drive.google.com/drive/folders/1k-FK-asIxCc3UG0KldxXBBmAGakN4RQ5?usp=sharing

EDIT: At launch, players protested the game’s online-only requirement as the gameplay was solo-focused and interacting with anyone else was never required. So they released a major patch featuring a separate offline mode, which is what I’ve been attempting to mod/troubleshoot for weeks - just to preface in case someone thinks modding this could be against the rules. It isn’t, at least not anymore. I thought maybe some tamper protection was left enabled for the offline mode, but it loads iostore container mods just fine, and injecting a console unlock made using the dumper-7 sdk also works. It seems like the crashing might not be caused by integrity checking or something EOS/EAS/EAC-related. Though it is possible, I guess.. So, unless UE4SS is not completely compatible with 5.3.2, or the game has significant engine changes, this despite offset scans being successful, I am at a loss at this point.