https://bugs.winehq.org/show_bug.cgi?id=46753
Bug ID: 46753
Summary: osu! icon has black borders around
Product: Wine
Version: 4.2
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: minor
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: angelito.13.pintos(a)gmail.com
Distribution: ---
Hi! i have see some issues in the videogame osu!. When the game is starting the
logo has black borders around, and when you're in the game some configurations
are completely in black. It's not an important problem, but is annoying anyway.
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=44184
Bug ID: 44184
Summary: osu!: installer stuck in a loop
Product: Wine
Version: 3.0-rc1
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: reduxpl(a)gmail.com
Distribution: ---
Created attachment 59947
--> https://bugs.winehq.org/attachment.cgi?id=59947
Terminal output; I let the installer restart 3 times, then I proceeded to close
it.
When attempting to install osu! using Wine, the installation process seems to
look fine at a first glance, but after it reaches 100% and the installer shuts
down, the loop begins - the installer starts again, progress meter goes from 0%
to 100% in a few seconds, then it closes, rinse and repeat. The game never
starts.
The installer runs properly on Windows. Additionally, the issue can be worked
around by copying the already installed game files from Windows to Linux - then
the game also starts and runs properly.
Download link: http://m1.ppy.sh/r/osu!install.exe
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=48727
Bug ID: 48727
Summary: osu!lazer 2020.306.0 crashes on install
Product: Wine
Version: 5.3
Hardware: x86
URL: https://github.com/ppy/osu
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: huupoke12(a)gmail.com
Distribution: ---
Created attachment 66603
--> https://bugs.winehq.org/attachment.cgi?id=66603
Terminal log
Reproduce step:
1. Download osu!lazer 2020.306.0 at:
https://github.com/ppy/osu/releases/download/2020.306.0/install.exe
2. Run it with wine
3. It crashes
The install executable is a 64-bit program.
sha256sum install.exe
6880eb9f707c32c57a8d0e90700d23432e97aa84c0399ceb8a2a83ffecb2b4b3 install.exe
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=42856
Bug ID: 42856
Summary: osu! - high sound latency with winepulse compared to
winealsa
Product: Wine
Version: 2.6
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: directx-dsound
Assignee: wine-bugs(a)winehq.org
Reporter: yalterz(a)gmail.com
Distribution: ---
I'm trying to set up PulseAudio to achieve the same low audio latency as I'm
getting with just ALSA. Looks like I managed to achieve this, but not as I
would expect.
Currently my setup is: PulseAudio with default configuration, along with
pulseaudio-alsa integration which basically forwards all ALSA-using programs
straight to Pulse. I am using patched winealsa.drv for reduced latency
(changing three constants at the top of mmdevdrv.c — DefaultPeriod,
MinimumPeriod, EXTRA_SAFE_RT — to lower values, the ones that work for me:
20000, 20000, 11000 respectively). I applied a very similar patch to
winepulse.drv.
When running osu! through ALSA (sound=alsa), which effectively runs it through
ALSA->PulseAudio->ALSA device, the audio latency is almost non-existant —
similar if not the same as what I was getting with just ALSA.
When running osu! through PulseAudio (sound=pulse), effectively
PulseAudio->ALSA device, the audio latency is noticeably higher (at least 20ms
higher), even though it practically removes one extra step from the audio
"chain".
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=43769
Bug ID: 43769
Summary: Regression, osu!.exe freezes a few seconds after you
start it, probably a critical zone inter thread
deadlock
Product: Wine-staging
Version: 2.17
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: critical
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: matthias291999(a)gmail.com
CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de,
sebastian(a)fds-team.de
Distribution: ---
wine-staging 2.17
causes my game called "osu!" to enter deadlock shortly after the audio starts
playing.
Works fine in wine-staging 2.16
Someone do a git blame on the audio system, could be it, don't know, all i know
is that it works fine in wine-staging 2.16. If you have any tests that may give
you more info, go ahead.
I can not get out of borderless fullscreen, dont know why, dont care to report
a 2'nd bug, as it works fine, and i can deal with it.
I have CSMT enabled. If i have to disable CSMT, that is just a temporary fix, I
am not at all satisfied if you seguest i disable it, go test it yourself, if
you can actually reproduce my bug with CSMT enabled, go ahead and prove i could
run it wo CSMT enabled with a video recording...
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=48360
Bug ID: 48360
Summary: osu: .NET framework IndexOutOfRangeException crash
Product: Wine
Version: 4.16
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: ntdll
Assignee: wine-bugs(a)winehq.org
Reporter: bugs.winehq(a)webfreak.org
CC: julliard(a)winehq.org
Regression SHA1: df3fad6383e79d1485413ad549c55240843d2418
Distribution: ArchLinux
Created attachment 66104
--> https://bugs.winehq.org/attachment.cgi?id=66104
crash log occuring with wine 4.16
since wine 4.16 the game "osu!" started crashing often. For more
application-specific context see the bug report there for more details:
https://github.com/ppy/osu-stable-issues/issues/284
It seems that on Windows no such issue is present and prior to wine 4.15 this
bug was not present. It seems to be an issue somewhere with array indexing on
.NET inside some rendering function. This crash occurs when starting the game
"osu!" and then moving the mouse cursor relatively quickly (causing longer
lines to be rendered)
The issue in wine seems to be that the behavior of the page faults has changed
in df3fad6383e79d1485413ad549c55240843d2418 so that now it started to throw
array index exceptions which don't happen on Windows.
I have attached the full application log with ntdll warn log up with the crash
with Wine 4.16 (precompiled from ArchLinux archives)
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=45402
Bug ID: 45402
Summary: Sniper Elite V2 benchmark tool: white texture glitch
Product: Wine
Version: 3.11
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: trivial
Priority: P2
Component: directx-d3d
Assignee: wine-bugs(a)winehq.org
Reporter: moihack.inside(a)gmail.com
Distribution: ArchLinux
Created attachment 61715
--> https://bugs.winehq.org/attachment.cgi?id=61715
Sniper Elite V2 benchmark tool - white textures glitch
You can download the free benchmark tool from here:
http://www.guru3d.com/files-details/sniper-elite-v2-benchmark-tool.html
The benchmark installs, runs and exits fine under wine.
Yet, there are some white "glitched" textures here and there while the camera
flies in the scene (see attached screenshoot).
Here is how a normal run should look:
https://www.youtube.com/watch?v=WNs3mnKAdRQ (without the glitched textures)
System: Arch Linux fully updated with wine-3.11 and Radeon HD6870 GPU.
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=43637
Bug ID: 43637
Summary: Fallout New Vegas: Crash on launch using 64-bit prefix
Product: Wine
Version: 2.15
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: iamtimscampi(a)gmail.com
Distribution: ---
Upon launching Fallout New Vegas (With or without New Vegas Script Extender) on
a 64-bit prefix, the game crashes after the initial splash screen.
On a 32-bit prefix, the game works as intended, without a crash.
This was tested both with Staging and regular versions of Wine, with and
without the "New Vegas Script Extender" addon.
While not necessary to play the game, a 64bit prefix is necessary for the new
version of Mod Organizer, a third party utility for the game that handles mod
loading. This crash prevents users from using the latest version of it
alongside the game.
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=38381
Bug ID: 38381
Summary: Fallout New Vegas (Steam Version) Crashes at Startup
on the Splash Screen
Product: Wine
Version: 1.7.40
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: gordan(a)bobich.net
Distribution: ---
Created attachment 51228
--> https://bugs.winehq.org/attachment.cgi?id=51228
Fallout New Vegas Crash Backtrace
Fallout New Vegas (Steam Version) Crashes at Startup on the Splash Screen.
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=49051
Bug ID: 49051
Summary: Got "rawinput:RegisterRawInputDevices Unhandled flags
0x230 for device 0" in Fallout3 and NV
Product: Wine-staging
Version: 5.7
Hardware: x86-64
OS: Mac OS X
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: avenjames(a)live.com
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
As title description I got this problem since I updated version after 5.0
stable, from 5.1 to 5.7 stable/staging/dev, the game's cursor could hardly move
and unhandled at all.
I tested version 5.7 staging as usually as I did once notice the update's
coming, but this time I got messages:
0061:fixme:rawinput:RegisterRawInputDevices Unhandled flags 0x230 for device 0.
0061:fixme:rawinput:RegisterRawInputDevices Unhandled flags 0x230 for device 0.
0061:fixme:rawinput:RegisterRawInputDevices Unhandled flags 0x230 for device 0.
0061:fixme:rawinput:RegisterRawInputDevices Unhandled flags 0x230 for device 0.
I think it must be related to the problem that I have, any idea friends?
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.