Unavoidable crash post splittening when logged in.
Describe the bug?
I'm not sure why, but every time I start up the game, even without mods enabled, I crash after about two minutes.
To Reproduce
https://pastebin.com/phsMbvTa Game didn't crash pre-splittening and my mental health has been bad so I haven't reported it.
Reproduction Item/World
N/A
Expected behavior
Not crashing
Screenshots
No response
Resonite Version Number
Beta 2025.9.23.1237
What Platforms does this occur on?
Linux
What headset if any do you use?
Desktop for tests
Log Files
~~https://pastebin.com/phsMbvTa~~ https://gist.github.com/EmergencyTemporalShift/b6597ac63055938ab1b4aaf4eef7173e
Additional Context
Tried wiping and reinstalling the game and all data and works until I log in.
Fedora Wayland KDE, Proton 9.0-4 (and others) Operating System: Fedora Linux 42 KDE Plasma Version: 6.4.5 KDE Frameworks Version: 6.18.0 Qt Version: 6.9.2 Kernel Version: 6.16.9-200.fc42.x86_64 (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 5600X 6-Core Processor Memory: 32 GiB of RAM (31.3 GiB usable) Graphics Processor: NVIDIA GeForce RTX 3060 Manufacturer: Micro-Star International Co., Ltd Product Name: MS-7C02 System Version: 1.0
Reporters
@EmergencyTemporalShift
Hi! Thank you for reporting this bug on the Resonite issue tracker.
We noticed you haven't attached a proper log file in your report. Including a log helps us pinpoint the exact issue which is why it is required during the report process.
If you do not know where to find log files, please see this tutorial on the Resonite Wiki to see where to find them.
Thank you!
Hey, I see you used Pastebin, but I'd recommend using GitHub Gist. It has fewer issues overall and doesn't have a timer on your pastes.
For instance, your logs are inaccessible:
Oops, fixed
Perfect, thanks!
In later bug reports, please upload the file directly, it makes it easier for the bot to parse and give us some details quicker!
Log data:
| Version | OS | CPU | GPU | VRAM | RAM | Headset | Plug-ins/Mods | Renderer | Clean Exit |
|---|---|---|---|---|---|---|---|---|---|
| Beta 2025.9.23.1237 | Steam Runtime | AMD Ryzen 5 5600X 6-Core Processor | GA106 [GeForce RTX 3060 Lite Hash Rate] (rev a1) | 0.00 B | 31.26 GB | Screen | no | Renderite.Renderer.Unity 2025.9.19.820 (2019.4.19f1) (WindowPtr: 0x30080 | ❌ |
Due to the circumstances of me having cleared data and reinstalled, Ultra thinks it might be a facet, it might be my choose avatar facet.
try removing the yt-dlp. exe its a work around atleast for mine
I was able to somehow run without crashing, I swapped between vr and desktop after deleting the facet. log follows. (Don't think it's that facet anymore, I deleted it (also my hand facets disappeared I think.)) https://gist.github.com/EmergencyTemporalShift/bf07f4778b056dc941798225e1770381
Are there any crash logs and memory dumps by chance? It would be interesting to see how they compare to #5740.
I don't seem to have that folder? (compatdata/2519830/pfx/drive_c) Edit: Yes I do, hold on. (I was looking in the wrong number of digits range, most sorting does this wrong)
Player.log Wait, does that make a gist? /home/Shark/.local/share/Steam/steamapps/compatdata/2519830/pfx/drive_c/users/steamuser/AppData/Local/Temp/ Doesn't seem to have ANY folders
If it helps narrow it down, I did a clean run with my underpowered laptop and although it didn't run great (It's very old) It didn't crash: https://gist.github.com/EmergencyTemporalShift/f2bbfba249cf380c4378791782fe45c2
@jae1911 Can you reactivate the bot for the working run log or do those specs not matter?
The bot only runs when the issue is opened. But don't worry, the original logs are already parsed, no need to parse every single ones generally.
I asked in case it was a hardware issue, I ran it on a different machine. Also, it might crash after the initial run on the machine, it ran fine first run. Can confirm it crashed subsequent runs.
I'd like to mention that this is still a breaking issue for me, I want to continue supporting this project because I really believe in what it could become, but I am currently unable to reap the benefits of my contribution. Please look into this.
Do you have a crash log or Player.log from a crash?
The last Player.log one seems to exit normally rather than crashing.
Here's info on how to get other types of crash logs too: https://wiki.resonite.com/Log_files#Crash_logs
What about the other types of crash logs?
Are there no Renderite.Host.Crash.<timestamp>.log logs?
I don't see that in the home directory no.
Hmm... that is odd. I don't really see anything in any of these logs, it just... "ends".
You said that it happens after you log in though? This might be an issue with the Bepu physics engine.
What if you launch Resonite with -DoNotAutoLoadHome argument?
Hmm, I thought I tried that before, that seems to fix it. Any way to diagnose what it is in the world? I'm not too attached to it if not.
Not easily without a dev build and digging around.
If that fixes it, I'd recommend using that as a workaround for now.
We're working on updating Bepu to latest version which has bugfixes for these types of crashes, which might fix this implicitly: https://github.com/Yellow-Dog-Man/Resonite-Issues/issues/4748
Good to know. Thanks Froox, you deserve all the headpats.