![]() ![]() Maybe I'll try again and see what happens there. I got the exec(number).bat on my sister's 2020 M1 MBP but as we know that doesn't seem to be related to osu! being unable to start. ![]() This is on my 2016 MBP wo/ touch bar - Intel x86 i5. WS11WineCX6420.0.0 :: wine: '/Users/Adrian/Desktop/WS11CX20.0.0.app/Contents/Resources' is a 64-bit installation, it cannot be used with a 32-bit wineserver. WS11WineCX64Bit20.0.0 :: Works fine normally, Test Run opens osu! as expected WS11WineCX64Bit19.0.1-1 :: Works fine normally, Test Run opens osu! as expected So far I haven't been able to replicate the crash report on any Wineskin. I would be very surprised if it works but seeing as the Reddit thread aidswidjaja linked suggests some success with this engine, it's worth a try. Please try using this Wineskin which uses WineCX20 instead: and I'm running macOS Catalina, not Big Sur or M1. Technocoder wrote:Strangely enough, I get the same crash report when using the WineCX20 engine but not with the WineCX64Bit20 engine. Can you elaborate on what's not working? Are you able to open it and/or do you get any crash reports? Any help would be great!Sorry yeah, it looks like Big Sur is a little bit hit or miss at the moment. TheNamesTen wrote:Not quite sure what to do from here. Is there a way to fix this?Ĭan you please try running a Test Run from Wineskin (Right click osu! > Show Package Contents > Wineskin > Advanced > Test Run) and paste the logs somewhere (such as: ) when it crashes? The only way to fix this so far for me is to completely redownload osu! everytime I want to play it, which is a huge pain. I have tried using the Osu mac agent to repair but it does not seem to fix it. I checked activity monitor while trying to open it, and it seems like it is trying to open up with the wineskin but it just stops and disappears from activity monitor. However, after I close it after playing for ONE session, when I try to open it up it does not open. After installing osu with these steps on Catalina 10.15.7, I am able to run it perfectly. ![]()
0 Comments
Leave a Reply. |