forum

Solution: Running osu! In Ubuntu or Xubuntu

posted
Total Posts
943
show more
Espionage724

Kurokami wrote:

I downloaded ubuntu 10.04 lts and I don't really want to update it. I able to update it through updater but... I only have 6GB space. Wine is 1.2.2 if I remember right so I don't think its old. osume.exe is working but osu! couldn't start. There is really no other way except update?

m42a wrote:

Please post the entire output of osu! when you try to run it.
How?
The latest version of Wine currently is 1.6 (stable) and 1.7 (development). Prior to that, Wine 1.4 was the stable version for I believe two years. Wine 1.2.2 seems "really" old in-comparison.

If osume runs, then dotnet20 seems to be ok, but I'm thinking it's graphics driver-related. What graphics hardware do you have, and are you using FOSS drivers or proprietary?

I would of course also recommend updating the OS itself to at least LTS 12.04.2 (there's non LTS 13.04 and also 13.10 daily images too); almost certain 10.04 isn't supported at all anymore for the most part.

Edit: As for how to get the output; open a Terminal window, type "wine " and drag osu!'s exe to the window. Everything that occurs should be outputted to that window. From there, just select all that text, and put it here.
bahamete
Hello all,

I just saw this thread and I can't help much but osu! runs perfect for me on Arch Linux (I know this is an Ubuntu thread but I can't find somewhere else this would fit) without any lag or crashing or anything - using wine-1.7.0 on kernel 3.10.3-1-ARCH. If you build the latest wine from source (or the release candidate) for Ubuntu it might just work, who knows.

My graphics card is some ancient thing.

bahamete@arch ~> lspci | grep VGA
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] R580 [Radeon X1900 XT]

If I can assist in some way (winecfg or something else) please PM me though I don't know what makes my build able to work.
I know that many in this thread have said they have gotten it working for them but with issues, yet for me it runs the same as on Windows. Hmm. I hope an official port to Linux will occur at some point.
Kurokami
Then I guess there is no other way just an update. q.q
Anyways here is what terminal says:
SPOILER
kurokami@kurokami-laptop:~$ wine
Usage: wine PROGRAM [ARGUMENTS...] Run the specified program
wine --help Display this help and exit
wine --version Output version information and exit
kurokami@kurokami-laptop:~$ '/media/Stuffs/osu!/osu!.exe'
fixme:actctx:parse_manifest_buffer root element is L"asmv1:assembly", not <assembly>
fixme:advapi:RegisterTraceGuidsW (0x79fd471e, 0x125500, {e13c0d23-ccbc-4e12-931b-d9cc2eee27e4}, 9, 0x7a390368, (null), (null), 0x7a38d250,)
fixme:sync:CreateMemoryResourceNotification (0) stub
fixme:service:QueryServiceConfig2W Level 6 not implemented
fixme:service:QueryServiceConfig2W Level 6 not implemented
fixme:shell:URL_ParseUrl failed to parse L"Microsoft.Xna.Framework"
fixme:shell:URL_ParseUrl failed to parse L"System.Drawing"
fixme:shell:URL_ParseUrl failed to parse L"System"
fixme:shell:URL_ParseUrl failed to parse L"msvcm80"
fixme:shell:URL_ParseUrl failed to parse L"System.Windows.Forms"
fixme:process:SetProcessPriorityBoost (0x1b8,0): stub
fixme:shell:URL_ParseUrl failed to parse L"osu"
err:ntdll:RtlpWaitForCriticalSection section 0x7bca5e20 "virtual.c: csVirtual" wait timed out in thread 0023, blocked by 0009, retrying (60 sec)
fixme:shell:URL_ParseUrl failed to parse L"System.Configuration"
fixme:shell:URL_ParseUrl failed to parse L"System.Xml"
fixme:shell:URL_ParseUrl failed to parse L"System.Drawing.resources"
fixme:shell:URL_ParseUrl failed to parse L"System.Drawing.resources"
fixme:shell:URL_ParseUrl failed to parse L"osu!framework"
fixme:shell:URL_ParseUrl failed to parse L"osu!.resources"
fixme:shell:URL_ParseUrl failed to parse L"osu!.resources"
fixme:shell:URL_ParseUrl failed to parse L"{91ca184b-6868-4d57-a19a-79a3c2217c13}"
fixme:shell:URL_ParseUrl failed to parse L"System.resources"
fixme:shell:URL_ParseUrl failed to parse L"System.resources"
fixme:dsalsa:IDsDriverBufferImpl_SetVolumePan (0x1fc278,0x2069d0): stub
bt_audio_service_open: connect() failed: Connection refused (111)
bt_audio_service_open: connect() failed: Connection refused (111)
bt_audio_service_open: connect() failed: Connection refused (111)
bt_audio_service_open: connect() failed: Connection refused (111)
bt_audio_service_open: connect() failed: Connection refused (111)
bt_audio_service_open: connect() failed: Connection refused (111)
bt_audio_service_open: connect() failed: Connection refused (111)
bt_audio_service_open: connect() failed: Connection refused (111)
Segmentation fault
kurokami@kurokami-laptop:~$

After I updated only my wine into 1.4 which was hard to find osu! crashed with this error:
SPOILER
System.NullReferenceException: Object reference not set to an instance of an object.
at #Aj.#dm.#F8(String )
at #Aj.#dm.#G8(String )
at #Qj.#Qo.#bqb(String , Boolean )
at #Qj.#Qo.#bqb(String )
at #Ai.#Go.#6ob(Boolean )
at #Ai.#Go.#Br()
at #Yc.#4c.#Br()
at #Wo.#Xo.#Br()
at #Yc.#4c.#It()
at #Wo.#Vo.#0qb(String , Boolean )
Samidare
I'm on a i5 with Intel graphics running Ubuntu 13.04. Osu works pretty well using the Bloodcat package. But I've had one very specific, consistent problem, and I'm curious if other people were experiencing it.

If I select a Taiko map, then attempt to return to the menu by hitting Escape, Osu invariably hangs (I was only able to terminate it with a SIGKILL). However, if I select a regular map and then do the same thing (hit Escape, select Return to Menu) then nothing bad happens. I haven't tested playing through a Taiko map and seeing if the score menu still works.

Kind of a shame, since everything else works super smoothly. Are other people getting this problem too?
ErunamoJAZZ
The Bloodcat deb package no works for me. u.u
nightbane112

ErunamoJAZZ wrote:

The Bloodcat deb package no works for me. u.u
Ever since I upgraded Wine from 1.6 to 1.7, Bloodcat packages stop working. Previously, on 1.6, it worked smoothly :(
Espionage724
Just a quick status report: osu! seems to run nicely in Wine 1.7.1 (CSMT-patched) with fglrx (13.8b2) on Xubuntu 13.10 (saucy daily). No FPS drops, and the graphic glitches I reported before are gone. This is in DirectX mode. OpenGL mode still appears unselectable currently (via in-game or .cfg modifying).
Espionage724
Newer guide: p/3822351

(last updated September 7th, 2014)

Imgur album breifly describing my process: http://imgur.com/a/7JEig (do not rely on this alone as it isn't up-to-date with latest changes; refer to text guide below for updates)

Here's some detailed instructions for getting osu! on Ubuntu (tested on 13.04, 13.10, and 14.04 (x86_64)):

1. Add the Wine PPA
System Settings > Software & Updates > Other Software > Add... > ppa:ubuntu-wine/ppa > Close
or
Terminal > sudo add-apt-repository ppa:ubuntu-wine/ppa

2. Update Software Sources
Terminal > sudo apt-get update

3. Install Wine
Terminal > sudo apt-get install wine1.7
- Should install around 230 or so MB of archives
- At the time of writing, wine1.7 will give you the latest Wine, 1.7.9. If you specify just wine, it will give you 1.6.
- Accept the license for the fonts package (well, read it first of course 8-); may have to click the Terminal window and use Tab and Arrow Keys to navigate)

4. Set up a 32-bit Wine Prefix
Terminal > WINEARCH=win32 winecfg
- This implies you want your main Wine prefix to be 32-bit. If you want osu! to be in it's own prefix, make a folder somewhere and use WINEPREFIX=[location] to specify it)
- Feel free to just close the configuration window afterwards

5. Install .NET Framework 2.0
Terminal > winetricks dotnet20
- You do not need any other dotnet. People seem to feel the need to install dotnet30 and 40, but I'm unsure why...

6. Download osume.exe
Terminal > wget http://osu.ppy.sh/release/osume.exe

7. Create a osu! folder in the Program Files folder in your Wine prefix, move osume.exe to it, and start osume.exe
Terminal > mkdir '.wine/drive_c/Program Files/osu!' && mv osume.exe '.wine/drive_c/Program Files/osu!' && cd '.wine/drive_c/Program Files/osu!' && wine osume.exe
- Long command that creates the directory, moves osume.exe to it, puts the Terminal into that folder, and runs osume.exe
- You can manually create the folders and move osume.exe with GUI also (just create an osu! folder in Program Files and drag osume.exe to it and right-click it to run it with Wine Windows Program Loader)

8. Wait for osu! update to completely download osu!
- If you have a beatmap and/or skin library backup somewhere, now would be a good time to restore it.

9. Start osu!
- If you cannot start osu! at this point, it is likely because of graphics drivers. If this is the case, you have to either install proprietary drivers, update the open-source drivers, or install 32-bit OGL libraries.
- Run osu! from Terminal via wine 'osu!.exe' and try checking for any specific errors if issues appear.

10. Do any initial in-game setup you want
- Includes logging-in, setting a resolution, changing keybinds, etc.
- If you cannot see the login prompt (likely the osu! game window will be above it), you'll have to exit osu! and either try disabling compositing, or setting osu!'s resolution lower in its cfg file
- If setting a fullscreen resolution causes osu! to crash and you cannot close it, see additional notes.

11. Exit osu!

At this point, you should have osu! on your computer, congratulations :)

Additional Notes:

- From this point on, the only thing you need to do to run osu! is just run the osu!.exe binary (double-click it or use the wine command from Terminal).

- If you want a Desktop and/or Menu shortcut to osu!, you'll have to either do this manually (really easy once you get the hang of it), or use something like wine-launcher-creator (that program is pretty helpful, especially if you have/want osu! on it's own prefix easily)
My XFCE icon for reference: http://pastebin.com/R6sM63ju (use it as a guideline)

- .osz downloads should automatically just work (did for me anyway; otherwise, just drag them to the Songs folder manually)

- You do not need gdiplus, but it is optional if you really want the few things it affects to look better. If you do opt for this, be prepared to download 538M, and run winetricks gdiplus and also note I cannot vouch for how compatible gdiplus is currently.

- I cannot vouch for how well osu! runs in a Wine prefix with other things installed, but I imagine it would be fine for most things (if any problems occur, do try it from a clean prefix if you didn't already)

- Choosing OpenGL mode in osu!'s Options will likely not work (osu! restarts back to DirectX mode). The reasoning for this is unknown.

- You cannot use the current osu! Installer from the Download page unless you install .NET Framework 3.0 (3.5?), and even then I'm not too sure if that works. As-per the guide above, you shouldn't need to do this at all though, but should you try it, be prepared for a troubleshooting process if things go wrong.

- If you have the older osu! installer that relies on .NET Framework 2.0 instead, you can use it, but last I tried it, it would crash during install. If this happens, do not re-run the installer, and copy osume.exe to the osu! folder and run it. You should have all the needed shortcuts if using this method.

- The reason for a 32-bit Wine Prefix is because of the dotnet20 installer. If you want a multiarch prefix (32/64 bit), you'll have to modify the dotnet20 installer package to accept 64-bit OSes. There are very few situations I can think of where this would be wanted... (you're better off putting osu! in a separate 32-bit prefix)

- If you have a Program Files (x86) folder present in the Wine prefix you tried installing osu! to, you have a multiarch prefix, which (for sake of simplicity) you don't want. You'll want to start over from Step 4.

- Should osu! crash or lock-up, you can try one of the following commands after pressing Alt + F2:
wineserver -k
killall wineserver
xkill > *click on osu!*
- If none of that works, try bringing up Terminal instead (Ctrl + Alt + T is default in most DEs) and trying the command(s) there
- If all else fails, do REISUB (be prepared for reboot)
- You may wish to try different video drivers (like going from fglrx to radeon) or other driver-specific troubleshooting (like --tls=0 on fglrx) if a crash or lock-up occurs

- If you have in-game scoreboard, combo popup, or other graphical corruption, a solution may be to enable StrictDrawOrdering (Terminal > winetricks strictdrawordering=enabled) but this can drop performance (your experience may vary). Another option is to use a d3d command stream-patched Wine and enable it (CSMT=enabled). Here's a PPA for such a version of Wine (do not submit AppDB results with this version of Wine). Do either one or the other. If going from StrictDrawOrdering to CSMT though, make sure to remove the StrictDrawOrdering setting, or set it back to disabled. Using gallium-nine also fixes corruption. Be sure to only choose one of these methods though (don't use more than one at a time).

- If you use a fullscreen resolution other than your native resolution, osu! may scale strangely in some cases. A quick fix I found was to just go under Options and set the frame limit to Unlimited (gameplay). Another option is to disable the window decorator from controlling windows (under winecfg)

- You may have to look into some hardware-specific stuff to get everything working good with your setup (such as setting a primary screen for multi-monitor setups, setting tablets to only hook to one screen, switching your touchpad to absolute mode, etc.)

- You may have to alter some commands slightly if you happen to use another desktop environment, distro of Linux, or some non-standard Ubuntu setup.

Here is the Wine AppDB entry for osu!.

And if all of that is seemingly too complicated, you could try PlayOnLinux. boat wrote a pretty nice guide here. I can't vouch for how well it may work or offer support about it directly, but I'm sure others can.

Good luck :)

Random Tips:

- If your tablet is experiencing strange behavior (see my thread here for reference), try removing xserver-xorg-input-wacom (and it's dependency xserver-xorg-input-all).

- If using open-source graphics drivers, it is recommended to have the latest Kernel you feel comfortable with. When using radeon, it is also recommended you manually enable DPM (radeon.dpm=1 as a kernel parameter; unless it's automatically enabled). If using Saucy Salamander (13.10) or feel brave with another similar distro (Mint, Debian, etc;) you should also consider adding Oibaf's Updated and Optimized Open Graphics Drivers PPA.

- Setting the environment variable vblank_mode=0 (either via EXPORT or just run it like vblank_mode=0 wine 'osu!.exe') disables vsync, and may lessen input delay. Only applicable to open-source graphics drivers.

- Disabling PulseAudio may lessen audio delay and issues. Use pasuspender, as removing PulseAudio is generally a bad idea. You may have to go through winecfg or winetricks to set ALSA to be used.

- Use of a Realtime Kernel may also further lessen any latency.
uzzi
Thanks for the explanation! I managed to get osu! to work after having to alter my wine to set the prefix to 32-bit, but after that it worked just fine. The only thing wrong now is that the frames seem to cap out at 60ish, even with the frame limiter off. I'm not sure if it's my hardware, because when I play on my Windows installation i get anywhere from 200-400fps, and anything under 140fps seems to delay my cursor. Have any idea as to what I can do?
Espionage724

- [ U z z I ] - wrote:

Thanks for the explanation! I managed to get osu! to work after having to alter my wine to set the prefix to 32-bit, but after that it worked just fine. The only thing wrong now is that the frames seem to cap out at 60ish, even with the frame limiter off. I'm not sure if it's my hardware, because when I play on my Windows installation i get anywhere from 200-400fps, and anything under 140fps seems to delay my cursor. Have any idea as to what I can do?
Hmm, are you using the open-source included drivers, or proprietary?

Could try using Terminal to start osu! with a environment variable to disable vsync:

Terminal > cd (wherever osu! is) > vblank_mode=0 wine 'osu!.exe'

(if it mentions some bash error or doesn't like osu!'s "!", then try dragging osu!.exe to the Terminal window instead of typing the exe (type the vblank_mode=0 wine part first, and leave a space after wine before dragging))
uzzi

Espionage724 wrote:

- [ U z z I ] - wrote:

Thanks for the explanation! I managed to get osu! to work after having to alter my wine to set the prefix to 32-bit, but after that it worked just fine. The only thing wrong now is that the frames seem to cap out at 60ish, even with the frame limiter off. I'm not sure if it's my hardware, because when I play on my Windows installation i get anywhere from 200-400fps, and anything under 140fps seems to delay my cursor. Have any idea as to what I can do?
Hmm, are you using the open-source included drivers, or proprietary?

Could try using Terminal to start osu! with a environment variable to disable vsync:

Terminal > cd (wherever osu! is) > vblank_mode=0 wine 'osu!.exe'

(if it mentions some bash error or doesn't like osu!'s "!", then try dragging osu!.exe to the Terminal window instead of typing the exe (type the vblank_mode=0 wine part first, and leave a space after wine before dragging))
I gave your suggestion a shot, and it seems to have rid of the frame cap, but the fps doesn't even pass 70 while playing, and the highest I saw out of the game was around 80-90. Not sure what to do at this point.

Oh and I'm not entirely sure which drivers I am using, as it has been a long time since I installed Ubuntu (not sure how to find out D;)
Espionage724
What GPU do you have?

If it's AMD or ATI, try typing fglrxinfo in Terminal and see if it reports something (if it gives a OpenGL version, you have AMD's proprietary driver). If it doesn't work, you likely have the open-source driver (radeon)

If it's NVIDIA, try typing nvidia-settings in Terminal and see if it opens anything (if a control panel opens, you have NVIDIA's proprietary driver). If it doesn't work, you likely have the open-source driver (nouveau)

If it's Intel, you likely have the open-source driver (there is a driver you can download from Intel, but it came out rather recently, and you'd probably know if you've did this).

Could also try using glxinfo | grep render from Terminal but this requires mesa-utils to be installed.
Fenek Alfa
Did exactly as you wrote, Everything worked except for the game itself.

fenek@fenek-MS-7693:~/.wine/drive_c/Program Files/osu!$ err:ole:CoGetContextToken apartment not initialised
fixme:shell:URL_ParseUrl failed to parse L"Microsoft.Xna.Framework"
fixme:shell:URL_ParseUrl failed to parse L"System.Drawing"
fixme:shell:URL_ParseUrl failed to parse L"msvcm80"
fixme:shell:URL_ParseUrl failed to parse L"System"
fixme:shell:URL_ParseUrl failed to parse L"System.Windows.Forms"
fixme:shell:URL_ParseUrl failed to parse L"System.Xml"
fixme:shell:URL_ParseUrl failed to parse L"mscorlib.resources"
fixme:shell:URL_ParseUrl failed to parse L"mscorlib.resources"
fixme:process:SetProcessPriorityBoost (0x228,0): stub
fixme:shell:URL_ParseUrl failed to parse L"osu"
fixme:shell:URL_ParseUrl failed to parse L"System.Configuration"
fixme:shell:URL_ParseUrl failed to parse L"Accessibility"
fixme:win:EnumDisplayDevicesW ((null),0,0x33df30,0x00000000), stub!
fixme:shell:URL_ParseUrl failed to parse L"System.resources"
fixme:shell:URL_ParseUrl failed to parse L"System.resources"
fixme:ole:RemUnknown_QueryInterface No interface for iid {00000019-0000-0000-c000-000000000046}
fixme:shell:URL_ParseUrl failed to parse L"osu!framework"
fixme:shell:URL_ParseUrl failed to parse L"osu!.resources"
fixme:shell:URL_ParseUrl failed to parse L"osu!.resources"
fixme:shell:URL_ParseUrl failed to parse L"{9ef86bea-cd1d-4cfd-a8e2-db51e2cb25c1}"
fixme:process:FlushProcessWriteBuffers : stub
fixme:winediag:AUDDRV_GetAudioEndpoint Winepulse is not officially supported by the wine project
fixme:winediag:AUDDRV_GetAudioEndpoint For sound related feedback and support, please visit http://ubuntuforums.org/showthread.php?t=1960599
err:winediag:X11DRV_WineGL_InitOpenglInfo Direct rendering is disabled, most likely your 32-bit OpenGL drivers haven't been installed correctly (using GL renderer "Gallium 0.4 on llvmpipe (LLVM 0x300)", version "1.4 (2.1 Mesa 8.0.4)").
err:d3d:test_arb_vs_offset_limit >>>>>>>>>>>>>>>>> GL_INVALID_OPERATION (0x502) from ARB vp offset limit test cleanup @ directx.c / 478
fixme:d3d:wined3d_guess_card No card selector available for card vendor 0000 (using GL_RENDERER "Gallium 0.4 on llvmpipe (LLVM 0x300)").
err:d3d:match_fbo_tex_update FBO status 0
err:d3d:match_broken_arb_fog FBO status 0
fixme:shell:URL_ParseUrl failed to parse L"osu!.resources"

And then it gives this line every few seconds:
fixme:thread:NtQueryInformationThread info class 16 not supported yet
Espionage724

Fenek Alfa wrote:

Did exactly as you wrote, Everything worked except for the game itself.

And then it gives this line every few seconds:
fixme:thread:NtQueryInformationThread info class 16 not supported yet
err:winediag:X11DRV_WineGL_InitOpenglInfo Direct rendering is disabled, most likely your 32-bit OpenGL drivers haven't been installed correctly (using GL renderer "Gallium 0.4 on llvmpipe (LLVM 0x300)", version "1.4 (2.1 Mesa 8.0.4)").
err:d3d:test_arb_vs_offset_limit >>>>>>>>>>>>>>>>> GL_INVALID_OPERATION (0x502) from ARB vp offset limit test cleanup @ directx.c / 478
fixme:d3d:wined3d_guess_card No card selector available for card vendor 0000 (using GL_RENDERER "Gallium 0.4 on llvmpipe (LLVM 0x300)").
You either need proper graphics drivers, or 32-bit OGL driver libraries installed. That shows that you're falling back to software acceleration via llvmpipe, which may not include some required features to get osu! running.

What's your GPU? (the post above should give you some ideas as to how to find out specifically along with what driver is in-use)
Marcin
Nice guide Espionage724, I'll add it into OP!
boat
I'm no good at this, I don't understand what went wrong :-(

I'd appreciate some help on this.



Doing it manually doesn't work for me either. Nothing happens when I open osume with the wine windows program loader.

Re-doing it gave me this

boat@theboat:~$ mkdir '.wine/drive_c/Program Files/osu!' && mv osume.exe '.wine/drive_c/Program Files/osu!' && cd '.wine/drive_c/Program Files/osu!' && wine osume.exe

Unhandled Exception:
System.InvalidProgramException: Invalid IL code in #ryb.#syb:#Zqb (string[]): IL_0165: stloc.3


[ERROR] FATAL UNHANDLED EXCEPTION: System.InvalidProgramException: Invalid IL code in #ryb.#syb:#Zqb (string[]): IL_0165: stloc.3
Espionage724
Hmm, what version of Wine are you using boat?
boat
Should be whatever the latest one is as this is a fresh install from just a day or so ago, although I'm on ubuntu 12.04, not 13.

Wine configuration says it's at 1.6
Espionage724
Hmm, not too sure what was done wrong on the second attempt to throw a FATAL UNHANDLED EXCEPTION.

Could you give the terminal output for what happens when you try running osume.exe?
boat
I'm sorry but I don't even really know how I'd run it through the terminal. Right clicking the file and trying to open it with wine windows program launcher doesn't do anything at all.
Espionage724

boat wrote:

I'm sorry but I don't even really know how I'd run it through the terminal. Right clicking the file and trying to open it with wine windows program launcher doesn't do anything at all.
Either open a Terminal at the osu! folder location (Xfce and KDE has a right-click Action for it; Nautilus I believe has it on the top-bar menu somewhere), or cd into it manually. Then type wine osume.exe
boat
boat@theboat:~/.wine/drive_c/Program Files/osu!$ wine osume.exe

Unhandled Exception:
System.InvalidProgramException: Invalid IL code in #ryb.#syb:#Zqb (string[]): IL_0165: stloc.3


[ERROR] FATAL UNHANDLED EXCEPTION: System.InvalidProgramException: Invalid IL code in #ryb.#syb:#Zqb (string[]): IL_0165: stloc.3
Espionage724

boat wrote:

boat@theboat:~/.wine/drive_c/Program Files/osu!$ wine osume.exe

Unhandled Exception:
System.InvalidProgramException: Invalid IL code in #ryb.#syb:#Zqb (string[]): IL_0165: stloc.3


[ERROR] FATAL UNHANDLED EXCEPTION: System.InvalidProgramException: Invalid IL code in #ryb.#syb:#Zqb (string[]): IL_0165: stloc.3
Try doing winetricks dotnet20 if you haven't already
boat
Well I have already, but I'll try redoing it all. Would reinstalling/installing a different (confirmed working) version of wine also be something to try?

The installer for net framework 2.0 fails because it's not supported on a 64bit os apparently. Odd, thought it worked the first time. I guess that's probably the problem, then.
Espionage724

boat wrote:

Well I have already, but I'll try redoing it all. Would reinstalling/installing a different (confirmed working) version of wine also be something to try?
If you are trying to redo it, just make sure to delete the old prefix (either through winetricks --gui or just manually delete the .wine folder from your Home directory).

I got the same error just now when I tried running osume.exe, but I didn't do the dotnet20 setup yet. When you try rerunning the command in a clean prefix, make sure it actually finishes (took maybe 2 minutes to complete for me in the past).

I've seen osu! run fine on wine1.6, and I don't believe anyone had any problem with some previous versions, but it's nice to be on the latest one if possible. On raring with just the official ubuntu-wine PPA added for Wine, the latest should be 1.7.2 (you might to reinstall wine using wine1.7, or just select it from a package manager like Synaptic). But in any case, wine1.6 should work fine.
boat
Well I got it running without reinstalling, I just messed up the prefix step.

It runs, but, uh



I get good framerates on dx (300-400), but it's the same issue there.
Espionage724

boat wrote:

Well I got it running without reinstalling, I just messed up the prefix step.

It runs, but, uh
Are you by some chance using AMD/ATI hardware and fglrx?
boat
Well I installed the "AMD Catalyst™ 13.4 Proprietary Linux x86 Display Driver" when I was fiddling with getting dota2 to run, which it handles very well.

Couldn't run it on fglrx. Is this not fixable, and if not, would getting an nvidia gpu solve it?
Espionage724

boat wrote:

Well I installed the "AMD Catalyst™ 13.4 Proprietary Linux x86 Display Driver" when I was fiddling with getting dota2 to run, which it handles very well.

Couldn't run it on fglrx.
fglrx is the name of AMD's proprietary driver on Linux (FireGL and Radeon for X). A quick way to check if that's what you're using is typing fglrxinfo from Terminal.

If you are using fglrx though, that particular glitching seems to be a known issue. You could try either enabling StrictDrawOrder with winetricks strictdrawordering=enabled or use a D3D Command Stream-patched version of Wine (either have to do this via acquiring Wine's source, patching it, and compiling/installing it; or try this PPA)

I'm not entirely sure why fglrx would cause such an issue though.
boat
winetricks strictdrawordering=enabled solved it. It runs significantly worse, but at least it works. Thanks a load!
Fenek Alfa

Espionage724 wrote:

Fenek Alfa wrote:

Did exactly as you wrote, Everything worked except for the game itself.

And then it gives this line every few seconds:
fixme:thread:NtQueryInformationThread info class 16 not supported yet
err:winediag:X11DRV_WineGL_InitOpenglInfo Direct rendering is disabled, most likely your 32-bit OpenGL drivers haven't been installed correctly (using GL renderer "Gallium 0.4 on llvmpipe (LLVM 0x300)", version "1.4 (2.1 Mesa 8.0.4)").
err:d3d:test_arb_vs_offset_limit >>>>>>>>>>>>>>>>> GL_INVALID_OPERATION (0x502) from ARB vp offset limit test cleanup @ directx.c / 478
fixme:d3d:wined3d_guess_card No card selector available for card vendor 0000 (using GL_RENDERER "Gallium 0.4 on llvmpipe (LLVM 0x300)").
You either need proper graphics drivers, or 32-bit OGL driver libraries installed. That shows that you're falling back to software acceleration via llvmpipe, which may not include some required features to get osu! running.

What's your GPU? (the post above should give you some ideas as to how to find out specifically along with what driver is in-use)
(been away, finally got some time to do it)
So I have a Gigabyte GeForce GTX 650, and no matter whether I downloaded the drivers from Nvida's site or through "Additional Drivers", both of them caused my pc to turn on only with console. I got it working again in both cases(by "sudo apt-get remove --purge nvidia* " and then "sudo start lightdm" and rebooting, I heard that's the first thing to do when a Nvidia driver install related fail happens), although now my cursor sometimes disappears.
Espionage724

Fenek Alfa wrote:

(been away, finally got some time to do it)
So I have a Gigabyte GeForce GTX 650, and no matter whether I downloaded the drivers from Nvida's site or through "Additional Drivers", both of them caused my pc to turn on only with console. I got it working again in both cases(by "sudo apt-get remove --purge nvidia* " and then "sudo start lightdm" and rebooting, I heard that's the first thing to do when a Nvidia driver install related fail happens), although now my cursor sometimes disappears.
Hmm, unfortunately I have no experience with NVIDIA hardware under Linux :/

I don't know how well nouveau suports your card, but here's a pretty up-to-date PPA for graphics drivers that might help. Might also recommend updating your kernel as well to the latest you're comfortable with (there's 3.12 nightlies, 3.12rc2, and 3.11.1 currently; raring by default comes with 3.8). Newer kernels tend to have some open-source driver improvements.

Another option to try is to use a Desktop Environment that doesn't require 3D acceleration (Unity on Ubuntu I believe since 12.10 requires 3D acceleration, either via hardware or llvmpipe). Not sure if this would be helpful to a computer that doesn't seem to start lightdm though at all...
marshallracer
Wow, it's been quite some time since I used Linux .. nice to be back again

So, I tried to follow your (in fact easy to understand) guide Espionage, but I have Ubuntu 12.04 LTS 64Bit installed and I just don't know where or how to setup a 32 bit Prefix for Wine

Anyway, nice to see how People keep up with osu! on Linux, I'm impressed
Espionage724

marshallracer wrote:

Wow, it's been quite some time since I used Linux .. nice to be back again

So, I tried to follow your (in fact easy to understand) guide Espionage, but I have Ubuntu 12.04 LTS 64Bit installed and I just don't know where or how to setup a 32 bit Prefix for Wine

Anyway, nice to see how People keep up with osu! on Linux, I'm impressed
Once you have Wine installed, you first run WINEARCH=win32 winecfg to create the 32-bit prefix (you can close the Wine Configuration window once it appears). Then from there, you run the winetricks dotnet20 command. If it completes without error, you've successfully created a 32-bit prefix :) If it mentions it can't install on a 64-bit OS, that means the prefix isn't 32-bit.
marshallracer
Yeah, I somehow got that far but everytime I type that in the result looks like this:
martin@martin-PC:~$ WINEARCH=win32 winecfg
wine: WINEARCH set to win32 but '/home/martin/.wine' is a 64-bit installation.

And when I try to use winetricks dotnet20 the installer just tells me that it can't be installed on 64-bit architecture
Espionage724

marshallracer wrote:

Yeah, I somehow got that far but everytime I type that in the result looks like this:
martin@martin-PC:~$ WINEARCH=win32 winecfg
wine: WINEARCH set to win32 but '/home/martin/.wine' is a 64-bit installation.

And when I try to use winetricks dotnet20 the installer just tells me that it can't be installed on 64-bit architecture
Ah; as long as you don't have anything else in the prefix you'd want, just delete the .wine folder from your Home directory, then run the WINEARCH=win32 winecfg command again.

Running rm -rf ~/.wine should do the job for removing the folder.
marshallracer
Ok, I got it working, then got gdiplus and enabled strictdrawordering
Results : osu! is running perfectly fine, no performance drops to be honest and no graphical issues

Somewhat different procedure from what I remember how it was back then (I guess the one I used was from somewhere around pages 13-15), but it seems this doesn't change the outcome

Thanks for helping out on that one :D
mmstick
You guys do realize it's far easier to configure a Play On Linux install than simply using Wine, right? PlayOnLinux already provides a CSMT-patched wine version (1.7.1-CSMT) but you must disable Strict Draw Ordering on the Display tab.
Espionage724

mmstick wrote:

You guys do realize it's far easier to configure a Play On Linux install than simply using Wine, right? PlayOnLinux already provides a CSMT-patched wine version (1.7.1-CSMT) but you must disable Strict Draw Ordering on the Display tab.
I don't use POL, but wouldn't it run into the same exact issues and basically be the same install process?

You still need a 32-bit Wine prefix, you still need dotnet20, and afaik, you still need to manually create the folder for osu!, copy osume.exe over to it, and run it.

POL is an unsupported Wine frontend, so if anyone has any unexpected issues with osu!, now not only is the problem not limited to just Wine, but also with POL. It might make the menu/desktop shortcut creation easier, if anything, along with easier handling of multiple prefixes if you need them.
mmstick

Espionage724 wrote:

mmstick wrote:

You guys do realize it's far easier to configure a Play On Linux install than simply using Wine, right? PlayOnLinux already provides a CSMT-patched wine version (1.7.1-CSMT) but you must disable Strict Draw Ordering on the Display tab.
I don't use POL, but wouldn't it run into the same exact issues and basically be the same install process?

You still need a 32-bit Wine prefix, you still need dotnet20, and afaik, you still need to manually create the folder for osu!, copy osume.exe over to it, and run it.

POL is an unsupported Wine frontend, so if anyone has any unexpected issues with osu!, now not only is the problem not limited to just Wine, but also with POL. It might make the menu/desktop shortcut creation easier, if anything, along with easier handling of multiple prefixes if you need them.
In other words, you don't know much about PlayOnLinux. You should try it out. dotnet20 is installed on the "Install components" tab. Prefixes are called "virtual drives'. If you know what 'front end' means then it won't cause any problems that wine itself wouldn't have already caused by itself. It will certainly make debugging wine problems easier. The purpose is to make wine installation and management easier.
boat

Espionage724 wrote:

you still need to manually create the folder for osu!, copy osume.exe over to it, and run it.
nop

I've written a script that does literally everything for you.

http://www.playonlinux.com/en/topic-110 ... t_osu.html

mkdir "$WINEPREFIX/drive_c/$PROGRAMFILES/osu!"
cd "$WINEPREFIX/drive_c/$PROGRAMFILES/osu!"

POL_Download http://osu.ppy.sh/release/osume.exe
POL_Wine osume.exe

But it really is pretty much the same thing just that you can have a script do it for you, and it makes troubleshooting easier.
boat
Espionage724

boat wrote:

^ The script is validated.

http://www.playonlinux.com/en/app-1856-osu.html
Hmm, that is pretty cool looking. I'm curious about the user.cfg though?
boat
The updater doesn't create a osu!.user.cfg file (not sure if the installer does this either though), the game starts in fullscreen and on some machines the login window is displayed behind the game itself. It's an unnecessary step for the user to have to close the game (which can be buggy as well) and change the resolution manually through the cfg, so I made it download it automatically without having to emulate a virtual desktop with wine, which wouldn't let you change the resolution beyond the virtual desktop res.

I did make an icon for the shortcut as well but petch didn't add it for some reason. In the meantime you can manually set it to this.

nightbane112
Funny thing is the Bloodcat .deb file work but only for the 1.0-5 version http://blog.bloodcat.com/207 :P . According to the steps, I'm suppose to install ver. 1.0-5 and then the latter, 1.0-6 . Whenever I uninstall osu! and reinstall it, it magically doesn't work :( . But, there's a catch, if I install the 1.0-5 ver.only , osu! works ! :) . Here, have some screenshots!


antiflash
So today I spent 2 hours getting this to work properly. Here's what I did:

1) sudo apt-get install wine
2) rm -rf ~/.wine (I had to do this because I have 64bit installation. This command removes wine folder.)
3) WINEARCH=win32 winecfg (And this command forces it to be 32bit.)
4) winetricks dotnet20 (And proceed with installation of framework.)
5) Copy folder with installed Osu somewhere on your computer. (I didn't install it, I just took it from my Windows.)
6) Right click on Osu.exe, run with Wine aaaaand... It's working!

I don't have any graphical issues and OpenGL works fine.

Issues I have:
- audio is slightly off the rhythm sometimes
- I need to have mouse speed set on 1.0 in Osu, otherwise the mouse speed changes from like 1cm to other side of the screen with the same lenght of mouse moved.

HW:
AMD Radeon HD7770
AMD Phenom II x4 965
I'm running Linux Mint 15 Oliva, so it should work exactly the same on Ubuntu 13.04 and newest version of Debian.
I don't have any lags and fps is around the same as on Windows.

Hope it somehow help anybody who can't get it to work.

PS: Sorry for my bad english, I hope it's understandable.

;)
boat
Yeah, that's pretty much the same procedure as the currently recommended one, osume does the same but with new files.

I'm surprised you're able to run it in openGL though, I've been trying to do that myself but can't get it to work.
Espionage724

antiflash wrote:

I don't have any graphical issues and OpenGL works fine.

HW:
AMD Radeon HD7770
Hmm, what driver are you using?
Lomadriel
Hello

For Ubuntu 13.10, i have a nice trick :
The following commands install PlayoneLinux and osu

1.
sudo apt-get install p7zip-full

2.
wget -q "http://deb.playonlinux.com/public.gpg" -O- | sudo apt-key add -

3.
sudo wget http://deb.playonlinux.com/playonlinux_precise.list -O /etc/apt/sources.list.d/playonlinux.list

4.
sudo apt-get update

5.
sudo apt-get install curl
6.
sudo apt-get install playonlinux


When you have finished these steps. Open Playonlinux. Click on "Install". Check "test" and search osu. Follow the installation steps ( install the recommended programs ) it's finished. The best Wine's Version is installed for Osu! by Playonlinux. ^^

PS : I am French, sry for my english. ^^
PS2 : With this tool you can install many Windows games ^^
Espionage724

Lomadriel wrote:

Hello

For Ubuntu 13.10, i have a nice trick :
The following commands install PlayoneLinux and osu
Is all of that really necessary? I was on Ubuntu 13.10 a few days ago, and the only thing I had to do to get PoL was download their .deb package from their website, install it, and run it (all done from GUI). Didn't need to manually install p7zip, add any keys, or mess with curl.

PoL might even be in Ubuntu's repository (but don't quote me on this), so you might even be able to get away with just running command 6.
Lomadriel
Hum, I am not sure but the version in the repository is not the last version. On my computer p7zip and curl were not installed automatically.
marshallracer
13.10 has the newest PoL package in its repository, previous Versions probably don't for whatever reasons (atleast I had an older version in the 12.04 repo 2 days ago)
didn't check if it works on 13.10 but I guess there wouldn't be any reason it shouldn't
Lomadriel

marshallracer wrote:

13.10 has the newest PoL package in its repository
Okay so open the official repository and install playonlinux is sufficient ^^
mmstick

Espionage724 wrote:

antiflash wrote:

I don't have any graphical issues and OpenGL works fine.

HW:
AMD Radeon HD7770
Hmm, what driver are you using?
As long as you use strict draw ordering, you won't have any graphical issues with RadeonSI, but you will have significantly lower performance. He's probably using Catalyst, as I only recommend Catalyst 13.11 with RadeonSI GPUs. I've been able to get 1000-2000FPS with my HD 7950 with strict draw ordering disabled with Cat 13.11 on Ubuntu 13.04 with kernel 3.12.

Also, yes playonlinux is in Ubuntu 13.10's repos. Just 'sudo aptitude install playonlinux -y' and you're done.
Espionage724

mmstick wrote:

As long as you use strict draw ordering, you won't have any graphical issues with RadeonSI, but you will have significantly lower performance. He's probably using Catalyst, as I only recommend Catalyst 13.11 with RadeonSI GPUs. I've been able to get 1000-2000FPS with my HD 7950 with strict draw ordering disabled with Cat 13.11 on Ubuntu 13.04 with kernel 3.12.
Yeah but the thing I was curious about was him using OpenGL rendering with osu!. At least in my experience, osu! will always use DirectX, regardless of ticking the OpenGL box from options or setting it via cfg.
marshallracer
hey, has anyone an idea why I'm having a pure black screen in all wine applications on 13.10 (including osu!, ofcourse)?
I completely reinstalled Ubuntu a few days ago since I had problems with the display manager in 12.04 and I got myself Saucy now and somehow Starting osu results in a simple black screen
Newest Catalyst Beta is installed using a HD 5670 and osu was installed using boats POL script
mmstick

marshallracer wrote:

hey, has anyone an idea why I'm having a pure black screen in all wine applications on 13.10 (including osu!, ofcourse)?
I completely reinstalled Ubuntu a few days ago since I had problems with the display manager in 12.04 and I got myself Saucy now and somehow Starting osu results in a simple black screen
Newest Catalyst Beta is installed using a HD 5670 and osu was installed using boats POL script
Your first and biggest issue is the fact that you are using Catalyst for a non-GCN card. It's only advised to use Catalyst if, and only if, you have a Radeon HD 7000 or higher. For everyone else, AMD is putting almost all of their development effort into the open source drivers, which massively outperforms Catalyst on non-GCN hardware.

Second, the drivers that ship with Ubuntu 13.10 are horrible, and Ubuntu 13.10 has launched with a ton of bugs which may take a month to get fixed. Ubuntu 13.04 on the other hand is very stable.

First, uninstall Catalyst and then do the following:

## Install Kernel 3.12-rc6 (It has massively improved performance due to CPU governor improvements)
cd /tmp
wget http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.12-rc6-saucy/linux-headers-3.12.0-031200rc6-generic_3.12.0-031200rc6.201310191635_amd64.deb
wget http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.12-rc6-saucy/linux-headers-3.12.0-031200rc6_3.12.0-031200rc6.201310191635_all.deb
wget http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.12-rc6-saucy/linux-image-3.12.0-031200rc6-generic_3.12.0-031200rc6.201310191635_amd64.deb
sudo dpkg -i linux*.deb

## Install the latest 'Updated and Optimized' open source drivers via Oibaf's PPA then reboot
sudo add-apt-repository -y ppa:oibaf/graphics-drivers; sudo apt-get update; sudo aptitude upgrade -y; sudo aptitude dist-upgrade -y; sudo reboot
Espionage724

marshallracer wrote:

hey, has anyone an idea why I'm having a pure black screen in all wine applications on 13.10 (including osu!, ofcourse)?
I completely reinstalled Ubuntu a few days ago since I had problems with the display manager in 12.04 and I got myself Saucy now and somehow Starting osu results in a simple black screen
Newest Catalyst Beta is installed using a HD 5670 and osu was installed using boats POL script
Have you verified fglrx to be working properly? Try typing fglrxinfo in Terminal to see info, and then fgl_glxgears and see if anything appears.

As for mmstick's note, the open-source radeon driver is also something to try if fglrx isn't working out for you.

mmstick wrote:

First, uninstall Catalyst and then do the following:
## Install the latest 'Updated and Optimized' open source drivers via Oibaf's PPA then reboot
sudo add-apt-repository -y ppa:oibaf/graphics-drivers; sudo apt-get update; sudo aptitude upgrade -y; sudo aptitude dist-upgrade -y; sudo reboot
Last I heard, Oibaf's PPA had little-to-no support for saucy (still appears to be the case). Only things you'd get out of it on saucy are "glamor-egl" and "wayland" if I understand right, unless you manually specify the raring branch instead?
mmstick

Espionage724 wrote:

marshallracer wrote:

hey, has anyone an idea why I'm having a pure black screen in all wine applications on 13.10 (including osu!, ofcourse)?
I completely reinstalled Ubuntu a few days ago since I had problems with the display manager in 12.04 and I got myself Saucy now and somehow Starting osu results in a simple black screen
Newest Catalyst Beta is installed using a HD 5670 and osu was installed using boats POL script
Have you verified fglrx to be working properly? Try typing fglrxinfo in Terminal to see info, and then fgl_glxgears and see if anything appears.

As for mmstick's note, the open-source radeon driver is also something to try if fglrx isn't working out for you.

mmstick wrote:

First, uninstall Catalyst and then do the following:
## Install the latest 'Updated and Optimized' open source drivers via Oibaf's PPA then reboot
sudo add-apt-repository -y ppa:oibaf/graphics-drivers; sudo apt-get update; sudo aptitude upgrade -y; sudo aptitude dist-upgrade -y; sudo reboot
Last I heard, Oibaf's PPA had little-to-no support for saucy (still appears to be the case). Only things you'd get out of it on saucy are "glamor-egl" and "wayland" if I understand right, unless you manually specify the raring branch instead?

Support for Saucy was added two days ago. The benefit of Oibaf is more than just glamor, but that the xorg drivers that shipped with Ubuntu 13.10 are nearly 3 months old. Marek Olsak joined AMD's open source team and began submitting patches on July 30th 2013, of which he has regularly submitted a substantial amount of patches, especially in the last 3 months. To benefit from that, you need the latest drivers, aka Oibaf, who stays up-to-date with the latest git efforts.
Espionage724

mmstick wrote:

Support for Saucy was added two days ago. The benefit of Oibaf is more than just glamor, but that the xorg drivers that shipped with Ubuntu 13.10 are nearly 3 months old. Marek Olsak joined AMD's open source team and began submitting patches on July 30th 2013, of which he has regularly submitted a substantial amount of patches, especially in the last 3 months. To benefit from that, you need the latest drivers, aka Oibaf, who stays up-to-date with the latest git efforts.
saucy: https://launchpad.net/~oibaf/+archive/g ... lter=saucy is only showing glamor and wayland packages.

raring: https://launchpad.net/~oibaf/+archive/g ... ter=raring on the other hand is showing the drivers and more.

If I understand right, if you add a PPA to Ubuntu as-is (in this case, ppa:oibaf/graphics-drivers), it will only grab packages from whatever distro version you're using at the time (in marshallracer's case, saucy).
marshallracer
so .. I already did follow mm's steps, just need to reboot but I still need to download a file so I just wait a bit as long as everything's still running

On a side note : I was using the same beta drivers on 12.04 a week ago and everything was running fine (except LoL which could've been because of Unity 3D), so I've been wondering now why it's not working on 13.10 (bugs, kernel, anything? I'm still not very experienced with Linux/Ubuntu but I'm figuring things out .. or atleast I try to)

Edit: sooo, I can tell something's not right .. or atleast I guess so
How I come to this conclusion .. well, I can't start Steam anymore, which was possible before, due to missing libraries

I don't know what to do, but then again I only followed your steps anyway, updating the Kernel (if that's what I've been doing), adding the repo, updating/upgrading and rebooting
Espionage724

marshallracer wrote:

Edit: sooo, I can tell something's not right .. or atleast I guess so
How I come to this conclusion .. well, I can't start Steam anymore, which was possible before, due to missing libraries

I don't know what to do, but then again I only followed your steps anyway, updating the Kernel (if that's what I've been doing), adding the repo, updating/upgrading and rebooting
Did you follow proper procedure to remove fglrx?

http://wiki.cchtml.com/index.php/Ubuntu ... st.2Ffglrx

Run the first two commands there (the fglrx-uninstall.sh and the --purge fglrx* ones), then proceed to those 5 below (running every command one at a time also). I never ran into that libgl1-mesa-dri issue that page mentions, but if you should happen to see it during the uninstall process, follow it's recommendation.

After all that, reboot, then you should be back on the open-source radeon driver.
Azern
Best to bookmarked it first....
marshallracer
ok, ok, I got everything running now, added oibaf's repo, got rid of catalyst/fglrx and fixed the libgl issue
Thanks alot guys, everythings running and hopefully keeps running for some time

edit: well, almost running .. when I go into beatmap selection the screen turn into something like this and stays like that until I restart osu

happens with and without StrictDrawOrdering
mmstick
AMD drivers were added to oibaf an hour ago so running an update/upgrade/dist-upgrade should pull in the new driver.
https://launchpad.net/~oibaf/+archive/g ... lter=saucy
marshallracer
Well, the driver is now downloaded and in I guess, but osu's still not working though .. atleast I'm done with the setup procedure .. am I?
Also, how do I check if the driver I got from oibaf are working? Just to be sure
mmstick
glxinfo | grep OpenGL will display the currently running graphics card. If it says llvmpipe then it is using software rendering. Although oibaf has the AMD driver on Saucy, it hasn't received the latest mesa/llvm and other assorted packages yet.
marshallracer
martin@martinPC:~$ glxinfo | grep OpenGL
OpenGL vendor string: X.Org
OpenGL renderer string: Gallium 0.4 on AMD REDWOOD
OpenGL core profile version string: 3.1 (Core Profile) Mesa 9.2.1
OpenGL core profile shading language version string: 1.40
OpenGL core profile context flags: (none)
OpenGL core profile extensions:
OpenGL version string: 3.0 Mesa 9.2.1
OpenGL shading language version string: 1.30
OpenGL context flags: (none)
OpenGL extensions:

I guess I simply need to wait until everything's ready
Espionage724

marshallracer wrote:

martin@martinPC:~$ glxinfo | grep OpenGL
OpenGL vendor string: X.Org
OpenGL renderer string: Gallium 0.4 on AMD REDWOOD
OpenGL core profile version string: 3.1 (Core Profile) Mesa 9.2.1
OpenGL core profile shading language version string: 1.40
OpenGL core profile context flags: (none)
OpenGL core profile extensions:
OpenGL version string: 3.0 Mesa 9.2.1
OpenGL shading language version string: 1.30
OpenGL context flags: (none)
OpenGL extensions:

I guess I simply need to wait until everything's ready
How did you install fglrx before? Did you just use the hardware tab thing from Ubuntu's Software and Sources window, or did you download it manually?

I can't imagine why osu! wouldn't just work properly, especially for a 5xxx card (my rebranded dual-graphics 6xxx laptop and 7xxx desktop ran osu! with both fglrx and radeon on saucy).

Only thing I can think of is an improper setup somewhere (I know when I unintalled fglrx on my 7xxx desktop, I had broken radeon drivers and ended up doing a OS reinstall).
marshallracer
well, the very first thing I did after installing Saucy was downloading the latest drivers from AMD and installing them manually without any problems
Why I had a black screen on osu! then is way beyond my understanding
Espionage724

marshallracer wrote:

well, the very first thing I did after installing Saucy was downloading the latest drivers from AMD and installing them manually without any problems
Why I had a black screen on osu! then is way beyond my understanding
Just to be clear, you installed the 13.11 BETA1 driver? Did you do it in-accordance to this guide?: http://wiki.cchtml.com/index.php/Ubuntu ... PERIMENTAL
marshallracer
well, for once I tried the latest stable one and the Beta, but seemingly I simply installed it automatically through the installer and I was done with it .. habits of using windows, just installing everything without thinking about what to do or what'd be neccessary

Maybe I'll give it a last try, let's see, but this time I don't want to screw up again
Espionage724

marshallracer wrote:

well, for once I tried the latest stable one and the Beta, but seemingly I simply installed it automatically through the installer and I was done with it .. habits of using windows, just installing everything without thinking about what to do or what'd be neccessary

Maybe I'll give it a last try, let's see, but this time I don't want to screw up again
Ah, yeah apparently running the installer as-is isn't ideal on a few Linux distros (Ubuntu especially; afaik, the installer can only be ran as-is on SUSE). That guide lets you use the installer to generate some saucy-specific installers, which, in-short, leads to a better experience.

Just make sure of that final step to do sudo amdconfig --initial -f before rebooting. Then after reboot, do fglrxinfo and then fgl_glxgears to verify it installed properly. Then try out osu!.
marshallracer
martin@martinPC:~$ fglrxinfo
display: :0 screen: 0
OpenGL vendor string: Advanced Micro Devices, Inc.
OpenGL renderer string: ATI Radeon HD 5670
OpenGL version string: 4.3.12458 Compatibility Profile Context 13.20.16

martin@martinPC:~$ fgl_glxgears
Using GLX_SGIX_pbuffer
6114 frames in 5.0 seconds = 1222.800 FPS
5580 frames in 5.0 seconds = 1116.000 FPS
5210 frames in 5.0 seconds = 1042.000 FPS
6082 frames in 5.0 seconds = 1216.400 FPS
5838 frames in 5.0 seconds = 1167.600 FPS
5941 frames in 5.0 seconds = 1188.200 FPS
5894 frames in 5.0 seconds = 1178.800 FPS
[...]
fglrx installed and working (I assume) and no stragely pixelated frame anymore when scrolling through menus .. but osu now stops responding after switching through menus (following was after going back from map selection, applies to other actions aswell)


Saucy pls
Espionage724
Hmm, and this is with the latest version of Wine 1.7 (1.7.4 or 1.7.5; whatever Ubuntu has in it's repository atm), in a clean 32-bit wineprefix with only dotnet20 installed?
marshallracer

Espionage724 wrote:

Hmm, and this is with the latest version of Wine 1.7 (1.7.4 or 1.7.5; whatever Ubuntu has in it's repository atm), in a clean 32-bit wineprefix with only dotnet20 installed?
-Yes
-Yes
-Yes

holy shit this is like, the only thing that won't give me any rest and it isn't even important at all
But through this we'll atleast have a way to help people running osu on Saucy ..I hope
Shock_T
When I typed in "mkdir '.wine/drive_c/Program Files/osu!' && mv osume.exe '.wine/drive_c/Program Files/osu!' && cd '.wine/drive_c/Program Files/osu!' && wine osume.exe" it said "mkdir: cannot create directory ‘.wine/drive_c/Program Files/osu!’: File exists"

It also said something about my OS being a 64 bit OS and the program being 32 bit when installing the dot net 20 thing or whatever...

I don't like Linux. I only use it because it's much faster than my old Windows Vista. Please help - I have no idea what I'm doing.
marshallracer
This is where PlayonLinux aids you with boats script but yeah, when you try to do it with wine itself there was some good suggestion a few pages ago

Espionage724 wrote:

Once you have Wine installed, you first run WINEARCH=win32 winecfg to create the 32-bit prefix (you can close the Wine Configuration window once it appears). Then from there, you run the winetricks dotnet20 command. If it completes without error, you've successfully created a 32-bit prefix :) If it mentions it can't install on a 64-bit OS, that means the prefix isn't 32-bit.
Edit : regarding my personal problem .. the solution was disturbingly easy ...


Why not using proprietary drivers provided by Ubuntu?
I decided to uninstall fglrx manually and choose fglrx-updates here, restarted Ubuntu to be sure and voila, osu!'s finally running (a bit slow due to StrictDrawordering I guess, but still)
mekadon_old
I managed to get osu! running on Arch, but if I run it this happens:

Sound is not working (guess I didn't make wine use alsa, I'm not sure about it yet)
Default skin is using the old skin, no idea why
Any beatmap can not be loaded
No beatmap backgrounds at all

Framerate is fine though, it's really smooth
EDIT: just need to install some libraries, resolved everything but this

Sliders look terribly ugly
Fonts look terrible (maybe I should change the font rendering in wineprefix, but I'm kinda sleepy so doing that later when I wake up)

Commands I did

$ su -c "pacman -S wine winetricks lib32-alsa-lib lib32-mpg123 lib32-giflib lib32-libjpeg lib32-libpng"
$ rm -rf ~/.wine
$ WINEARCH=win32 winecfg
$ winetricks dotnet20
$ cd /mnt/sda2/Program\ Files\ \(x86\)/osu\! (Basically my osu! folder, obviously)
$ wine osu!.exe

Using Wine 1.7.5, kernel version is 3.11.6-1 and it's Arch's stock kernel.

Extra stuff, just in case.

┌─[yucachaaaan @ kininarimars]-[1:57:05]
└─[~]-[$]> lspci | grep VGA
00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09)
02:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Thames [Radeon 7550M/7570M/7650M] (rev ff)

Using xf86-video-ati and xf86-video-intel as drivers, disabled the ATI one using
# echo OFF > /sys/kernel/debug/vgaswitcheroo/switch
since it tends to overheat. I don't think it'll affect anything if I turn it on, I did just to check *just in case* and it's still the same.

Screenshot

Espionage724

Shock_T wrote:

When I typed in "mkdir '.wine/drive_c/Program Files/osu!' && mv osume.exe '.wine/drive_c/Program Files/osu!' && cd '.wine/drive_c/Program Files/osu!' && wine osume.exe" it said "mkdir: cannot create directory ‘.wine/drive_c/Program Files/osu!’: File exists"

It also said something about my OS being a 64 bit OS and the program being 32 bit when installing the dot net 20 thing or whatever...

I don't like Linux. I only use it because it's much faster than my old Windows Vista. Please help - I have no idea what I'm doing.
Go to your home folder, press CTRL + H to unhide all files/folders, and delete the .wine folder (as long as you don't have anything in it you want to keep); then do WINEARCH=win32 winecfg to make the 32-bit prefix. Then try the guide again, or try PlayOnLinux if you want.

marshallracer wrote:

Why not using proprietary drivers provided by Ubuntu?
I decided to uninstall fglrx manually and choose fglrx-updates here, restarted Ubuntu to be sure and voila, osu!'s finally running (a bit slow due to StrictDrawordering I guess, but still)
Hmm, hasn't crossed my mind to try that lol, but great that it works :) Last time I tried that though, it ended up breaking Unity strangely...

mekadon wrote:

Sliders look terribly ugly
Fonts look terrible (maybe I should change the font rendering in wineprefix, but I'm kinda sleepy so doing that later when I wake up)
Not entirely sure what's up with the sliders (maybe try the Force slider setting from osu!'s Options), but as for Fonts, maybe try installing gdiplus with winetricks?
mekadon_old

Espionage724 wrote:

mekadon wrote:

Sliders look terribly ugly
Fonts look terrible (maybe I should change the font rendering in wineprefix, but I'm kinda sleepy so doing that later when I wake up)
Not entirely sure what's up with the sliders (maybe try the Force slider setting from osu!'s Options), but as for Fonts, maybe try installing gdiplus with winetricks?
Tried forcing slider rendering, doesn't work. Gdiplus helps with my fonts though.

Another interesting thing I find, the window moves by itself when on Taiko mode.



I'm not sure if it's due to my window manager (dwm), but I made an openbox session (just a tiny edit on ~/.xinitrc), and it works...
m42a
Yeah, that happens on xmonad as well. If I sink the window and force it to tile it stops moving. I think the window border is messing it up.
Espionage724

m42a wrote:

Yeah, that happens on xmonad as well. If I sink the window and force it to tile it stops moving. I think the window border is messing it up.
Hmm from winecfg, try toggling the settings that reference to controlling Windows and Borders.
m42a
Both the "Allow the window manager to decorate the windows" and "Allow the window manager to control the windows" work when unchecked, but they cause ugly and out-of-place Windows-style titlebars to be drawn on top of the window and cause the osu! cursor to be offset from the actual mouse position. Emulating a virtual desktop and running osu! in fulscreen also works, but then I can't see the window title. Sinking the window is, IMO, the least bad option.
mekadon_old

m42a wrote:

Emulating a virtual desktop and running osu! in fulscreen also works, but then I can't see the window title. Sinking the window is, IMO, the least bad option.
What does sinking a window mean? I know it's a term used in xmonad, but I'm not sure how do they call it in DWM.
Maybe I'll try get osu! running on qemu, but I don't really want to install things I don't use often lol. Maybe I should just load an openbox session instead of DWM in ~/.xinitrc, but it's really a pain editing every time I want to play osu! (btw other games I tried that run on wine works fine)
m42a
I'm not sure how much this applies to dwm, but in xmonad, there are 2 types of windows: floating windows, and sunk windows. Floating windows can be moved around and resized using the mouse. Sunk windows are arranged by the window manager rather than the user. So if you sink osu!, when it tries to move the window manager says "No, you go over there" and the window stays in the same spot.

And when I say "virtual desktop" I don't mean something like qemu or virtualbox. In winecfg, there's an option under the Graphics tab to create a windows desktop to run the wine program on rather than letting it use your Linux desktop. This desktop acts like a window in your Linux desktop with Windows windows inside it. If you run osu! in fullscreen there's only 1 window, so it looks normal.
Katsuo_old_1
when i try to wine osume.exe i get this:

Unhandled Exception:
System.InvalidProgramException: Invalid IL code in #ryb.#syb:#Zqb (string[]): IL_0165: stloc.3


[ERROR] FATAL UNHANDLED EXCEPTION: System.InvalidProgramException: Invalid IL code in #ryb.#syb:#Zqb (string[]): IL_0165: stloc.3

can someone help me? I added repository, i also setup 32-bit prefix for wine, i have installed net framework 2.0... any ideas?
ukeluppi
can someone upload a video on how to install that I can not really
ukeluppi
can someone upload a video on how to install that I can not really
boat
If doing it manually seems too complicated (even though it really isn't), install playonlinux http://www.playonlinux.com/en/download.html and use this script to install osu! http://www.playonlinux.com/en/app-1856-osu.html

It's pretty much literally the same procedure, just that the script does it for you.
Espionage724

Katsuo wrote:

when i try to wine osume.exe i get this:

Unhandled Exception:
System.InvalidProgramException: Invalid IL code in #ryb.#syb:#Zqb (string[]): IL_0165: stloc.3


[ERROR] FATAL UNHANDLED EXCEPTION: System.InvalidProgramException: Invalid IL code in #ryb.#syb:#Zqb (string[]): IL_0165: stloc.3

can someone help me? I added repository, i also setup 32-bit prefix for wine, i have installed net framework 2.0... any ideas?
Hmm, that error particularly I believe occurs when dotnet20 wasn't installed properly. I might recommend trying it again.
ukeluppi
the specified location is not supported???? no found!!!! help meee please
ukeluppi

boat wrote:

If doing it manually seems too complicated (even though it really isn't), install playonlinux http://www.playonlinux.com/en/download.html and use this script to install osu! http://www.playonlinux.com/en/app-1856-osu.html

It's pretty much literally the same procedure, just that the script does it for you.

^the specified location is not supported^ no found! help me
Espionage724

ukeluppi wrote:

boat wrote:

If doing it manually seems too complicated (even though it really isn't), install playonlinux http://www.playonlinux.com/en/download.html and use this script to install osu! http://www.playonlinux.com/en/app-1856-osu.html

It's pretty much literally the same procedure, just that the script does it for you.

^the specified location is not supported^ no found! help me
Can you get the screenshot or quote of the exact problem?
ukeluppi
Espionage724
Hmm, I'm unsure about how to troubleshoot POL issues, but last time I checked, I believe the process was pretty smooth. Only thing I could suggest is to maybe start over from the beginning and remove the old osu! install.
bahamete
Okay, here are my general points of advice for running osu! in Arch Linux (I recently bought a new hard drive and had to do it all again)
1. Create a NEW, FRESH 32-bit wineprefix. ($ WINEARCH=win32 WINEPREFIX='~/.wine'; rm -rf ~/.wine; wine 'wineboot') or so
2. Install .NET 2.0 ($ winetricks dotnet20)
3. Install image libraries. (# pacman -S lib32-libpng lib32-giflib lib32-libjpeg-turbo)
4. Install graphics libraries. (# pacman -S lib32-mesa) but choose your graphics card of course ($ lspci | grep VGA)
4. Set proper audio output in Wine. ($ winecfg)

DO NOT run osu! with Mono though that seems counter-intuitive; it will immediately throw an InvalidProgram exception.
If you get pink sliders and backgrounds do not load, etc, you need the 32-bit image libraries mentioned above.
If you aren't using open-source driver for your graphics card, you probably should be, but it's your system so you know best.

These steps work for me. It is very finicky but once you get it, it should run absolutely fine. Good luck
ukeluppi

bahamete wrote:

Okay, here are my general points of advice for running osu! in Arch Linux (I recently bought a new hard drive and had to do it all again)
1. Create a NEW, FRESH 32-bit wineprefix. ($ WINEARCH=win32 WINEPREFIX='~/.wine'; rm -rf ~/.wine; wine 'wineboot') or so
2. Install .NET 2.0 ($ winetricks dotnet20)
3. Install image libraries. (# pacman -S lib32-libpng lib32-giflib lib32-libjpeg-turbo)
4. Install graphics libraries. (# pacman -S lib32-mesa) but choose your graphics card of course ($ lspci | grep VGA)
4. Set proper audio output in Wine. ($ winecfg)

DO NOT run osu! with Mono though that seems counter-intuitive; it will immediately throw an InvalidProgram exception.
If you get pink sliders and backgrounds do not load, etc, you need the 32-bit image libraries mentioned above.
If you aren't using open-source driver for your graphics card, you probably should be, but it's your system so you know best.

These steps work for me. It is very finicky but once you get it, it should run absolutely fine. Good luck
I really do not understand anything, you could upload a video tutorial
bahamete

ukeluppi wrote:

I really do not understand anything, you could upload a video tutorial
Maybe, if you don't understand what I said or don't want to research the stuff, Linux isn't really for you. :)
I would do a video tutorial but I think my explanation is good enough... I am getting a new laptop soon and I will try and install osu! on there, too. I will make note of everything I do from a fresh Arch install.

The 5 stuff in my post I wrote in brackets, you must type them in a terminal, but please research all the commands I posted so you don't do anything silly - in particular, 'rm -rf ~/.wine' will remove your entire Wine prefix.

For those Arch users, I realised there is an "osu!" package on the AUR (https://aur.archlinux.org/packages/osu/). I haven't tried it, yet.
mekadon_old

bahamete wrote:

For those Arch users, I realised there is an "osu!" package on the AUR (https://aur.archlinux.org/packages/osu/). I haven't tried it, yet.
judging at the pkgbuild it should be pretty much the same anyway. Also for convenience I just write a bash script that launches the game and dumped it into /usr/bin so that I can run it with dmenu
show more
Please sign in to reply.

New reply