dudey5691
-
Posts
4 -
Joined
-
Last visited
Content Type
Profiles
Forums
Store
Articles
A20 Bugs
A21 Bugs
Events
Record Comments posted by dudey5691
-
-
1 hour ago, dudey5691 said:
I was able to reproduce this without the HUD mod. Tested between 1040 and 1105.
Server log: https://pastebin.com/YZQkWjvN
Client log: https://pastebin.com/4cbH7aC8
Is there a way to verify that the player profiles are not to cause? One player has not experienced this issue yet. We recently moved servers and had not been experiencing this until a few days into the new server.I validated via SteamCMD and tried a T1 clear quest. It did work; however, I did a T4 fetch/clear and the issue continued.
Server log: https://pastebin.com/EbQ8fhd2
Client log: https://pastebin.com/ygM3EP4fFrom the logs, it looks like around the time I experienced the issue, it is throwing "Calling Animator.GotoState on Synchronize layer" (approximately 12:53). This is present in the previous log as well. A quick google search indicates this may be a corrupted player or region file.
0 -
2 hours ago, TSBX said:
@dudey5691 Are you or your user able to reproduce this without using a HUD mod?
@Wolfz@wicker Can you guys post your reports via the template here please?I was able to reproduce this without the HUD mod. Tested between 1040 and 1105.
Server log: https://pastebin.com/YZQkWjvN
Client log: https://pastebin.com/4cbH7aC8
Is there a way to verify that the player profiles are not to cause? One player has not experienced this issue yet. We recently moved servers and had not been experiencing this until a few days into the new server.0
"Clear Areas" not completing with POI clear, no visual indicators provided for missing
in Fixed
Posted
Resetting the region files resolved the issue. Likely a combination of the server move + update.
For anyone else that experiences this, you can use the debugmenu > F3 > "Ch" to identify the region you are in. This is useful for keeping any built base structures. Deleting the other region files in the save will reset them. I suspect a chunk reset of the trader locations may also fix it, but cannot confirm.