Will try right now.
(EDIT: WORKS !) Thx, I can play again.
Will try right now.
(EDIT: WORKS !) Thx, I can play again.
Iām currently experience the same as what @SWProzee1 described.
Stepping out of my portal by the Hopperdrome on game start-up causes the game to freeze up and crash.
It happened three times before I decided to try using the warp on the right. I tried warping to another location, but the same thing occurs. I pass through the warp and the game freezes up and crashes.
I blame the Spitters.
Edit; sixth timeās a charm. Seem to be stable now, though Iāll leave this post here.
Can you send in your crash dumps?
Thanks.
Iām no techie, but thereās no crash dump that was ālast modifiedā today. Is that a problem? Did it not log the crashes or is that not how it works?
"Another list of possible solutions, if you manage to get in that is, that will hopefully stop it from happening again;
Try giving all your gem tools to @The-Velociraptor
If that doesnāt work, you can also try giving him all your coins."
It does not create a dump file. Had the same thing.
Donāt reinstall the game, it does not help.
They solved it for me by doing something on beacon information.
Seems that a beacon sends out beacon information that crashes your client.
Even with a 2nd account going there crashes your client. So people, donāt go there !
I can get on and play now, so it seems to have resolved itself, whatever was doing it? No dump file though for whatever reason. I guess because it wasnāt a āregular crashā. It just stopped working.
āthis program is no loner respondingā or whatever.
Anyway, Iāll wait to see what @michaelb suggests. Iām able to get in-game and play, but Iād still like to help out with this bug if possible.
I think there is very little that we can test or help out with. Seems a server problem.
The moment the Sanctum portal on the right gets information from the server (just before opening) the client crashes.
The boundless_log shows the last thing it could do on the client but not really usefull to troubleshoot, that is all I could seeā¦
The bug before SWProzee1 hit was a limit on the size of data that we fixed. If there is a specific location your seeing a problem let us know and we can check it out.