I don't know much about this but I don't know what you mean about start C:\osu!\bridge.exe and start C:\osu!\osu!.exe being in execute.bat. I can see three papers named execute.bat, bridge.exe, and osu!.exe
Could you make sure thatoblicue wrote: 5d5a5h
When i try the osu! wineskin.app, i get the error
"Error while writting file: The folder “exec814803833.bat” doesn’t exist."
So basically, execute.bat is a text file which should contain two lines.TLXlayer wrote: 2s3j32
I don't know much about this but I don't know what you mean about start C:\osu!\bridge.exe and start C:\osu!\osu!.exe being in execute.bat. I can see three papers named execute.bat, bridge.exe, and osu!.exe
I reinstalled, but the wineskin still didn't work, then I installed Wineskin.app manually. That seems to have worked, and I have opened it. I don't have an antivirus and definitely used The Unarchiver. I followed the steps to configure a windows program to open a file (which the properties look like they've worked) , but when I open a .osz or .osk file, I get the same error.aidswidjaja wrote: 4a1ul
Could you make sure thatoblicue wrote: 5d5a5h
When i try the osu! wineskin.app, i get the error
"Error while writting file: The folder “exec814803833.bat” doesn’t exist."
1. You unzip the file using The Unarchiver instead of the default Archive Utility on macOS. I think someone else said that it caused problems.
2. Make sure there are no antivirus software interfering with your installation
(community/forums/posts/7756236)
You might need to reinstall it afterwards. You can also try installing Wineskin.app manually (community/forums/posts/7793479) but I doubt that would work if your install is corrupted.
So basically, execute.bat is a text file which should contain two lines.TLXlayer wrote: 2s3j32
I don't know much about this but I don't know what you mean about start C:\osu!\bridge.exe and start C:\osu!\osu!.exe being in execute.bat. I can see three papers named execute.bat, bridge.exe, and osu!.exe
You also want to make sure that Wineskin.app points to this file in the Windows EXE field.
And you mentioned that you could only see execute.bat, bridge.exe, and osu!.exe in your osu! folder? For reference this is what my folder setup looks like.
If there are only three files there, it could be possible that an antivirus is removing your dll files or something. So just make sure that you've also followed the guidelines I sent to oblicue above which you can follow if the first guidelines I gave you don't work.
Hope this helps everyone![]()
I did another fresh reinstall, ed your wineskin from google drive, and made sure in the Windows EXE section it had execute.bat, yet it still has the same error. I have SIP disabled, so unless having it off is interfering with it, there is nothing I can see wrong.oblicue wrote: 5d5a5h
I reinstalled, but the wineskin still didn't work, then I installed Wineskin.app manually. That seems to have worked, and I have opened it. I don't have an antivirus and definitely used The Unarchiver. I followed the steps to configure a windows program to open a file (which the properties look like they've worked) , but when I open a .osz or .osk file, I get the same error.aidswidjaja wrote: 4a1ul
Could you make sure thatoblicue wrote: 5d5a5h
When i try the osu! wineskin.app, i get the error
"Error while writting file: The folder “exec814803833.bat” doesn’t exist."
1. You unzip the file using The Unarchiver instead of the default Archive Utility on macOS. I think someone else said that it caused problems.
2. Make sure there are no antivirus software interfering with your installation
(community/forums/posts/7756236)
You might need to reinstall it afterwards. You can also try installing Wineskin.app manually (community/forums/posts/7793479) but I doubt that would work if your install is corrupted.
So basically, execute.bat is a text file which should contain two lines.TLXlayer wrote: 2s3j32
I don't know much about this but I don't know what you mean about start C:\osu!\bridge.exe and start C:\osu!\osu!.exe being in execute.bat. I can see three papers named execute.bat, bridge.exe, and osu!.exe
You also want to make sure that Wineskin.app points to this file in the Windows EXE field.
And you mentioned that you could only see execute.bat, bridge.exe, and osu!.exe in your osu! folder? For reference this is what my folder setup looks like.
If there are only three files there, it could be possible that an antivirus is removing your dll files or something. So just make sure that you've also followed the guidelines I sent to oblicue above which you can follow if the first guidelines I gave you don't work.
Hope this helps everyone![]()
https://gyazo.com/6a0a45296a8dc07deca0e9c66983a3f6 Here is a screenshot of my "Advanced" settings in the osu wineskin. I have all the file types in the dropdown menu.
oblicue wrote: 5d5a5h
I reinstalled, but the wineskin still didn't work, then I installed Wineskin.app manually. That seems to have worked, and I have opened it. I don't have an antivirus and definitely used The Unarchiver. I followed the steps to configure a windows program to open a file (which the properties look like they've worked) , but when I open a .osz or .osk file, I get the same error.aidswidjaja wrote: 4a1ul
Could you make sure thatoblicue wrote: 5d5a5h
When i try the osu! wineskin.app, i get the error
"Error while writting file: The folder “exec814803833.bat” doesn’t exist."
1. You unzip the file using The Unarchiver instead of the default Archive Utility on macOS. I think someone else said that it caused problems.
2. Make sure there are no antivirus software interfering with your installation
(community/forums/posts/7756236)
You might need to reinstall it afterwards. You can also try installing Wineskin.app manually (community/forums/posts/7793479) but I doubt that would work if your install is corrupted.
So basically, execute.bat is a text file which should contain two lines.TLXlayer wrote: 2s3j32
I don't know much about this but I don't know what you mean about start C:\osu!\bridge.exe and start C:\osu!\osu!.exe being in execute.bat. I can see three papers named execute.bat, bridge.exe, and osu!.exe
You also want to make sure that Wineskin.app points to this file in the Windows EXE field.
And you mentioned that you could only see execute.bat, bridge.exe, and osu!.exe in your osu! folder? For reference this is what my folder setup looks like.
If there are only three files there, it could be possible that an antivirus is removing your dll files or something. So just make sure that you've also followed the guidelines I sent to oblicue above which you can follow if the first guidelines I gave you don't work.
Hope this helps everyone![]()
https://gyazo.com/6a0a45296a8dc07deca0e9c66983a3f6 Here is a screenshot of my "Advanced" settings in the osu wineskin. I have all the file types in the dropdown menu.
To your changes:
6. Click Tools, then click Command Line (cmd). A console-like should open (it takes a while tho)
7. Type explorer.exe
8. Navigate to My Computer\osu!\Songs and locate the osz beatmap you just dropped
9. Right click on the file, click Properties and it worked. It should look like the image below.
https://gyazo.com/b6282b14ef06ea96d760d2c6cfc4d2ed
Tuxedo23 wrote: 1q7234
I came to this thread to find out myself if it works on Big Sur, hahaoblicue wrote: 5d5a5h
got this working on big sur
Either way, how does the app run on Big Sur? Does it run better than Intel-based macs? Which runs better; crossover through Rosetta or MacOS osu! Agent?
Oblivous wrote: 246345
I come back.
AND I DON'T UNDERSTAND ANYTHING THAT IS GOING ON ANYMORE.
aidswidjaja wrote: 4a1ul
oblicueoblicue wrote: 5d5a5h
I reinstalled, but the wineskin still didn't work, then I installed Wineskin.app manually. That seems to have worked, and I have opened it. I don't have an antivirus and definitely used The Unarchiver. I followed the steps to configure a windows program to open a file (which the properties look like they've worked) , but when I open a .osz or .osk file, I get the same error.aidswidjaja wrote: 4a1ul
Could you make sure thatoblicue wrote: 5d5a5h
When i try the osu! wineskin.app, i get the error
"Error while writting file: The folder “exec814803833.bat” doesn’t exist."
1. You unzip the file using The Unarchiver instead of the default Archive Utility on macOS. I think someone else said that it caused problems.
2. Make sure there are no antivirus software interfering with your installation
(community/forums/posts/7756236)
You might need to reinstall it afterwards. You can also try installing Wineskin.app manually (community/forums/posts/7793479) but I doubt that would work if your install is corrupted.
So basically, execute.bat is a text file which should contain two lines.TLXlayer wrote: 2s3j32
I don't know much about this but I don't know what you mean about start C:\osu!\bridge.exe and start C:\osu!\osu!.exe being in execute.bat. I can see three papers named execute.bat, bridge.exe, and osu!.exe
You also want to make sure that Wineskin.app points to this file in the Windows EXE field.
And you mentioned that you could only see execute.bat, bridge.exe, and osu!.exe in your osu! folder? For reference this is what my folder setup looks like.
If there are only three files there, it could be possible that an antivirus is removing your dll files or something. So just make sure that you've also followed the guidelines I sent to oblicue above which you can follow if the first guidelines I gave you don't work.
Hope this helps everyone![]()
https://gyazo.com/6a0a45296a8dc07deca0e9c66983a3f6 Here is a screenshot of my "Advanced" settings in the osu wineskin. I have all the file types in the dropdown menu.
Can you take a screenshot of the error message you receive as well as the Properties pane
To your changes:
6. Click Tools, then click Command Line (cmd). A console-like should open (it takes a while tho)
7. Type explorer.exe
8. Navigate to My Computer\osu!\Songs and locate the osz beatmap you just dropped
9. Right click on the file, click Properties and it worked. It should look like the image below.
https://gyazo.com/b6282b14ef06ea96d760d2c6cfc4d2edTuxedo23Tuxedo23 wrote: 1q7234
I came to this thread to find out myself if it works on Big Sur, hahaoblicue wrote: 5d5a5h
got this working on big sur
Either way, how does the app run on Big Sur? Does it run better than Intel-based macs? Which runs better; crossover through Rosetta or MacOS osu! Agent?
I found slc's Wineskin was more stable but obviously that is pre-Catalina only and Techno's Catalina< Wineskin uses the WS11 engines that have wine32on64 (basically in a nutshell: adds more dependencies and complexities since we're trying to run 32bit code on 64bit only hardware)
In general, I found that Techno's Wineskin has a few performance issues on Big Sur compared to Mojave on a 2016 MBP Intel i5. I think others reported a few issues too? But generally speaking it's tolerable and I still play on Wineskin.
I don't know if the M1 Macs have been tested yet (or if they even work at all). I don't really know what you mean by running through Rosetta/Crossover/Agent however I don't know whether Rosetta 2 will Wineskin/Wine. However the folks at Crossover might have found a solution already.
ObliviousOblivous wrote: 246345
I come back.
AND I DON'T UNDERSTAND ANYTHING THAT IS GOING ON ANYMORE.
Haha lol I'm trying to keep track of all the questions as well... but please feel free to help out as well since I think Techno's on hiatus
I'll try updating the FAQ on https://osu-mac.readthedocs.io/en/latest/issues/index.html, maybe provide some bbcode templates and work through formatting issues on the site today so that I can address these issues faster without jumping through forum threads as well.
And that reminds me, if you did mention an issue please please please follow up on it and someone here should be able to help you - otherwise we'll forget about it
Note to future people about Wineskin.app I've just realised that if you haven't ran the Repair tool on osu!macOS Agent that your Wineskin.app might not be able to run (even if osu! does) - so do that first before any other troubleshooting methods I might have mentioned above
oblicue wrote: 5d5a5h
aidswidjajaaidswidjaja wrote: 4a1ul
oblicueoblicue wrote: 5d5a5h
I reinstalled, but the wineskin still didn't work, then I installed Wineskin.app manually. That seems to have worked, and I have opened it. I don't have an antivirus and definitely used The Unarchiver. I followed the steps to configure a windows program to open a file (which the properties look like they've worked) , but when I open a .osz or .osk file, I get the same error.aidswidjaja wrote: 4a1ul
Could you make sure thatoblicue wrote: 5d5a5h
When i try the osu! wineskin.app, i get the error
"Error while writting file: The folder “exec814803833.bat” doesn’t exist."
1. You unzip the file using The Unarchiver instead of the default Archive Utility on macOS. I think someone else said that it caused problems.
2. Make sure there are no antivirus software interfering with your installation
(community/forums/posts/7756236)
You might need to reinstall it afterwards. You can also try installing Wineskin.app manually (community/forums/posts/7793479) but I doubt that would work if your install is corrupted.
So basically, execute.bat is a text file which should contain two lines.TLXlayer wrote: 2s3j32
I don't know much about this but I don't know what you mean about start C:\osu!\bridge.exe and start C:\osu!\osu!.exe being in execute.bat. I can see three papers named execute.bat, bridge.exe, and osu!.exe
You also want to make sure that Wineskin.app points to this file in the Windows EXE field.
And you mentioned that you could only see execute.bat, bridge.exe, and osu!.exe in your osu! folder? For reference this is what my folder setup looks like.
If there are only three files there, it could be possible that an antivirus is removing your dll files or something. So just make sure that you've also followed the guidelines I sent to oblicue above which you can follow if the first guidelines I gave you don't work.
Hope this helps everyone![]()
https://gyazo.com/6a0a45296a8dc07deca0e9c66983a3f6 Here is a screenshot of my "Advanced" settings in the osu wineskin. I have all the file types in the dropdown menu.
Can you take a screenshot of the error message you receive as well as the Properties pane
To your changes:
6. Click Tools, then click Command Line (cmd). A console-like should open (it takes a while tho)
7. Type explorer.exe
8. Navigate to My Computer\osu!\Songs and locate the osz beatmap you just dropped
9. Right click on the file, click Properties and it worked. It should look like the image below.
https://gyazo.com/b6282b14ef06ea96d760d2c6cfc4d2edTuxedo23Tuxedo23 wrote: 1q7234
I came to this thread to find out myself if it works on Big Sur, hahaoblicue wrote: 5d5a5h
got this working on big sur
Either way, how does the app run on Big Sur? Does it run better than Intel-based macs? Which runs better; crossover through Rosetta or MacOS osu! Agent?
I found slc's Wineskin was more stable but obviously that is pre-Catalina only and Techno's Catalina< Wineskin uses the WS11 engines that have wine32on64 (basically in a nutshell: adds more dependencies and complexities since we're trying to run 32bit code on 64bit only hardware)
In general, I found that Techno's Wineskin has a few performance issues on Big Sur compared to Mojave on a 2016 MBP Intel i5. I think others reported a few issues too? But generally speaking it's tolerable and I still play on Wineskin.
I don't know if the M1 Macs have been tested yet (or if they even work at all). I don't really know what you mean by running through Rosetta/Crossover/Agent however I don't know whether Rosetta 2 will Wineskin/Wine. However the folks at Crossover might have found a solution already.
ObliviousOblivous wrote: 246345
I come back.
AND I DON'T UNDERSTAND ANYTHING THAT IS GOING ON ANYMORE.
Haha lol I'm trying to keep track of all the questions as well... but please feel free to help out as well since I think Techno's on hiatus
I'll try updating the FAQ on https://osu-mac.readthedocs.io/en/latest/issues/index.html, maybe provide some bbcode templates and work through formatting issues on the site today so that I can address these issues faster without jumping through forum threads as well.
And that reminds me, if you did mention an issue please please please follow up on it and someone here should be able to help you - otherwise we'll forget about it
Note to future people about Wineskin.app I've just realised that if you haven't ran the Repair tool on osu!macOS Agent that your Wineskin.app might not be able to run (even if osu! does) - so do that first before any other troubleshooting methods I might have mentioned above
Here are the screenshots:
https://gyazo.com/37de9997646aa92e0f585052c1cbf33d
https://gyazo.com/a7db9712a250d35901b2bfccc77ac19c
https://gyazo.com/4e5cd49aa1e9bcd3d4a706b6a7ece353
I am not sure which error you wanted, so I included when I try open the .osz and also when I open the old Wineskin.app
aidswidjaja wrote: 4a1ul
oblicueoblicue wrote: 5d5a5h
aidswidjajaaidswidjaja wrote: 4a1ul
oblicueoblicue wrote: 5d5a5h
I reinstalled, but the wineskin still didn't work, then I installed Wineskin.app manually. That seems to have worked, and I have opened it. I don't have an antivirus and definitely used The Unarchiver. I followed the steps to configure a windows program to open a file (which the properties look like they've worked) , but when I open a .osz or .osk file, I get the same error.aidswidjaja wrote: 4a1ul
Could you make sure thatoblicue wrote: 5d5a5h
When i try the osu! wineskin.app, i get the error
"Error while writting file: The folder “exec814803833.bat” doesn’t exist."
1. You unzip the file using The Unarchiver instead of the default Archive Utility on macOS. I think someone else said that it caused problems.
2. Make sure there are no antivirus software interfering with your installation
(community/forums/posts/7756236)
You might need to reinstall it afterwards. You can also try installing Wineskin.app manually (community/forums/posts/7793479) but I doubt that would work if your install is corrupted.
So basically, execute.bat is a text file which should contain two lines.TLXlayer wrote: 2s3j32
I don't know much about this but I don't know what you mean about start C:\osu!\bridge.exe and start C:\osu!\osu!.exe being in execute.bat. I can see three papers named execute.bat, bridge.exe, and osu!.exe
You also want to make sure that Wineskin.app points to this file in the Windows EXE field.
And you mentioned that you could only see execute.bat, bridge.exe, and osu!.exe in your osu! folder? For reference this is what my folder setup looks like.
If there are only three files there, it could be possible that an antivirus is removing your dll files or something. So just make sure that you've also followed the guidelines I sent to oblicue above which you can follow if the first guidelines I gave you don't work.
Hope this helps everyone![]()
https://gyazo.com/6a0a45296a8dc07deca0e9c66983a3f6 Here is a screenshot of my "Advanced" settings in the osu wineskin. I have all the file types in the dropdown menu.
Can you take a screenshot of the error message you receive as well as the Properties pane
To your changes:
6. Click Tools, then click Command Line (cmd). A console-like should open (it takes a while tho)
7. Type explorer.exe
8. Navigate to My Computer\osu!\Songs and locate the osz beatmap you just dropped
9. Right click on the file, click Properties and it worked. It should look like the image below.
https://gyazo.com/b6282b14ef06ea96d760d2c6cfc4d2edTuxedo23Tuxedo23 wrote: 1q7234
I came to this thread to find out myself if it works on Big Sur, hahaoblicue wrote: 5d5a5h
got this working on big sur
Either way, how does the app run on Big Sur? Does it run better than Intel-based macs? Which runs better; crossover through Rosetta or MacOS osu! Agent?
I found slc's Wineskin was more stable but obviously that is pre-Catalina only and Techno's Catalina< Wineskin uses the WS11 engines that have wine32on64 (basically in a nutshell: adds more dependencies and complexities since we're trying to run 32bit code on 64bit only hardware)
In general, I found that Techno's Wineskin has a few performance issues on Big Sur compared to Mojave on a 2016 MBP Intel i5. I think others reported a few issues too? But generally speaking it's tolerable and I still play on Wineskin.
I don't know if the M1 Macs have been tested yet (or if they even work at all). I don't really know what you mean by running through Rosetta/Crossover/Agent however I don't know whether Rosetta 2 will Wineskin/Wine. However the folks at Crossover might have found a solution already.
ObliviousOblivous wrote: 246345
I come back.
AND I DON'T UNDERSTAND ANYTHING THAT IS GOING ON ANYMORE.
Haha lol I'm trying to keep track of all the questions as well... but please feel free to help out as well since I think Techno's on hiatus
I'll try updating the FAQ on https://osu-mac.readthedocs.io/en/latest/issues/index.html, maybe provide some bbcode templates and work through formatting issues on the site today so that I can address these issues faster without jumping through forum threads as well.
And that reminds me, if you did mention an issue please please please follow up on it and someone here should be able to help you - otherwise we'll forget about it
Note to future people about Wineskin.app I've just realised that if you haven't ran the Repair tool on osu!macOS Agent that your Wineskin.app might not be able to run (even if osu! does) - so do that first before any other troubleshooting methods I might have mentioned above
Here are the screenshots:
https://gyazo.com/37de9997646aa92e0f585052c1cbf33d
https://gyazo.com/a7db9712a250d35901b2bfccc77ac19c
https://gyazo.com/4e5cd49aa1e9bcd3d4a706b6a7ece353
I am not sure which error you wanted, so I included when I try open the .osz and also when I open the old Wineskin.app
So I went back and tested this out - it looks like with the recent update to Techno's Wineskin I hadn't realised this method doesn't exactly work. Weirdly enough, if you open explorer.exe and then open the Wineskin through that window it will work.
I'll try and figure something out but in the meantime try using drag/drop into the osu! window as outlined here https://osu-mac.readthedocs.io/en/latest/welcome/import.html#drag-and-drop
I think you have a typo in your execute.bat file?Chanw11 wrote: 2j21p
I tried it on my MBA M1, doesnt seem to work. (After scanning and repairing) OSU app opens with a terminal
C:\osu!>start C:\osu!\bridge.exe
C:\osu!>start C:\osu!\osu!.exe -noplash
then it closes
C:\osu!>start C:\osu!\osu!.exe -noplashshould be
C:\osu!>start C:\osu!\osu!.exe -nosplash
Could you try doing a test run?twentyonekoalas wrote: 1o5e
Followed all the steps but osu! still won't open. Double-clicking the app doesn't do anything. OS version is Catalina 10.15.7.
ReportVersion 10.15.7 (Build 19H15)
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 configuration is absent
System Integrity Protection is enabled
Engine version is ed
Razer Synapse is absent
No errors in: update.log
Log file: runtime.log is absent
aidswidjaja wrote: 4a1ul
oblicueoblicue wrote: 5d5a5h
aidswidjajaaidswidjaja wrote: 4a1ul
oblicueoblicue wrote: 5d5a5h
I reinstalled, but the wineskin still didn't work, then I installed Wineskin.app manually. That seems to have worked, and I have opened it. I don't have an antivirus and definitely used The Unarchiver. I followed the steps to configure a windows program to open a file (which the properties look like they've worked) , but when I open a .osz or .osk file, I get the same error.aidswidjaja wrote: 4a1ul
Could you make sure thatoblicue wrote: 5d5a5h
When i try the osu! wineskin.app, i get the error
"Error while writting file: The folder “exec814803833.bat” doesn’t exist."
1. You unzip the file using The Unarchiver instead of the default Archive Utility on macOS. I think someone else said that it caused problems.
2. Make sure there are no antivirus software interfering with your installation
(community/forums/posts/7756236)
You might need to reinstall it afterwards. You can also try installing Wineskin.app manually (community/forums/posts/7793479) but I doubt that would work if your install is corrupted.
So basically, execute.bat is a text file which should contain two lines.TLXlayer wrote: 2s3j32
I don't know much about this but I don't know what you mean about start C:\osu!\bridge.exe and start C:\osu!\osu!.exe being in execute.bat. I can see three papers named execute.bat, bridge.exe, and osu!.exe
You also want to make sure that Wineskin.app points to this file in the Windows EXE field.
And you mentioned that you could only see execute.bat, bridge.exe, and osu!.exe in your osu! folder? For reference this is what my folder setup looks like.
If there are only three files there, it could be possible that an antivirus is removing your dll files or something. So just make sure that you've also followed the guidelines I sent to oblicue above which you can follow if the first guidelines I gave you don't work.
Hope this helps everyone![]()
https://gyazo.com/6a0a45296a8dc07deca0e9c66983a3f6 Here is a screenshot of my "Advanced" settings in the osu wineskin. I have all the file types in the dropdown menu.
Can you take a screenshot of the error message you receive as well as the Properties pane
To your changes:
6. Click Tools, then click Command Line (cmd). A console-like should open (it takes a while tho)
7. Type explorer.exe
8. Navigate to My Computer\osu!\Songs and locate the osz beatmap you just dropped
9. Right click on the file, click Properties and it worked. It should look like the image below.
https://gyazo.com/b6282b14ef06ea96d760d2c6cfc4d2edTuxedo23Tuxedo23 wrote: 1q7234
I came to this thread to find out myself if it works on Big Sur, hahaoblicue wrote: 5d5a5h
got this working on big sur
Either way, how does the app run on Big Sur? Does it run better than Intel-based macs? Which runs better; crossover through Rosetta or MacOS osu! Agent?
I found slc's Wineskin was more stable but obviously that is pre-Catalina only and Techno's Catalina< Wineskin uses the WS11 engines that have wine32on64 (basically in a nutshell: adds more dependencies and complexities since we're trying to run 32bit code on 64bit only hardware)
In general, I found that Techno's Wineskin has a few performance issues on Big Sur compared to Mojave on a 2016 MBP Intel i5. I think others reported a few issues too? But generally speaking it's tolerable and I still play on Wineskin.
I don't know if the M1 Macs have been tested yet (or if they even work at all). I don't really know what you mean by running through Rosetta/Crossover/Agent however I don't know whether Rosetta 2 will Wineskin/Wine. However the folks at Crossover might have found a solution already.
ObliviousOblivous wrote: 246345
I come back.
AND I DON'T UNDERSTAND ANYTHING THAT IS GOING ON ANYMORE.
Haha lol I'm trying to keep track of all the questions as well... but please feel free to help out as well since I think Techno's on hiatus
I'll try updating the FAQ on https://osu-mac.readthedocs.io/en/latest/issues/index.html, maybe provide some bbcode templates and work through formatting issues on the site today so that I can address these issues faster without jumping through forum threads as well.
And that reminds me, if you did mention an issue please please please follow up on it and someone here should be able to help you - otherwise we'll forget about it
Note to future people about Wineskin.app I've just realised that if you haven't ran the Repair tool on osu!macOS Agent that your Wineskin.app might not be able to run (even if osu! does) - so do that first before any other troubleshooting methods I might have mentioned above
Here are the screenshots:
https://gyazo.com/37de9997646aa92e0f585052c1cbf33d
https://gyazo.com/a7db9712a250d35901b2bfccc77ac19c
https://gyazo.com/4e5cd49aa1e9bcd3d4a706b6a7ece353
I am not sure which error you wanted, so I included when I try open the .osz and also when I open the old Wineskin.app
So I went back and tested this out - it looks like with the recent update to Techno's Wineskin I hadn't realised this method doesn't exactly work. Weirdly enough, if you open explorer.exe and then open the Wineskin through that window it will work.
I'll try and figure something out but in the meantime try using drag/drop into the osu! window as outlined here https://osu-mac.readthedocs.io/en/latest/welcome/import.html#drag-and-drop
C:\osu!\osu!.exe C:\osu!\Songs\YourBeatmapHere.oszin cmd somehow under the same prefix/instance. But Agent already achieves that so there's not really much point in creating another program to do that.
aidswidjaja wrote: 4a1ul
I think you have a typo in your execute.bat file?Chanw11 wrote: 2j21p
I tried it on my MBA M1, doesnt seem to work. (After scanning and repairing) OSU app opens with a terminal
C:\osu!>start C:\osu!\bridge.exe
C:\osu!>start C:\osu!\osu!.exe -noplash
then it closes
C:\osu!>start C:\osu!\osu!.exe -noplashshould be
C:\osu!>start C:\osu!\osu!.exe -nosplash
Note the -nosplash flag.
Edit: also please read https://github.com/Gcenx/WineskinServer#apple-silicon-device- and https://github.com/Gcenx/WineskinServer/issues/65
Could you try doing a test run?twentyonekoalas wrote: 1o5e
Followed all the steps but osu! still won't open. Double-clicking the app doesn't do anything. OS version is Catalina 10.15.7.
ReportVersion 10.15.7 (Build 19H15)
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 configuration is absent
System Integrity Protection is enabled
Engine version is ed
Razer Synapse is absent
No errors in: update.log
Log file: runtime.log is absent
Instructions here: https://osu-mac.readthedocs.io/en/latest/issues/troubleshooting.html#generating-logs-for-wineskin
With the logs, you can paste them to a pastebin like paste.ubuntu.com
Hope this helps everyone
aidswidjajaaidswidjaja wrote: 4a1ul
oblicueoblicue wrote: 5d5a5h
aidswidjajaaidswidjaja wrote: 4a1ul
oblicueoblicue wrote: 5d5a5h
I reinstalled, but the wineskin still didn't work, then I installed Wineskin.app manually. That seems to have worked, and I have opened it. I don't have an antivirus and definitely used The Unarchiver. I followed the steps to configure a windows program to open a file (which the properties look like they've worked) , but when I open a .osz or .osk file, I get the same error.aidswidjaja wrote: 4a1ul
Could you make sure thatoblicue wrote: 5d5a5h
When i try the osu! wineskin.app, i get the error
"Error while writting file: The folder “exec814803833.bat” doesn’t exist."
1. You unzip the file using The Unarchiver instead of the default Archive Utility on macOS. I think someone else said that it caused problems.
2. Make sure there are no antivirus software interfering with your installation
(community/forums/posts/7756236)
You might need to reinstall it afterwards. You can also try installing Wineskin.app manually (community/forums/posts/7793479) but I doubt that would work if your install is corrupted.
So basically, execute.bat is a text file which should contain two lines.TLXlayer wrote: 2s3j32
I don't know much about this but I don't know what you mean about start C:\osu!\bridge.exe and start C:\osu!\osu!.exe being in execute.bat. I can see three papers named execute.bat, bridge.exe, and osu!.exe
You also want to make sure that Wineskin.app points to this file in the Windows EXE field.
And you mentioned that you could only see execute.bat, bridge.exe, and osu!.exe in your osu! folder? For reference this is what my folder setup looks like.
If there are only three files there, it could be possible that an antivirus is removing your dll files or something. So just make sure that you've also followed the guidelines I sent to oblicue above which you can follow if the first guidelines I gave you don't work.
Hope this helps everyone![]()
https://gyazo.com/6a0a45296a8dc07deca0e9c66983a3f6 Here is a screenshot of my "Advanced" settings in the osu wineskin. I have all the file types in the dropdown menu.
Can you take a screenshot of the error message you receive as well as the Properties pane
To your changes:
6. Click Tools, then click Command Line (cmd). A console-like should open (it takes a while tho)
7. Type explorer.exe
8. Navigate to My Computer\osu!\Songs and locate the osz beatmap you just dropped
9. Right click on the file, click Properties and it worked. It should look like the image below.
https://gyazo.com/b6282b14ef06ea96d760d2c6cfc4d2edTuxedo23Tuxedo23 wrote: 1q7234
I came to this thread to find out myself if it works on Big Sur, hahaoblicue wrote: 5d5a5h
got this working on big sur
Either way, how does the app run on Big Sur? Does it run better than Intel-based macs? Which runs better; crossover through Rosetta or MacOS osu! Agent?
I found slc's Wineskin was more stable but obviously that is pre-Catalina only and Techno's Catalina< Wineskin uses the WS11 engines that have wine32on64 (basically in a nutshell: adds more dependencies and complexities since we're trying to run 32bit code on 64bit only hardware)
In general, I found that Techno's Wineskin has a few performance issues on Big Sur compared to Mojave on a 2016 MBP Intel i5. I think others reported a few issues too? But generally speaking it's tolerable and I still play on Wineskin.
I don't know if the M1 Macs have been tested yet (or if they even work at all). I don't really know what you mean by running through Rosetta/Crossover/Agent however I don't know whether Rosetta 2 will Wineskin/Wine. However the folks at Crossover might have found a solution already.
ObliviousOblivous wrote: 246345
I come back.
AND I DON'T UNDERSTAND ANYTHING THAT IS GOING ON ANYMORE.
Haha lol I'm trying to keep track of all the questions as well... but please feel free to help out as well since I think Techno's on hiatus
I'll try updating the FAQ on https://osu-mac.readthedocs.io/en/latest/issues/index.html, maybe provide some bbcode templates and work through formatting issues on the site today so that I can address these issues faster without jumping through forum threads as well.
And that reminds me, if you did mention an issue please please please follow up on it and someone here should be able to help you - otherwise we'll forget about it
Note to future people about Wineskin.app I've just realised that if you haven't ran the Repair tool on osu!macOS Agent that your Wineskin.app might not be able to run (even if osu! does) - so do that first before any other troubleshooting methods I might have mentioned above
Here are the screenshots:
https://gyazo.com/37de9997646aa92e0f585052c1cbf33d
https://gyazo.com/a7db9712a250d35901b2bfccc77ac19c
https://gyazo.com/4e5cd49aa1e9bcd3d4a706b6a7ece353
I am not sure which error you wanted, so I included when I try open the .osz and also when I open the old Wineskin.app
So I went back and tested this out - it looks like with the recent update to Techno's Wineskin I hadn't realised this method doesn't exactly work. Weirdly enough, if you open explorer.exe and then open the Wineskin through that window it will work.
I'll try and figure something out but in the meantime try using drag/drop into the osu! window as outlined here https://osu-mac.readthedocs.io/en/latest/welcome/import.html#drag-and-drop
dw, still working on this!
Ok so here's what I've found
After many hours of work scripting potential fixes and researching Wineskin I think the best alternative to Associated Extensions in Wine is Technocoder's osu!macOS Agent which can automatically move beatmaps to osu!. You can see this is an open issue on GitHub https://github.com/Gcenx/WineskinServer/issues/47 which would explain why a lot of people here are having trouble with that
In theory, you could move an osz to the osu! directory automatically and then trigger a refresh of it in Wineskin by somehow running
C:\osu!\osu!.exe C:\osu!\Songs\YourBeatmapHere.oszin cmd somehow under the same prefix/instance. But Agent already achieves that so there's not really much point in creating another program to do that.
For some reason winecfg doesn't work and I was hoping to modify the extensions through there. But anyway, that's all I've got. Sorry to everyone hoping for a better fix![]()
Turns out my antivirus software (that I completely forgot I had) was messing with it. Set my osu! folder as an exception so it wouldn't scan it, repeated the steps and I got osu! to start.aidswidjaja wrote: 4a1ul
I think you have a typo in your execute.bat file?Chanw11 wrote: 2j21p
I tried it on my MBA M1, doesnt seem to work. (After scanning and repairing) OSU app opens with a terminal
C:\osu!>start C:\osu!\bridge.exe
C:\osu!>start C:\osu!\osu!.exe -noplash
then it closes
C:\osu!>start C:\osu!\osu!.exe -noplashshould be
C:\osu!>start C:\osu!\osu!.exe -nosplash
Note the -nosplash flag.
Edit: also please read https://github.com/Gcenx/WineskinServer#apple-silicon-device- and https://github.com/Gcenx/WineskinServer/issues/65
Could you try doing a test run?twentyonekoalas wrote: 1o5e
Followed all the steps but osu! still won't open. Double-clicking the app doesn't do anything. OS version is Catalina 10.15.7.
ReportVersion 10.15.7 (Build 19H15)
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 configuration is absent
System Integrity Protection is enabled
Engine version is ed
Razer Synapse is absent
No errors in: update.log
Log file: runtime.log is absent
Instructions here: https://osu-mac.readthedocs.io/en/latest/issues/troubleshooting.html#generating-logs-for-wineskin
With the logs, you can paste them to a pastebin like paste.ubuntu.com
Hope this helps everyone
aidswidjajaaidswidjaja wrote: 4a1ul
oblicueoblicue wrote: 5d5a5h
aidswidjajaaidswidjaja wrote: 4a1ul
oblicueoblicue wrote: 5d5a5h
I reinstalled, but the wineskin still didn't work, then I installed Wineskin.app manually. That seems to have worked, and I have opened it. I don't have an antivirus and definitely used The Unarchiver. I followed the steps to configure a windows program to open a file (which the properties look like they've worked) , but when I open a .osz or .osk file, I get the same error.aidswidjaja wrote: 4a1ul
Could you make sure thatoblicue wrote: 5d5a5h
When i try the osu! wineskin.app, i get the error
"Error while writting file: The folder “exec814803833.bat” doesn’t exist."
1. You unzip the file using The Unarchiver instead of the default Archive Utility on macOS. I think someone else said that it caused problems.
2. Make sure there are no antivirus software interfering with your installation
(community/forums/posts/7756236)
You might need to reinstall it afterwards. You can also try installing Wineskin.app manually (community/forums/posts/7793479) but I doubt that would work if your install is corrupted.
So basically, execute.bat is a text file which should contain two lines.TLXlayer wrote: 2s3j32
I don't know much about this but I don't know what you mean about start C:\osu!\bridge.exe and start C:\osu!\osu!.exe being in execute.bat. I can see three papers named execute.bat, bridge.exe, and osu!.exe
You also want to make sure that Wineskin.app points to this file in the Windows EXE field.
And you mentioned that you could only see execute.bat, bridge.exe, and osu!.exe in your osu! folder? For reference this is what my folder setup looks like.
If there are only three files there, it could be possible that an antivirus is removing your dll files or something. So just make sure that you've also followed the guidelines I sent to oblicue above which you can follow if the first guidelines I gave you don't work.
Hope this helps everyone![]()
https://gyazo.com/6a0a45296a8dc07deca0e9c66983a3f6 Here is a screenshot of my "Advanced" settings in the osu wineskin. I have all the file types in the dropdown menu.
Can you take a screenshot of the error message you receive as well as the Properties pane
To your changes:
6. Click Tools, then click Command Line (cmd). A console-like should open (it takes a while tho)
7. Type explorer.exe
8. Navigate to My Computer\osu!\Songs and locate the osz beatmap you just dropped
9. Right click on the file, click Properties and it worked. It should look like the image below.
https://gyazo.com/b6282b14ef06ea96d760d2c6cfc4d2edTuxedo23Tuxedo23 wrote: 1q7234
I came to this thread to find out myself if it works on Big Sur, hahaoblicue wrote: 5d5a5h
got this working on big sur
Either way, how does the app run on Big Sur? Does it run better than Intel-based macs? Which runs better; crossover through Rosetta or MacOS osu! Agent?
I found slc's Wineskin was more stable but obviously that is pre-Catalina only and Techno's Catalina< Wineskin uses the WS11 engines that have wine32on64 (basically in a nutshell: adds more dependencies and complexities since we're trying to run 32bit code on 64bit only hardware)
In general, I found that Techno's Wineskin has a few performance issues on Big Sur compared to Mojave on a 2016 MBP Intel i5. I think others reported a few issues too? But generally speaking it's tolerable and I still play on Wineskin.
I don't know if the M1 Macs have been tested yet (or if they even work at all). I don't really know what you mean by running through Rosetta/Crossover/Agent however I don't know whether Rosetta 2 will Wineskin/Wine. However the folks at Crossover might have found a solution already.
ObliviousOblivous wrote: 246345
I come back.
AND I DON'T UNDERSTAND ANYTHING THAT IS GOING ON ANYMORE.
Haha lol I'm trying to keep track of all the questions as well... but please feel free to help out as well since I think Techno's on hiatus
I'll try updating the FAQ on https://osu-mac.readthedocs.io/en/latest/issues/index.html, maybe provide some bbcode templates and work through formatting issues on the site today so that I can address these issues faster without jumping through forum threads as well.
And that reminds me, if you did mention an issue please please please follow up on it and someone here should be able to help you - otherwise we'll forget about it
Note to future people about Wineskin.app I've just realised that if you haven't ran the Repair tool on osu!macOS Agent that your Wineskin.app might not be able to run (even if osu! does) - so do that first before any other troubleshooting methods I might have mentioned above
Here are the screenshots:
https://gyazo.com/37de9997646aa92e0f585052c1cbf33d
https://gyazo.com/a7db9712a250d35901b2bfccc77ac19c
https://gyazo.com/4e5cd49aa1e9bcd3d4a706b6a7ece353
I am not sure which error you wanted, so I included when I try open the .osz and also when I open the old Wineskin.app
So I went back and tested this out - it looks like with the recent update to Techno's Wineskin I hadn't realised this method doesn't exactly work. Weirdly enough, if you open explorer.exe and then open the Wineskin through that window it will work.
I'll try and figure something out but in the meantime try using drag/drop into the osu! window as outlined here https://osu-mac.readthedocs.io/en/latest/welcome/import.html#drag-and-drop
dw, still working on this!
Ok so here's what I've found
After many hours of work scripting potential fixes and researching Wineskin I think the best alternative to Associated Extensions in Wine is Technocoder's osu!macOS Agent which can automatically move beatmaps to osu!. You can see this is an open issue on GitHub https://github.com/Gcenx/WineskinServer/issues/47 which would explain why a lot of people here are having trouble with that
In theory, you could move an osz to the osu! directory automatically and then trigger a refresh of it in Wineskin by somehow running
C:\osu!\osu!.exe C:\osu!\Songs\YourBeatmapHere.oszin cmd somehow under the same prefix/instance. But Agent already achieves that so there's not really much point in creating another program to do that.
For some reason winecfg doesn't work and I was hoping to modify the extensions through there. But anyway, that's all I've got. Sorry to everyone hoping for a better fix![]()
twentyonekoalas wrote: 1o5e
aidswidjaja wrote: 4a1ul
I think you have a typo in your execute.bat file?Chanw11 wrote: 2j21p
I tried it on my MBA M1, doesnt seem to work. (After scanning and repairing) OSU app opens with a terminal
C:\osu!>start C:\osu!\bridge.exe
C:\osu!>start C:\osu!\osu!.exe -noplash
then it closes
C:\osu!>start C:\osu!\osu!.exe -noplashshould be
C:\osu!>start C:\osu!\osu!.exe -nosplash
Note the -nosplash flag.
Edit: also please read https://github.com/Gcenx/WineskinServer#apple-silicon-device- and https://github.com/Gcenx/WineskinServer/issues/65
Could you try doing a test run?twentyonekoalas wrote: 1o5e
Followed all the steps but osu! still won't open. Double-clicking the app doesn't do anything. OS version is Catalina 10.15.7.
ReportVersion 10.15.7 (Build 19H15)
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 configuration is absent
System Integrity Protection is enabled
Engine version is ed
Razer Synapse is absent
No errors in: update.log
Log file: runtime.log is absent
Instructions here: https://osu-mac.readthedocs.io/en/latest/issues/troubleshooting.html#generating-logs-for-wineskin
With the logs, you can paste them to a pastebin like paste.ubuntu.com
Hope this helps everyone
aidswidjajaaidswidjaja wrote: 4a1ul
oblicueoblicue wrote: 5d5a5h
aidswidjajaaidswidjaja wrote: 4a1ul
oblicueoblicue wrote: 5d5a5h
I reinstalled, but the wineskin still didn't work, then I installed Wineskin.app manually. That seems to have worked, and I have opened it. I don't have an antivirus and definitely used The Unarchiver. I followed the steps to configure a windows program to open a file (which the properties look like they've worked) , but when I open a .osz or .osk file, I get the same error.aidswidjaja wrote: 4a1ul
Could you make sure thatoblicue wrote: 5d5a5h
When i try the osu! wineskin.app, i get the error
"Error while writting file: The folder “exec814803833.bat” doesn’t exist."
1. You unzip the file using The Unarchiver instead of the default Archive Utility on macOS. I think someone else said that it caused problems.
2. Make sure there are no antivirus software interfering with your installation
(community/forums/posts/7756236)
You might need to reinstall it afterwards. You can also try installing Wineskin.app manually (community/forums/posts/7793479) but I doubt that would work if your install is corrupted.
So basically, execute.bat is a text file which should contain two lines.TLXlayer wrote: 2s3j32
I don't know much about this but I don't know what you mean about start C:\osu!\bridge.exe and start C:\osu!\osu!.exe being in execute.bat. I can see three papers named execute.bat, bridge.exe, and osu!.exe
You also want to make sure that Wineskin.app points to this file in the Windows EXE field.
And you mentioned that you could only see execute.bat, bridge.exe, and osu!.exe in your osu! folder? For reference this is what my folder setup looks like.
If there are only three files there, it could be possible that an antivirus is removing your dll files or something. So just make sure that you've also followed the guidelines I sent to oblicue above which you can follow if the first guidelines I gave you don't work.
Hope this helps everyone![]()
https://gyazo.com/6a0a45296a8dc07deca0e9c66983a3f6 Here is a screenshot of my "Advanced" settings in the osu wineskin. I have all the file types in the dropdown menu.
Can you take a screenshot of the error message you receive as well as the Properties pane
To your changes:
6. Click Tools, then click Command Line (cmd). A console-like should open (it takes a while tho)
7. Type explorer.exe
8. Navigate to My Computer\osu!\Songs and locate the osz beatmap you just dropped
9. Right click on the file, click Properties and it worked. It should look like the image below.
https://gyazo.com/b6282b14ef06ea96d760d2c6cfc4d2edTuxedo23Tuxedo23 wrote: 1q7234
I came to this thread to find out myself if it works on Big Sur, hahaoblicue wrote: 5d5a5h
got this working on big sur
Either way, how does the app run on Big Sur? Does it run better than Intel-based macs? Which runs better; crossover through Rosetta or MacOS osu! Agent?
I found slc's Wineskin was more stable but obviously that is pre-Catalina only and Techno's Catalina< Wineskin uses the WS11 engines that have wine32on64 (basically in a nutshell: adds more dependencies and complexities since we're trying to run 32bit code on 64bit only hardware)
In general, I found that Techno's Wineskin has a few performance issues on Big Sur compared to Mojave on a 2016 MBP Intel i5. I think others reported a few issues too? But generally speaking it's tolerable and I still play on Wineskin.
I don't know if the M1 Macs have been tested yet (or if they even work at all). I don't really know what you mean by running through Rosetta/Crossover/Agent however I don't know whether Rosetta 2 will Wineskin/Wine. However the folks at Crossover might have found a solution already.
ObliviousOblivous wrote: 246345
I come back.
AND I DON'T UNDERSTAND ANYTHING THAT IS GOING ON ANYMORE.
Haha lol I'm trying to keep track of all the questions as well... but please feel free to help out as well since I think Techno's on hiatus
I'll try updating the FAQ on https://osu-mac.readthedocs.io/en/latest/issues/index.html, maybe provide some bbcode templates and work through formatting issues on the site today so that I can address these issues faster without jumping through forum threads as well.
And that reminds me, if you did mention an issue please please please follow up on it and someone here should be able to help you - otherwise we'll forget about it
Note to future people about Wineskin.app I've just realised that if you haven't ran the Repair tool on osu!macOS Agent that your Wineskin.app might not be able to run (even if osu! does) - so do that first before any other troubleshooting methods I might have mentioned above
Here are the screenshots:
https://gyazo.com/37de9997646aa92e0f585052c1cbf33d
https://gyazo.com/a7db9712a250d35901b2bfccc77ac19c
https://gyazo.com/4e5cd49aa1e9bcd3d4a706b6a7ece353
I am not sure which error you wanted, so I included when I try open the .osz and also when I open the old Wineskin.app
So I went back and tested this out - it looks like with the recent update to Techno's Wineskin I hadn't realised this method doesn't exactly work. Weirdly enough, if you open explorer.exe and then open the Wineskin through that window it will work.
I'll try and figure something out but in the meantime try using drag/drop into the osu! window as outlined here https://osu-mac.readthedocs.io/en/latest/welcome/import.html#drag-and-drop
dw, still working on this!
Ok so here's what I've found
After many hours of work scripting potential fixes and researching Wineskin I think the best alternative to Associated Extensions in Wine is Technocoder's osu!macOS Agent which can automatically move beatmaps to osu!. You can see this is an open issue on GitHub https://github.com/Gcenx/WineskinServer/issues/47 which would explain why a lot of people here are having trouble with that
In theory, you could move an osz to the osu! directory automatically and then trigger a refresh of it in Wineskin by somehow running
C:\osu!\osu!.exe C:\osu!\Songs\YourBeatmapHere.oszin cmd somehow under the same prefix/instance. But Agent already achieves that so there's not really much point in creating another program to do that.
For some reason winecfg doesn't work and I was hoping to modify the extensions through there. But anyway, that's all I've got. Sorry to everyone hoping for a better fix![]()
Turns out my antivirus software (that I completely forgot I had) was messing with it. Set my osu! folder as an exception so it wouldn't scan it, repeated the steps and I got osu! to start.aidswidjaja wrote: 4a1ul
I think you have a typo in your execute.bat file?Chanw11 wrote: 2j21p
I tried it on my MBA M1, doesnt seem to work. (After scanning and repairing) OSU app opens with a terminal
C:\osu!>start C:\osu!\bridge.exe
C:\osu!>start C:\osu!\osu!.exe -noplash
then it closes
C:\osu!>start C:\osu!\osu!.exe -noplashshould be
C:\osu!>start C:\osu!\osu!.exe -nosplash
Note the -nosplash flag.
Edit: also please read https://github.com/Gcenx/WineskinServer#apple-silicon-device- and https://github.com/Gcenx/WineskinServer/issues/65
Could you try doing a test run?twentyonekoalas wrote: 1o5e
Followed all the steps but osu! still won't open. Double-clicking the app doesn't do anything. OS version is Catalina 10.15.7.
ReportVersion 10.15.7 (Build 19H15)
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 configuration is absent
System Integrity Protection is enabled
Engine version is ed
Razer Synapse is absent
No errors in: update.log
Log file: runtime.log is absent
Instructions here: https://osu-mac.readthedocs.io/en/latest/issues/troubleshooting.html#generating-logs-for-wineskin
With the logs, you can paste them to a pastebin like paste.ubuntu.com
Hope this helps everyone
aidswidjajaaidswidjaja wrote: 4a1ul
oblicueoblicue wrote: 5d5a5h
aidswidjajaaidswidjaja wrote: 4a1ul
oblicueoblicue wrote: 5d5a5h
I reinstalled, but the wineskin still didn't work, then I installed Wineskin.app manually. That seems to have worked, and I have opened it. I don't have an antivirus and definitely used The Unarchiver. I followed the steps to configure a windows program to open a file (which the properties look like they've worked) , but when I open a .osz or .osk file, I get the same error.aidswidjaja wrote: 4a1ul
Could you make sure thatoblicue wrote: 5d5a5h
When i try the osu! wineskin.app, i get the error
"Error while writting file: The folder “exec814803833.bat” doesn’t exist."
1. You unzip the file using The Unarchiver instead of the default Archive Utility on macOS. I think someone else said that it caused problems.
2. Make sure there are no antivirus software interfering with your installation
(community/forums/posts/7756236)
You might need to reinstall it afterwards. You can also try installing Wineskin.app manually (community/forums/posts/7793479) but I doubt that would work if your install is corrupted.
So basically, execute.bat is a text file which should contain two lines.TLXlayer wrote: 2s3j32
I don't know much about this but I don't know what you mean about start C:\osu!\bridge.exe and start C:\osu!\osu!.exe being in execute.bat. I can see three papers named execute.bat, bridge.exe, and osu!.exe
You also want to make sure that Wineskin.app points to this file in the Windows EXE field.
And you mentioned that you could only see execute.bat, bridge.exe, and osu!.exe in your osu! folder? For reference this is what my folder setup looks like.
If there are only three files there, it could be possible that an antivirus is removing your dll files or something. So just make sure that you've also followed the guidelines I sent to oblicue above which you can follow if the first guidelines I gave you don't work.
Hope this helps everyone![]()
https://gyazo.com/6a0a45296a8dc07deca0e9c66983a3f6 Here is a screenshot of my "Advanced" settings in the osu wineskin. I have all the file types in the dropdown menu.
Can you take a screenshot of the error message you receive as well as the Properties pane
To your changes:
6. Click Tools, then click Command Line (cmd). A console-like should open (it takes a while tho)
7. Type explorer.exe
8. Navigate to My Computer\osu!\Songs and locate the osz beatmap you just dropped
9. Right click on the file, click Properties and it worked. It should look like the image below.
https://gyazo.com/b6282b14ef06ea96d760d2c6cfc4d2edTuxedo23Tuxedo23 wrote: 1q7234
I came to this thread to find out myself if it works on Big Sur, hahaoblicue wrote: 5d5a5h
got this working on big sur
Either way, how does the app run on Big Sur? Does it run better than Intel-based macs? Which runs better; crossover through Rosetta or MacOS osu! Agent?
I found slc's Wineskin was more stable but obviously that is pre-Catalina only and Techno's Catalina< Wineskin uses the WS11 engines that have wine32on64 (basically in a nutshell: adds more dependencies and complexities since we're trying to run 32bit code on 64bit only hardware)
In general, I found that Techno's Wineskin has a few performance issues on Big Sur compared to Mojave on a 2016 MBP Intel i5. I think others reported a few issues too? But generally speaking it's tolerable and I still play on Wineskin.
I don't know if the M1 Macs have been tested yet (or if they even work at all). I don't really know what you mean by running through Rosetta/Crossover/Agent however I don't know whether Rosetta 2 will Wineskin/Wine. However the folks at Crossover might have found a solution already.
ObliviousOblivous wrote: 246345
I come back.
AND I DON'T UNDERSTAND ANYTHING THAT IS GOING ON ANYMORE.
Haha lol I'm trying to keep track of all the questions as well... but please feel free to help out as well since I think Techno's on hiatus
I'll try updating the FAQ on https://osu-mac.readthedocs.io/en/latest/issues/index.html, maybe provide some bbcode templates and work through formatting issues on the site today so that I can address these issues faster without jumping through forum threads as well.
And that reminds me, if you did mention an issue please please please follow up on it and someone here should be able to help you - otherwise we'll forget about it
Note to future people about Wineskin.app I've just realised that if you haven't ran the Repair tool on osu!macOS Agent that your Wineskin.app might not be able to run (even if osu! does) - so do that first before any other troubleshooting methods I might have mentioned above
Here are the screenshots:
https://gyazo.com/37de9997646aa92e0f585052c1cbf33d
https://gyazo.com/a7db9712a250d35901b2bfccc77ac19c
https://gyazo.com/4e5cd49aa1e9bcd3d4a706b6a7ece353
I am not sure which error you wanted, so I included when I try open the .osz and also when I open the old Wineskin.app
So I went back and tested this out - it looks like with the recent update to Techno's Wineskin I hadn't realised this method doesn't exactly work. Weirdly enough, if you open explorer.exe and then open the Wineskin through that window it will work.
I'll try and figure something out but in the meantime try using drag/drop into the osu! window as outlined here https://osu-mac.readthedocs.io/en/latest/welcome/import.html#drag-and-drop
dw, still working on this!
Ok so here's what I've found
After many hours of work scripting potential fixes and researching Wineskin I think the best alternative to Associated Extensions in Wine is Technocoder's osu!macOS Agent which can automatically move beatmaps to osu!. You can see this is an open issue on GitHub https://github.com/Gcenx/WineskinServer/issues/47 which would explain why a lot of people here are having trouble with that
In theory, you could move an osz to the osu! directory automatically and then trigger a refresh of it in Wineskin by somehow running
C:\osu!\osu!.exe C:\osu!\Songs\YourBeatmapHere.oszin cmd somehow under the same prefix/instance. But Agent already achieves that so there's not really much point in creating another program to do that.
For some reason winecfg doesn't work and I was hoping to modify the extensions through there. But anyway, that's all I've got. Sorry to everyone hoping for a better fix![]()
Please exclude osu! from your antivirus! More info here:jaloley wrote: 73634v
I cant open the first file, my antivirus-program said, that the complete file is a virus and deleted it instantly. What should i do? I want to play osu...
aidswidjaja wrote: 4a1ul
Sorry for disappearing for a while, let's see how many I can get through lol
pinkfujoshiYou could try updating the osu!.exe manually by ing it from home/ then replacing it in your Wineskin. If that doesn't work let us know and attach the contents of drive_c/osu!/Logs/update.to a pastebin such as paste.ubuntu.comHello again, I did follow your advice, and it started working. But as of right now, I cannot open it again. T~T Here's the report:
lucid126Good to hear you fixed everything, let us know if you encounter any more issues. Also feel free to let us know what you did to fix it.all right, when I opened osu! and tried to a map, a pop up box said that no windows app could run it, so i followed the steps and checked the automatically move ed songs to the songs folder, now there's only 1 song on there and its birdsong. i ran the report and said everything was fine. I'm on mojave. has anyone experienced this? Edit: I got the song to work, but now whenever I try to exit to the main menu it just goes to a black screen. Edit 2: I fixed everyrhing
raiqoUpdating to Big Sur won't really fix your problem unfortunately. If the test run is giving you different results to the actual executable, try repairing the exe through agent again or alternatively running this command:so i launched osu! through the wineskin and it opened, it was working fine and all my maps and skins were there. i then closed it and the thing popped up so i clicked yes and got this: https://paste.ubuntu.com/p/K8XxgNzqc4/
i tried launching osu normally but it still tells me that its damaged. do i just use the wineskin to launch from now on or is there someway to fix the problem? i've also considered updating to Big Sur (i'm currently running Mojave 10.14.6) would that help solve the problem?
edit: just tried launching it again from the test run and it lets me but i cant use any skins and when i try to play maps the game crashes
sudo xattr -rd com.apple.quarantine "~/path/to/my/osu\!.app"
Can you also make sure that your Skins and Songs folders in drive_c/osu! aren't corrupted or anything. It *is* pretty weird how your install is behaving and somewhat corrupted... You're getting a lot of errors, such as these
0098:fixme:path:parse_url failed to parse L"osu!ui" 0098:fixme:path:parse_url failed to parse L"osu!ui.resources"
If you haven't already, I'd try reinstalling just to be sure and to isolate that issue. Also you could try to go to Wineskin.app > Advanced > Tools > and under Wrapper Tools click Refresh Wrapper (do NOT click Rebuild as this will delete everything including your Songs, scores, etc, unless you have them backed up - if they're backed up you could try that as well) - BE CAREFUL ABOUT DOING THIS (I may have done it to myself and now my osu! won't update :/ - maybe make a backup first
Also are the logs the same on your second test run (when the skins don't load, maps crash the game etc) ?
It's some pretty weird stuff, keep us informed and try the stuff above
AmAWolfSorry for not replying,
no, I didn't try but could you give me the Wineskin.app so I can try it?
And could you explain me what I have to do? I'm not that techieWill to Google Drive now, and I'll provide instructions + link by editing this post once its doneSee below, let me know if there are any problems
Also yea, if Agent isn't returning anything weird then there won't be any useful debugging info there for us to find.
PaydruThe report is showing errors with respect to updating the osu! application. Could you try updating from osu!macOS Agent:i havent had any problems with this until now. osu doesnt re-open unless i restart my laptop and whwen i run the troubleshoot, it givess me this
Alternatively the executable binary directly from home/ and replace it within your application
- Open osu!macOS Agent
- Click the Other tab
- Click Update osu!
- osu.exe from osu-ppy-sh.tvgratuite.org/home/.
- Locate where osu!.app (your Wineskin) is installed
- Right click on it and select Show Package Contents
- You should now see three files/folders: Contents, drive_c and Wineskin. Click drive_c.
- From here, click osu!.
- From here, locate osu!.exe and replace this file with the updated version that you just ed. Make sure you keep the filename the same.
Not much happening, just trying to debug different issuesOblivous wrote: 246345
Can someone quote this message and tell me what'd I miss? lmao
Wineskin.app replacement 3i2j1h
If you are experiencing issues with Wineskin.app, you can try ing it separately.
Instructions: https://osu-mac.readthedocs.io/en/latest/issues/wineskin.html#resolution
link: https://minhaskamal.github.io/DownGit/#/home?url=https://github.com/aidswidjaja/osu-mac/tree/main/src/wineskin or https://drive.google.com/drive/folders/1Gz5Y0M4WoMxTTwb5aHUccebO5AlVm3SN?usp=sharing
Please be advised if that this hasn't been tested and that distributing the Wineskin.app file on its own is completely experimental so it might not fix your issues. But definitely let me know if there are any problems with it
- Click the Link above
- If using Google Drive, click ALL in the top-right corner of the screen
- It will this as a zip file. Extract the zip file until you just have the Wineskin.app file
- Inside osu!.app (Right click > Show Package Contents) locate Wineskin.app - make a backup of it (you can just rename it to say something like Wineskin.app.backup if you want)
- Move the new version of Wineskin.app from Google Drive into osu!.app
- Try and open it and see if everything works out.
![]()
aidswidjaja wrote: 4a1ul
AmAWolfthank you very much, now i can open properly winskin.app
I have another issue, I can't open .osz files directly with osu!, so I have to open the folder Song and put them there, when I try to open an .osz file it shows a warning saying there's no windows program that can open that file....is there any way to fix it?
I'm running osu! for Catalina on High Sierra
Yea this is unfortunately a known issue so the best alternative is to use osu!macOS Agent.
It's an upstream issue with Gcenx's Wineskins wrapper so I'm not sure on what they're planning to do about the issue, it's more likely that the double click to open functionality won't ever be available in modern wineskins but we will see I guess
Edit: mobile editing sucks
gravitybalmain wrote: 6n68h
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 configuration is absent
System Integrity Protection is enabled
Engine version is ed
Razer Synapse is absent
No errors in: update.log
Log file: runtime.log is absent
AmAWolf wrote: 3gg1f
aidswidjajaaidswidjaja wrote: 4a1ul
AmAWolfthank you very much, now i can open properly winskin.app
I have another issue, I can't open .osz files directly with osu!, so I have to open the folder Song and put them there, when I try to open an .osz file it shows a warning saying there's no windows program that can open that file....is there any way to fix it?
I'm running osu! for Catalina on High Sierra
Yea this is unfortunately a known issue so the best alternative is to use osu!macOS Agent.
It's an upstream issue with Gcenx's Wineskins wrapper so I'm not sure on what they're planning to do about the issue, it's more likely that the double click to open functionality won't ever be available in modern wineskins but we will see I guess
Edit: mobile editing sucks
okay thank you
another question
I set osu!macOS Agent with everything on in the general page but still when I a beatmap that is in the s folder when I open osu! I can't find it.
I missed something or....idk
aidswidjaja wrote: 4a1ul
gravitybalmaingravitybalmain wrote: 6n68h
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 configuration is absent
System Integrity Protection is enabled
Engine version is ed
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.
AmAWolfAmAWolf wrote: 3gg1f
aidswidjajaaidswidjaja wrote: 4a1ul
AmAWolfthank you very much, now i can open properly winskin.app
I have another issue, I can't open .osz files directly with osu!, so I have to open the folder Song and put them there, when I try to open an .osz file it shows a warning saying there's no windows program that can open that file....is there any way to fix it?
I'm running osu! for Catalina on High Sierra
Yea this is unfortunately a known issue so the best alternative is to use osu!macOS Agent.
It's an upstream issue with Gcenx's Wineskins wrapper so I'm not sure on what they're planning to do about the issue, it's more likely that the double click to open functionality won't ever be available in modern wineskins but we will see I guess
Edit: mobile editing sucks
okay thank you
another question
I set osu!macOS Agent with everything on in the general page but still when I a beatmap that is in the s folder when I open osu! I can't find it.
I missed something or....idk
Hmm... did you check inside osu!.app/drive_c/osu!/Songs to see if it was actually auto-moved there by osu!macOS Agent. If it is still in the s folder then make sure osu!macOS Agent is open and running while ing a beatmap. If it did get moved to the Songs folder make sure to hit F5 to reload like on Windows.
R3st wrote: 2z4f4z
ReportVersion 10.15.6 (Build 19G2021)
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 configuration is absent
System Integrity Protection is enabled
Engine version is ed
Razer Synapse is absent
No errors in: update.log
Log file: runtime.log is absent
It seems like everything is fine after I followed the instructions on both the installation to osu!macOS Agent and osu, but osu doesn't open.
Thanks for the reply, it seems like I'm unable to see/obtain a crash log because the system doeesn't open. When I tried opening wineskin, there's an error that says "Error while writting file: The folder "exec1791796820.bat" doesn't exist." Again, thanks for the help.aidswidjaja wrote: 4a1ul
R3stR3st wrote: 2z4f4z
ReportVersion 10.15.6 (Build 19G2021)
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 configuration is absent
System Integrity Protection is enabled
Engine version is ed
Razer Synapse is absent
No errors in: update.log
Log file: runtime.log is absent
It seems like everything is fine after I followed the instructions on both the installation to osu!macOS Agent and osu, but osu doesn't open.
Heyo, 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 a pastebin service such as paste.ubuntu.com.
R3st wrote: 2z4f4z
Thanks for the reply, it seems like I'm unable to see/obtain a crash log because the system doeesn't open. When I tried opening wineskin, there's an error that says "Error while writting file: The folder "exec1791796820.bat" doesn't exist." Again, thanks for the help.aidswidjaja wrote: 4a1ul
R3stR3st wrote: 2z4f4z
ReportVersion 10.15.6 (Build 19G2021)
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 configuration is absent
System Integrity Protection is enabled
Engine version is ed
Razer Synapse is absent
No errors in: update.log
Log file: runtime.log is absent
It seems like everything is fine after I followed the instructions on both the installation to osu!macOS Agent and osu, but osu doesn't open.
Heyo, 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 a pastebin service such as paste.ubuntu.com.
Sure. Here's the log.aidswidjaja wrote: 4a1ul
gravitybalmaingravitybalmain wrote: 6n68h
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 configuration is absent
System Integrity Protection is enabled
Engine version is ed
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.
gravitybalmain wrote: 6n68h
Sure. Here's the log.aidswidjaja wrote: 4a1ul
gravitybalmaingravitybalmain wrote: 6n68h
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 configuration is absent
System Integrity Protection is enabled
Engine version is ed
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__shared_data_thread Creating shared data update thread.
000d:fixme:thread:create__shared_data_thread Creating shared data update thread.
0010:fixme:thread:create__shared_data_thread Creating shared data update thread.
0018:fixme:thread:create__shared_data_thread Creating shared data update thread.
001d:fixme:thread:create__shared_data_thread Creating 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__shared_data_thread Creating shared data update thread.
[box]
0009:fixme:exec:SHELL_execute flags ignored: 0x00000100
start C:\osu!\bridge.exe -nosplash start C:\osu!\osu!.exe
I did the above steps!aidswidjaja wrote: 4a1ul
gravitybalmaingravitybalmain wrote: 6n68h
Sure. Here's the log.aidswidjaja wrote: 4a1ul
gravitybalmaingravitybalmain wrote: 6n68h
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 configuration is absent
System Integrity Protection is enabled
Engine version is ed
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__shared_data_thread Creating shared data update thread.
000d:fixme:thread:create__shared_data_thread Creating shared data update thread.
0010:fixme:thread:create__shared_data_thread Creating shared data update thread.
0018:fixme:thread:create__shared_data_thread Creating shared data update thread.
001d:fixme:thread:create__shared_data_thread Creating 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__shared_data_thread Creating 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! 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 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 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 ing 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.
gravitybalmain wrote: 6n68h
I did the above steps!aidswidjaja wrote: 4a1ul
gravitybalmaingravitybalmain wrote: 6n68h
Sure. Here's the log.aidswidjaja wrote: 4a1ul
gravitybalmaingravitybalmain wrote: 6n68h
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 configuration is absent
System Integrity Protection is enabled
Engine version is ed
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__shared_data_thread Creating shared data update thread.
000d:fixme:thread:create__shared_data_thread Creating shared data update thread.
0010:fixme:thread:create__shared_data_thread Creating shared data update thread.
0018:fixme:thread:create__shared_data_thread Creating shared data update thread.
001d:fixme:thread:create__shared_data_thread Creating 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__shared_data_thread Creating 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! 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 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 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 ing 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.
y0lky wrote: 4g4a37
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: 4x1g1d
I cant scan it because it wont let me press it.
Chanw11 wrote: 2j21p
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: 453p3f
my scan:
ReportVersion 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 configuration is absent
System Integrity Protection is enabled
Engine version is ed
Razer Synapse is absent
No errors in: update.log
Log file: runtime.log is absent
zoko91 wrote: 6p1p3g
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: v545v
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 that I'm not installing some complex trojan?
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: 4a1ul
hi everyone I'm back, I'll try and get through as many as possible but please 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: 6p1p3g
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
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 started from a fresh re-install -- I think I'm having the same problem other M1 s 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: 4a1ul
hi everyone I'm back, I'll try and get through as many as possible but please 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: 6n68h
I did the above steps!aidswidjaja wrote: 4a1ul
gravitybalmaingravitybalmain wrote: 6n68h
Sure. Here's the log.aidswidjaja wrote: 4a1ul
gravitybalmaingravitybalmain wrote: 6n68h
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 configuration is absent
System Integrity Protection is enabled
Engine version is ed
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__shared_data_thread Creating shared data update thread.
000d:fixme:thread:create__shared_data_thread Creating shared data update thread.
0010:fixme:thread:create__shared_data_thread Creating shared data update thread.
0018:fixme:thread:create__shared_data_thread Creating shared data update thread.
001d:fixme:thread:create__shared_data_thread Creating 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__shared_data_thread Creating 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! 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 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 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 ing 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.
zoko91 wrote: 6p1p3g
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: 4a1ul
hi everyone I'm back, I'll try and get through as many as possible but please 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: 6p1p3g
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
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 wrote: 685o4u
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 ed 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: 3x6w2m
The game only works the first time after ing, after exiting the game and reopening, nothing happens.
gravitybalmain wrote: 6n68h
I started from a fresh re-install -- I think I'm having the same problem other M1 s 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: 4a1ul
hi everyone I'm back, I'll try and get through as many as possible but please 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: 6n68h
I did the above steps!aidswidjaja wrote: 4a1ul
gravitybalmaingravitybalmain wrote: 6n68h
Sure. Here's the log.aidswidjaja wrote: 4a1ul
gravitybalmaingravitybalmain wrote: 6n68h
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 configuration is absent
System Integrity Protection is enabled
Engine version is ed
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__shared_data_thread Creating shared data update thread.
000d:fixme:thread:create__shared_data_thread Creating shared data update thread.
0010:fixme:thread:create__shared_data_thread Creating shared data update thread.
0018:fixme:thread:create__shared_data_thread Creating shared data update thread.
001d:fixme:thread:create__shared_data_thread Creating 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__shared_data_thread Creating 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! 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 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 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 ing 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. ed latest wineskin. Extracted using The Unarchiver.
2. ed 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 configuration is absent
System Integrity Protection is enabled
Engine version is ed
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.
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)aidswidjaja wrote: 4a1ul
AnimatedThinksPlease 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: 685o4u
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 ed 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.
gravitybalmaingravitybalmain wrote: 6n68h
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.
gravitybalmainThanks for your super detailed explanation!I started from a fresh re-install -- I think I'm having the same problem other M1 s 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. ed latest wineskin. Extracted using The Unarchiver.
2. ed 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 configuration is absent
System Integrity Protection is enabled
Engine version is ed
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 s 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 Wineskinespecially 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 hereand on that note, if you do happen to fix the issue, do let us all know here!
The whole crash report in a Pastebin if you can. Your name may appear in the report so if you'd like to keep that private, give it a find and replace with your name.AnimatedThinks wrote: 685o4u
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!
R a y e n wrote: 4e1j3y
This is my troubleshoot report:
ReportVersion 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 ed
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: 685o4u
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)aidswidjaja wrote: 4a1ul
AnimatedThinksPlease 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: 685o4u
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 ed 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.
gravitybalmaingravitybalmain wrote: 6n68h
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.
gravitybalmainThanks for your super detailed explanation!I started from a fresh re-install -- I think I'm having the same problem other M1 s 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. ed latest wineskin. Extracted using The Unarchiver.
2. ed 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 configuration is absent
System Integrity Protection is enabled
Engine version is ed
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 s 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 Wineskinespecially 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 hereand on that note, if you do happen to fix the issue, do let us all know here!
osu!macOS Agent report:ReportThe 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?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 configuration is absent
System Integrity Protection is enabled
Engine version is ed
Razer Synapse is absent
No errors in: update.log
Log file: runtime.log is absent
also sorry for the late response!
Technocoder wrote: 365p3v
The whole crash report in a Pastebin if you can. Your name may appear in the report so if you'd like to keep that private, give it a find and replace with your name.AnimatedThinks wrote: 685o4u
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!
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 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...
Its working perfectly!! thank you so much!! ;DTechnocoder wrote: 365p3v
"R a y e n"R a y e n wrote: 4e1j3y
This is my troubleshoot report:
ReportVersion 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 ed
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 ;
Press the Update osu! button under the Other tab.
ShadowstyleX wrote: 4a2f2v
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 ed 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: 685o4u
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 RunThen everything went downhillerr:thread:get_image_addr dyld image info is above 4GB limit for 32-bit-on-64-bit process
000b:fixme:thread:create__shared_data_thread Creating shared data update thread.
000d:fixme:thread:create__shared_data_thread Creating shared data update thread.
0010:fixme:thread:create__shared_data_thread Creating shared data update thread.
0018:fixme:thread:create__shared_data_thread Creating shared data update thread.
001d:fixme:thread:create__shared_data_thread Creating 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__shared_data_thread Creating shared data update thread.
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 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: 145w5b
ReportVersion 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 ed
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: 2i1k3o
ReportVersion 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 configuration is absent
System Integrity Protection is enabled
Engine version is ed
Razer Synapse is absent
No errors in: update.log
Log file: runtime.log is absent
AnimatedThinks wrote: 685o4u
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 RunThen everything went downhillerr:thread:get_image_addr dyld image info is above 4GB limit for 32-bit-on-64-bit process
000b:fixme:thread:create__shared_data_thread Creating shared data update thread.
000d:fixme:thread:create__shared_data_thread Creating shared data update thread.
0010:fixme:thread:create__shared_data_thread Creating shared data update thread.
0018:fixme:thread:create__shared_data_thread Creating shared data update thread.
001d:fixme:thread:create__shared_data_thread Creating 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__shared_data_thread Creating shared data update thread.
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 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: 365p3v
AnimatedThinksAnimatedThinks wrote: 685o4u
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 RunThen everything went downhillerr:thread:get_image_addr dyld image info is above 4GB limit for 32-bit-on-64-bit process
000b:fixme:thread:create__shared_data_thread Creating shared data update thread.
000d:fixme:thread:create__shared_data_thread Creating shared data update thread.
0010:fixme:thread:create__shared_data_thread Creating shared data update thread.
0018:fixme:thread:create__shared_data_thread Creating shared data update thread.
001d:fixme:thread:create__shared_data_thread Creating 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__shared_data_thread Creating shared data update thread.
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 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- 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.
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.Don't worry, I think I know what you mean (this right? https://osu-mac.readthedocs.io/en/latest/_images/graphics-context.png) but the solution to that is to undo Compatibility Mode. yep, compatibility mode ruins things for osu! on mac as Techno has mentioned.
Wineskin-2.9.0.7-rc4https://github.com/Gcenx/WineskinServer/issues/65
This new wrapper will function under Rosetta2, included the custom MoltenVK needed for DXVK .
WineCX19 based engine are functional on Apple Silicon.Not sure if you've looked through these yet (or whether the wrappers have already been updated), but it may be worthwhile to create a new wrapper for Apple Silicon. WineCX20 seems to be the priority for M1 .
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 to that version or greater.
Nylo23 wrote: 336a5n
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-rc4https://github.com/Gcenx/WineskinServer/issues/65
This new wrapper will function under Rosetta2, included the custom MoltenVK needed for DXVK .
WineCX19 based engine are functional on Apple Silicon.Not sure if you've looked through these yet (or whether the wrappers have already been updated), but it may be worthwhile to create a new wrapper for Apple Silicon. WineCX20 seems to be the priority for M1 .[/quote]
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 to that version or greater.
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;Technocoder wrote: 365p3v
AnimatedThinksAnimatedThinks wrote: 685o4u
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 RunThen everything went downhillerr:thread:get_image_addr dyld image info is above 4GB limit for 32-bit-on-64-bit process
000b:fixme:thread:create__shared_data_thread Creating shared data update thread.
000d:fixme:thread:create__shared_data_thread Creating shared data update thread.
0010:fixme:thread:create__shared_data_thread Creating shared data update thread.
0018:fixme:thread:create__shared_data_thread Creating shared data update thread.
001d:fixme:thread:create__shared_data_thread Creating 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__shared_data_thread Creating shared data update thread.
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 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- 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.
AnimatedThinks wrote: 685o4u
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;Technocoder wrote: 365p3v
AnimatedThinksAnimatedThinks wrote: 685o4u
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 RunThen everything went downhillerr:thread:get_image_addr dyld image info is above 4GB limit for 32-bit-on-64-bit process
000b:fixme:thread:create__shared_data_thread Creating shared data update thread.
000d:fixme:thread:create__shared_data_thread Creating shared data update thread.
0010:fixme:thread:create__shared_data_thread Creating shared data update thread.
0018:fixme:thread:create__shared_data_thread Creating shared data update thread.
001d:fixme:thread:create__shared_data_thread Creating 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__shared_data_thread Creating shared data update thread.
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 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- 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.
ReportVersion 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 ed
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.
I opened the agent and hit Update in the Other tab.aidswidjaja wrote: 4a1ul
AnimatedThinksAnimatedThinks wrote: 685o4u
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;Technocoder wrote: 365p3v
AnimatedThinksAnimatedThinks wrote: 685o4u
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 RunThen everything went downhillerr:thread:get_image_addr dyld image info is above 4GB limit for 32-bit-on-64-bit process
000b:fixme:thread:create__shared_data_thread Creating shared data update thread.
000d:fixme:thread:create__shared_data_thread Creating shared data update thread.
0010:fixme:thread:create__shared_data_thread Creating shared data update thread.
0018:fixme:thread:create__shared_data_thread Creating shared data update thread.
001d:fixme:thread:create__shared_data_thread Creating 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__shared_data_thread Creating shared data update thread.
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 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- 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.
ReportVersion 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 ed
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![]()
AnimatedThinks wrote: 685o4u
I opened the agent and hit Update in the Other tab.aidswidjaja wrote: 4a1ul
AnimatedThinksAnimatedThinks wrote: 685o4u
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;Technocoder wrote: 365p3v
AnimatedThinksAnimatedThinks wrote: 685o4u
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 RunThen everything went downhillerr:thread:get_image_addr dyld image info is above 4GB limit for 32-bit-on-64-bit process
000b:fixme:thread:create__shared_data_thread Creating shared data update thread.
000d:fixme:thread:create__shared_data_thread Creating shared data update thread.
0010:fixme:thread:create__shared_data_thread Creating shared data update thread.
0018:fixme:thread:create__shared_data_thread Creating shared data update thread.
001d:fixme:thread:create__shared_data_thread Creating 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__shared_data_thread Creating shared data update thread.
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 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- 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.
ReportVersion 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 ed
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 think it's more broken now uhh
ReportVersion 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 ed
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)
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.aidswidjaja wrote: 4a1ul
AnimatedThinksAnimatedThinks wrote: 685o4u
I opened the agent and hit Update in the Other tab.aidswidjaja wrote: 4a1ul
AnimatedThinksAnimatedThinks wrote: 685o4u
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;Technocoder wrote: 365p3v
AnimatedThinksAnimatedThinks wrote: 685o4u
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 RunThen everything went downhillerr:thread:get_image_addr dyld image info is above 4GB limit for 32-bit-on-64-bit process
000b:fixme:thread:create__shared_data_thread Creating shared data update thread.
000d:fixme:thread:create__shared_data_thread Creating shared data update thread.
0010:fixme:thread:create__shared_data_thread Creating shared data update thread.
0018:fixme:thread:create__shared_data_thread Creating shared data update thread.
001d:fixme:thread:create__shared_data_thread Creating 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__shared_data_thread Creating shared data update thread.
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 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- 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.
ReportVersion 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 ed
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 think it's more broken now uhh
ReportVersion 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 ed
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~
AnimatedThinks wrote: 685o4u
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.aidswidjaja wrote: 4a1ul
AnimatedThinksAnimatedThinks wrote: 685o4u
I opened the agent and hit Update in the Other tab.aidswidjaja wrote: 4a1ul
AnimatedThinksAnimatedThinks wrote: 685o4u
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;Technocoder wrote: 365p3v
AnimatedThinksAnimatedThinks wrote: 685o4u
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 RunThen everything went downhillerr:thread:get_image_addr dyld image info is above 4GB limit for 32-bit-on-64-bit process
000b:fixme:thread:create__shared_data_thread Creating shared data update thread.
000d:fixme:thread:create__shared_data_thread Creating shared data update thread.
0010:fixme:thread:create__shared_data_thread Creating shared data update thread.
0018:fixme:thread:create__shared_data_thread Creating shared data update thread.
001d:fixme:thread:create__shared_data_thread Creating 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__shared_data_thread Creating shared data update thread.
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 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- 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.
ReportVersion 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 ed
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 think it's more broken now uhh
ReportVersion 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 ed
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~
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.
gravitybalmain wrote: 6n68h
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
ReportVersion 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 configuration is absent
System Integrity Protection is enabled
Engine version is ed
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).
Exception Type: EXC_BAD_INSTRUCTION (SIGILL) Exception Codes: 0x0000000000000001, 0x0000000000000000 Exception Note: EXC_CORPSE_NOTIFY
cd ../../osu! echo %CD% # this command should print C:\ osu!.exe
Technocoder wrote: 365p3v
Strangely enough, I get the same crash report when using the WineCX20 engine but not with the WineCX64Bit20 engine... and I'm running macOS Catalina, not Big Sur or M1.
Please try using this Wineskin which uses WineCX20 instead: https://mega.nz/file/ZxlQ1AiS#A-2sPJI5zg_7Dn___VXmO5EEY4qRyJm6uAu7TpiLA9U
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.
AnimatedThinks wrote: 685o4u
I tried out the new Wineskin just now (I also ed the new mac!OS Agent, I realized the old one wouldn't detect the new Wineskin.)
When opening it (either through Test Run or by normal double-clicking), it shows the osu! popup, but never actually opens.
Here's the Test Run that popped up when I tried opening osu! that way:
Test Run000b:fixme:thread:create__shared_data_thread Creating shared data update thread.
000d:fixme:thread:create__shared_data_thread Creating shared data update thread.
0010:fixme:thread:create__shared_data_thread Creating shared data update thread.
0018:fixme:thread:create__shared_data_thread Creating shared data update thread.
001d:fixme:thread:create__shared_data_thread Creating shared data update thread.
0009:fixme:thread:create__shared_data_thread Creating shared data update thread.
0009:fixme:exec:SHELL_execute flags ignored: 0x00000100
0009:fixme:ntdll:FILE_GetNtStatus Converting errno 8 to STATUS_UNSUCCESSFUL
0026:fixme:thread:create__shared_data_thread Creating shared data update thread.
0028:fixme:thread:create__shared_data_thread Creating shared data update thread.
002a:fixme:thread:create__shared_data_thread Creating shared data update thread.
0031:fixme:thread:create__shared_data_thread Creating shared data update thread.
0036:fixme:ntdll:NtQuerySystemInformation info_class SYSTEM_PERFORMANCE_INFORMATION
0036:fixme:heap:GetNumaHighestNodeNumber semi-stub: 0031FAC8
0038:err:ole:CoGetContextToken apartment not initialised
0036:fixme:time:QueryThreadCycleTime (0xfffffffe,0x5d52560): stub!
0036:fixme:path:parse_url failed to parse L"System.Windows.Forms"
0036:fixme:path:parse_url failed to parse L"System.Drawing"
0036:fixme:path:parse_url failed to parse L"System"
0036:fixme:path:parse_url failed to parse L"System.Configuration"
0036:fixme:path:parse_url failed to parse L"System.Xml"
0036:fixme:path:parse_url failed to parse L"Accessibility"
0036:fixme:path:parse_url failed to parse L"System.Security"
0036:fixme:path:parse_url failed to parse L"System.Runtime.Serialization.Formatters.Soap"
0036:fixme:path:parse_url failed to parse L"System.Deployment"
0036:fixme:path:parse_url failed to parse L"System.Core"
0036:fixme:path:parse_url failed to parse L"System.Drawing"
0036:fixme:path:parse_url failed to parse L"System"
0036:fixme:path:parse_url failed to parse L"System.Core"
0036:fixme:path:parse_url failed to parse L"System.Numerics"
0036:fixme:nls:get_dummy_preferred_ui_language (0x8 0x31daf4 0x0 0x31daf0) returning a dummy value (current locale)
0036:fixme:nls:get_dummy_preferred_ui_language (0x8 0x31daf4 0x3aa40d0 0x31daf0) returning a dummy value (current locale)
0036:fixme:process:SetProcessPriorityBoost (00000268,0): stub
0042:fixme:path:parse_url failed to parse L"System.Web"
0036:fixme:path:parse_url failed to parse L"OpenTK"
0042:fixme:path:parse_url failed to parse L"Microsoft.Build.Framework"
0042:fixme:path:parse_url failed to parse L"Microsoft.Build.Utilities.v4.0"
0042:fixme:path:parse_url failed to parse L"System.ComponentModel.DataAnnotations"
0042:fixme:path:parse_url failed to parse L"System.Runtime.Caching"
0042:fixme:path:parse_url failed to parse L"System.Data"
0042:fixme:path:parse_url failed to parse L"System.Web.ApplicationServices"
0042:fixme:path:parse_url failed to parse L"System.DirectoryServices.Protocols"
0042:fixme:path:parse_url failed to parse L"System.DirectoryServices"
0042:fixme:path:parse_url failed to parse L"System.EnterpriseServices"
0042:fixme:path:parse_url failed to parse L"System.ServiceProcess"
0042:fixme:path:parse_url failed to parse L"System.Web.Services"
0042:fixme:path:parse_url failed to parse L"System.Design"
0042:fixme:path:parse_url failed to parse L"Microsoft.Build.Tasks.v4.0"
0042:fixme:path:parse_url failed to parse L"System.Web.RegularExpressions"
0042:fixme:path:parse_url failed to parse L"System.Transactions"
0042:fixme:combase:RoGetParameterizedTypeInstanceIID stub: 4 03B35268 0831B62C 0831BC90 00000000
0042:fixme:combase:RoGetParameterizedTypeInstanceIID stub: 3 03B285A4 0831B81C 0831BE80 00000000
0042:fixme:combase:RoGetParameterizedTypeInstanceIID stub: 3 03B285A4 0831B81C 0831BE80 00000000
0036:err:winediag:wined3d_dll_init Setting multithreaded command stream to 0x1.
0043:fixme:path:parse_url failed to parse L"System.Configuration"
0043:fixme:path:parse_url failed to parse L"System.Xml"
0043:fixme:path:parse_url failed to parse L"System.Data.SqlXml"
0043:fixme:ras:RasEnumConnectionsW (03B65D40,084BEE80,084BEE84),stub!
0043:fixme:ras:RasEnumConnectionsW RAS is not implemented! Configure program to use LAN connection/winsock instead!
0043:fixme:winsock:set_dont_fragment IP_DONTFRAGMENT for IPv4 not ed in this platform
0043:fixme:winsock:set_dont_fragment IP_DONTFRAGMENT for IPv6 not ed in this platform
0043:err:winsock:WSAIoctl -> SIO_ADDRESS_LIST_CHANGE request failed with status 0x2733
0043:err:winsock:WSAIoctl -> SIO_ADDRESS_LIST_CHANGE request failed with status 0x2733
0043:fixme:ras:RasConnectionNotificationW (FFFFFFFF,00000328,0x00000003),stub!
0036:fixme:combase:RoGetParameterizedTypeInstanceIID stub: 4 03B5DD78 0031D24C 0031D8B0 00000000
0036:fixme:combase:RoGetParameterizedTypeInstanceIID stub: 3 03B5DC54 0031D43C 0031DAA0 00000000
0036:fixme:combase:RoGetParameterizedTypeInstanceIID stub: 3 03B5DC54 0031D43C 0031DAA0 00000000
0036:fixme:ntdll:EtwEvent ({8e9f5090-2d75-4d03-8a81-e5afbf85daf1}, 0xa60732, 0x0, 0x194cb44) stub.
0036:fixme:path:parse_url failed to parse L"osu!.resources"
0036:fixme:nls:LCMapStringEx uned lparam 3ac0d80
0036:fixme:path:parse_url failed to parse L"osu!.resources"
0036:fixme:coreaudio:ca_channel_layout_to_channel_mask Unhandled channel 0xffffffff
0036:fixme:coreaudio:ca_channel_layout_to_channel_mask Unhandled channel 0xffffffff
0036:fixme:coreaudio:ca_channel_layout_to_channel_mask Unhandled channel 0xffffffff
0036:fixme:coreaudio:ca_channel_layout_to_channel_mask Unhandled channel 0xffffffff
0036:fixme:coreaudio:ca_channel_layout_to_channel_mask Unhandled channel 0xffffffff
0048:fixme:avrt:AvSetMmThreadCharacteristicsW (L"Audio",0B4CFDF8): stub
0036:fixme:process:FlushProcessWriteBuffers : stub
004c:fixme:thread:NtGetCurrentProcessorNumber need multicore (8 processors)
004c:fixme:path:parse_url failed to parse L"System.Runtime.Serialization"
004c:fixme:path:parse_url failed to parse L"SMDiagnostics"
004c:fixme:path:parse_url failed to parse L"System.ServiceModel.Internals"
004c:fixme:path:parse_url failed to parse L"System.Numerics"
0036:fixme:path:parse_url failed to parse L"osu!ui"
0036:fixme:path:parse_url failed to parse L"osu!ui.resources"
004c:fixme:path:parse_url failed to parse L"System.Data"
0042:fixme:path:parse_url failed to parse L"System.Runtime.Remoting"
004c:fixme:advapi:EventSourceW ((null),L".NET Runtime"): stub
004c:fixme:advapi:ReportEventW (0xcafe4242,0x0001,0x0000,0x000003ff,0x0,0x0001,0x00000000,0xb90d5bc,0x0): stub
004c:err:eventlog:ReportEventW L"Application: osu!.exe\nFramework Version: v4.0.30319\nDescription: The process was terminated due to an internal error in the .NET Runtime at IP 00E03BED (00D90000) with exit code 80131506.\n"
004c:fixme:advapi:DeEventSource (0xcafe4242) stub
I'll see if deleting and replacing the files on the old Wineskin works
Thanks to everyone for helping fix these issues
Update - For the old Wineskin: I deleted all the files mentioned, ed the osu! exe for Windows, and dragged it into the drive_c/osu! folder.
There were a few files I didn't see mentioned (namely d3dx9_31.dll, Microsoft.Xna.Framework.dll, osu!seasonal.dll, osu!dll, and x3daudio1_1.dll.) I left them alone for now.
When I did the Agent again, it didn't seem to help. I might have done something wrong, though.
ReportVersion 10.16 (Build 20C69)
Engine: WS11WineCX64Bit19.0.1-1
Wineskin 2.9.0.6 1
Game configuration is absent
Quarantine attribute is absent
Execute flag is present
Detect Direct3D is enabled
Compatibility mode is disabled
System Integrity Protection is enabled
Engine version is ed
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
warning: This package (dotnet40) may not fully work on a 64-bit installation. 32-bit prefixes may work better. ------------------------------------------------------ ------------------------------------------------------ warning: dotnet40 does not yet fully work or install on wine. Caveat emptor.
Kyzui wrote: 5l7011
My osu has been fine opening ever since I ed like 4 months ago but for some reason the "Restart" button won't pop up now when I try to open osu!. There is no way for me to get into the application without this option. Any ideas?
Kyzui wrote: 5l7011
When I first ed osu! using Technocoder's version in Catilina every time I would open osu it said "osu! crashed" and all I had to do was simply press restart which would boot up the game. I have been doing this for a few months now. All of a sudden yesterday that option stopped popping up and osu! would not run at all. I did the Test Run and these were the logs:aidswidjaja wrote: 4a1ul
TechnocoderTechnocoder wrote: 365p3v
Strangely enough, I get the same crash report when using the WineCX20 engine but not with the WineCX64Bit20 engine... and I'm running macOS Catalina, not Big Sur or M1.
Please try using this Wineskin which uses WineCX20 instead: https://mega.nz/file/ZxlQ1AiS#A-2sPJI5zg_7Dn___VXmO5EEY4qRyJm6uAu7TpiLA9U
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.
Hmm... So far I haven't been able to replicate the crash report on any Wineskin.
WS11WineCX64Bit19.0.1-1 :: Works fine normally, Test Run opens osu! as expected
WS11WineCX64Bit20.0.0 :: Works fine normally, Test Run opens osu! as expected
WS11WineCX6420.0.0 :: wine: '/s/Adrian/Desktop/WS11CX20.0.0.app/Contents/Resources' is a 64-bit installation, it cannot be used with a 32-bit wineserver. (expected error)
This is on my 2016 MBP wo/ touch bar - Intel x86 i5. 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. Maybe I'll try again and see what happens there.
How did you get WineCX20 to run (on Catalina)? As expected I'm getting 64-bit compatibility issues on 32-bit wineserver (hence why wine32on64 is used)
AnimatedThinksAnimatedThinks wrote: 685o4u
I tried out the new Wineskin just now (I also ed the new mac!OS Agent, I realized the old one wouldn't detect the new Wineskin.)
When opening it (either through Test Run or by normal double-clicking), it shows the osu! popup, but never actually opens.
Here's the Test Run that popped up when I tried opening osu! that way:
Test Run000b:fixme:thread:create__shared_data_thread Creating shared data update thread.
000d:fixme:thread:create__shared_data_thread Creating shared data update thread.
0010:fixme:thread:create__shared_data_thread Creating shared data update thread.
0018:fixme:thread:create__shared_data_thread Creating shared data update thread.
001d:fixme:thread:create__shared_data_thread Creating shared data update thread.
0009:fixme:thread:create__shared_data_thread Creating shared data update thread.
0009:fixme:exec:SHELL_execute flags ignored: 0x00000100
0009:fixme:ntdll:FILE_GetNtStatus Converting errno 8 to STATUS_UNSUCCESSFUL
0026:fixme:thread:create__shared_data_thread Creating shared data update thread.
0028:fixme:thread:create__shared_data_thread Creating shared data update thread.
002a:fixme:thread:create__shared_data_thread Creating shared data update thread.
0031:fixme:thread:create__shared_data_thread Creating shared data update thread.
0036:fixme:ntdll:NtQuerySystemInformation info_class SYSTEM_PERFORMANCE_INFORMATION
0036:fixme:heap:GetNumaHighestNodeNumber semi-stub: 0031FAC8
0038:err:ole:CoGetContextToken apartment not initialised
0036:fixme:time:QueryThreadCycleTime (0xfffffffe,0x5d52560): stub!
0036:fixme:path:parse_url failed to parse L"System.Windows.Forms"
0036:fixme:path:parse_url failed to parse L"System.Drawing"
0036:fixme:path:parse_url failed to parse L"System"
0036:fixme:path:parse_url failed to parse L"System.Configuration"
0036:fixme:path:parse_url failed to parse L"System.Xml"
0036:fixme:path:parse_url failed to parse L"Accessibility"
0036:fixme:path:parse_url failed to parse L"System.Security"
0036:fixme:path:parse_url failed to parse L"System.Runtime.Serialization.Formatters.Soap"
0036:fixme:path:parse_url failed to parse L"System.Deployment"
0036:fixme:path:parse_url failed to parse L"System.Core"
0036:fixme:path:parse_url failed to parse L"System.Drawing"
0036:fixme:path:parse_url failed to parse L"System"
0036:fixme:path:parse_url failed to parse L"System.Core"
0036:fixme:path:parse_url failed to parse L"System.Numerics"
0036:fixme:nls:get_dummy_preferred_ui_language (0x8 0x31daf4 0x0 0x31daf0) returning a dummy value (current locale)
0036:fixme:nls:get_dummy_preferred_ui_language (0x8 0x31daf4 0x3aa40d0 0x31daf0) returning a dummy value (current locale)
0036:fixme:process:SetProcessPriorityBoost (00000268,0): stub
0042:fixme:path:parse_url failed to parse L"System.Web"
0036:fixme:path:parse_url failed to parse L"OpenTK"
0042:fixme:path:parse_url failed to parse L"Microsoft.Build.Framework"
0042:fixme:path:parse_url failed to parse L"Microsoft.Build.Utilities.v4.0"
0042:fixme:path:parse_url failed to parse L"System.ComponentModel.DataAnnotations"
0042:fixme:path:parse_url failed to parse L"System.Runtime.Caching"
0042:fixme:path:parse_url failed to parse L"System.Data"
0042:fixme:path:parse_url failed to parse L"System.Web.ApplicationServices"
0042:fixme:path:parse_url failed to parse L"System.DirectoryServices.Protocols"
0042:fixme:path:parse_url failed to parse L"System.DirectoryServices"
0042:fixme:path:parse_url failed to parse L"System.EnterpriseServices"
0042:fixme:path:parse_url failed to parse L"System.ServiceProcess"
0042:fixme:path:parse_url failed to parse L"System.Web.Services"
0042:fixme:path:parse_url failed to parse L"System.Design"
0042:fixme:path:parse_url failed to parse L"Microsoft.Build.Tasks.v4.0"
0042:fixme:path:parse_url failed to parse L"System.Web.RegularExpressions"
0042:fixme:path:parse_url failed to parse L"System.Transactions"
0042:fixme:combase:RoGetParameterizedTypeInstanceIID stub: 4 03B35268 0831B62C 0831BC90 00000000
0042:fixme:combase:RoGetParameterizedTypeInstanceIID stub: 3 03B285A4 0831B81C 0831BE80 00000000
0042:fixme:combase:RoGetParameterizedTypeInstanceIID stub: 3 03B285A4 0831B81C 0831BE80 00000000
0036:err:winediag:wined3d_dll_init Setting multithreaded command stream to 0x1.
0043:fixme:path:parse_url failed to parse L"System.Configuration"
0043:fixme:path:parse_url failed to parse L"System.Xml"
0043:fixme:path:parse_url failed to parse L"System.Data.SqlXml"
0043:fixme:ras:RasEnumConnectionsW (03B65D40,084BEE80,084BEE84),stub!
0043:fixme:ras:RasEnumConnectionsW RAS is not implemented! Configure program to use LAN connection/winsock instead!
0043:fixme:winsock:set_dont_fragment IP_DONTFRAGMENT for IPv4 not ed in this platform
0043:fixme:winsock:set_dont_fragment IP_DONTFRAGMENT for IPv6 not ed in this platform
0043:err:winsock:WSAIoctl -> SIO_ADDRESS_LIST_CHANGE request failed with status 0x2733
0043:err:winsock:WSAIoctl -> SIO_ADDRESS_LIST_CHANGE request failed with status 0x2733
0043:fixme:ras:RasConnectionNotificationW (FFFFFFFF,00000328,0x00000003),stub!
0036:fixme:combase:RoGetParameterizedTypeInstanceIID stub: 4 03B5DD78 0031D24C 0031D8B0 00000000
0036:fixme:combase:RoGetParameterizedTypeInstanceIID stub: 3 03B5DC54 0031D43C 0031DAA0 00000000
0036:fixme:combase:RoGetParameterizedTypeInstanceIID stub: 3 03B5DC54 0031D43C 0031DAA0 00000000
0036:fixme:ntdll:EtwEvent ({8e9f5090-2d75-4d03-8a81-e5afbf85daf1}, 0xa60732, 0x0, 0x194cb44) stub.
0036:fixme:path:parse_url failed to parse L"osu!.resources"
0036:fixme:nls:LCMapStringEx uned lparam 3ac0d80
0036:fixme:path:parse_url failed to parse L"osu!.resources"
0036:fixme:coreaudio:ca_channel_layout_to_channel_mask Unhandled channel 0xffffffff
0036:fixme:coreaudio:ca_channel_layout_to_channel_mask Unhandled channel 0xffffffff
0036:fixme:coreaudio:ca_channel_layout_to_channel_mask Unhandled channel 0xffffffff
0036:fixme:coreaudio:ca_channel_layout_to_channel_mask Unhandled channel 0xffffffff
0036:fixme:coreaudio:ca_channel_layout_to_channel_mask Unhandled channel 0xffffffff
0048:fixme:avrt:AvSetMmThreadCharacteristicsW (L"Audio",0B4CFDF8): stub
0036:fixme:process:FlushProcessWriteBuffers : stub
004c:fixme:thread:NtGetCurrentProcessorNumber need multicore (8 processors)
004c:fixme:path:parse_url failed to parse L"System.Runtime.Serialization"
004c:fixme:path:parse_url failed to parse L"SMDiagnostics"
004c:fixme:path:parse_url failed to parse L"System.ServiceModel.Internals"
004c:fixme:path:parse_url failed to parse L"System.Numerics"
0036:fixme:path:parse_url failed to parse L"osu!ui"
0036:fixme:path:parse_url failed to parse L"osu!ui.resources"
004c:fixme:path:parse_url failed to parse L"System.Data"
0042:fixme:path:parse_url failed to parse L"System.Runtime.Remoting"
004c:fixme:advapi:EventSourceW ((null),L".NET Runtime"): stub
004c:fixme:advapi:ReportEventW (0xcafe4242,0x0001,0x0000,0x000003ff,0x0,0x0001,0x00000000,0xb90d5bc,0x0): stub
004c:err:eventlog:ReportEventW L"Application: osu!.exe\nFramework Version: v4.0.30319\nDescription: The process was terminated due to an internal error in the .NET Runtime at IP 00E03BED (00D90000) with exit code 80131506.\n"
004c:fixme:advapi:DeEventSource (0xcafe4242) stub
I'll see if deleting and replacing the files on the old Wineskin works
Thanks to everyone for helping fix these issues
Update - For the old Wineskin: I deleted all the files mentioned, ed the osu! exe for Windows, and dragged it into the drive_c/osu! folder.
There were a few files I didn't see mentioned (namely d3dx9_31.dll, Microsoft.Xna.Framework.dll, osu!seasonal.dll, osu!dll, and x3daudio1_1.dll.) I left them alone for now.
When I did the Agent again, it didn't seem to help. I might have done something wrong, though.
ReportVersion 10.16 (Build 20C69)
Engine: WS11WineCX64Bit19.0.1-1
Wineskin 2.9.0.6 1
Game configuration is absent
Quarantine attribute is absent
Execute flag is present
Detect Direct3D is enabled
Compatibility mode is disabled
System Integrity Protection is enabled
Engine version is ed
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
I think there are two possibilities to this...
- somehow its a problem with osu. I doubt this is the issue but just to make sure maybe update it through Agent again.
- .NET (aka dotnet) isn't working properly (see tech note below) - e.g compatibility problem. This one is probably more likely though I'm not really sure how it would be caused.
To be entirely honest, for myself at least I'll probably need a bit of time to figure out what's going on with dotnet. But maybe Techno or someone else has an idea...
tech note: according to stack overflow its a GC issue, but I feel like that's irrelevant to a -facing fix. I recall that Techno used dotnet45 which pointed at dotnet40 - this seems to have worked looking at your log, but I also slc had issues getting dotnet45 to work (community/forums/posts/6919370). So maybe switch over to dotnet40 (and also gets to ensure one cleans out the failing dependency)?
I also note the following messages that I got while trying to mess about with Winetricks (which resulted in a wineserver crash, yay) - Probably not relevant now, but probably worth keeping in the back of my mind
warning: This package (dotnet40) may not fully work on a 64-bit installation. 32-bit prefixes may work better. ------------------------------------------------------ ------------------------------------------------------ warning: dotnet40 does not yet fully work or install on wine. Caveat emptor.
With respect to the old Wineskin, that is super weird. Could you look through the files in drive_c/osu/Logs and see if you can find anything of interest. In particular network.log, update.log, and if you have one, update_success.log. If you do find anything leave it in a pastie and we can take a look at it for ya. Might be better to reinstall the Wineskin (always the safest option even tho its annoying to move everything over and there's the offchance it doesn't work) but you could give that a shot too in the meantime. I assume osu! just isn't starting now as well.
Sorry I couldn't be of much help, I'll try and think about what could be causing that dotnet issue.
KyzuiKyzui wrote: 5l7011
My osu has been fine opening ever since I ed like 4 months ago but for some reason the "Restart" button won't pop up now when I try to open osu!. There is no way for me to get into the application without this option. Any ideas?
hi and welcome to the osu! forums! Which "Restart" button are you talking about precisely? It would also help if you could generate both a osu!macOS Agent report, as well as a Test Run, using the instructions linked below.
- Agent report: https://osu-mac.readthedocs.io/en/latest/issues/troubleshooting.html#generating-a-report-with-osu-macos-agent
- Test Run: https://osu-mac.readthedocs.io/en/latest/issues/troubleshooting.html#generating-logs-for-wineskin
osu!macOS Agent here: community/forums/topics/1036678
----
Edit: also I thought I was going crazy, but in attempting to experiment with some of the newer Wineskins, I managed to get the Kill Wineskin Processes button to start osu! xD
000b:fixme:thread:create__shared_data_thread Creating shared data update thread.
000d:fixme:thread:create__shared_data_thread Creating shared data update thread.
0010:fixme:thread:create__shared_data_thread Creating shared data update thread.
0018:fixme:thread:create__shared_data_thread Creating shared data update thread.
001d:fixme:thread:create__shared_data_thread Creating shared data update thread.
0023:err:plugplay:process_IOService_Device object 0x3a03
0023:err:plugplay:process_IOService_Device Unable to create plug in interface for USB deviceobject 0x3a07
0023:err:plugplay:process_IOService_Device Unable to create plug in interface for USB deviceobject 0x3a0b
0023:err:plugplay:process_IOService_Device Unable to create plug in interface for USB deviceobject 0x3a0f
0023:err:plugplay:process_IOService_Device Unable to create plug in interface for USB deviceobject 0x3a13
0023:err:plugplay:process_IOService_Device Unable to create plug in interface for USB deviceobject 0x3a17
0023:err:plugplay:process_IOService_Device Unable to create plug in interface for USB deviceobject 0x3a1b
0023:err:plugplay:process_IOService_Device Unable to create plug in interface for USB deviceobject 0x3a1f
0009:fixme:thread:create__shared_data_thread Creating shared data update thread.
0009:fixme:heap:RtlSetHeapInformation 0x240000 0 0x23e670 4 stub
0009:fixme:kernelbase:QuirkIsEnabled3 (000000000023F120, 00000000FFFFFFFF) stub!
0009:fixme:process:GetNumaHighestNodeNumber (0x23f9a4): semi-stub
0009:fixme:thread:SetThreadStackGuarantee (0x23f938): stub
0028:fixme:thread:create__shared_data_thread Creating shared data update thread.
0026:err:ole:CoGetContextToken apartment not initialised
0009:fixme:path:parse_url failed to parse L"System.Windows.Forms"
0009:fixme:path:parse_url failed to parse L"System.Drawing"
0009:fixme:path:parse_url failed to parse L"System"
0009:fixme:path:parse_url failed to parse L"System.Configuration"
0009:fixme:path:parse_url failed to parse L"System.Xml"
0009:fixme:path:parse_url failed to parse L"Accessibility"
0009:fixme:path:parse_url failed to parse L"System.Security"
0009:fixme:path:parse_url failed to parse L"System.Runtime.Serialization.Formatters.Soap"
0009:fixme:path:parse_url failed to parse L"System.Deployment"
0009:fixme:path:parse_url failed to parse L"System.Core"
0009:fixme:path:parse_url failed to parse L"System.Drawing"
0009:fixme:path:parse_url failed to parse L"System"
0009:fixme:ntdll:EtwEvent ({8e9f5090-2d75-4d03-8a81-e5afbf85daf1}, 0x1a31040c, 0x0, 0x1abb018) stub.
0009:fixme:path:parse_url failed to parse L"System.Core"
0009:fixme:path:parse_url failed to parse L"System.Numerics"
0009:fixme:nls:get_dummy_preferred_ui_language (0x8 0x23b940 0x0 0x23b944) returning a dummy value (current locale)
0009:fixme:nls:get_dummy_preferred_ui_language (0x8 0x23b940 0xdf8f0 0x23b944) returning a dummy value (current locale)
0009:fixme:process:SetProcessPriorityBoost (0x254,0): stub
0009:fixme:path:parse_url failed to parse L"OpenTK"
0034:fixme:path:parse_url failed to parse L"System.Web"
0034:fixme:path:parse_url failed to parse L"Microsoft.Build.Framework"
0034:fixme:path:parse_url failed to parse L"Microsoft.Build.Utilities.v4.0"
0034:fixme:path:parse_url failed to parse L"System.ComponentModel.DataAnnotations"
0034:fixme:path:parse_url failed to parse L"System.Runtime.Caching"
0034:fixme:path:parse_url failed to parse L"System.Data"
0034:fixme:path:parse_url failed to parse L"System.Web.ApplicationServices"
0034:fixme:path:parse_url failed to parse L"System.DirectoryServices.Protocols"
0034:fixme:path:parse_url failed to parse L"System.DirectoryServices"
0034:fixme:path:parse_url failed to parse L"System.EnterpriseServices"
0034:fixme:path:parse_url failed to parse L"System.ServiceProcess"
0034:fixme:path:parse_url failed to parse L"System.Web.Services"
0034:fixme:path:parse_url failed to parse L"System.Design"
0034:fixme:path:parse_url failed to parse L"Microsoft.Build.Tasks.v4.0"
0034:fixme:path:parse_url failed to parse L"System.Web.RegularExpressions"
0034:fixme:path:parse_url failed to parse L"System.Transactions"
0034:fixme:combase:RoGetParameterizedTypeInstanceIID stub: 4 000000001B15AD00 000000001C367880 000000001C368230 0000000000000000
0034:fixme:combase:RoGetParameterizedTypeInstanceIID stub: 3 000000001B12EFB0 000000001C367C20 000000001C3685D0 0000000000000000
0034:fixme:combase:RoGetParameterizedTypeInstanceIID stub: 3 000000001B12EFB0 000000001C367C20 000000001C3685D0 0000000000000000
0034:fixme:crypt:SystemFunction041 (0xde268, 10, 0): stub [RtlDecryptMemory]
0034:fixme:crypt:SystemFunction040 (0x1b12e9e8, 10, 0): stub [RtlEncryptMemory]
0034:fixme:crypt:SystemFunction041 (0x1b12e9e8, 10, 0): stub [RtlDecryptMemory]
0034:fixme:crypt:SystemFunction040 (0x1b12e9e8, 10, 0): stub [RtlEncryptMemory]
0034:fixme:crypt:SystemFunction041 (0x1b12e9e8, 10, 0): stub [RtlDecryptMemory]
0034:fixme:crypt:SystemFunction040 (0x1b12e9e8, 10, 0): stub [RtlEncryptMemory]
0034:fixme:crypt:SystemFunction041 (0x1b12e9e8, 10, 0): stub [RtlDecryptMemory]
0034:fixme:crypt:SystemFunction040 (0x1b12e9e8, 10, 0): stub [RtlEncryptMemory]
0034:fixme:crypt:SystemFunction041 (0x1b12e9e8, 10, 0): stub [RtlDecryptMemory]
0034:fixme:crypt:SystemFunction040 (0x1b12e9e8, 10, 0): stub [RtlEncryptMemory]
0034:fixme:crypt:SystemFunction041 (0x1b12e9e8, 10, 0): stub [RtlDecryptMemory]
0034:fixme:crypt:SystemFunction040 (0x1b12e9e8, 10, 0): stub [RtlEncryptMemory]
0034:fixme:crypt:SystemFunction041 (0x1b12e9e8, 10, 0): stub [RtlDecryptMemory]
0034:fixme:crypt:SystemFunction040 (0x1b12e9e8, 10, 0): stub [RtlEncryptMemory]
0034:fixme:crypt:SystemFunction041 (0x1b12e9e8, 10, 0): stub [RtlDecryptMemory]
0034:fixme:crypt:SystemFunction040 (0x1b12e9e8, 10, 0): stub [RtlEncryptMemory]
0034:fixme:crypt:SystemFunction041 (0x1b12e9e8, 10, 0): stub [RtlDecryptMemory]
0034:fixme:crypt:SystemFunction040 (0x1b12e9e8, 10, 0): stub [RtlEncryptMemory]
0009:fixme:combase:RoGetParameterizedTypeInstanceIID stub: 2 000000001B137608 000000000023A780 000000000023B130 0000000000000000
0009:fixme:combase:RoGetParameterizedTypeInstanceIID stub: 2 000000001B137908 000000000023A780 000000000023B130 0000000000000000
0036:fixme:path:parse_url failed to parse L"System.Configuration"
0036:fixme:path:parse_url failed to parse L"System.Xml"
0036:fixme:path:parse_url failed to parse L"System.Data.SqlXml"
0036:fixme:ras:RasEnumConnectionsW (000000001B18A020,000000001D78E484,000000001D78E480),stub!
0036:fixme:ras:RasEnumConnectionsW RAS is not implemented! Configure program to use LAN connection/winsock instead!
0036:fixme:winsock:set_dont_fragment IP_DONTFRAGMENT for IPv4 not ed in this platform
0036:fixme:winsock:set_dont_fragment IP_DONTFRAGMENT for IPv6 not ed in this platform
0036:err:winsock:WSAIoctl -> SIO_ADDRESS_LIST_CHANGE request failed with status 0x2733
0036:err:winsock:WSAIoctl -> SIO_ADDRESS_LIST_CHANGE request failed with status 0x2733
0036:fixme:ras:RasConnectionNotificationW (FFFFFFFFFFFFFFFF,0000000000000334,0x00000003),stub!
0036:fixme:nls:LCMapStringEx uned lparam 10ba90
0036:fixme:ntdll:EtwEvent ({38ed3633-5e3f-5989-bf25-f0b1b3318c9b}, 0x1a310a0c, 0x0, 0x1c0efd8) stub.
0036:fixme:winhttp:WinHttpDetectAutoProxyConfigUrl discovery via DH not ed
0009:fixme:combase:RoGetParameterizedTypeInstanceIID stub: 4 000000001B1A96D8 000000000023ABF0 000000000023B5A0 0000000000000000
0009:fixme:combase:RoGetParameterizedTypeInstanceIID stub: 3 000000001B1A9798 000000000023AF90 000000000023B940 0000000000000000
0009:fixme:combase:RoGetParameterizedTypeInstanceIID stub: 3 000000001B1A9798 000000000023AF90 000000000023B940 0000000000000000
0009:fixme:path:parse_url failed to parse L"osu!.resources"
0009:fixme:path:parse_url failed to parse L"osu!.resources"
0009:fixme:ver:GetCurrentPackageId (0x239f70 0x0): stub
003a:fixme:process:FlushProcessWriteBuffers : stub
0026:fixme:ntdll:EtwEventUn (deadbeef) stub.
0026:fixme:ntdll:EtwEventUn (deadbeef) stub.
0026:fixme:ole:Context_CC_ContextCallback (000000001B1AB1C0/000000001B1AB1C8)->(0000000000D00D80, 000000001A02F140, {d7174f82-36b8-4aa8-800a-e963ab2dfab9}, 2, 0000000000000000)
0026:fixme:ole:Context_CC_ContextCallback (000000001B1AB1C0/000000001B1AB1C8)->(0000000000D00D80, 000000001A02F040, {d7174f82-36b8-4aa8-800a-e963ab2dfab9}, 2, 0000000000000000)
0026:fixme:ole:Context_CC_ContextCallback (000000001B1AB1C0/000000001B1AB1C8)->(0000000000D00D80, 000000001A02F040, {d7174f82-36b8-4aa8-800a-e963ab2dfab9}, 2, 0000000000000000)
Let me know if I should just re- osu!.
aidswidjaja wrote: 4a1ul
TechnocoderTechnocoder wrote: 365p3v
Strangely enough, I get the same crash report when using the WineCX20 engine but not with the WineCX64Bit20 engine... and I'm running macOS Catalina, not Big Sur or M1.
Please try using this Wineskin which uses WineCX20 instead: https://mega.nz/file/ZxlQ1AiS#A-2sPJI5zg_7Dn___VXmO5EEY4qRyJm6uAu7TpiLA9U
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.
Hmm... So far I haven't been able to replicate the crash report on any Wineskin.
WS11WineCX64Bit19.0.1-1 :: Works fine normally, Test Run opens osu! as expected
WS11WineCX64Bit20.0.0 :: Works fine normally, Test Run opens osu! as expected
WS11WineCX6420.0.0 :: wine: '/s/Adrian/Desktop/WS11CX20.0.0.app/Contents/Resources' is a 64-bit installation, it cannot be used with a 32-bit wineserver. (expected error)
This is on my 2016 MBP wo/ touch bar - Intel x86 i5. 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. Maybe I'll try again and see what happens there.
How did you get WineCX20 to run (on Catalina)? As expected I'm getting 64-bit compatibility issues on 32-bit wineserver (hence why wine32on64 is used)
AnimatedThinksAnimatedThinks wrote: 685o4u
I tried out the new Wineskin just now (I also ed the new mac!OS Agent, I realized the old one wouldn't detect the new Wineskin.)
When opening it (either through Test Run or by normal double-clicking), it shows the osu! popup, but never actually opens.
Here's the Test Run that popped up when I tried opening osu! that way:
Test Run000b:fixme:thread:create__shared_data_thread Creating shared data update thread.
000d:fixme:thread:create__shared_data_thread Creating shared data update thread.
0010:fixme:thread:create__shared_data_thread Creating shared data update thread.
0018:fixme:thread:create__shared_data_thread Creating shared data update thread.
001d:fixme:thread:create__shared_data_thread Creating shared data update thread.
0009:fixme:thread:create__shared_data_thread Creating shared data update thread.
0009:fixme:exec:SHELL_execute flags ignored: 0x00000100
0009:fixme:ntdll:FILE_GetNtStatus Converting errno 8 to STATUS_UNSUCCESSFUL
0026:fixme:thread:create__shared_data_thread Creating shared data update thread.
0028:fixme:thread:create__shared_data_thread Creating shared data update thread.
002a:fixme:thread:create__shared_data_thread Creating shared data update thread.
0031:fixme:thread:create__shared_data_thread Creating shared data update thread.
0036:fixme:ntdll:NtQuerySystemInformation info_class SYSTEM_PERFORMANCE_INFORMATION
0036:fixme:heap:GetNumaHighestNodeNumber semi-stub: 0031FAC8
0038:err:ole:CoGetContextToken apartment not initialised
0036:fixme:time:QueryThreadCycleTime (0xfffffffe,0x5d52560): stub!
0036:fixme:path:parse_url failed to parse L"System.Windows.Forms"
0036:fixme:path:parse_url failed to parse L"System.Drawing"
0036:fixme:path:parse_url failed to parse L"System"
0036:fixme:path:parse_url failed to parse L"System.Configuration"
0036:fixme:path:parse_url failed to parse L"System.Xml"
0036:fixme:path:parse_url failed to parse L"Accessibility"
0036:fixme:path:parse_url failed to parse L"System.Security"
0036:fixme:path:parse_url failed to parse L"System.Runtime.Serialization.Formatters.Soap"
0036:fixme:path:parse_url failed to parse L"System.Deployment"
0036:fixme:path:parse_url failed to parse L"System.Core"
0036:fixme:path:parse_url failed to parse L"System.Drawing"
0036:fixme:path:parse_url failed to parse L"System"
0036:fixme:path:parse_url failed to parse L"System.Core"
0036:fixme:path:parse_url failed to parse L"System.Numerics"
0036:fixme:nls:get_dummy_preferred_ui_language (0x8 0x31daf4 0x0 0x31daf0) returning a dummy value (current locale)
0036:fixme:nls:get_dummy_preferred_ui_language (0x8 0x31daf4 0x3aa40d0 0x31daf0) returning a dummy value (current locale)
0036:fixme:process:SetProcessPriorityBoost (00000268,0): stub
0042:fixme:path:parse_url failed to parse L"System.Web"
0036:fixme:path:parse_url failed to parse L"OpenTK"
0042:fixme:path:parse_url failed to parse L"Microsoft.Build.Framework"
0042:fixme:path:parse_url failed to parse L"Microsoft.Build.Utilities.v4.0"
0042:fixme:path:parse_url failed to parse L"System.ComponentModel.DataAnnotations"
0042:fixme:path:parse_url failed to parse L"System.Runtime.Caching"
0042:fixme:path:parse_url failed to parse L"System.Data"
0042:fixme:path:parse_url failed to parse L"System.Web.ApplicationServices"
0042:fixme:path:parse_url failed to parse L"System.DirectoryServices.Protocols"
0042:fixme:path:parse_url failed to parse L"System.DirectoryServices"
0042:fixme:path:parse_url failed to parse L"System.EnterpriseServices"
0042:fixme:path:parse_url failed to parse L"System.ServiceProcess"
0042:fixme:path:parse_url failed to parse L"System.Web.Services"
0042:fixme:path:parse_url failed to parse L"System.Design"
0042:fixme:path:parse_url failed to parse L"Microsoft.Build.Tasks.v4.0"
0042:fixme:path:parse_url failed to parse L"System.Web.RegularExpressions"
0042:fixme:path:parse_url failed to parse L"System.Transactions"
0042:fixme:combase:RoGetParameterizedTypeInstanceIID stub: 4 03B35268 0831B62C 0831BC90 00000000
0042:fixme:combase:RoGetParameterizedTypeInstanceIID stub: 3 03B285A4 0831B81C 0831BE80 00000000
0042:fixme:combase:RoGetParameterizedTypeInstanceIID stub: 3 03B285A4 0831B81C 0831BE80 00000000
0036:err:winediag:wined3d_dll_init Setting multithreaded command stream to 0x1.
0043:fixme:path:parse_url failed to parse L"System.Configuration"
0043:fixme:path:parse_url failed to parse L"System.Xml"
0043:fixme:path:parse_url failed to parse L"System.Data.SqlXml"
0043:fixme:ras:RasEnumConnectionsW (03B65D40,084BEE80,084BEE84),stub!
0043:fixme:ras:RasEnumConnectionsW RAS is not implemented! Configure program to use LAN connection/winsock instead!
0043:fixme:winsock:set_dont_fragment IP_DONTFRAGMENT for IPv4 not ed in this platform
0043:fixme:winsock:set_dont_fragment IP_DONTFRAGMENT for IPv6 not ed in this platform
0043:err:winsock:WSAIoctl -> SIO_ADDRESS_LIST_CHANGE request failed with status 0x2733
0043:err:winsock:WSAIoctl -> SIO_ADDRESS_LIST_CHANGE request failed with status 0x2733
0043:fixme:ras:RasConnectionNotificationW (FFFFFFFF,00000328,0x00000003),stub!
0036:fixme:combase:RoGetParameterizedTypeInstanceIID stub: 4 03B5DD78 0031D24C 0031D8B0 00000000
0036:fixme:combase:RoGetParameterizedTypeInstanceIID stub: 3 03B5DC54 0031D43C 0031DAA0 00000000
0036:fixme:combase:RoGetParameterizedTypeInstanceIID stub: 3 03B5DC54 0031D43C 0031DAA0 00000000
0036:fixme:ntdll:EtwEvent ({8e9f5090-2d75-4d03-8a81-e5afbf85daf1}, 0xa60732, 0x0, 0x194cb44) stub.
0036:fixme:path:parse_url failed to parse L"osu!.resources"
0036:fixme:nls:LCMapStringEx uned lparam 3ac0d80
0036:fixme:path:parse_url failed to parse L"osu!.resources"
0036:fixme:coreaudio:ca_channel_layout_to_channel_mask Unhandled channel 0xffffffff
0036:fixme:coreaudio:ca_channel_layout_to_channel_mask Unhandled channel 0xffffffff
0036:fixme:coreaudio:ca_channel_layout_to_channel_mask Unhandled channel 0xffffffff
0036:fixme:coreaudio:ca_channel_layout_to_channel_mask Unhandled channel 0xffffffff
0036:fixme:coreaudio:ca_channel_layout_to_channel_mask Unhandled channel 0xffffffff
0048:fixme:avrt:AvSetMmThreadCharacteristicsW (L"Audio",0B4CFDF8): stub
0036:fixme:process:FlushProcessWriteBuffers : stub
004c:fixme:thread:NtGetCurrentProcessorNumber need multicore (8 processors)
004c:fixme:path:parse_url failed to parse L"System.Runtime.Serialization"
004c:fixme:path:parse_url failed to parse L"SMDiagnostics"
004c:fixme:path:parse_url failed to parse L"System.ServiceModel.Internals"
004c:fixme:path:parse_url failed to parse L"System.Numerics"
0036:fixme:path:parse_url failed to parse L"osu!ui"
0036:fixme:path:parse_url failed to parse L"osu!ui.resources"
004c:fixme:path:parse_url failed to parse L"System.Data"
0042:fixme:path:parse_url failed to parse L"System.Runtime.Remoting"
004c:fixme:advapi:EventSourceW ((null),L".NET Runtime"): stub
004c:fixme:advapi:ReportEventW (0xcafe4242,0x0001,0x0000,0x000003ff,0x0,0x0001,0x00000000,0xb90d5bc,0x0): stub
004c:err:eventlog:ReportEventW L"Application: osu!.exe\nFramework Version: v4.0.30319\nDescription: The process was terminated due to an internal error in the .NET Runtime at IP 00E03BED (00D90000) with exit code 80131506.\n"
004c:fixme:advapi:DeEventSource (0xcafe4242) stub
I'll see if deleting and replacing the files on the old Wineskin works
Thanks to everyone for helping fix these issues
Update - For the old Wineskin: I deleted all the files mentioned, ed the osu! exe for Windows, and dragged it into the drive_c/osu! folder.
There were a few files I didn't see mentioned (namely d3dx9_31.dll, Microsoft.Xna.Framework.dll, osu!seasonal.dll, osu!dll, and x3daudio1_1.dll.) I left them alone for now.
When I did the Agent again, it didn't seem to help. I might have done something wrong, though.
ReportVersion 10.16 (Build 20C69)
Engine: WS11WineCX64Bit19.0.1-1
Wineskin 2.9.0.6 1
Game configuration is absent
Quarantine attribute is absent
Execute flag is present
Detect Direct3D is enabled
Compatibility mode is disabled
System Integrity Protection is enabled
Engine version is ed
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
I think there are two possibilities to this...
- somehow its a problem with osu. I doubt this is the issue but just to make sure maybe update it through Agent again.
- .NET (aka dotnet) isn't working properly (see tech note below) - e.g compatibility problem. This one is probably more likely though I'm not really sure how it would be caused.
To be entirely honest, for myself at least I'll probably need a bit of time to figure out what's going on with dotnet. But maybe Techno or someone else has an idea...
tech note: according to stack overflow its a GC issue, but I feel like that's irrelevant to a -facing fix. I recall that Techno used dotnet45 which pointed at dotnet40 - this seems to have worked looking at your log, but I also slc had issues getting dotnet45 to work (community/forums/posts/6919370). So maybe switch over to dotnet40 (and also gets to ensure one cleans out the failing dependency)?
I also note the following messages that I got while trying to mess about with Winetricks (which resulted in a wineserver crash, yay) - Probably not relevant now, but probably worth keeping in the back of my mind
warning: This package (dotnet40) may not fully work on a 64-bit installation. 32-bit prefixes may work better. ------------------------------------------------------ ------------------------------------------------------ warning: dotnet40 does not yet fully work or install on wine. Caveat emptor.
With respect to the old Wineskin, that is super weird. Could you look through the files in drive_c/osu/Logs and see if you can find anything of interest. In particular network.log, update.log, and if you have one, update_success.log. If you do find anything leave it in a pastie and we can take a look at it for ya. Might be better to reinstall the Wineskin (always the safest option even tho its annoying to move everything over and there's the offchance it doesn't work) but you could give that a shot too in the meantime. I assume osu! just isn't starting now as well.
Sorry I couldn't be of much help, I'll try and think about what could be causing that dotnet issue.
KyzuiKyzui wrote: 5l7011
My osu has been fine opening ever since I ed like 4 months ago but for some reason the "Restart" button won't pop up now when I try to open osu!. There is no way for me to get into the application without this option. Any ideas?
hi and welcome to the osu! forums! Which "Restart" button are you talking about precisely? It would also help if you could generate both a osu!macOS Agent report, as well as a Test Run, using the instructions linked below.
- Agent report: https://osu-mac.readthedocs.io/en/latest/issues/troubleshooting.html#generating-a-report-with-osu-macos-agent
- Test Run: https://osu-mac.readthedocs.io/en/latest/issues/troubleshooting.html#generating-logs-for-wineskin
osu!macOS Agent here: community/forums/topics/1036678
----
Edit: also I thought I was going crazy, but in attempting to experiment with some of the newer Wineskins, I managed to get the Kill Wineskin Processes button to start osu! xD
aidswidjaja wrote: 4a1ul
Sorry for disappearing for a while, let's see how many I can get through lol
pinkfujoshiYou could try updating the osu!.exe manually by ing it from home/ then replacing it in your Wineskin. If that doesn't work let us know and attach the contents of drive_c/osu!/Logs/update.to a pastebin such as paste.ubuntu.comHello again, I did follow your advice, and it started working. But as of right now, I cannot open it again. T~T Here's the report:
lucid126Good to hear you fixed everything, let us know if you encounter any more issues. Also feel free to let us know what you did to fix it.all right, when I opened osu! and tried to a map, a pop up box said that no windows app could run it, so i followed the steps and checked the automatically move ed songs to the songs folder, now there's only 1 song on there and its birdsong. i ran the report and said everything was fine. I'm on mojave. has anyone experienced this? Edit: I got the song to work, but now whenever I try to exit to the main menu it just goes to a black screen. Edit 2: I fixed everyrhing
raiqoUpdating to Big Sur won't really fix your problem unfortunately. If the test run is giving you different results to the actual executable, try repairing the exe through agent again or alternatively running this command:so i launched osu! through the wineskin and it opened, it was working fine and all my maps and skins were there. i then closed it and the thing popped up so i clicked yes and got this: https://paste.ubuntu.com/p/K8XxgNzqc4/
i tried launching osu normally but it still tells me that its damaged. do i just use the wineskin to launch from now on or is there someway to fix the problem? i've also considered updating to Big Sur (i'm currently running Mojave 10.14.6) would that help solve the problem?
edit: just tried launching it again from the test run and it lets me but i cant use any skins and when i try to play maps the game crashes
sudo xattr -rd com.apple.quarantine "~/path/to/my/osu\!.app"
Can you also make sure that your Skins and Songs folders in drive_c/osu! aren't corrupted or anything. It *is* pretty weird how your install is behaving and somewhat corrupted... You're getting a lot of errors, such as these
0098:fixme:path:parse_url failed to parse L"osu!ui" 0098:fixme:path:parse_url failed to parse L"osu!ui.resources"
If you haven't already, I'd try reinstalling just to be sure and to isolate that issue. Also you could try to go to Wineskin.app > Advanced > Tools > and under Wrapper Tools click Refresh Wrapper (do NOT click Rebuild as this will delete everything including your Songs, scores, etc, unless you have them backed up - if they're backed up you could try that as well) - BE CAREFUL ABOUT DOING THIS (I may have done it to myself and now my osu! won't update :/ - maybe make a backup first
Also are the logs the same on your second test run (when the skins don't load, maps crash the game etc) ?
It's some pretty weird stuff, keep us informed and try the stuff above
AmAWolfSorry for not replying,
no, I didn't try but could you give me the Wineskin.app so I can try it?
And could you explain me what I have to do? I'm not that techieWill to Google Drive now, and I'll provide instructions + link by editing this post once its doneSee below, let me know if there are any problems
Also yea, if Agent isn't returning anything weird then there won't be any useful debugging info there for us to find.
PaydruThe report is showing errors with respect to updating the osu! application. Could you try updating from osu!macOS Agent:i havent had any problems with this until now. osu doesnt re-open unless i restart my laptop and whwen i run the troubleshoot, it givess me this
Alternatively the executable binary directly from home/ and replace it within your application
- Open osu!macOS Agent
- Click the Other tab
- Click Update osu!
- osu.exe from osu-ppy-sh.tvgratuite.org/home/.
- Locate where osu!.app (your Wineskin) is installed
- Right click on it and select Show Package Contents
- You should now see three files/folders: Contents, drive_c and Wineskin. Click drive_c.
- From here, click osu!.
- From here, locate osu!.exe and replace this file with the updated version that you just ed. Make sure you keep the filename the same.
Not much happening, just trying to debug different issuesOblivous wrote: 246345
Can someone quote this message and tell me what'd I miss? lmao
Wineskin.app replacement 3i2j1h
If you are experiencing issues with Wineskin.app, you can try ing it separately.
Instructions: https://osu-mac.readthedocs.io/en/latest/issues/wineskin.html#resolution
link: https://minhaskamal.github.io/DownGit/#/home?url=https://github.com/aidswidjaja/osu-mac/tree/main/src/wineskin or https://drive.google.com/drive/folders/1Gz5Y0M4WoMxTTwb5aHUccebO5AlVm3SN?usp=sharing
Please be advised if that this hasn't been tested and that distributing the Wineskin.app file on its own is completely experimental so it might not fix your issues. But definitely let me know if there are any problems with it
- Click the Link above
- If using Google Drive, click ALL in the top-right corner of the screen
- It will this as a zip file. Extract the zip file until you just have the Wineskin.app file
- Inside osu!.app (Right click > Show Package Contents) locate Wineskin.app - make a backup of it (you can just rename it to say something like Wineskin.app.backup if you want)
- Move the new version of Wineskin.app from Google Drive into osu!.app
- Try and open it and see if everything works out.
![]()
You were probably using my old experimental Catalina Wineskin from my old thread? That one has the osu! crash on startup issue.Kyzui wrote: 5l7011
Alright I'll try it out thanks!However, can I get some help on how to transfer all my songs and skin or at least save them so I don't lose them all?
AnimatedThinks wrote: 685o4u
aidswidjajaaidswidjaja wrote: 4a1ul
TechnocoderTechnocoder wrote: 365p3v
Strangely enough, I get the same crash report when using the WineCX20 engine but not with the WineCX64Bit20 engine... and I'm running macOS Catalina, not Big Sur or M1.
Please try using this Wineskin which uses WineCX20 instead: https://mega.nz/file/ZxlQ1AiS#A-2sPJI5zg_7Dn___VXmO5EEY4qRyJm6uAu7TpiLA9U
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.
Hmm... So far I haven't been able to replicate the crash report on any Wineskin.
WS11WineCX64Bit19.0.1-1 :: Works fine normally, Test Run opens osu! as expected
WS11WineCX64Bit20.0.0 :: Works fine normally, Test Run opens osu! as expected
WS11WineCX6420.0.0 :: wine: '/s/Adrian/Desktop/WS11CX20.0.0.app/Contents/Resources' is a 64-bit installation, it cannot be used with a 32-bit wineserver. (expected error)
This is on my 2016 MBP wo/ touch bar - Intel x86 i5. 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. Maybe I'll try again and see what happens there.
How did you get WineCX20 to run (on Catalina)? As expected I'm getting 64-bit compatibility issues on 32-bit wineserver (hence why wine32on64 is used)
AnimatedThinksAnimatedThinks wrote: 685o4u
I tried out the new Wineskin just now (I also ed the new mac!OS Agent, I realized the old one wouldn't detect the new Wineskin.)
When opening it (either through Test Run or by normal double-clicking), it shows the osu! popup, but never actually opens.
Here's the Test Run that popped up when I tried opening osu! that way:
Test Run000b:fixme:thread:create__shared_data_thread Creating shared data update thread.
000d:fixme:thread:create__shared_data_thread Creating shared data update thread.
0010:fixme:thread:create__shared_data_thread Creating shared data update thread.
0018:fixme:thread:create__shared_data_thread Creating shared data update thread.
001d:fixme:thread:create__shared_data_thread Creating shared data update thread.
0009:fixme:thread:create__shared_data_thread Creating shared data update thread.
0009:fixme:exec:SHELL_execute flags ignored: 0x00000100
0009:fixme:ntdll:FILE_GetNtStatus Converting errno 8 to STATUS_UNSUCCESSFUL
0026:fixme:thread:create__shared_data_thread Creating shared data update thread.
0028:fixme:thread:create__shared_data_thread Creating shared data update thread.
002a:fixme:thread:create__shared_data_thread Creating shared data update thread.
0031:fixme:thread:create__shared_data_thread Creating shared data update thread.
0036:fixme:ntdll:NtQuerySystemInformation info_class SYSTEM_PERFORMANCE_INFORMATION
0036:fixme:heap:GetNumaHighestNodeNumber semi-stub: 0031FAC8
0038:err:ole:CoGetContextToken apartment not initialised
0036:fixme:time:QueryThreadCycleTime (0xfffffffe,0x5d52560): stub!
0036:fixme:path:parse_url failed to parse L"System.Windows.Forms"
0036:fixme:path:parse_url failed to parse L"System.Drawing"
0036:fixme:path:parse_url failed to parse L"System"
0036:fixme:path:parse_url failed to parse L"System.Configuration"
0036:fixme:path:parse_url failed to parse L"System.Xml"
0036:fixme:path:parse_url failed to parse L"Accessibility"
0036:fixme:path:parse_url failed to parse L"System.Security"
0036:fixme:path:parse_url failed to parse L"System.Runtime.Serialization.Formatters.Soap"
0036:fixme:path:parse_url failed to parse L"System.Deployment"
0036:fixme:path:parse_url failed to parse L"System.Core"
0036:fixme:path:parse_url failed to parse L"System.Drawing"
0036:fixme:path:parse_url failed to parse L"System"
0036:fixme:path:parse_url failed to parse L"System.Core"
0036:fixme:path:parse_url failed to parse L"System.Numerics"
0036:fixme:nls:get_dummy_preferred_ui_language (0x8 0x31daf4 0x0 0x31daf0) returning a dummy value (current locale)
0036:fixme:nls:get_dummy_preferred_ui_language (0x8 0x31daf4 0x3aa40d0 0x31daf0) returning a dummy value (current locale)
0036:fixme:process:SetProcessPriorityBoost (00000268,0): stub
0042:fixme:path:parse_url failed to parse L"System.Web"
0036:fixme:path:parse_url failed to parse L"OpenTK"
0042:fixme:path:parse_url failed to parse L"Microsoft.Build.Framework"
0042:fixme:path:parse_url failed to parse L"Microsoft.Build.Utilities.v4.0"
0042:fixme:path:parse_url failed to parse L"System.ComponentModel.DataAnnotations"
0042:fixme:path:parse_url failed to parse L"System.Runtime.Caching"
0042:fixme:path:parse_url failed to parse L"System.Data"
0042:fixme:path:parse_url failed to parse L"System.Web.ApplicationServices"
0042:fixme:path:parse_url failed to parse L"System.DirectoryServices.Protocols"
0042:fixme:path:parse_url failed to parse L"System.DirectoryServices"
0042:fixme:path:parse_url failed to parse L"System.EnterpriseServices"
0042:fixme:path:parse_url failed to parse L"System.ServiceProcess"
0042:fixme:path:parse_url failed to parse L"System.Web.Services"
0042:fixme:path:parse_url failed to parse L"System.Design"
0042:fixme:path:parse_url failed to parse L"Microsoft.Build.Tasks.v4.0"
0042:fixme:path:parse_url failed to parse L"System.Web.RegularExpressions"
0042:fixme:path:parse_url failed to parse L"System.Transactions"
0042:fixme:combase:RoGetParameterizedTypeInstanceIID stub: 4 03B35268 0831B62C 0831BC90 00000000
0042:fixme:combase:RoGetParameterizedTypeInstanceIID stub: 3 03B285A4 0831B81C 0831BE80 00000000
0042:fixme:combase:RoGetParameterizedTypeInstanceIID stub: 3 03B285A4 0831B81C 0831BE80 00000000
0036:err:winediag:wined3d_dll_init Setting multithreaded command stream to 0x1.
0043:fixme:path:parse_url failed to parse L"System.Configuration"
0043:fixme:path:parse_url failed to parse L"System.Xml"
0043:fixme:path:parse_url failed to parse L"System.Data.SqlXml"
0043:fixme:ras:RasEnumConnectionsW (03B65D40,084BEE80,084BEE84),stub!
0043:fixme:ras:RasEnumConnectionsW RAS is not implemented! Configure program to use LAN connection/winsock instead!
0043:fixme:winsock:set_dont_fragment IP_DONTFRAGMENT for IPv4 not ed in this platform
0043:fixme:winsock:set_dont_fragment IP_DONTFRAGMENT for IPv6 not ed in this platform
0043:err:winsock:WSAIoctl -> SIO_ADDRESS_LIST_CHANGE request failed with status 0x2733
0043:err:winsock:WSAIoctl -> SIO_ADDRESS_LIST_CHANGE request failed with status 0x2733
0043:fixme:ras:RasConnectionNotificationW (FFFFFFFF,00000328,0x00000003),stub!
0036:fixme:combase:RoGetParameterizedTypeInstanceIID stub: 4 03B5DD78 0031D24C 0031D8B0 00000000
0036:fixme:combase:RoGetParameterizedTypeInstanceIID stub: 3 03B5DC54 0031D43C 0031DAA0 00000000
0036:fixme:combase:RoGetParameterizedTypeInstanceIID stub: 3 03B5DC54 0031D43C 0031DAA0 00000000
0036:fixme:ntdll:EtwEvent ({8e9f5090-2d75-4d03-8a81-e5afbf85daf1}, 0xa60732, 0x0, 0x194cb44) stub.
0036:fixme:path:parse_url failed to parse L"osu!.resources"
0036:fixme:nls:LCMapStringEx uned lparam 3ac0d80
0036:fixme:path:parse_url failed to parse L"osu!.resources"
0036:fixme:coreaudio:ca_channel_layout_to_channel_mask Unhandled channel 0xffffffff
0036:fixme:coreaudio:ca_channel_layout_to_channel_mask Unhandled channel 0xffffffff
0036:fixme:coreaudio:ca_channel_layout_to_channel_mask Unhandled channel 0xffffffff
0036:fixme:coreaudio:ca_channel_layout_to_channel_mask Unhandled channel 0xffffffff
0036:fixme:coreaudio:ca_channel_layout_to_channel_mask Unhandled channel 0xffffffff
0048:fixme:avrt:AvSetMmThreadCharacteristicsW (L"Audio",0B4CFDF8): stub
0036:fixme:process:FlushProcessWriteBuffers : stub
004c:fixme:thread:NtGetCurrentProcessorNumber need multicore (8 processors)
004c:fixme:path:parse_url failed to parse L"System.Runtime.Serialization"
004c:fixme:path:parse_url failed to parse L"SMDiagnostics"
004c:fixme:path:parse_url failed to parse L"System.ServiceModel.Internals"
004c:fixme:path:parse_url failed to parse L"System.Numerics"
0036:fixme:path:parse_url failed to parse L"osu!ui"
0036:fixme:path:parse_url failed to parse L"osu!ui.resources"
004c:fixme:path:parse_url failed to parse L"System.Data"
0042:fixme:path:parse_url failed to parse L"System.Runtime.Remoting"
004c:fixme:advapi:EventSourceW ((null),L".NET Runtime"): stub
004c:fixme:advapi:ReportEventW (0xcafe4242,0x0001,0x0000,0x000003ff,0x0,0x0001,0x00000000,0xb90d5bc,0x0): stub
004c:err:eventlog:ReportEventW L"Application: osu!.exe\nFramework Version: v4.0.30319\nDescription: The process was terminated due to an internal error in the .NET Runtime at IP 00E03BED (00D90000) with exit code 80131506.\n"
004c:fixme:advapi:DeEventSource (0xcafe4242) stub
I'll see if deleting and replacing the files on the old Wineskin works
Thanks to everyone for helping fix these issues
Update - For the old Wineskin: I deleted all the files mentioned, ed the osu! exe for Windows, and dragged it into the drive_c/osu! folder.
There were a few files I didn't see mentioned (namely d3dx9_31.dll, Microsoft.Xna.Framework.dll, osu!seasonal.dll, osu!dll, and x3daudio1_1.dll.) I left them alone for now.
When I did the Agent again, it didn't seem to help. I might have done something wrong, though.
ReportVersion 10.16 (Build 20C69)
Engine: WS11WineCX64Bit19.0.1-1
Wineskin 2.9.0.6 1
Game configuration is absent
Quarantine attribute is absent
Execute flag is present
Detect Direct3D is enabled
Compatibility mode is disabled
System Integrity Protection is enabled
Engine version is ed
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
I think there are two possibilities to this...
- somehow its a problem with osu. I doubt this is the issue but just to make sure maybe update it through Agent again.
- .NET (aka dotnet) isn't working properly (see tech note below) - e.g compatibility problem. This one is probably more likely though I'm not really sure how it would be caused.
To be entirely honest, for myself at least I'll probably need a bit of time to figure out what's going on with dotnet. But maybe Techno or someone else has an idea...
tech note: according to stack overflow its a GC issue, but I feel like that's irrelevant to a -facing fix. I recall that Techno used dotnet45 which pointed at dotnet40 - this seems to have worked looking at your log, but I also slc had issues getting dotnet45 to work (community/forums/posts/6919370). So maybe switch over to dotnet40 (and also gets to ensure one cleans out the failing dependency)?
I also note the following messages that I got while trying to mess about with Winetricks (which resulted in a wineserver crash, yay) - Probably not relevant now, but probably worth keeping in the back of my mind
warning: This package (dotnet40) may not fully work on a 64-bit installation. 32-bit prefixes may work better. ------------------------------------------------------ ------------------------------------------------------ warning: dotnet40 does not yet fully work or install on wine. Caveat emptor.
With respect to the old Wineskin, that is super weird. Could you look through the files in drive_c/osu/Logs and see if you can find anything of interest. In particular network.log, update.log, and if you have one, update_success.log. If you do find anything leave it in a pastie and we can take a look at it for ya. Might be better to reinstall the Wineskin (always the safest option even tho its annoying to move everything over and there's the offchance it doesn't work) but you could give that a shot too in the meantime. I assume osu! just isn't starting now as well.
Sorry I couldn't be of much help, I'll try and think about what could be causing that dotnet issue.
KyzuiKyzui wrote: 5l7011
My osu has been fine opening ever since I ed like 4 months ago but for some reason the "Restart" button won't pop up now when I try to open osu!. There is no way for me to get into the application without this option. Any ideas?
hi and welcome to the osu! forums! Which "Restart" button are you talking about precisely? It would also help if you could generate both a osu!macOS Agent report, as well as a Test Run, using the instructions linked below.
- Agent report: https://osu-mac.readthedocs.io/en/latest/issues/troubleshooting.html#generating-a-report-with-osu-macos-agent
- Test Run: https://osu-mac.readthedocs.io/en/latest/issues/troubleshooting.html#generating-logs-for-wineskin
osu!macOS Agent here: community/forums/topics/1036678
----
Edit: also I thought I was going crazy, but in attempting to experiment with some of the newer Wineskins, I managed to get the Kill Wineskin Processes button to start osu! xD
New Wineskin:
I updated osu! through the Agent. It didn't seem to change anything, so it's probably the compatibility thing you were mentioning.
Update: Didn't think of doing an Agent scan again until now, I don't this error being here when I originally scanned to remove quarantine
ReportVersion 11.1 (Build 20C69)
Engine: WS11WineCX64Bit20.0.0
Wineskin 2.9.0.7-rc4
Release: Stable40
Quarantine attribute is absent (bundle)
Quarantine attribute is absent (wrapper)
Execute flag is present
Detect Direct3D is enabled
Game configuration is absent
System Integrity Protection is enabled
Engine version is ed
Razer Synapse is absent
[Warning] Errors in: update.log
2021-01-25T23:52:57: _pending\osu!.exe => osu!.exe: FAIL
No errors in: runtime.log
Old Wineskin:
I didn't find a network.log, but I did have an update.log and an update_success.log.
Pastebin of the update.log -- https://paste.ubuntu.com/p/RG7xxyxFmq/
(I did notice that I think it said bass.dll, osu!gameplay.dll, and osu!ui.dll failed at the end.)
Pastebin of the update_success.log -- https://paste.ubuntu.com/p/6Ch3VD6bwv/
Not sure if there's anything to note in here, it's short but I still put it in case there is.
I'll try reinstalling the Wineskin (the Wineskin this one uses is in the first Wineskin link in the below post)
(also, just to clarify, is there anything I have to move over to the new Wineskin if I didn't do anything that one time when osu! was working?)
Post 185 - aidswidjajaaidswidjaja wrote: 4a1ul
Sorry for disappearing for a while, let's see how many I can get through lol
pinkfujoshiYou could try updating the osu!.exe manually by ing it from home/ then replacing it in your Wineskin. If that doesn't work let us know and attach the contents of drive_c/osu!/Logs/update.to a pastebin such as paste.ubuntu.comHello again, I did follow your advice, and it started working. But as of right now, I cannot open it again. T~T Here's the report:
lucid126Good to hear you fixed everything, let us know if you encounter any more issues. Also feel free to let us know what you did to fix it.all right, when I opened osu! and tried to a map, a pop up box said that no windows app could run it, so i followed the steps and checked the automatically move ed songs to the songs folder, now there's only 1 song on there and its birdsong. i ran the report and said everything was fine. I'm on mojave. has anyone experienced this? Edit: I got the song to work, but now whenever I try to exit to the main menu it just goes to a black screen. Edit 2: I fixed everyrhing
raiqoUpdating to Big Sur won't really fix your problem unfortunately. If the test run is giving you different results to the actual executable, try repairing the exe through agent again or alternatively running this command:so i launched osu! through the wineskin and it opened, it was working fine and all my maps and skins were there. i then closed it and the thing popped up so i clicked yes and got this: https://paste.ubuntu.com/p/K8XxgNzqc4/
i tried launching osu normally but it still tells me that its damaged. do i just use the wineskin to launch from now on or is there someway to fix the problem? i've also considered updating to Big Sur (i'm currently running Mojave 10.14.6) would that help solve the problem?
edit: just tried launching it again from the test run and it lets me but i cant use any skins and when i try to play maps the game crashes
sudo xattr -rd com.apple.quarantine "~/path/to/my/osu\!.app"
Can you also make sure that your Skins and Songs folders in drive_c/osu! aren't corrupted or anything. It *is* pretty weird how your install is behaving and somewhat corrupted... You're getting a lot of errors, such as these
0098:fixme:path:parse_url failed to parse L"osu!ui" 0098:fixme:path:parse_url failed to parse L"osu!ui.resources"
If you haven't already, I'd try reinstalling just to be sure and to isolate that issue. Also you could try to go to Wineskin.app > Advanced > Tools > and under Wrapper Tools click Refresh Wrapper (do NOT click Rebuild as this will delete everything including your Songs, scores, etc, unless you have them backed up - if they're backed up you could try that as well) - BE CAREFUL ABOUT DOING THIS (I may have done it to myself and now my osu! won't update :/ - maybe make a backup first
Also are the logs the same on your second test run (when the skins don't load, maps crash the game etc) ?
It's some pretty weird stuff, keep us informed and try the stuff above
AmAWolfSorry for not replying,
no, I didn't try but could you give me the Wineskin.app so I can try it?
And could you explain me what I have to do? I'm not that techieWill to Google Drive now, and I'll provide instructions + link by editing this post once its doneSee below, let me know if there are any problems
Also yea, if Agent isn't returning anything weird then there won't be any useful debugging info there for us to find.
PaydruThe report is showing errors with respect to updating the osu! application. Could you try updating from osu!macOS Agent:i havent had any problems with this until now. osu doesnt re-open unless i restart my laptop and whwen i run the troubleshoot, it givess me this
Alternatively the executable binary directly from home/ and replace it within your application
- Open osu!macOS Agent
- Click the Other tab
- Click Update osu!
- osu.exe from osu-ppy-sh.tvgratuite.org/home/.
- Locate where osu!.app (your Wineskin) is installed
- Right click on it and select Show Package Contents
- You should now see three files/folders: Contents, drive_c and Wineskin. Click drive_c.
- From here, click osu!.
- From here, locate osu!.exe and replace this file with the updated version that you just ed. Make sure you keep the filename the same.
Not much happening, just trying to debug different issuesOblivous wrote: 246345
Can someone quote this message and tell me what'd I miss? lmao
Wineskin.app replacement 3i2j1h
If you are experiencing issues with Wineskin.app, you can try ing it separately.
Instructions: https://osu-mac.readthedocs.io/en/latest/issues/wineskin.html#resolution
link: https://minhaskamal.github.io/DownGit/#/home?url=https://github.com/aidswidjaja/osu-mac/tree/main/src/wineskin or https://drive.google.com/drive/folders/1Gz5Y0M4WoMxTTwb5aHUccebO5AlVm3SN?usp=sharing
Please be advised if that this hasn't been tested and that distributing the Wineskin.app file on its own is completely experimental so it might not fix your issues. But definitely let me know if there are any problems with it
- Click the Link above
- If using Google Drive, click ALL in the top-right corner of the screen
- It will this as a zip file. Extract the zip file until you just have the Wineskin.app file
- Inside osu!.app (Right click > Show Package Contents) locate Wineskin.app - make a backup of it (you can just rename it to say something like Wineskin.app.backup if you want)
- Move the new version of Wineskin.app from Google Drive into osu!.app
- Try and open it and see if everything works out.
![]()
sorry for the delay on this.aidswidjaja wrote: 4a1ul
gravitybalmaingravitybalmain wrote: 6n68h
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
ReportVersion 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 configuration is absent
System Integrity Protection is enabled
Engine version is ed
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).
Thanks, that's weird...
I note your previous logs and it seems to be experiencing the same issue. A crashed thread => exception: EXC_BAD_INSTRUCTION <=> same processes running in the thread that crashes. There is a difference - the older Wineskin considered the Terminal (zsh) its parent process while the newer one runs directly under Wineskin.app tho I'd doubt that would change much
Exception Type: EXC_BAD_INSTRUCTION (SIGILL) Exception Codes: 0x0000000000000001, 0x0000000000000000 Exception Note: EXC_CORPSE_NOTIFY
Jan 3: https://paste.ubuntu.com/p/pfvsJr9xYQ/
Jan 24: https://paste.ubuntu.com/p/yh5Kf8qd52/
This problem isn't linked directly to the exec(number).bat problem then. That arised out of the wrapper not being quarantined in osu!macOS Agent which would explain why my experimental drop-in fix is exhibiting similar behaviour. That means this is a problem linked to the wrapper/bundle/Wine somehow - or less likely an upstream bug in unofficial Wineskin (though I doubt this is the case).
Your bundle is opening the terminal tho which I suppose is good news. I might ask if its ok if you do some testing for me thenthough Techno or someone else might have other ideas as well
Troubleshooting stepsI'll ask you to run the osu! executable through the Windows command line instead of the wrapper.
1. Right click on osu!.app
2. Open Wineskin.app (which you reported works)
3. Click Advanced
4. Click the Tools tab
5. Click Command Line (cmd) under the Wine Tools header
6. A terminal-like window should appear though it does take a bit of time to load
7. Type the following commands in order (excluding comments with are indicated with #s)
cd ../../osu! echo %CD% # this command should print C:\ osu!.exe
In a properly working Wineskin this will start osu! (albeit with heavy performance issues) - when you do this what happens?
Also, if you're feeling up to it, you could also try making your own wrapper from scratch: community/forums/posts/7879865, but dw about it if you can't. If you choose to, you can grab Gcenx's Unofficial Wineskin Winery form https://github.com/Gcenx/WineskinServer/issues/26
Technocoder mentioned that the illegal instruction issue could have been a compatibility error between 32-bit and 64-bit? However I would have expected that to catch earlier and be more obvious too with a bad U statement or something similar in the test logs - which coincidentally (or maybe not?) crash the program. WineCX20 is a 32-bit arch though, so maybe the wine32on64 process isn't working for you? I have a feeling though this illegal instruction is linked directly to something acting up within Wineskin.app as other people have reported different issues on Wine but experiencing the same crashes on Wineskin.app (https://www.reddit.com/r/wine_gaming/comments/kxur3i/problems_with_most_visual_novels_videos_wont_play/) Could also be an issue with dependencies (winetricks) and/or wineprefix but at this stage I'm finding it pretty difficult to isolate the issue down to any single possible cause...
Feel free to let me know what happens with the troubleshooting steps above, and if anyone else has any idea of what's going on do let us know!
Jyxle wrote: 66a5n
Hi, I've run into an error. After installing osu with these steps on Catalina 10.15.7, I am able to run it perfectly. However, after I close it after playing for ONE session, when I try to open it up it does not open. 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. I have tried using the Osu mac agent to repair but it does not seem to fix it.
The only way to fix this so far for me is to completely re osu! everytime I want to play it, which is a huge pain. Is there a way to fix this?
Thanks!
Sorry yeah, it looks like Big Sur is a little bit hit or miss at the moment. Can you elaborate on what's not working? Are you able to open it and/or do you get any crash reports?TheNamesTen wrote: 6k2e3k
Not quite sure what to do from here. Followed everything to the t. Any help would be great!
aidswidjaja wrote: 4a1ul
AnimatedThinksAnimatedThinks wrote: 685o4u
aidswidjajaaidswidjaja wrote: 4a1ul
TechnocoderTechnocoder wrote: 365p3v
Strangely enough, I get the same crash report when using the WineCX20 engine but not with the WineCX64Bit20 engine... and I'm running macOS Catalina, not Big Sur or M1.
Please try using this Wineskin which uses WineCX20 instead: https://mega.nz/file/ZxlQ1AiS#A-2sPJI5zg_7Dn___VXmO5EEY4qRyJm6uAu7TpiLA9U
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.
Hmm... So far I haven't been able to replicate the crash report on any Wineskin.
WS11WineCX64Bit19.0.1-1 :: Works fine normally, Test Run opens osu! as expected
WS11WineCX64Bit20.0.0 :: Works fine normally, Test Run opens osu! as expected
WS11WineCX6420.0.0 :: wine: '/s/Adrian/Desktop/WS11CX20.0.0.app/Contents/Resources' is a 64-bit installation, it cannot be used with a 32-bit wineserver. (expected error)
This is on my 2016 MBP wo/ touch bar - Intel x86 i5. 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. Maybe I'll try again and see what happens there.
How did you get WineCX20 to run (on Catalina)? As expected I'm getting 64-bit compatibility issues on 32-bit wineserver (hence why wine32on64 is used)
AnimatedThinksAnimatedThinks wrote: 685o4u
I tried out the new Wineskin just now (I also ed the new mac!OS Agent, I realized the old one wouldn't detect the new Wineskin.)
When opening it (either through Test Run or by normal double-clicking), it shows the osu! popup, but never actually opens.
Here's the Test Run that popped up when I tried opening osu! that way:
Test Run000b:fixme:thread:create__shared_data_thread Creating shared data update thread.
000d:fixme:thread:create__shared_data_thread Creating shared data update thread.
0010:fixme:thread:create__shared_data_thread Creating shared data update thread.
0018:fixme:thread:create__shared_data_thread Creating shared data update thread.
001d:fixme:thread:create__shared_data_thread Creating shared data update thread.
0009:fixme:thread:create__shared_data_thread Creating shared data update thread.
0009:fixme:exec:SHELL_execute flags ignored: 0x00000100
0009:fixme:ntdll:FILE_GetNtStatus Converting errno 8 to STATUS_UNSUCCESSFUL
0026:fixme:thread:create__shared_data_thread Creating shared data update thread.
0028:fixme:thread:create__shared_data_thread Creating shared data update thread.
002a:fixme:thread:create__shared_data_thread Creating shared data update thread.
0031:fixme:thread:create__shared_data_thread Creating shared data update thread.
0036:fixme:ntdll:NtQuerySystemInformation info_class SYSTEM_PERFORMANCE_INFORMATION
0036:fixme:heap:GetNumaHighestNodeNumber semi-stub: 0031FAC8
0038:err:ole:CoGetContextToken apartment not initialised
0036:fixme:time:QueryThreadCycleTime (0xfffffffe,0x5d52560): stub!
0036:fixme:path:parse_url failed to parse L"System.Windows.Forms"
0036:fixme:path:parse_url failed to parse L"System.Drawing"
0036:fixme:path:parse_url failed to parse L"System"
0036:fixme:path:parse_url failed to parse L"System.Configuration"
0036:fixme:path:parse_url failed to parse L"System.Xml"
0036:fixme:path:parse_url failed to parse L"Accessibility"
0036:fixme:path:parse_url failed to parse L"System.Security"
0036:fixme:path:parse_url failed to parse L"System.Runtime.Serialization.Formatters.Soap"
0036:fixme:path:parse_url failed to parse L"System.Deployment"
0036:fixme:path:parse_url failed to parse L"System.Core"
0036:fixme:path:parse_url failed to parse L"System.Drawing"
0036:fixme:path:parse_url failed to parse L"System"
0036:fixme:path:parse_url failed to parse L"System.Core"
0036:fixme:path:parse_url failed to parse L"System.Numerics"
0036:fixme:nls:get_dummy_preferred_ui_language (0x8 0x31daf4 0x0 0x31daf0) returning a dummy value (current locale)
0036:fixme:nls:get_dummy_preferred_ui_language (0x8 0x31daf4 0x3aa40d0 0x31daf0) returning a dummy value (current locale)
0036:fixme:process:SetProcessPriorityBoost (00000268,0): stub
0042:fixme:path:parse_url failed to parse L"System.Web"
0036:fixme:path:parse_url failed to parse L"OpenTK"
0042:fixme:path:parse_url failed to parse L"Microsoft.Build.Framework"
0042:fixme:path:parse_url failed to parse L"Microsoft.Build.Utilities.v4.0"
0042:fixme:path:parse_url failed to parse L"System.ComponentModel.DataAnnotations"
0042:fixme:path:parse_url failed to parse L"System.Runtime.Caching"
0042:fixme:path:parse_url failed to parse L"System.Data"
0042:fixme:path:parse_url failed to parse L"System.Web.ApplicationServices"
0042:fixme:path:parse_url failed to parse L"System.DirectoryServices.Protocols"
0042:fixme:path:parse_url failed to parse L"System.DirectoryServices"
0042:fixme:path:parse_url failed to parse L"System.EnterpriseServices"
0042:fixme:path:parse_url failed to parse L"System.ServiceProcess"
0042:fixme:path:parse_url failed to parse L"System.Web.Services"
0042:fixme:path:parse_url failed to parse L"System.Design"
0042:fixme:path:parse_url failed to parse L"Microsoft.Build.Tasks.v4.0"
0042:fixme:path:parse_url failed to parse L"System.Web.RegularExpressions"
0042:fixme:path:parse_url failed to parse L"System.Transactions"
0042:fixme:combase:RoGetParameterizedTypeInstanceIID stub: 4 03B35268 0831B62C 0831BC90 00000000
0042:fixme:combase:RoGetParameterizedTypeInstanceIID stub: 3 03B285A4 0831B81C 0831BE80 00000000
0042:fixme:combase:RoGetParameterizedTypeInstanceIID stub: 3 03B285A4 0831B81C 0831BE80 00000000
0036:err:winediag:wined3d_dll_init Setting multithreaded command stream to 0x1.
0043:fixme:path:parse_url failed to parse L"System.Configuration"
0043:fixme:path:parse_url failed to parse L"System.Xml"
0043:fixme:path:parse_url failed to parse L"System.Data.SqlXml"
0043:fixme:ras:RasEnumConnectionsW (03B65D40,084BEE80,084BEE84),stub!
0043:fixme:ras:RasEnumConnectionsW RAS is not implemented! Configure program to use LAN connection/winsock instead!
0043:fixme:winsock:set_dont_fragment IP_DONTFRAGMENT for IPv4 not ed in this platform
0043:fixme:winsock:set_dont_fragment IP_DONTFRAGMENT for IPv6 not ed in this platform
0043:err:winsock:WSAIoctl -> SIO_ADDRESS_LIST_CHANGE request failed with status 0x2733
0043:err:winsock:WSAIoctl -> SIO_ADDRESS_LIST_CHANGE request failed with status 0x2733
0043:fixme:ras:RasConnectionNotificationW (FFFFFFFF,00000328,0x00000003),stub!
0036:fixme:combase:RoGetParameterizedTypeInstanceIID stub: 4 03B5DD78 0031D24C 0031D8B0 00000000
0036:fixme:combase:RoGetParameterizedTypeInstanceIID stub: 3 03B5DC54 0031D43C 0031DAA0 00000000
0036:fixme:combase:RoGetParameterizedTypeInstanceIID stub: 3 03B5DC54 0031D43C 0031DAA0 00000000
0036:fixme:ntdll:EtwEvent ({8e9f5090-2d75-4d03-8a81-e5afbf85daf1}, 0xa60732, 0x0, 0x194cb44) stub.
0036:fixme:path:parse_url failed to parse L"osu!.resources"
0036:fixme:nls:LCMapStringEx uned lparam 3ac0d80
0036:fixme:path:parse_url failed to parse L"osu!.resources"
0036:fixme:coreaudio:ca_channel_layout_to_channel_mask Unhandled channel 0xffffffff
0036:fixme:coreaudio:ca_channel_layout_to_channel_mask Unhandled channel 0xffffffff
0036:fixme:coreaudio:ca_channel_layout_to_channel_mask Unhandled channel 0xffffffff
0036:fixme:coreaudio:ca_channel_layout_to_channel_mask Unhandled channel 0xffffffff
0036:fixme:coreaudio:ca_channel_layout_to_channel_mask Unhandled channel 0xffffffff
0048:fixme:avrt:AvSetMmThreadCharacteristicsW (L"Audio",0B4CFDF8): stub
0036:fixme:process:FlushProcessWriteBuffers : stub
004c:fixme:thread:NtGetCurrentProcessorNumber need multicore (8 processors)
004c:fixme:path:parse_url failed to parse L"System.Runtime.Serialization"
004c:fixme:path:parse_url failed to parse L"SMDiagnostics"
004c:fixme:path:parse_url failed to parse L"System.ServiceModel.Internals"
004c:fixme:path:parse_url failed to parse L"System.Numerics"
0036:fixme:path:parse_url failed to parse L"osu!ui"
0036:fixme:path:parse_url failed to parse L"osu!ui.resources"
004c:fixme:path:parse_url failed to parse L"System.Data"
0042:fixme:path:parse_url failed to parse L"System.Runtime.Remoting"
004c:fixme:advapi:EventSourceW ((null),L".NET Runtime"): stub
004c:fixme:advapi:ReportEventW (0xcafe4242,0x0001,0x0000,0x000003ff,0x0,0x0001,0x00000000,0xb90d5bc,0x0): stub
004c:err:eventlog:ReportEventW L"Application: osu!.exe\nFramework Version: v4.0.30319\nDescription: The process was terminated due to an internal error in the .NET Runtime at IP 00E03BED (00D90000) with exit code 80131506.\n"
004c:fixme:advapi:DeEventSource (0xcafe4242) stub
I'll see if deleting and replacing the files on the old Wineskin works
Thanks to everyone for helping fix these issues
Update - For the old Wineskin: I deleted all the files mentioned, ed the osu! exe for Windows, and dragged it into the drive_c/osu! folder.
There were a few files I didn't see mentioned (namely d3dx9_31.dll, Microsoft.Xna.Framework.dll, osu!seasonal.dll, osu!dll, and x3daudio1_1.dll.) I left them alone for now.
When I did the Agent again, it didn't seem to help. I might have done something wrong, though.
ReportVersion 10.16 (Build 20C69)
Engine: WS11WineCX64Bit19.0.1-1
Wineskin 2.9.0.6 1
Game configuration is absent
Quarantine attribute is absent
Execute flag is present
Detect Direct3D is enabled
Compatibility mode is disabled
System Integrity Protection is enabled
Engine version is ed
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
I think there are two possibilities to this...
- somehow its a problem with osu. I doubt this is the issue but just to make sure maybe update it through Agent again.
- .NET (aka dotnet) isn't working properly (see tech note below) - e.g compatibility problem. This one is probably more likely though I'm not really sure how it would be caused.
To be entirely honest, for myself at least I'll probably need a bit of time to figure out what's going on with dotnet. But maybe Techno or someone else has an idea...
tech note: according to stack overflow its a GC issue, but I feel like that's irrelevant to a -facing fix. I recall that Techno used dotnet45 which pointed at dotnet40 - this seems to have worked looking at your log, but I also slc had issues getting dotnet45 to work (community/forums/posts/6919370). So maybe switch over to dotnet40 (and also gets to ensure one cleans out the failing dependency)?
I also note the following messages that I got while trying to mess about with Winetricks (which resulted in a wineserver crash, yay) - Probably not relevant now, but probably worth keeping in the back of my mind
warning: This package (dotnet40) may not fully work on a 64-bit installation. 32-bit prefixes may work better. ------------------------------------------------------ ------------------------------------------------------ warning: dotnet40 does not yet fully work or install on wine. Caveat emptor.
With respect to the old Wineskin, that is super weird. Could you look through the files in drive_c/osu/Logs and see if you can find anything of interest. In particular network.log, update.log, and if you have one, update_success.log. If you do find anything leave it in a pastie and we can take a look at it for ya. Might be better to reinstall the Wineskin (always the safest option even tho its annoying to move everything over and there's the offchance it doesn't work) but you could give that a shot too in the meantime. I assume osu! just isn't starting now as well.
Sorry I couldn't be of much help, I'll try and think about what could be causing that dotnet issue.
KyzuiKyzui wrote: 5l7011
My osu has been fine opening ever since I ed like 4 months ago but for some reason the "Restart" button won't pop up now when I try to open osu!. There is no way for me to get into the application without this option. Any ideas?
hi and welcome to the osu! forums! Which "Restart" button are you talking about precisely? It would also help if you could generate both a osu!macOS Agent report, as well as a Test Run, using the instructions linked below.
- Agent report: https://osu-mac.readthedocs.io/en/latest/issues/troubleshooting.html#generating-a-report-with-osu-macos-agent
- Test Run: https://osu-mac.readthedocs.io/en/latest/issues/troubleshooting.html#generating-logs-for-wineskin
osu!macOS Agent here: community/forums/topics/1036678
----
Edit: also I thought I was going crazy, but in attempting to experiment with some of the newer Wineskins, I managed to get the Kill Wineskin Processes button to start osu! xD
New Wineskin:
I updated osu! through the Agent. It didn't seem to change anything, so it's probably the compatibility thing you were mentioning.
Update: Didn't think of doing an Agent scan again until now, I don't this error being here when I originally scanned to remove quarantine
ReportVersion 11.1 (Build 20C69)
Engine: WS11WineCX64Bit20.0.0
Wineskin 2.9.0.7-rc4
Release: Stable40
Quarantine attribute is absent (bundle)
Quarantine attribute is absent (wrapper)
Execute flag is present
Detect Direct3D is enabled
Game configuration is absent
System Integrity Protection is enabled
Engine version is ed
Razer Synapse is absent
[Warning] Errors in: update.log
2021-01-25T23:52:57: _pending\osu!.exe => osu!.exe: FAIL
No errors in: runtime.log
Old Wineskin:
I didn't find a network.log, but I did have an update.log and an update_success.log.
Pastebin of the update.log -- https://paste.ubuntu.com/p/RG7xxyxFmq/
(I did notice that I think it said bass.dll, osu!gameplay.dll, and osu!ui.dll failed at the end.)
Pastebin of the update_success.log -- https://paste.ubuntu.com/p/6Ch3VD6bwv/
Not sure if there's anything to note in here, it's short but I still put it in case there is.
I'll try reinstalling the Wineskin (the Wineskin this one uses is in the first Wineskin link in the below post)
(also, just to clarify, is there anything I have to move over to the new Wineskin if I didn't do anything that one time when osu! was working?)
Post 185 - aidswidjajaaidswidjaja wrote: 4a1ul
Sorry for disappearing for a while, let's see how many I can get through lol
pinkfujoshiYou could try updating the osu!.exe manually by ing it from home/ then replacing it in your Wineskin. If that doesn't work let us know and attach the contents of drive_c/osu!/Logs/update.to a pastebin such as paste.ubuntu.comHello again, I did follow your advice, and it started working. But as of right now, I cannot open it again. T~T Here's the report:
lucid126Good to hear you fixed everything, let us know if you encounter any more issues. Also feel free to let us know what you did to fix it.all right, when I opened osu! and tried to a map, a pop up box said that no windows app could run it, so i followed the steps and checked the automatically move ed songs to the songs folder, now there's only 1 song on there and its birdsong. i ran the report and said everything was fine. I'm on mojave. has anyone experienced this? Edit: I got the song to work, but now whenever I try to exit to the main menu it just goes to a black screen. Edit 2: I fixed everyrhing
raiqoUpdating to Big Sur won't really fix your problem unfortunately. If the test run is giving you different results to the actual executable, try repairing the exe through agent again or alternatively running this command:so i launched osu! through the wineskin and it opened, it was working fine and all my maps and skins were there. i then closed it and the thing popped up so i clicked yes and got this: https://paste.ubuntu.com/p/K8XxgNzqc4/
i tried launching osu normally but it still tells me that its damaged. do i just use the wineskin to launch from now on or is there someway to fix the problem? i've also considered updating to Big Sur (i'm currently running Mojave 10.14.6) would that help solve the problem?
edit: just tried launching it again from the test run and it lets me but i cant use any skins and when i try to play maps the game crashes
sudo xattr -rd com.apple.quarantine "~/path/to/my/osu\!.app"
Can you also make sure that your Skins and Songs folders in drive_c/osu! aren't corrupted or anything. It *is* pretty weird how your install is behaving and somewhat corrupted... You're getting a lot of errors, such as these
0098:fixme:path:parse_url failed to parse L"osu!ui" 0098:fixme:path:parse_url failed to parse L"osu!ui.resources"
If you haven't already, I'd try reinstalling just to be sure and to isolate that issue. Also you could try to go to Wineskin.app > Advanced > Tools > and under Wrapper Tools click Refresh Wrapper (do NOT click Rebuild as this will delete everything including your Songs, scores, etc, unless you have them backed up - if they're backed up you could try that as well) - BE CAREFUL ABOUT DOING THIS (I may have done it to myself and now my osu! won't update :/ - maybe make a backup first
Also are the logs the same on your second test run (when the skins don't load, maps crash the game etc) ?
It's some pretty weird stuff, keep us informed and try the stuff above
AmAWolfSorry for not replying,
no, I didn't try but could you give me the Wineskin.app so I can try it?
And could you explain me what I have to do? I'm not that techieWill to Google Drive now, and I'll provide instructions + link by editing this post once its doneSee below, let me know if there are any problems
Also yea, if Agent isn't returning anything weird then there won't be any useful debugging info there for us to find.
PaydruThe report is showing errors with respect to updating the osu! application. Could you try updating from osu!macOS Agent:i havent had any problems with this until now. osu doesnt re-open unless i restart my laptop and whwen i run the troubleshoot, it givess me this
Alternatively the executable binary directly from home/ and replace it within your application
- Open osu!macOS Agent
- Click the Other tab
- Click Update osu!
- osu.exe from osu-ppy-sh.tvgratuite.org/home/.
- Locate where osu!.app (your Wineskin) is installed
- Right click on it and select Show Package Contents
- You should now see three files/folders: Contents, drive_c and Wineskin. Click drive_c.
- From here, click osu!.
- From here, locate osu!.exe and replace this file with the updated version that you just ed. Make sure you keep the filename the same.
Not much happening, just trying to debug different issuesOblivous wrote: 246345
Can someone quote this message and tell me what'd I miss? lmao
Wineskin.app replacement 3i2j1h
If you are experiencing issues with Wineskin.app, you can try ing it separately.
Instructions: https://osu-mac.readthedocs.io/en/latest/issues/wineskin.html#resolution
link: https://minhaskamal.github.io/DownGit/#/home?url=https://github.com/aidswidjaja/osu-mac/tree/main/src/wineskin or https://drive.google.com/drive/folders/1Gz5Y0M4WoMxTTwb5aHUccebO5AlVm3SN?usp=sharing
Please be advised if that this hasn't been tested and that distributing the Wineskin.app file on its own is completely experimental so it might not fix your issues. But definitely let me know if there are any problems with it
- Click the Link above
- If using Google Drive, click ALL in the top-right corner of the screen
- It will this as a zip file. Extract the zip file until you just have the Wineskin.app file
- Inside osu!.app (Right click > Show Package Contents) locate Wineskin.app - make a backup of it (you can just rename it to say something like Wineskin.app.backup if you want)
- Move the new version of Wineskin.app from Google Drive into osu!.app
- Try and open it and see if everything works out.
![]()
Thanks for your comprehensive reply!
New Wineskin
That error will definitely have something to do with osu! failing. Are you sure that osu! and mirror sites aren't blocked or anything on your internet? Going to https://m1.ppy.sh/ should return "osu! update mirror"
Old Wineskin
Yea, you're experiencing a similar error with osu! having trouble updating for some reason. In both Wineskins osu! is returning update errors
But with your new Wineskin, you're only experiencing one error which is the osu! executable not ing. Perhaps you could try ing that from the website, and manually replacing it. Then, when opening osu!, press the close icon within the updater (to by updates) and launch the game from there.
gcenx wrote: 2w6139
@Technocoder I see that the provided wrapper is using WS11WineCX20.0.0/WS11WineCX64Bit20.0.0 those builds were not optimized for running under Rosetta2 me directly for optimized Engine(s).
Also see your providing an app that's setting some options externally, one thing to keep disabled is the GPU Detection as it has issues with Apple Silicon devices possibly also T1/T2 systems.
Seeing that some s are not able to launch consistently, I noticed the issue with a wrapper I quickly thrown together this only seems to happen when having multiple native overrides set as all that's required is mscoree for .Net. With only that set to native osu! now launched constantly on my M1 Mac Mini.
Technocoder wrote: 365p3v
"Jyxle"Jyxle wrote: 66a5n
Hi, I've run into an error. After installing osu with these steps on Catalina 10.15.7, I am able to run it perfectly. However, after I close it after playing for ONE session, when I try to open it up it does not open. 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. I have tried using the Osu mac agent to repair but it does not seem to fix it.
The only way to fix this so far for me is to completely re osu! everytime I want to play it, which is a huge pain. Is there a way to fix this?
Thanks!
Can 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: https://paste.ubuntu.com) when it crashes?
Sorry yeah, it looks like Big Sur is a little bit hit or miss at the moment. Can you elaborate on what's not working? Are you able to open it and/or do you get any crash reports?TheNamesTen wrote: 6k2e3k
Not quite sure what to do from here. Followed everything to the t. Any help would be great!
Technocoder wrote: 365p3v
"gcenx"gcenx wrote: 2w6139
@Technocoder I see that the provided wrapper is using WS11WineCX20.0.0/WS11WineCX64Bit20.0.0 those builds were not optimized for running under Rosetta2 me directly for optimized Engine(s).
Also see your providing an app that's setting some options externally, one thing to keep disabled is the GPU Detection as it has issues with Apple Silicon devices possibly also T1/T2 systems.
Seeing that some s are not able to launch consistently, I noticed the issue with a wrapper I quickly thrown together this only seems to happen when having multiple native overrides set as all that's required is mscoree for .Net. With only that set to native osu! now launched constantly on my M1 Mac Mini.
Hi there! Much appreciated for maintaining the Wineskin project and many thanks for reaching out! I'm sure that thousands of hours of playtime have only been possible due to your efforts.
I will you through osu!'s web chat. Otherwise if you'd prefer, I can open an issue on your WineskinServer repository or you can find me in the unofficial osu! Discord (invite link: https://discord.gg/0Vxo9AsejDkGlk3H) as @Technocoder (or some other method if these are unsuitable).
Thanks for the heads up regarding GPU detection. I'll add a configuration check in osu!macOS Agent for that and keep it disabled in the subsequent Wineskin release. Regarding mscoree, it looks like that's the only native override I have in the latest Wineskin so I think that's fine here.
Edit: The engine has now been updated to 20.0.2. @gravitybalmain, @AnimatedThinks, please try ing the latest Wineskin again and hopefully it should work. You may also need to re osu!macOS Agent (although this shouldn't be necessary but just in case).
Echoing similar issues as AnimatedThinks. ed the new wineskin and macOS fresh after deleting all old files.Technocoder wrote: 365p3v
"gcenx"gcenx wrote: 2w6139
@Technocoder I see that the provided wrapper is using WS11WineCX20.0.0/WS11WineCX64Bit20.0.0 those builds were not optimized for running under Rosetta2 me directly for optimized Engine(s).
Also see your providing an app that's setting some options externally, one thing to keep disabled is the GPU Detection as it has issues with Apple Silicon devices possibly also T1/T2 systems.
Seeing that some s are not able to launch consistently, I noticed the issue with a wrapper I quickly thrown together this only seems to happen when having multiple native overrides set as all that's required is mscoree for .Net. With only that set to native osu! now launched constantly on my M1 Mac Mini.
Hi there! Much appreciated for maintaining the Wineskin project and many thanks for reaching out! I'm sure that thousands of hours of playtime have only been possible due to your efforts.
I will you through osu!'s web chat. Otherwise if you'd prefer, I can open an issue on your WineskinServer repository or you can find me in the unofficial osu! Discord (invite link: https://discord.gg/0Vxo9AsejDkGlk3H) as @Technocoder (or some other method if these are unsuitable).
Thanks for the heads up regarding GPU detection. I'll add a configuration check in osu!macOS Agent for that and keep it disabled in the subsequent Wineskin release. Regarding mscoree, it looks like that's the only native override I have in the latest Wineskin so I think that's fine here.
Edit: The engine has now been updated to 20.0.2. @gravitybalmain, @AnimatedThinks, please try ing the latest Wineskin again and hopefully it should work. You may also need to re osu!macOS Agent (although this shouldn't be necessary but just in case).
Jyxle wrote: 66a5n
Technocoder wrote: 365p3v
"Jyxle"Jyxle wrote: 66a5n
Hi, I've run into an error. After installing osu with these steps on Catalina 10.15.7, I am able to run it perfectly. However, after I close it after playing for ONE session, when I try to open it up it does not open. 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. I have tried using the Osu mac agent to repair but it does not seem to fix it.
The only way to fix this so far for me is to completely re osu! everytime I want to play it, which is a huge pain. Is there a way to fix this?
Thanks!
Can 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: https://paste.ubuntu.com) when it crashes?
Sorry yeah, it looks like Big Sur is a little bit hit or miss at the moment. Can you elaborate on what's not working? Are you able to open it and/or do you get any crash reports?TheNamesTen wrote: 6k2e3k
Not quite sure what to do from here. Followed everything to the t. Any help would be great!
Hi TechnoCoder, here are the logs from the Test Run
https://paste.ubuntu.com/p/YJQvcb2bf6/
Thanks!
_sassy_girl_ wrote: 1e5h1s
Hi! I have minor issues with displaying icons in osu!(Wineskin with Rosetta ).
Here's a screenshot that describing an issue:
This issue is not present in Catalina version:
Report if needed:
ReportVersion 11.2 (Build 20D64)
Engine: WS11WineCX64Bit20.0.2
Wineskin 2.9.0.7-rc4
Release: Stable40
Quarantine attribute is absent (bundle)
Quarantine attribute is absent (wrapper)
Execute flag is present
Detect Direct3D is disabled
Compatibility mode is disabled
System Integrity Protection is enabled
Engine version is ed
Razer Synapse is absent
Log file: update.log is absent
No errors in: runtime.log
Oh, unfortunately, it didn't help meaidswidjaja wrote: 4a1ul
Hi! Sorry to hear you're having issues. osu! tends to be a bit fiddly with graphics on Wine but usually it isn't too hard to fix. You may need to fiddle around with the in-game settings (e.g resolution) to see if that gets the graphics to work. don't turn on compatibility mode! <-- that will break your wrapper- I also tend to stay away from enabling full screen mode since that makes graphical glitches for me (tho it may work for you).
Failing the above, please try and make a Test Run using the instructions available at https://osu-mac.readthedocs.io/en/latest/issues/troubleshooting.html#generating-logs-for-wineskin - thanks!