another thing you could try is installing gdiplus with winetricks like you did with dotnet
SanteriP wrote:
Yeah I'm using proprietary drivers. Tried installing gdiplus, didn't do anything in this case.
Here's what comes up in xterm when I launch osu!.exe (since osu!install.exe disappears and gets replaced with osu!.exe when you launch it): http://pastebin.com/49XGPRpV
Not sure how it could help, but in the possible case it could, I decided to pastebin it.
err:wincodecs:PngDecoder_CreateInstance Failed reading PNG because unable to find libpng12.so.0
yaourt -Sy lib32-libpng libpng
from some googling it seems that libpng is a common problem in arch... not sure why.SanteriP wrote:
Reinstalling libpng did not fix the issue and it doesn't seem like the installer is actually installing or downloading anything. Instead the progress bar is just flashing and nothing is happening...
sudo ln /usr/lib/libpng16.so /usr/lib/libpng12.so.0
sudo ln /usr/lib32/libpng16.so /usr/lib32/libpng12.so.0
fixme:ras:RasEnumConnectionsW (0x1d8c90,0xf6cde30,0xf6cde34),stub!
fixme:ras:RasEnumConnectionsW RAS support is not implemented! Configure program to use LAN connection/winsock instead!
err:winsock:WSAIoctl -> _WSAIO(IOC_WS2, 23) request failed with status 0x2733
err:winsock:WSAIoctl -> _WSAIO(IOC_WS2, 23) request failed with status 0x2733
fixme:ras:RasConnectionNotificationW (0xffffffff,0x388,0x00000003),stub!
fixme:winhttp:get_system_proxy_autoconfig_url no support on this platform
fixme:winhttp:WinHttpDetectAutoProxyConfigUrl discovery via DHCP not supported
err:winsock:WSAIoctl -> _WSAIO(IOC_WS2, 23) request failed with status 0x2733
err:winsock:WSAIoctl -> _WSAIO(IOC_WS2, 23) request failed with status 0x2733
err:winediag:schan_imp_init Failed to load libgnutls, secure connections will not be available.
Nevermind, I'm retarded. Installing gdiplus solved my crashing problem and it works fine now.arihosu wrote:
Yeah I've been having the same issue for a few weeks now. Different wine versions (and .net combinations) yield different results, sometimes the launcher graphics are glitched (red X's), sometimes they show fine, but in all cases it always crashes before launching the game. Furthest I got was wine 2.2 with only dotnet4 installed, which would launch the game and you'd hear the sound effect from hovering menu icons, but crashes 1 second later anyway.
Maybe a recent osu update broke wine compatibility?
ppy pls, osu!next when
------------------------------------------------------
Setting windows version so installer works
------------------------------------------------------
Setting Windows version to win2k
Executing winetricks_early_wine regedit /S C:\windows\Temp\_dotnet20sp1\set-winver.reg
WINEPREFIX=~/osu-wine WINEARCH=win32 winetricks -q dotnet45 cjkfonts
I've had this issue on latest wine but not 1.8.3, hmmm make sure winetricks is up to date, try deleting and recreating the wine prefix, try messing with the windows version on winecfg. could also try installing without -q and clicking the installer stuff manually.Dozy Van wrote:
Hi I have been scracting my head over this issue for 2 days now.
I keep getting this problem:------------------------------------------------------
Setting windows version so installer works
------------------------------------------------------
Setting Windows version to win2k
Executing winetricks_early_wine regedit /S C:\windows\Temp\_dotnet20sp1\set-winver.reg
No matter how long I leave it, it won't go passed that point
Its when I do this:WINEPREFIX=~/osu-wine WINEARCH=win32 winetricks -q dotnet45 cjkfonts
I get the same error when I try to install Osu! from the Arch AUR witch I think is just a packaged version of your guide.
input lag is a common issue with the ctl-490, it's caused by the tablet. I heard taping the nib so it's always pressed fixes it.ichinose-san wrote:
This may be unrelated, but I've just went through the whole thing and I noticed quite a bit of latency with my Wacom CTL-490, I looked around but I can't seem to find where this comes from. Do you have an idea?
Also , thanks a lot for this guide!
One last thing, do you know why no images are showing in the UI? They are transparent, and for buttons I can't even click them
huh, really weird. you could try installing gdiplus from winetricks, but that will probably break cjk fonts.ichinose-san wrote:
Input lag with the ctl490 on Windows is caused by the drivers when hovering
Linux drivers don't have this problem, lag occurs regardless of drag or hover, less so than on Windows, but since there's no workaround like holding the nib, it's quite annoying
As for UI, profile picture, music controls and leftside icons in settings are not showing. I ran it from the terminal and there was no particular issue.. weird :/
winetricks sound=alsa
YaLTeR wrote:
Hey, just wanted to throw my two cents on the audio latency.
I'm on Arch Linux x64, using the latest wine (2.7 at the time of writing). I switched from a pure ALSA setup I had previously, all tweaked to lowest osu! latency, to PulseAudio, with the same non-existant audio latency. The trick was to force wine to use winealsa.drv:winetricks sound=alsa
This way, even though the audio is going through alsa->pulseaudio->alsa as opposed to pulseaudio->alsa, the latency is much better (I submitted a bug report into wine about that). The PulseAudio settings are all set to default (none of the tsched=0 stuff, that actually made it worse). And don't forget to do the winealsa.drv patch as described in the OP.
ichinose-san wrote:
Input lag with the ctl490 on Windows is caused by the drivers when hovering
Linux drivers don't have this problem, lag occurs regardless of drag or hover, less so than on Windows, but since there's no workaround like holding the nib, it's quite annoying
As for UI, profile picture, music controls and leftside icons in settings are not showing. I ran it from the terminal and there was no particular issue.. weird :/
Just tested this and it does indeed work! major props to you, will update the guide to use latest wine eventuallyYaLTeR wrote:
Hey, just wanted to throw my two cents on the audio latency.
I'm on Arch Linux x64, using the latest wine (2.7 at the time of writing). I switched from a pure ALSA setup I had previously, all tweaked to lowest osu! latency, to PulseAudio, with the same non-existant audio latency. The trick was to force wine to use winealsa.drv:winetricks sound=alsaThis way, even though the audio is going through alsa->pulseaudio->alsa as opposed to pulseaudio->alsa, the latency is much better (I submitted a bug report into wine about that). The PulseAudio settings are all set to default (none of the tsched=0 stuff, that actually made it worse). And don't forget to do the winealsa.drv patch as described in the OP.
you can either approximate it by counting pixels and then converting to coordinates ((x / pixelwidth) * maxareawidth, (y / pixelheight) * maxareaheight) or try to export the tablet preferences to a file and see if you can find them in it with a text editor or something. or just start from scratch and tweak your area until it feels right. unfortunately that's wacom's fault for not showing values in older driversIcePixel_ wrote:
I don't know how the get my coordinates with my Wacom One the Driver doesn't show any coordinates can someone help me? And i use forced proportions.
latest wine yes plsFranc[e]sco wrote:
Just tested this and it does indeed work! major props to you, will update the guide to use latest wine eventuallyYaLTeR wrote:
Hey, just wanted to throw my two cents on the audio latency.
I'm on Arch Linux x64, using the latest wine (2.7 at the time of writing). I switched from a pure ALSA setup I had previously, all tweaked to lowest osu! latency, to PulseAudio, with the same non-existant audio latency. The trick was to force wine to use winealsa.drv:winetricks sound=alsaThis way, even though the audio is going through alsa->pulseaudio->alsa as opposed to pulseaudio->alsa, the latency is much better (I submitted a bug report into wine about that). The PulseAudio settings are all set to default (none of the tsched=0 stuff, that actually made it worse). And don't forget to do the winealsa.drv patch as described in the OP.
$ virsh -c lxc:/// net-start defaultAnd also I tried restarting the libvirtd service as I found in another forum post and I get this:
error: Failed to start network default
error: direct firewall backend requested, but /sbin/ebtables is not available: No such file or directory
$ systemctl status libvirtd
Failed to get D-Bus connection: Unknown error -1
$ systemctl start libvirtd
Failed to get D-Bus connection: Unknown error -1
libGL error: unable to load driver: i965_dri.so
libGL error: driver pointer missing
libGL error: failed to load driver: i965
libGL error: unable to load driver: swrast_dri.so
libGL error: failed to load driver: swrast
X Error of failed request: BadValue (integer parameter out of range for operation)
Major opcode of failed request: 155 (GLX)
Minor opcode of failed request: 3 (X_GLXCreateContext)
Value in failed request: 0x0
Serial number of failed request: 346
Current serial number in output stream: 350
glxCreateContext is failing, which seems to indicate that your acceleration isn't working. could be broken gpu driversLux wrote:
Hey I'm trying to get osu up and running on MX Linux 16.1, following the Debian based guide to build Wine from source. I installed all the packages fine and added the deb-src lines to the list files, but I'm having trouble in the next step.$ virsh -c lxc:/// net-start defaultAnd also I tried restarting the libvirtd service as I found in another forum post and I get this:
error: Failed to start network default
error: direct firewall backend requested, but /sbin/ebtables is not available: No such file or directory$ systemctl status libvirtd
Failed to get D-Bus connection: Unknown error -1
$ systemctl start libvirtd
Failed to get D-Bus connection: Unknown error -1
Anyways, I tried the guide using PlayOnLinux and that didn't work either, osu! would "install" but then when I run it the icon appears and then nothing shows up afterwards. Lots of stuff shows up in the POL Shell end of which is:libGL error: unable to load driver: i965_dri.so
libGL error: driver pointer missing
libGL error: failed to load driver: i965
libGL error: unable to load driver: swrast_dri.so
libGL error: failed to load driver: swrast
X Error of failed request: BadValue (integer parameter out of range for operation)
Major opcode of failed request: 155 (GLX)
Minor opcode of failed request: 3 (X_GLXCreateContext)
Value in failed request: 0x0
Serial number of failed request: 346
Current serial number in output stream: 350
Any thoughts?
defaults.ctl.card 1
pcm.!default {
type plug
slave.pcm "dmixer"
}
pcm.dmixer {
type dmix
ipc_key 1024
slave {
pcm "hw:1,0"
period_size 32
buffer_size 512
}
}
maybe you set it to the wrong driver, check what it uses by default when it works from the xorg logtleydxdy wrote:
the "More tweaks to get rid of vsync" part causes my arch to login loop. but I'm using a Radeon HD graphic so maybe it doesn't matter.
as the error says, you need to find packages that have development headers for X for your distro. on mint it should be something like libx11-dev and xserver-xorg-devsselecaf wrote:
edit : followed all your tutorial to the point where i have to put this command : ../configure --prefix=/home/loli/wine-1.8.3
i get this :
configure: error: X development files not found. Wine will be built
without X support, which probably isn't what you want. You will need
to install development packages of Xlib/Xfree86 at the very least.
Use the --without-x option if you really want this.
what can i do from there ?
re:edit
I also tried to install osu via playonlinux i'm on mint*
i get to the point where we have to open a shell into POL and he show me the message "Ce script doit être executé dans Playonlinux" in english "This script has to be executed in POL" and anything i type is ignored when i press enter the shell just close
so i tried to open a shell into the POL folder to create a osu folder and install it in it
but i cant do the "winetricks -q dotnet45 cjkfonts" so osu say me that he hasn't .NET 4.5
20ms is acceptable if you use local offset everywhereLux wrote:
After I checked the Open GL hardware acceleration setting with glxinfo it just worked when I started it...
So I got it working on just Intel graphics with MX Linux 16.1 using the PlayOnLinux guide. The input latency is good but I can't really figure out the audio latency (but that's really my problem) it's just off by like 20-30 ms I think. The only minor inconvenience is that my tablet area resets each time I disconnect/reconnect it.
Anyways, thanks for the guide/help!
sudo apt-get install libx11-dev xserver-xorg-dev libx11-dev:i386 libfreetype6-dev:i386
WINEPREFIX=~/osu-wine WINEARCH=win32 ~/wine-1.8.3/bin/wineboot
bash: /home/gerard/wine-1.8.3/bin/wineboot: Aucun fichier ou dossier de ce type
run steam with "vblank_mode=0 steam" to unlock fpssselecaf wrote:
Ok so if someone has the same error that i had you have to install all theses librariessudo apt-get install libx11-dev xserver-xorg-dev libx11-dev:i386 libfreetype6-dev:i386
and for Playonlinux the error that i had didnt showed on my laptop who use ubuntu 16.04
edit : i see you know it reading last post x')
another thing that you can add to your tutorial is mc osu who's a good solution if any of your way to get osu installed dont work
it can be installed with steam
the only problem with it is that he limit the amount of fps at 60 (on my computer)
ty for your response Franc[e]sco i'll come back if i find another problem haha
compilation failed or you compiled wine to the wrong folder, double check the path you specified in configure and make outputsselecaf wrote:
WINEPREFIX=~/osu-wine WINEARCH=win32 ~/wine-1.8.3/bin/wineboot
bash: /home/gerard/wine-1.8.3/bin/wineboot: Aucun fichier ou dossier de ce type
i checked into the folder and i dont find "wine-1.8.3" like the shell what could i do wrong?
maybe it's wine-git instead ? but he give me the same answer when i replace "wine-1.8.3" by "wine-git"
err:ole:marshal_object Failed to create an IRpcStubBuffer from IPSFactory for {659cdeac-489e-11d9-a9cd-000d56965251} with error 0x80004002please advise.. what should I do?