You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Screenshots, UE4SS Log, and .dmp file
If applicable, add screenshots to help explain your problem, and upload the log and .dmp files located in the Win64 directory.
Desktop (please complete the following information):
OS: Win10
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
Does your game crash if you uninstall the mods in your LogicMods folder?
Buckminsterfullerene02
changed the title
[BUG - Release] EXCEPTION_ACCESS_VIOLATION reading address 0x00000000000000a0
[BUG - Release] Crash on Palworld
Aug 23, 2024
nstalled this mod as well as dump and I didn't crash @Buckminsterfullerene02
For game crashes, is there a better solution to locate the source of the error, because if you don't generate a ue4ss DMP file or a game DMP file, it is difficult to determine whether some crashes are due to UE4SS or the game itself, as long as there is a crash, UE4SS will definitely enter the error stack, because it has been injected, causing users to mistakenly think that it is a UE4SS problem
Branch or Release
3.0.1
Game and Engine Version
Game where the bug occurred, and the UE engine version of the game.
v3.0.5
dx12
Describe the bug
A clear and concise description of what the bug is.
Mods directory
A zip of your Mods folder if you've installed any mods that don't come with UE4SS by default
E:\SteamLibrary\steamapps\common\Palworld\Pal\Content\Paks\LogicMods
LogicMods.zip
To Reproduce
Steps to reproduce the behavior:
Expected behavior
palworld process crashed
Screenshots, UE4SS Log, and .dmp file
If applicable, add screenshots to help explain your problem, and upload the log and .dmp files located in the Win64 directory.
Desktop (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: