zoko91
Sounds great! Thanks for sharing your setup too~zoko91 wrote:
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 !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.zoko91In 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 infozoko91 wrote:
HelloI 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
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.
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
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.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
Hi there! Could you please copy and paste your osu!macOS Agent report (https://osu-mac.readthedocs.io/en/latest/issues/troubleshooting.html#generating-a-report-with-osu-macos-agent) and make a Test Run with Wineskin (https://osu-mac.readthedocs.io/en/latest/issues/troubleshooting.html#generating-logs-for-wineskin) - thanks!speko wrote:
The game only works the first time after downloading, after exiting the game and reopening, nothing happens.
If you're experiencing the same error as gravity, please see below for more.
gravitybalmain
Thanks for your super detailed explanation!gravitybalmain wrote:
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.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.gravitybalmainerr, 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:gravitybalmain wrote:
I did the above steps!aidswidjaja wrote:
gravitybalmaingravitybalmain wrote:
Sure. Here's the log.aidswidjaja wrote:
gravitybalmaingravitybalmain 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!ReportVersion 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.log1
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:------
- 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.
- 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- 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
- 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.
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.
- 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.
1. Downloaded latest wineskin. Extracted using The Unarchiver.
2. Downloaded osu!macOS Agent, extracted and opened, scanned and repaired.
Report:Report3. Double clicked Osu! to open: Wineskin briefly flashes open, then immediately closes. See image: https://imgur.com/a/OvoTurKVersion 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
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.
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.
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 may try and do an install on my sister's laptop (which is a M1 MBA) but that might take a while to do.
thanks everyone