gravitybalmain wrote:

aidswidjaja wrote:

gravitybalmain

gravitybalmain wrote:

aidswidjaja wrote:

gravitybalmain

gravitybalmain wrote:

Hey, so the MacOS Agent seems to override the "damaged and must be moved to trash" issue, but double clicking on the app afterwards brings up the terminal, which then crashes, and Osu doesn't open. Here's a c/p of the troubleshoot. I'm probably just missing something super obvious but I'd appreciate any help!

Report

Version 10.16 (Build 20B29)
Engine: WS11WineCX64Bit19.0.1-1
Wineskin 2.9.0.6 1
Release: Stable40
Quarantine attribute is absent
Execute flag is present
Detect Direct3D is enabled
Game user configuration is absent
System Integrity Protection is enabled
Engine version is supported
Razer Synapse is absent
No errors in: update.log
Log file: runtime.log is absent

Hi, thanks for the report! Could you try doing a Test Run using the instructions available here: https://osu-mac.readthedocs.io/en/latest/issues/troubleshooting.html#generating-logs-for-wineskin, thanks! You can copy and paste the contents of the log files to paste.ubuntu.com or another pastebin service.

Sure. Here's the log.

log

1
2
3
4
5
6
7
8
9
10
err:thread:get_image_addr dyld image info is above 4GB limit for 32-bit-on-64-bit process
000b:fixme:thread:create_user_shared_data_thread Creating user shared data update thread.
000d:fixme:thread:create_user_shared_data_thread Creating user shared data update thread.
0010:fixme:thread:create_user_shared_data_thread Creating user shared data update thread.
0018:fixme:thread:create_user_shared_data_thread Creating user shared data update thread.
001d:fixme:thread:create_user_shared_data_thread Creating user shared data update thread.
0009:fixme:exec:SHELL_execute flags ignored: 0x00000100
err:thread:get_image_addr dyld image info is above 4GB limit for 32-bit-on-64-bit process
err:thread:get_image_addr dyld image info is above 4GB limit for 32-bit-on-64-bit process
002a:fixme:thread:create_user_shared_data_thread Creating user shared data update thread.
[box]

Thanks, there's a particular line that interests me here:

0009:fixme:exec:SHELL_execute flags ignored: 0x00000100

It indicates that there is an issue with the execute.bat file included with the Wineskin that triggers osu! to run.

Could you please make sure:

1. that inside Wineskin options that "C:\osu!\execute.bat" is the executable target set. This should be under the Windows EXE field in the Configuration tab.
2. that inside osu!.app/drive_c/osu!/execute.bat, which is a batch/text file that can be opened using TextEdit, the following text is written.
   

   start C:\osu!\bridge.exe -nosplash
   start C:\osu!\osu!.exe

3. if that fails, try and set the previously mentioned Windows EXE field from C:\osu!\execute.bat to C:\osu!\osu!.app - note that discord rich presence will no longer work if this step is performed
4. Try running a Test Run again with the above steps performed and feel free to leave a log down here if its still not working

------
Need help this holidays?

It's been nice being able to try and help people out this year, and doing my best to help Techno, Oblivious and the osu! support team in trying to troubleshoot problems. Especially over the past month or two I've tried to be pretty active down here so that someone can keep the thread alive. After today (23 Dec 2020 AEDT) I'll probably try and stop myself from looking at this thread until 1 Jan 2020 AEDT. I realise that many of the other regulars here will probably be inactive during this time, so I just wanted to give a heads up to anyone expecting support over the next week should probably know that myself and the majority of people will likely be inactive on the forums. (I don't think I even monitor other threads other than this one really, I think the support team has done a lot of excellent work there.)

Of course anyone is welcome to provide what help they can to others in this thread (and you should definietly leave any questions/logs/reports you have in the thread) but if you need quick help and the forums are inactive over the holidays then you can take a look at this site https://osu-mac.readthedocs.io which should provide some info into downloading wrappers and troubleshooting common errors. There is also a list of alternative resources here - https://osu-mac.readthedocs.io/en/latest/about/resources.html. Enjoy your holidays!

tl:dr; during holiday inactivity check out https://osu-mac.readthedocs.io and https://osu-mac.readthedocs.io/en/latest/about/resources.html for help, still leave your questions/logs/reports down here for help but please note that response times may be slower.

I did the above steps!

Step 1 was already complete.

Step 2 was complete as well -- the "-nosplash" was after the osu!.exe and not the bridge, but I think that may be a typo on your end compared to what's listed upthread -- either way, I tried both variations to no avail.

Step 3: After setting the EXE field to the suggested, double clicking on the OSU App simply opens the Wineskin interface that you'd get by just opening Wineskin from the Package Contents.

Step 4: Weirdly, after completing the above steps, Wineskin no longer allows me to do a test run -- upon clicking the button, it just immediately crashes the program and I get an Apple error report.

y0lky wrote:

for some reason this wineskin doesnt work for me anymore it wont let me open and when i check the osu folder there is no longer a beatmap and skin folder, and only contains 2 files. The format of the package contents look different than usual and I am stuck, please help

999999 wrote:

I cant scan it because it wont let me press it.

Chanw11 wrote:

I just did a fresh reinstall of osu with the agent on my m1 macbook. Got it to open but when I select a song it will continually load.

mazzystar98 wrote:

my scan:

Report

Version 10.13.6 (Build 17G11023)
Engine: WS11WineCX64Bit19.0.1-1
Wineskin 2.9.0.6 1
Release: Stable40
Quarantine attribute is absent
Execute flag is present
Detect Direct3D is disabled
Game user configuration is absent
System Integrity Protection is enabled
Engine version is supported
Razer Synapse is absent
No errors in: update.log
Log file: runtime.log is absent

zoko91 wrote:

Hello
I just installed osu on my macbook pro, seems to work perfectly fine
Even thought I have some issues, I wonder if it can be solved, I'm using a gaming mouse and with an usb usb-c adapter and it works fine browsing and playing small games, but then in osu the cursor doesn't follow me perfectly, it's nearly impossible to aim correctly, I can't even do more than 3 stars maps. It's so smooth on the menu and slow in game.

Is there any possible fix, driver update or thing I can do to make it more playable? Thanks !

FIXED: You can actually deactivate the mac mouse acceleration from an application: Looked at a tutorial on youtube here's the link : https://www.youtube.com/watch?v=IzZUeBD5Yp0

Still have some imput lag on the keystrokes tho

Brendan_OM wrote:

Hi. I really want to install the wineskin but I recently had another device that got hacked after I tried to install free RAM. Is there any way for me to verify that I'm not installing some complex trojan?

zoko91 wrote:

aidswidjaja wrote:

hi everyone I'm back, I'll try and get through as many as possible but please remember to ping me with your issues/questions/problems if you're still experiencing them.

zoko91

zoko91 wrote:

Hello
I just installed osu on my macbook pro, seems to work perfectly fine
Even thought I have some issues, I wonder if it can be solved, I'm using a gaming mouse and with an usb usb-c adapter and it works fine browsing and playing small games, but then in osu the cursor doesn't follow me perfectly, it's nearly impossible to aim correctly, I can't even do more than 3 stars maps. It's so smooth on the menu and slow in game.

Is there any possible fix, driver update or thing I can do to make it more playable? Thanks !

FIXED: You can actually deactivate the mac mouse acceleration from an application: Looked at a tutorial on youtube here's the link : https://www.youtube.com/watch?v=IzZUeBD5Yp0

Still have some imput lag on the keystrokes tho

In regards to mouse settings, I think what might help you here is enabling some of the ingame osu! options. Enabling the options Raw input or Mapping absolute raw input might help with mouse positioning. See https://osu-mac.readthedocs.io/en/latest/issues/input.html for more info

As for keystroke lag input, this could just be general performance issues. There are some tweaks you could probably adjust for better overall performance so let me know if you need any ideas. But generally performance tweaking and workarounds like universal offset is the same as regular osu! on Windows.

I've tried to optimize the game as much as I could and it's actually fine now, not as good as on windows but close !
Steel-series is providing a software which disables mouse acceleration on MAC OS (that helped a lot)
Then I enable raw input on osu settings and that was pretty much it for the mouse settings.
As for the keystrokes, I've put some offset (-17ms) which seems fine in the gameplay but the sound comes late (click sound) I now have to get used to it !
Thanks

AnimatedThinks wrote:

I've been basically lurking this thread for a while, but I'm kind of stuck now. I'm using an M1 MacBook Air, and I've had the problem where osu! tries to open but says:
C:osu!>start C:\osu!\bridge.exe
C:osu!>start C:\osu!\osu!.exe -nosplash.
I tried opening the Wineskin to do a test run, but it didn't open and showed the exec(number).bat does not exist error, so I followed the steps listed above for that (which didn't work for me). I downloaded the other Wineskin and moved it into the osu! package contents, which worked and Wineskin opened now. However, whenever I try to do a test run, it crashes and shows a problem report saying Wineskin quit.
If you need, I should be able to provide the crash report - it says something about 'thread 7' crashing.

speko wrote:

The game only works the first time after downloading, after exiting the game and reopening, nothing happens.

gravitybalmain wrote:

aidswidjaja wrote:

hi everyone I'm back, I'll try and get through as many as possible but please remember to ping me with your issues/questions/problems if you're still experiencing them.

gravitybalmain

gravitybalmain wrote:

aidswidjaja wrote:

gravitybalmain

gravitybalmain wrote:

aidswidjaja wrote:

gravitybalmain

gravitybalmain wrote:

Hey, so the MacOS Agent seems to override the "damaged and must be moved to trash" issue, but double clicking on the app afterwards brings up the terminal, which then crashes, and Osu doesn't open. Here's a c/p of the troubleshoot. I'm probably just missing something super obvious but I'd appreciate any help!

Report

Version 10.16 (Build 20B29)
Engine: WS11WineCX64Bit19.0.1-1
Wineskin 2.9.0.6 1
Release: Stable40
Quarantine attribute is absent
Execute flag is present
Detect Direct3D is enabled
Game user configuration is absent
System Integrity Protection is enabled
Engine version is supported
Razer Synapse is absent
No errors in: update.log
Log file: runtime.log is absent

Hi, thanks for the report! Could you try doing a Test Run using the instructions available here: https://osu-mac.readthedocs.io/en/latest/issues/troubleshooting.html#generating-logs-for-wineskin, thanks! You can copy and paste the contents of the log files to paste.ubuntu.com or another pastebin service.

Sure. Here's the log.

log

1
2
3
4
5
6
7
8
9
10
err:thread:get_image_addr dyld image info is above 4GB limit for 32-bit-on-64-bit process
000b:fixme:thread:create_user_shared_data_thread Creating user shared data update thread.
000d:fixme:thread:create_user_shared_data_thread Creating user shared data update thread.
0010:fixme:thread:create_user_shared_data_thread Creating user shared data update thread.
0018:fixme:thread:create_user_shared_data_thread Creating user shared data update thread.
001d:fixme:thread:create_user_shared_data_thread Creating user shared data update thread.
0009:fixme:exec:SHELL_execute flags ignored: 0x00000100
err:thread:get_image_addr dyld image info is above 4GB limit for 32-bit-on-64-bit process
err:thread:get_image_addr dyld image info is above 4GB limit for 32-bit-on-64-bit process
002a:fixme:thread:create_user_shared_data_thread Creating user shared data update thread.
[box]

Thanks, there's a particular line that interests me here:

0009:fixme:exec:SHELL_execute flags ignored: 0x00000100

It indicates that there is an issue with the execute.bat file included with the Wineskin that triggers osu! to run.

Could you please make sure:

1. that inside Wineskin options that "C:\osu!\execute.bat" is the executable target set. This should be under the Windows EXE field in the Configuration tab.
2. that inside osu!.app/drive_c/osu!/execute.bat, which is a batch/text file that can be opened using TextEdit, the following text is written.
   

   start C:\osu!\bridge.exe -nosplash
   start C:\osu!\osu!.exe

3. if that fails, try and set the previously mentioned Windows EXE field from C:\osu!\execute.bat to C:\osu!\osu!.app - note that discord rich presence will no longer work if this step is performed
4. Try running a Test Run again with the above steps performed and feel free to leave a log down here if its still not working

------
Need help this holidays?

It's been nice being able to try and help people out this year, and doing my best to help Techno, Oblivious and the osu! support team in trying to troubleshoot problems. Especially over the past month or two I've tried to be pretty active down here so that someone can keep the thread alive. After today (23 Dec 2020 AEDT) I'll probably try and stop myself from looking at this thread until 1 Jan 2020 AEDT. I realise that many of the other regulars here will probably be inactive during this time, so I just wanted to give a heads up to anyone expecting support over the next week should probably know that myself and the majority of people will likely be inactive on the forums. (I don't think I even monitor other threads other than this one really, I think the support team has done a lot of excellent work there.)

Of course anyone is welcome to provide what help they can to others in this thread (and you should definietly leave any questions/logs/reports you have in the thread) but if you need quick help and the forums are inactive over the holidays then you can take a look at this site https://osu-mac.readthedocs.io which should provide some info into downloading wrappers and troubleshooting common errors. There is also a list of alternative resources here - https://osu-mac.readthedocs.io/en/latest/about/resources.html. Enjoy your holidays!

tl:dr; during holiday inactivity check out https://osu-mac.readthedocs.io and https://osu-mac.readthedocs.io/en/latest/about/resources.html for help, still leave your questions/logs/reports down here for help but please note that response times may be slower.

I did the above steps!

Step 1 was already complete.

Step 2 was complete as well -- the "-nosplash" was after the osu!.exe and not the bridge, but I think that may be a typo on your end compared to what's listed upthread -- either way, I tried both variations to no avail.

Step 3: After setting the EXE field to the suggested, double clicking on the OSU App simply opens the Wineskin interface that you'd get by just opening Wineskin from the Package Contents.

Step 4: Weirdly, after completing the above steps, Wineskin no longer allows me to do a test run -- upon clicking the button, it just immediately crashes the program and I get an Apple error report.

err, sounds like your install is corrupted terribly... do you happen to have the Apple error report? If you do, please paste it into a pastebin such as paste.ubuntu.com and I'll be happy to have a look through it. But either way if you can reinstall and make sure the following is all good:

- you're using The Unarchiver (https://theunarchiver.com/) instead of the in-built Archive Utility
- no antivirus is removing files
- that the insides of osu!.app/drive_c/osu! look normal and everything

Feel free to run a Test Run after your install and copy-paste the logs to a pastebin if you're still having problems.

I started from a fresh re-install -- I think I'm having the same problem other M1 users are talking about this thread but I might have complicated things somewhat before. Here's a step-by-step with logs to help clarify the problem, because I really do think we're all experiencing the same thing. I'm starting with everything uninstalled, no anti-virus software, M1 macbook pro, using The Unarchiver for all purposes.


1. Downloaded latest wineskin. Extracted using The Unarchiver.
2. Downloaded osu!macOS Agent, extracted and opened, scanned and repaired.
Report:

Report

Version 10.16 (Build 20B29)
Engine: WS11WineCX64Bit19.0.1-1
Wineskin 2.9.0.6 1
Release: Stable40
[Error][Fixed] Quarantine attribute is present
Execute flag is present
Detect Direct3D is enabled
Game user configuration is absent
System Integrity Protection is enabled
Engine version is supported
Razer Synapse is absent
No errors in: update.log
Log file: runtime.log is absent

3. Double clicked Osu! to open: Wineskin briefly flashes open, then immediately closes. See image: https://imgur.com/a/OvoTurK
4. Right clicked osu to access package contents -- drive_c -> osu! -> logs. only log present is update.log
5. Went back to package contents and double clicked Wineskin to open -- following error presented https://imgur.com/a/xjPuVzj
6. Right clicked the Wineskin icon inside Package contents and went Wineskin -> Contents -> MacOS -> Wineskin to run directly from terminal.
7. Inside Wineskin app, went Advanced -> Test Run. This crashes the program and generates apple crash report. https://paste.ubuntu.com/p/pfvsJr9xYQ/
8. Double checked that inside Winskin app, Windows EXE is set to "C:\osu!\execute.bat" and that osu!.app/drive_c/osu!/execute.bat text is correct.
9. Changed Windows EXE from C:\osu!\execute.bat to C:\osu!\osu!.app and pressed test run. This also crashes the program and generates an apple crash report.

Hopefully this step-by-step helps explain the issue a little better! I'm working off a fresh computer (didn't back up old data or anything) so there shouldn't be any underlying software conflicts or anything like that.

R a y e n wrote:

This is my troubleshoot report:

Report

Version 10.14.6 (Build 18G4032)
Engine: WS9Wine4.0-rc3
Wineskin 2.8.8Beta6
Release: Stable40
Quarantine attribute is absent
Execute flag is present
Detect Direct3D is disabled
Compatibility mode is disabled
System Integrity Protection is enabled
Engine version is supported
Razer Synapse is absent
[Warning] Errors in: update.log
2021-01-10T10:19:57: _pending\osu!.exe => osu!.exe: FAIL
2021-01-10T10:20:01: _pending\osu!.exe => osu!.exe: FAIL
2021-01-10T10:20:06: _pending\osu!.exe => osu!.exe: FAIL
2021-01-10T10:20:10: _pending\osu!.exe => osu!.exe: FAIL
2021-01-10T10:20:17: _pending\osu!.exe => osu!.exe: FAIL
2021-01-10T10:20:21: _pending\osu!.exe => osu!.exe: FAIL
2021-01-10T10:20:25: _pending\osu!.exe => osu!.exe: FAIL
2021-01-10T10:20:29: _pending\osu!.exe => osu!.exe: FAIL
2021-01-10T10:20:33: _pending\osu!.exe => osu!.exe: FAIL
2021-01-10T10:20:37: _pending\osu!.exe => osu!.exe: FAIL
2021-01-10T10:20:40: _pending\osu!.exe => osu!.exe: FAIL
2021-01-10T10:20:43: _pending\osu!.exe => osu!.exe: FAIL
2021-01-10T10:20:46: _pending\osu!.exe => osu!.exe: FAIL
2021-01-10T10:20:49: _pending\osu!.exe => osu!.exe: FAIL
Log file: runtime.log is absent

It just keeps repeating the update closing and opening back up please help ; u ;

AnimatedThinks wrote:

aidswidjaja wrote:

AnimatedThinks

AnimatedThinks wrote:

I've been basically lurking this thread for a while, but I'm kind of stuck now. I'm using an M1 MacBook Air, and I've had the problem where osu! tries to open but says:
C:osu!>start C:\osu!\bridge.exe
C:osu!>start C:\osu!\osu!.exe -nosplash.
I tried opening the Wineskin to do a test run, but it didn't open and showed the exec(number).bat does not exist error, so I followed the steps listed above for that (which didn't work for me). I downloaded the other Wineskin and moved it into the osu! package contents, which worked and Wineskin opened now. However, whenever I try to do a test run, it crashes and shows a problem report saying Wineskin quit.
If you need, I should be able to provide the crash report - it says something about 'thread 7' crashing.

Please make sure that you're using The Unarchiver to extract all zip files and no antivirus is removing files off your computer. If that doesn't work, please refer to the info provided to gravity below.

gravitybalmain

gravitybalmain wrote:

I did the above steps!

Step 1 was already complete.

Step 2 was complete as well -- the "-nosplash" was after the osu!.exe and not the bridge, but I think that may be a typo on your end compared to what's listed upthread -- either way, I tried both variations to no avail.

Step 3: After setting the EXE field to the suggested, double clicking on the OSU App simply opens the Wineskin interface that you'd get by just opening Wineskin from the Package Contents.

Step 4: Weirdly, after completing the above steps, Wineskin no longer allows me to do a test run -- upon clicking the button, it just immediately crashes the program and I get an Apple error report.

err, sounds like your install is corrupted terribly... do you happen to have the Apple error report? If you do, please paste it into a pastebin such as paste.ubuntu.com and I'll be happy to have a look through it. But either way if you can reinstall and make sure the following is all good:

- you're using The Unarchiver (https://theunarchiver.com/) instead of the in-built Archive Utility
- no antivirus is removing files
- that the insides of osu!.app/drive_c/osu! look normal and everything

Feel free to run a Test Run after your install and copy-paste the logs to a pastebin if you're still having problems.

gravitybalmain

I started from a fresh re-install -- I think I'm having the same problem other M1 users are talking about this thread but I might have complicated things somewhat before. Here's a step-by-step with logs to help clarify the problem, because I really do think we're all experiencing the same thing. I'm starting with everything uninstalled, no anti-virus software, M1 macbook pro, using The Unarchiver for all purposes.


1. Downloaded latest wineskin. Extracted using The Unarchiver.
2. Downloaded osu!macOS Agent, extracted and opened, scanned and repaired.
Report:

Report

Version 10.16 (Build 20B29)
Engine: WS11WineCX64Bit19.0.1-1
Wineskin 2.9.0.6 1
Release: Stable40
[Error][Fixed] Quarantine attribute is present
Execute flag is present
Detect Direct3D is enabled
Game user configuration is absent
System Integrity Protection is enabled
Engine version is supported
Razer Synapse is absent
No errors in: update.log
Log file: runtime.log is absent

3. Double clicked Osu! to open: Wineskin briefly flashes open, then immediately closes. See image: https://imgur.com/a/OvoTurK
4. Right clicked osu to access package contents -- drive_c -> osu! -> logs. only log present is update.log
5. Went back to package contents and double clicked Wineskin to open -- following error presented https://imgur.com/a/xjPuVzj
6. Right clicked the Wineskin icon inside Package contents and went Wineskin -> Contents -> MacOS -> Wineskin to run directly from terminal.
7. Inside Wineskin app, went Advanced -> Test Run. This crashes the program and generates apple crash report. https://paste.ubuntu.com/p/pfvsJr9xYQ/
8. Double checked that inside Winskin app, Windows EXE is set to "C:\osu!\execute.bat" and that osu!.app/drive_c/osu!/execute.bat text is correct.
9. Changed Windows EXE from C:\osu!\execute.bat to C:\osu!\osu!.app and pressed test run. This also crashes the program and generates an apple crash report.

Hopefully this step-by-step helps explain the issue a little better! I'm working off a fresh computer (didn't back up old data or anything) so there shouldn't be any underlying software conflicts or anything like that.

Thanks for your super detailed explanation!

It's definitely possible that M1 users could be suffering from this issue, but it's really hard for me to treat this since a) I haven't experienced the issue first hand b) in the past people fixed this issue by ensuring that files weren't removed.

I want to do a bit more research on this since it seems to be a widespread issue. There's a few things I'd like to try but I'll need some more time first. And if this issue is in fact recurring across all M1 Macs (despite their being previous instances of success) or even just a common issue that isn't limited to any platform, I'd definitely like to either communicate this to Technocoder (who maintains the Wineskin and is on hiatus now) or Gcenx who maintains the WineskinServer.

aidswidjaja: to anyone experiencing issues with their Wineskin

especially on M1 Macs or Big Sur.

If you're experiencing any of the following:
- exec(number).bat could not be found error (while trying to open Wineskin)
- osu!.app doesn't do anything when clicked - after following all installation instructions
- osu!.app opens a command line window when clicked, then immediately closes - after following all installation instructions
- Wineskin crashes when attempting to perform a Test Run

Please send me the following (apologies if you have already done this, feel free to link it to an earlier post again)
- osu!macOS Agent report (https://osu-mac.readthedocs.io/en/latest/issues/troubleshooting.html#generating-a-report-with-osu-macos-agent)
- Wineskin Test Run (https://osu-mac.readthedocs.io/en/latest/issues/troubleshooting.html#generating-logs-for-wineskin)
- Apple Crash Report (if applicable - this usually triggers after Test Run)

the reason I ask is because if this does turn out to be an upstream issue with the WineskinServer I'll need to file a bug report on the GitHub. However, hopefully there is a simple fix that I'm missing here and on that note, if you do happen to fix the issue, do let us all know here!

I did use The Unarchiver, and I don't have any antivirus installed (unless there's an in-built one I didn't know existed)
osu!macOS Agent report:

Report

Version 10.16 (Build 20B29)
Engine: WS11WineCX64Bit19.0.1-1
Wineskin 2.9.0.6 1
Release: Stable40
Quarantine attribute is absent
Execute flag is present
Detect Direct3D is enabled
Game user configuration is absent
System Integrity Protection is enabled
Engine version is supported
Razer Synapse is absent
No errors in: update.log
Log file: runtime.log is absent

The Apple crash report after trying to do a Wineskin test run is really long. Do I still put it here (probably in a pastebin as mentioned), and is there anything I should exclude before pasting it all?
also sorry for the late response!

Technocoder wrote:

AnimatedThinks wrote:

The Apple crash report after trying to do a Wineskin test run is really long. Do I still put it here (probably in a pastebin as mentioned), and is there anything I should exclude before pasting it all?
also sorry for the late response!

The whole crash report in a Pastebin if you can. Your username may appear in the report so if you'd like to keep that private, give it a find and replace with your username.

Really sorry for not staying active on this thread. Been busy with university applications and my internship but I'm getting used to my workload now so I should be able to start helping out in some greater capacity by the end of this month. aidswidjaja literally carrying the entire macOS support team.

It's getting hard to track who's been replied to and what information they've provided. I wonder if it'd be better to start tracking help requests on the Help Forum instead...

ShadowstyleX wrote:

Ok so I've been trying to get this to work for about a day and I'm pretty stumped on what to do at this point. I have followed each instruction as stated and I have no errors on troubleshooting, but when I try opening osu, the terminal opens for a moment, runs two command lines then just closes with nothing

I've downloaded the wineskin, there are no errors when trouble shooting, bridge.exe is present, went and turned off the quarantine on the console in case it was that

When I try accessing the wineskin to try and install older versions, this error is given "'exec4213618756.bat' is missing"

Any help I may get here? It would be very much so appreciated

AnimatedThinks wrote:

so... osu! randomly decided to work when I clicked to Test Run on Wineskin.
(image here: https://ibb.co/ry3tPwy)

These were the test logs, by the way.

Test Run

err:thread:get_image_addr dyld image info is above 4GB limit for 32-bit-on-64-bit process
000b:fixme:thread:create_user_shared_data_thread Creating user shared data update thread.
000d:fixme:thread:create_user_shared_data_thread Creating user shared data update thread.
0010:fixme:thread:create_user_shared_data_thread Creating user shared data update thread.
0018:fixme:thread:create_user_shared_data_thread Creating user shared data update thread.
001d:fixme:thread:create_user_shared_data_thread Creating user shared data update thread.
0009:fixme:exec:SHELL_execute flags ignored: 0x00000100
err:thread:get_image_addr dyld image info is above 4GB limit for 32-bit-on-64-bit process
err:thread:get_image_addr dyld image info is above 4GB limit for 32-bit-on-64-bit process
002a:fixme:thread:create_user_shared_data_thread Creating user shared data update thread.

Then everything went downhill

I was getting 40-50 fps even when plugged into charger, so I tried to see if turning on Compatibility Mode would help.
osu! crashed when restarting!! The error said something about graphics drivers but I forgot to screenshot it, but it did make me google possible fixes.
A fix I saw said to go to the osu.cfg file and change what was in the _ReleaseStream line to Stable. (It was at Stable40, so I changed it to Stable.) This didn't help, and osu! now showed a different error that looked like this: https://ibb.co/YXjP511 (Reversing the change back to Stable40 doesn't change anything, same error)
When I click yes, it sends me to a Microsoft page that says to download a .exe file that would probably help if I wasn't using a Mac.

I tried test running 3 times yesterday and today, and for some reason it succeeded the first and third try but failed the second try.

Apple error log when it failed: https://paste.ubuntu.com/p/wQ23NqCZys/ (apparent correction - thread 9 was the one that crashed, not 7)
Wineskin test log (on 3rd try): https://paste.ubuntu.com/p/2jvXyT7yhg/

If the links don't work or something else is wrong in this post, please let me know because I'm confused too!

lucid126 wrote:



Report

Version 10.14.6 (Build 18G103)
Engine: WS11WineCX64Bit19.0.1-1
Wineskin 2.9.0.6 1
Release: Stable40
Quarantine attribute is absent
Execute flag is present
Detect Direct3D is disabled
Compatibility mode is disabled
System Integrity Protection is enabled
Engine version is supported
Razer Synapse is absent
Log file: update.log is absent
No errors in: runtime.log

I get decent frames and then all of a sudden my frames drop and the game lags so much that it freezez it's really annoying, any way to fix this?

milenablack wrote:

Report

Version 10.16 (Build 20A2411)
Engine: WS11WineCX64Bit19.0.1-1
Wineskin 2.9.0.6 1
Release: Stable40
Quarantine attribute is absent
Execute flag is present
Detect Direct3D is enabled
Game user configuration is absent
System Integrity Protection is enabled
Engine version is supported
Razer Synapse is absent
No errors in: update.log
Log file: runtime.log is absent

AnimatedThinks wrote:

so... osu! randomly decided to work when I clicked to Test Run on Wineskin.
(image here: https://ibb.co/ry3tPwy)

These were the test logs, by the way.

Test Run

err:thread:get_image_addr dyld image info is above 4GB limit for 32-bit-on-64-bit process
000b:fixme:thread:create_user_shared_data_thread Creating user shared data update thread.
000d:fixme:thread:create_user_shared_data_thread Creating user shared data update thread.
0010:fixme:thread:create_user_shared_data_thread Creating user shared data update thread.
0018:fixme:thread:create_user_shared_data_thread Creating user shared data update thread.
001d:fixme:thread:create_user_shared_data_thread Creating user shared data update thread.
0009:fixme:exec:SHELL_execute flags ignored: 0x00000100
err:thread:get_image_addr dyld image info is above 4GB limit for 32-bit-on-64-bit process
err:thread:get_image_addr dyld image info is above 4GB limit for 32-bit-on-64-bit process
002a:fixme:thread:create_user_shared_data_thread Creating user shared data update thread.

Then everything went downhill

I was getting 40-50 fps even when plugged into charger, so I tried to see if turning on Compatibility Mode would help.
osu! crashed when restarting!! The error said something about graphics drivers but I forgot to screenshot it, but it did make me google possible fixes.
A fix I saw said to go to the osu.cfg file and change what was in the _ReleaseStream line to Stable. (It was at Stable40, so I changed it to Stable.) This didn't help, and osu! now showed a different error that looked like this: https://ibb.co/YXjP511 (Reversing the change back to Stable40 doesn't change anything, same error)
When I click yes, it sends me to a Microsoft page that says to download a .exe file that would probably help if I wasn't using a Mac.

I tried test running 3 times yesterday and today, and for some reason it succeeded the first and third try but failed the second try.

Apple error log when it failed: https://paste.ubuntu.com/p/wQ23NqCZys/ (apparent correction - thread 9 was the one that crashed, not 7)
Wineskin test log (on 3rd try): https://paste.ubuntu.com/p/2jvXyT7yhg/

If the links don't work or something else is wrong in this post, please let me know because I'm confused too!

Technocoder wrote:

AnimatedThinks

AnimatedThinks wrote:

so... osu! randomly decided to work when I clicked to Test Run on Wineskin.
(image here: https://ibb.co/ry3tPwy)

These were the test logs, by the way.

Test Run

err:thread:get_image_addr dyld image info is above 4GB limit for 32-bit-on-64-bit process
000b:fixme:thread:create_user_shared_data_thread Creating user shared data update thread.
000d:fixme:thread:create_user_shared_data_thread Creating user shared data update thread.
0010:fixme:thread:create_user_shared_data_thread Creating user shared data update thread.
0018:fixme:thread:create_user_shared_data_thread Creating user shared data update thread.
001d:fixme:thread:create_user_shared_data_thread Creating user shared data update thread.
0009:fixme:exec:SHELL_execute flags ignored: 0x00000100
err:thread:get_image_addr dyld image info is above 4GB limit for 32-bit-on-64-bit process
err:thread:get_image_addr dyld image info is above 4GB limit for 32-bit-on-64-bit process
002a:fixme:thread:create_user_shared_data_thread Creating user shared data update thread.

Then everything went downhill

I was getting 40-50 fps even when plugged into charger, so I tried to see if turning on Compatibility Mode would help.
osu! crashed when restarting!! The error said something about graphics drivers but I forgot to screenshot it, but it did make me google possible fixes.
A fix I saw said to go to the osu.cfg file and change what was in the _ReleaseStream line to Stable. (It was at Stable40, so I changed it to Stable.) This didn't help, and osu! now showed a different error that looked like this: https://ibb.co/YXjP511 (Reversing the change back to Stable40 doesn't change anything, same error)
When I click yes, it sends me to a Microsoft page that says to download a .exe file that would probably help if I wasn't using a Mac.

I tried test running 3 times yesterday and today, and for some reason it succeeded the first and third try but failed the second try.

Apple error log when it failed: https://paste.ubuntu.com/p/wQ23NqCZys/ (apparent correction - thread 9 was the one that crashed, not 7)
Wineskin test log (on 3rd try): https://paste.ubuntu.com/p/2jvXyT7yhg/

If the links don't work or something else is wrong in this post, please let me know because I'm confused too!

Please do not enable Compatibility Mode as it crashes osu! on macOS (as you have found out). If you re-download the Wineskin or re-run the osu!macOS Agent repair it should fix it for you (although you seem to have gotten it somewhat working?).

... hang on, are you using Big Sur on an M1 processor? The Apple crash report says an illegal instruction was executed which makes me wonder if there's a bug in the instruction translations for Rosetta or if there's some shenanigans with 32 bit 64 bit stuff.

Nylo23 wrote:

Yeah so i know im like 6 months late but this problem is that when eer im clicking on a slider in a song the sensitivity goes down, i may just be a new player not knowing how to fix this but im not quite sure how to fix it

Wineskin-2.9.0.7-rc4

This new wrapper will function under Rosetta2, included the custom MoltenVK needed for DXVK support.

WineCX19 based engine are functional on Apple Silicon.
Known limitations (Apple Silicon)

direct draw (fails)
Direct3D (fails)

To work around these issues cnc-ddraw and DxWnd can be used to launch titles that uses these. This may be resolved in a later crossover-wine version if thats happens I’ll lock Rosetta2 support to that version or greater.

AnimatedThinks wrote:

Technocoder wrote:

AnimatedThinks

AnimatedThinks wrote:

so... osu! randomly decided to work when I clicked to Test Run on Wineskin.
(image here: https://ibb.co/ry3tPwy)

These were the test logs, by the way.

Test Run

err:thread:get_image_addr dyld image info is above 4GB limit for 32-bit-on-64-bit process
000b:fixme:thread:create_user_shared_data_thread Creating user shared data update thread.
000d:fixme:thread:create_user_shared_data_thread Creating user shared data update thread.
0010:fixme:thread:create_user_shared_data_thread Creating user shared data update thread.
0018:fixme:thread:create_user_shared_data_thread Creating user shared data update thread.
001d:fixme:thread:create_user_shared_data_thread Creating user shared data update thread.
0009:fixme:exec:SHELL_execute flags ignored: 0x00000100
err:thread:get_image_addr dyld image info is above 4GB limit for 32-bit-on-64-bit process
err:thread:get_image_addr dyld image info is above 4GB limit for 32-bit-on-64-bit process
002a:fixme:thread:create_user_shared_data_thread Creating user shared data update thread.

Then everything went downhill

I was getting 40-50 fps even when plugged into charger, so I tried to see if turning on Compatibility Mode would help.
osu! crashed when restarting!! The error said something about graphics drivers but I forgot to screenshot it, but it did make me google possible fixes.
A fix I saw said to go to the osu.cfg file and change what was in the _ReleaseStream line to Stable. (It was at Stable40, so I changed it to Stable.) This didn't help, and osu! now showed a different error that looked like this: https://ibb.co/YXjP511 (Reversing the change back to Stable40 doesn't change anything, same error)
When I click yes, it sends me to a Microsoft page that says to download a .exe file that would probably help if I wasn't using a Mac.

I tried test running 3 times yesterday and today, and for some reason it succeeded the first and third try but failed the second try.

Apple error log when it failed: https://paste.ubuntu.com/p/wQ23NqCZys/ (apparent correction - thread 9 was the one that crashed, not 7)
Wineskin test log (on 3rd try): https://paste.ubuntu.com/p/2jvXyT7yhg/

If the links don't work or something else is wrong in this post, please let me know because I'm confused too!

Please do not enable Compatibility Mode as it crashes osu! on macOS (as you have found out). If you re-download the Wineskin or re-run the osu!macOS Agent repair it should fix it for you (although you seem to have gotten it somewhat working?).

... hang on, are you using Big Sur on an M1 processor? The Apple crash report says an illegal instruction was executed which makes me wonder if there's a bug in the instruction translations for Rosetta or if there's some shenanigans with 32 bit 64 bit stuff.

I disabled Compatibility Mode using the macOS agent (which I totally forgot about, thanks!) That's fixed but osu! is still not opening, showing the same graphics context error. The agent did say there were "Errors in update.log". Report below;

Report

Version 10.16 (Build 20C69)
Engine: WS11WineCX64Bit19.0.1-1
Wineskin 2.9.0.6 1
Release: Stable40
Quarantine attribute is absent
Execute flag is present
Detect Direct3D is enabled
Compatibility mode is disabled
System Integrity Protection is enabled
Engine version is supported
Razer Synapse is absent
[Warning] Errors in: update.log
2021-01-14T00:14:49: _pending\osu!.exe => osu!.exe: FAIL
No errors in: runtime.log

Edit: Yeah, I am using Big Sur on an M1 processor.

AnimatedThinks wrote:

aidswidjaja wrote:

AnimatedThinks

AnimatedThinks wrote:

Technocoder wrote:

AnimatedThinks

AnimatedThinks wrote:

so... osu! randomly decided to work when I clicked to Test Run on Wineskin.
(image here: https://ibb.co/ry3tPwy)

These were the test logs, by the way.

Test Run

err:thread:get_image_addr dyld image info is above 4GB limit for 32-bit-on-64-bit process
000b:fixme:thread:create_user_shared_data_thread Creating user shared data update thread.
000d:fixme:thread:create_user_shared_data_thread Creating user shared data update thread.
0010:fixme:thread:create_user_shared_data_thread Creating user shared data update thread.
0018:fixme:thread:create_user_shared_data_thread Creating user shared data update thread.
001d:fixme:thread:create_user_shared_data_thread Creating user shared data update thread.
0009:fixme:exec:SHELL_execute flags ignored: 0x00000100
err:thread:get_image_addr dyld image info is above 4GB limit for 32-bit-on-64-bit process
err:thread:get_image_addr dyld image info is above 4GB limit for 32-bit-on-64-bit process
002a:fixme:thread:create_user_shared_data_thread Creating user shared data update thread.

Then everything went downhill

I was getting 40-50 fps even when plugged into charger, so I tried to see if turning on Compatibility Mode would help.
osu! crashed when restarting!! The error said something about graphics drivers but I forgot to screenshot it, but it did make me google possible fixes.
A fix I saw said to go to the osu.cfg file and change what was in the _ReleaseStream line to Stable. (It was at Stable40, so I changed it to Stable.) This didn't help, and osu! now showed a different error that looked like this: https://ibb.co/YXjP511 (Reversing the change back to Stable40 doesn't change anything, same error)
When I click yes, it sends me to a Microsoft page that says to download a .exe file that would probably help if I wasn't using a Mac.

I tried test running 3 times yesterday and today, and for some reason it succeeded the first and third try but failed the second try.

Apple error log when it failed: https://paste.ubuntu.com/p/wQ23NqCZys/ (apparent correction - thread 9 was the one that crashed, not 7)
Wineskin test log (on 3rd try): https://paste.ubuntu.com/p/2jvXyT7yhg/

If the links don't work or something else is wrong in this post, please let me know because I'm confused too!

Please do not enable Compatibility Mode as it crashes osu! on macOS (as you have found out). If you re-download the Wineskin or re-run the osu!macOS Agent repair it should fix it for you (although you seem to have gotten it somewhat working?).

... hang on, are you using Big Sur on an M1 processor? The Apple crash report says an illegal instruction was executed which makes me wonder if there's a bug in the instruction translations for Rosetta or if there's some shenanigans with 32 bit 64 bit stuff.

I disabled Compatibility Mode using the macOS agent (which I totally forgot about, thanks!) That's fixed but osu! is still not opening, showing the same graphics context error. The agent did say there were "Errors in update.log". Report below;

Report

Version 10.16 (Build 20C69)
Engine: WS11WineCX64Bit19.0.1-1
Wineskin 2.9.0.6 1
Release: Stable40
Quarantine attribute is absent
Execute flag is present
Detect Direct3D is enabled
Compatibility mode is disabled
System Integrity Protection is enabled
Engine version is supported
Razer Synapse is absent
[Warning] Errors in: update.log
2021-01-14T00:14:49: _pending\osu!.exe => osu!.exe: FAIL
No errors in: runtime.log

Edit: Yeah, I am using Big Sur on an M1 processor.

Could you try clicking Update in the Other tab? Thanks

I opened the agent and hit Update in the Other tab.
I think it's more broken now uhh

Report

Version 10.16 (Build 20C69)
Engine: WS11WineCX64Bit19.0.1-1
Wineskin 2.9.0.6 1
Release: Stable40
Quarantine attribute is absent
Execute flag is present
Detect Direct3D is enabled
Compatibility mode is disabled
System Integrity Protection is enabled
Engine version is supported
Razer Synapse is absent
[Warning] Errors in: update.log
2021-01-14T00:14:49: _pending\osu!.exe => osu!.exe: FAIL
2021-01-20T02:48:04: _pending\bass.dll => bass.dll: FAIL
2021-01-20T02:48:04: _pending\osu!gameplay.dll => osu!gameplay.dll: FAIL
2021-01-20T02:48:04: _pending\osu!ui.dll => osu!ui.dll: FAIL
2021-01-20T02:51:22: osu!.exe: MISMATCH
2021-01-20T02:52:17: _pending\bass.dll => bass.dll: FAIL
2021-01-20T02:52:18: _pending\osu!gameplay.dll => osu!gameplay.dll: FAIL
2021-01-20T02:52:18: _pending\osu!ui.dll => osu!ui.dll: FAIL
No errors in: runtime.log

When I try to open osu! either through test running or opening it normally, it opens a white screen that sometimes disappears and sometimes doesn't (I have to manually close it out)

AnimatedThinks wrote:

aidswidjaja wrote:

AnimatedThinks

AnimatedThinks wrote:

aidswidjaja wrote:

AnimatedThinks

AnimatedThinks wrote:

Technocoder wrote:

AnimatedThinks

AnimatedThinks wrote:

so... osu! randomly decided to work when I clicked to Test Run on Wineskin.
(image here: https://ibb.co/ry3tPwy)

These were the test logs, by the way.

Test Run

err:thread:get_image_addr dyld image info is above 4GB limit for 32-bit-on-64-bit process
000b:fixme:thread:create_user_shared_data_thread Creating user shared data update thread.
000d:fixme:thread:create_user_shared_data_thread Creating user shared data update thread.
0010:fixme:thread:create_user_shared_data_thread Creating user shared data update thread.
0018:fixme:thread:create_user_shared_data_thread Creating user shared data update thread.
001d:fixme:thread:create_user_shared_data_thread Creating user shared data update thread.
0009:fixme:exec:SHELL_execute flags ignored: 0x00000100
err:thread:get_image_addr dyld image info is above 4GB limit for 32-bit-on-64-bit process
err:thread:get_image_addr dyld image info is above 4GB limit for 32-bit-on-64-bit process
002a:fixme:thread:create_user_shared_data_thread Creating user shared data update thread.

Then everything went downhill

I was getting 40-50 fps even when plugged into charger, so I tried to see if turning on Compatibility Mode would help.
osu! crashed when restarting!! The error said something about graphics drivers but I forgot to screenshot it, but it did make me google possible fixes.
A fix I saw said to go to the osu.cfg file and change what was in the _ReleaseStream line to Stable. (It was at Stable40, so I changed it to Stable.) This didn't help, and osu! now showed a different error that looked like this: https://ibb.co/YXjP511 (Reversing the change back to Stable40 doesn't change anything, same error)
When I click yes, it sends me to a Microsoft page that says to download a .exe file that would probably help if I wasn't using a Mac.

I tried test running 3 times yesterday and today, and for some reason it succeeded the first and third try but failed the second try.

Apple error log when it failed: https://paste.ubuntu.com/p/wQ23NqCZys/ (apparent correction - thread 9 was the one that crashed, not 7)
Wineskin test log (on 3rd try): https://paste.ubuntu.com/p/2jvXyT7yhg/

If the links don't work or something else is wrong in this post, please let me know because I'm confused too!

Please do not enable Compatibility Mode as it crashes osu! on macOS (as you have found out). If you re-download the Wineskin or re-run the osu!macOS Agent repair it should fix it for you (although you seem to have gotten it somewhat working?).

... hang on, are you using Big Sur on an M1 processor? The Apple crash report says an illegal instruction was executed which makes me wonder if there's a bug in the instruction translations for Rosetta or if there's some shenanigans with 32 bit 64 bit stuff.

I disabled Compatibility Mode using the macOS agent (which I totally forgot about, thanks!) That's fixed but osu! is still not opening, showing the same graphics context error. The agent did say there were "Errors in update.log". Report below;

Report

Version 10.16 (Build 20C69)
Engine: WS11WineCX64Bit19.0.1-1
Wineskin 2.9.0.6 1
Release: Stable40
Quarantine attribute is absent
Execute flag is present
Detect Direct3D is enabled
Compatibility mode is disabled
System Integrity Protection is enabled
Engine version is supported
Razer Synapse is absent
[Warning] Errors in: update.log
2021-01-14T00:14:49: _pending\osu!.exe => osu!.exe: FAIL
No errors in: runtime.log

Edit: Yeah, I am using Big Sur on an M1 processor.

Could you try clicking Update in the Other tab? Thanks

I opened the agent and hit Update in the Other tab.
I think it's more broken now uhh

Report

Version 10.16 (Build 20C69)
Engine: WS11WineCX64Bit19.0.1-1
Wineskin 2.9.0.6 1
Release: Stable40
Quarantine attribute is absent
Execute flag is present
Detect Direct3D is enabled
Compatibility mode is disabled
System Integrity Protection is enabled
Engine version is supported
Razer Synapse is absent
[Warning] Errors in: update.log
2021-01-14T00:14:49: _pending\osu!.exe => osu!.exe: FAIL
2021-01-20T02:48:04: _pending\bass.dll => bass.dll: FAIL
2021-01-20T02:48:04: _pending\osu!gameplay.dll => osu!gameplay.dll: FAIL
2021-01-20T02:48:04: _pending\osu!ui.dll => osu!ui.dll: FAIL
2021-01-20T02:51:22: osu!.exe: MISMATCH
2021-01-20T02:52:17: _pending\bass.dll => bass.dll: FAIL
2021-01-20T02:52:18: _pending\osu!gameplay.dll => osu!gameplay.dll: FAIL
2021-01-20T02:52:18: _pending\osu!ui.dll => osu!ui.dll: FAIL
No errors in: runtime.log

When I try to open osu! either through test running or opening it normally, it opens a white screen that sometimes disappears and sometimes doesn't (I have to manually close it out)

Oh gosh, that doesn't look good :/ seems a lot of your files are corrupted somehow during some sort of update? - I think the easiest option here might be to do a full clean reinstall, but if you're not keen on doing that then if you can send me a screenie of your directory `osu!.app/drive_c/osu!` then I can probably point out which files you need to delete and which you need to replace.

Example screenie: https://gyazo.com/48c1ef5a9985c918963b409c784f43c7

But yea as I mentioned, might just be easier to transfer your data to a clean wrapper. Make sure you back your data up first! Largely the same as in Windows but if you need steps: https://osu-mac.readthedocs.io/en/latest/welcome/transfer.html#transferring-from-a-different-osu-wineskin - though don't replace your drive_c directory entirely (only the Scores, beatmaps, etc) since the install is corrupted.

I've never had the issue of compatibility mode corrupting an install (usually it goes away once I re-disable the option) but in your case I'm going to take a guess that compatibility mode crashed osu! while it was in the middle of an update. erp~

https://ibb.co/qM6wznY Here's a screenshot of my drive_c/osu! directory, I think it might be better/easier for me to do it this way.
Also, I didn't realize yesterday because I wasn't wearing my headphones, but osu! does play the music when opened, it just doesn't show anything besides the white screen.

1. pending
2. avcodec-51.dll
3. avformat-52.dll
4. avutil-49.dll
5. bass_fx.dll
6. bass.dll
   Do NOT delete bridge.exe
   Do NOT delete collection.db
7. d3dcompiler_47.dll
   Do NOT delete Data folder
   discord_rpc.dll I believe is deprecated so it will be removed by osu! anyway
   It is safe to leave the Downloads folder
   Do NOT delete execute.bat
8. libEGL.dll
9. libGLESv2.dll
   Do NOT delete Logs folder
10. Microsoft.Ink.dll
11. OpenTK.dll
    Do NOT delete osu!.user.cfg (if this file exists) unless you are fine to revert to default settings
12. osu!.cfg
    Do NOT delete osu!.crossover.cfg unless you are fine to revert to default settings
    You can delete osu!.db to refresh the cache of your beatmaps
13. osu!.exe
14. osu!auth.dll
15. osu!gameplay.dll
16. osu!ui.dll
    Do NOT delete presence.db
17. pthreadGC2.dll
    Do NOT delete scores.db
    Do NOT delete Screenshots, Skins or Songs folder.
    
    tl:dr; leave all db, bat, cfg files and folders intact.

gravitybalmain wrote:

Hey all! Thanks for all your hard work in fixing this -- unfortunately, I'm still experiencing the same issues as before. Here's a copy of my initial report upon first repairing with osu!macOS Agent

Report

Version 11.0.1 (Build 20B29)
Engine: WS11WineCX64Bit20.0.0
Wineskin 2.9.0.7-rc4
Release: Stable40
[Error][Fixed] Quarantine attribute is present (bundle)
[Error][Fixed] Quarantine attribute is present (wrapper)
Execute flag is present
Detect Direct3D is enabled
Game user configuration is absent
System Integrity Protection is enabled
Engine version is supported
Razer Synapse is absent
Log file: update.log is absent
Log file: runtime.log is absent

Upon opening osu! afterwards, the previous issue of the terminal popping up and two lines of code appearing before immediately shutting again occurred. Right clicking osu and opening the wineskin works now, but upon clicking test run it force quits and generates an Apple Report error (below).

error

https://paste.ubuntu.com/p/yh5Kf8qd52/

cd ../../osu!
echo %CD%              # this command should print C:\
osu!.exe