Hello, I’m sorry to say that nothing has worked so far.
I’ve tried several of the solutions you suggested:
– Updated Windows 10
– Updated my Nvidia graphics drivers
– Reinstalled DirectX
– Downloaded and placed the xinput9_1_0.dll file in the game folder
– My graphics card is a GTX 970, and the Nvidia control panel doesn’t offer a “Fast Sync” option but changing the VSync settings didn’t help either
– There are 10GB of free space remaining on the hard drive where the game is installed
Still hoping for a solution, and wishing you strength for the final stretch before the next milestone. Keep up the great work!
After the update - Everything also crashes, after the logo screen and loading (red ball in the lower right corner of the screen)
Tell me, maybe my processor is not suitable,
i7 3820
I was patiently waiting for the update to fix this problem, but alas…
I am severely dissapointed i still can’t play the game, can anyone respond if it’s being fixed ?
Well, I was hoping this new patch would let me play the game again. But, to my disappointment, the game still crashes on startup.
I was liking this game a lot, but since the updates that keep me from playing, I’m starting to think this was a waste of money
After this update, I once again cannot enter the game. It’s the same issue as before—it only shows “Moon Studios,” then the screen goes black and the game exits without any other error messages.
*After the recent update, I’m once again unable to launch the game—the same issue as before. It only shows the ‘Moon Studios’ logo, then crashes to a black screen without any error messages. This problem had been fixed in a previous update, but now it’s recurring. Please refer to this thread for context: I can not enter the game - Wicked Bug Reporting - No Rest For The Wicked
Previously, I had already updated my drivers, verified the integrity of game files through Steam, and confirmed that the DLL and VC++ runtime files were all functioning properly. Moreover, I was able to run this game without issues back in February.
Below is the .dmp file analysis from WinDbg Preview:
*
Exception Analysis *
*
*** WARNING: Unable to verify checksum for GameAssembly.dll
*** WARNING: Unable to verify checksum for NoRestForTheWicked.exe
*** WARNING: Unable to verify checksum for KERNEL32.DLL
*** WARNING: Unable to verify checksum for USER32.dll
*** WARNING: Unable to verify checksum for ole32.dll
*** WARNING: Unable to verify checksum for KERNELBASE.dll
*** WARNING: Unable to verify checksum for BacktraceCrashpadWindows.dll
Here are the relevant files you requested. Please review them.
I genuinely love this game and I’m eager to play it as soon as possible. However, this is already the second time during Early Access that I’ve been unable to launch the game after an update. I don’t know if you can permanently resolve this issue, but it’s extremely frustrating. I have to say this has significantly diminished my excitement for the game. While I truly enjoy it, But, if this problem persists, I may have to seriously consider requesting a refund
I am here on behalf of friends because I still do not download the Breach update out of fear or instability or potential bugs.
There are people reporting about crashing to desktop after the Moon Studio logo opening and black loading screen with spinning red orb with the new Breach update. They mentioned about access violation related to UnityPlayer.dll in their Player.log and there was nothing else. The access violation related to UnityPlayer.dll was the only error logged by the game before it crashed to desktop. According to them, verifying the game files did not help because Steam did not download or replace anything. Removing the game by uninstalling it and then reinstalling the game did not help either.
I cannot mention anything else other than what my friends have mentioned to me because I still do not update my game yet. And judging by many posts in Steam forums, I think I better keep my game as is and prevent Steam from updating it. I am still with the previous version and I can run my game normally and there was no error recorded in the log or crash to desktop.
As I have mentioned, I do not have the Breach update so I cannot test the issue myself, but please take a look at the issue those people are having after they installed the Breach update.
After a day of working with AI, I finally identified the issue: the game requires the AVX instruction set, but my BIOS had AVX disabled. As a result, when the game launched and detected no AVX support, it immediately crashed. I entered the BIOS, enabled AVX, and now the game launches normally. I hope this solution helps others facing the same problem!
You were wrong. My post had nothing to do with this thread because this thread is for people who were suffering crashes to desktop after Moon Studio logo since long before the Breach update and they are still suffering from the same crashes today.
My post is about users or players (my friends) who cannot open the main menu anymore after they downloaded and installed the Breach update, which means none of my friends whom my post was made on behalf of suffered any crash to desktop before they have the Breach update which was released recently. Their logs showing errors with exception and memory violation related to UnityPlayer.dll also occurred after they installed the problematic Breach update, not before like all people in this thread.
The crashes is tied exclusively to the Breach update because after I gave my copy of the game, which is the version before the Breach update (I did not download or install the update because it is problematic) to them they could run the game again without any crash or error related to any of the game files or data. The only thing they always need to do now is to open or run Steam first and then run the game by opening the game .exe file because if they run the game through Steam, Steam will ask them to update their game first before they can play.
I was also going to post to ask the developers about why the crucible legacy version of the game is not available to download on Steam despite the claims from some people that the crucible legacy version is made available for people who still want to play the version of the game without or before the Breach update. This is the reason why I offered my copy of the game to my friends so they can continue playing the game now without have to worry about the problematic Breach update because now is holiday period for us Japanese. Yet my thread was locked.
My apologies, I mean no offense, but my post which was incorrectly moved to this thread had nothing to do with AVX instruction set. I am here on behalf of my friends who do not have an account in this forum to report about issues. They did not have any problem with AVX instruction set because otherwise they would not be able to play Clair Obscur: Expedition 33 with the same PC now or played No Rest for the Wicked often with the Crucible update before the problematic Breach update was released and they installed it.
My friends could play No Rest for the Wicked without any crash to desktop before they installed the Breach update, and they played very often and only suffered constant crash to desktop after the Moon Studio logo recently after they installed the problematic update, so unfortunately whatever the issue that people have in this thread may not have anything to do with my friends.
there are a lot of reports here with different setups, but all have the same issue, the crash after the moon logo, so they can not enter the main menu. the bio that had AVX disabled was 1 person out of multiple. And all of them were quite helpful with sharing logfiles, etc.
i just try to keep things together. we collect them by how the bug or error presents.
when we have 1 thread for each individual “after moon logo crash”, then each of them gets burried somewhere within the 160 new posts and thread per day. i am pretty sure it is NOT in the interest of your friend, to have a separate post somewhere beneath all those new reports. that does not help anyone.
and it does not help the team either. when we keep all in one place to collect logfiles etc, they do not have to click though 50 threads but can download and receive all necessary information in just one.
No, it is not a good thing. My apologies if this sounds impolite but you do not know my friends. You were only assuming or thinking that you are pretty sure about my friends’ interest while in fact, you were completely wrong about my friends and their interests.
It was them who asked me to create a new thread in either the Bug Report section or Feedback section about the crash to desktop after Moon Studio logo because this issue occurrs only and only after the Breach update, not before.
My friends and I, all of us were already knew the existence of this thread, and none of them had any crash to desktop after the Moon Studio logo before they installed the Breach update. None of the issues or solutions posted here worked for any of us with the issue of crashing to desktop caused by the Breach update. That was why I did not post a feedback in this thread. Like I mentioned, you were only assuming. Please read again all my posts before assuming you know or sure about something, because the more you claim, the more you prove you are wrong.
My thread about the crash to desktop after the Moon Studio logo issue is occurred only and only after the Breach update, and that is why my thread or post is a feedback exclusive to the Breach update to raise the awareness to the developers about the crash to desktop issue that my friends are experiencing after they installed the Breach update. I mention this again, none of my friends had any crash to desktop before the main menu appears prior to installing the Breach update.
My thread was and is still a feedback exclusive to the Breach update directed to the developers, and it was requested specifically by my friends, who do not have accounts here. That was why it was posted in Feedback section and not the Bug Report section and not in this thread either, even though the exception or access violation related to UnityPlayer.dll may be a bug or a mistake on the developers’ end. I repeat this again, none of my friends had any crash to desktop, related to UnityPlayer.dll or anything else, prior to installing the Breach update.
