https://bugs.winehq.org/show_bug.cgi?id=55500
Bug ID: 55500
Summary: Launching new processes in Virtual Desktops is slow
and stutters the system
Product: Wine
Version: 8.14
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: winex11.drv
Assignee: wine-bugs(a)winehq.org
Reporter: gabrielopcode(a)gmail.com
Distribution: ---
When in Virtual Desktop mode, launching any processes (even start.exe) causes a
short burst of high GPU usage, at least with NVIDIA drivers. This happens
because of vkGetRandROutputDisplayEXT, which seems to be very expensive, and
it's supposed to be done only once per wineserver launch, but that doesn't work
in Virtual Desktop mode because it always calls get_host_primary_monitor_rect
which ends up calling that function, even though it only needs the ID.
This actually can cause huge graphical stutters/lag of half a second when
launching processes in a Virtual Desktop.
--
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=55351
Bug ID: 55351
Summary: gdiplus:graphicspath - test_flatten2() fails on
Windows 7 - 11
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: gdiplus
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
gdiplus:graphicspath - test_flatten2() fails on Windows 7 - 11:
graphicspath.c:1270: Test failed: Expected 00000000, got 00000002
See https://test.winehq.org/data/patterns.html#gdiplus:graphicspath
The failure started on the day test_flatten2() was introduced with the commit
below:
commit 36c3a51d6abbdba4054e02c2a10b9fd38f8a3d5d
Author: Fabian Maurer <dark.shadow4(a)web.de>
AuthorDate: Mon Jul 24 17:23:44 2023 +0200
gdiplus: Prevent infinite loops due to floating point inaccuracy.
Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=52492
--
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=55341
Bug ID: 55341
Summary: Colin McRae Rally 2.0 since wine 8.4 shows just black
screen
Product: Wine
Version: 8.4
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: winex11.drv
Assignee: wine-bugs(a)winehq.org
Reporter: marcinzw(a)gmail.com
Distribution: ---
Before wine 8.4 the game worked flawlessly, but now even through all version up
to the wine 8.13 and latest git version shows only a black screen after intro.
I was hoping that the next versions will fix the problem (I stayed with wine
8.3 until now) but it doesn't happen. So I bisected and find the commit
46c8a637525d0f1cf67830295fb460c819b800b6 is the problem. Exactly just one
change in file dlls/winex11.drv/opengl.c in line 1405 (line number from latest
git repo)
+ win32u_set_window_pixel_format( hwnd, pixel_format_index( format ), FALSE)
- win32u_set_window_pixel_format( hwnd, pixel_format_index( format ),
internal );
This reverts one of the change made in this commit and fixes problem with a
black screen with latest git version as well. I hope this change (or similar
which resolve the problem) can be applied.
--
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=43822
Bug ID: 43822
Summary: No car song TrackMania nation forever (steam version)
Product: Wine
Version: 2.18
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: maxi.cass11(a)gmail.com
Distribution: ---
Created attachment 59369
--> https://bugs.winehq.org/attachment.cgi?id=59369
trackmania without car song
Hello I have problem with trackMania nation forever on steam.
I don't have the car song (all other song work)
http://store.steampowered.com/app/11020/TrackMania_Nations_Forever/
The car song work on the standalone installer
(trackmania 1 demo)
http://trackmaniaforever.com/nations/
I have tried to change openAL version or override this but it not correct the
problem.
--
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=55457
Bug ID: 55457
Summary: Robot Battle 1.4 crashes on startup after commit
08dc691d
Product: Wine
Version: 8.13
Hardware: x86-64
URL: https://web.archive.org/web/20130317061354/http://www.
robotbattle.com/download/latest.php
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: mshtml
Assignee: wine-bugs(a)winehq.org
Reporter: telans(a)posteo.de
CC: gabrielopcode(a)gmail.com
Regression SHA1: 08dc691dfb410de7115db3f9c34b225327e21f67
Distribution: ---
Created attachment 75018
--> https://bugs.winehq.org/attachment.cgi?id=75018
Backtrace Log
Robot Battle 1.4 crashes on startup. A bisect found commit 08dc691d ("mshtml:
Explicitly hold ref to the plugin host in NPP_New.") is the cause.
I've set the URL field here to a working link for the installer.
It looks like a NULL dereference at IOleClientSite_AddRef when
container->plugin_host is failed to be created.
A simple patch that fixes this for me is to check for err before attempting
IOleClientSite_AddRef.
--
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=55259
Bug ID: 55259
Summary: TranscendPang has corrupted graphics in-game
Product: Wine
Version: 8.11
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: minor
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: skorohodov4219(a)gmail.com
Distribution: ---
Created attachment 74874
--> https://bugs.winehq.org/attachment.cgi?id=74874
what is output if i launch the game from terminal
Download link:
http://cerebralmuddystream.nekokan.dyndns.info/TranscendPang/downloads.html
(the link at the top that says
FULL PACKAGE(ver1.10 2012/8/01)(およそ60MB))
OS: Manjaro Linux x86_64
Kernel: 6.1.38-1-MANJARO
CPU: Intel i5-2320 (4) @ 3.000GHz
GPU: NVIDIA GeForce GTX 550 Ti (using the proprietary driver)
Main menu looks fine, but when you start the game, parts of the background and
balls are 100% black, can't see much; parts of the background that do get shown
seem to be squished to the left.
--
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=55499
Bug ID: 55499
Summary: Arturia Software Lab 2.6.0: Window
Product: Wine
Version: 8.14
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: mistria(a)redhat.com
Distribution: ---
Created attachment 75062
--> https://bugs.winehq.org/attachment.cgi?id=75062
Console Log
Using wine-devel 8.14 from the winehq dnf repo, on Fedora 38, and trying to run
latest Arturia Software Center (2.6.0.2328), I see a window quickly showing up
and then closing immediately, and the application seems to hang in the terminal
doing nothing.
Log is attached.
--
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=54070
Bug ID: 54070
Summary: winevulkan Assertion failed
Product: Wine
Version: 7.22
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: winevulkan
Assignee: wine-bugs(a)winehq.org
Reporter: santafejayyt(a)gmail.com
Distribution: ---
Created attachment 73619
--> https://bugs.winehq.org/attachment.cgi?id=73619
Image of the error
I'm currently unable to run Roblox Studio at all on the latest wine-staging
version, with winevulkan erroring with "Assertion failed! File:
wine-staging/dlls/winevulkan/loader_thunks.c Line: 5156"
Expression: "!status"
I don't see an stderr or stdout log anywhere except for this error. I tested
both a custom wine-staging build, the AUR package wine-staging, as well as
compiled from source.
--
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=49161
Bug ID: 49161
Summary: Trying to run
GrapeJuice(https://gitlab.com/brinkervii/grapejuice)
Product: Wine
Version: unspecified
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: blakeablin(a)icloud.com
Distribution: ---
Created attachment 67180
--> https://bugs.winehq.org/attachment.cgi?id=67180
Error details
Trying to run Roblox via GrapeJuice give me the error I will attach.
--
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=54758
Bug ID: 54758
Summary: shell32:progman_dde - test_parser() sometimes gets
DMLERR_NOTPROCESSED in Wine
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: shell32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
shell32:progman_dde - test_parser() sometimes gets DMLERR_NOTPROCESSED in Wine:
progman_dde.c:274: Test failed: expected DMLERR_NO_ERROR, got 16393
progman_dde.c:275: Test failed: directory should not exist
See https://test.winehq.org/data/patterns.html#shell32:progman_dde
Where 16393 == DMLERR_NOTPROCESSED
The first known instance happened on 2023-03-02: this did not happen in the
previous 6 months. Since then there has been a bit over 1 instance per week so
it seems likely this is caused by a commit in late February:
* 2023-03-02 on debian11-win32-ar-MA
* 2023-03-03 on fgtb-debian11-win32
* 2023-03-10 in MR!2368 on debian11-win32
* 2023-03-22 in MR!2466 in the test-linux32 GitLab CI
* 2023-03-28 in MR!2526 on debian11-win32
--
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=55417
Bug ID: 55417
Summary: user32:msg - test_showwindow() sometimes fails due to
an unexpected WM_SYNCPAINT message on Windows 10
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: user32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
user32:msg - test_showwindow() sometimes fails due to an unexpected
WM_SYNCPAINT message on Windows 10:
msg.c:5016: Test failed: ShowWindow(SW_SHOWNA) on visible top level window: 0:
the msg 0x0018 was expected, but got msg 0x0088 instead
msg.c:5016: Test failed: ShowWindow(SW_SHOWNA) on visible top level window: 1:
the msg 0x0046 was expected, but got msg 0x0018 instead
msg.c:5016: Test failed: ShowWindow(SW_SHOWNA) on visible top level window: 6:
the msg sequence is not complete: expected 0000 - actual 0046
See https://test.winehq.org/data/patterns.html#user32:msg
Where: 0x18 == WM_SHOWWINDOW
0x46 == WM_WINDOWPOSCHANGING
0x88 == WM_SYNCPAINT
Maybe the WM_SYNCPAINT should just be added as optional.
This only happened 4 times in the past 8 months:
* 2022-12-09 win21H1_newtb-w10pro64-zh-CN-64
* 2023-03-27 win21H1_newtb-w10pro64-ko-64
* 2023-06-09 win21H1_newtb-w10pro64-ja-64
* 2023-08-04 win21H1_newtb-w10pro64-ja-64
--
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=53505
Bug ID: 53505
Summary: d3d9:visual - test_vshader_input() sometimes fails on
Windows <= 10 1607
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: d3d
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
d3d9:visual - test_vshader_input() sometimes fails on Windows <= 10 1607:
visual.c:8907: Test failed: Input test: Quad 3(2crd-wrongidx) returned color
0x00ff00ff, expected 0x00ff0080
https://test.winehq.org/data/patterns.html#d3d9:visual
This happens on Windows 8, Windows 10 1507 and 1607 but is rare enough (~7%) to
sometimes cause false positives.
--
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=53385
Bug ID: 53385
Summary: Vulkan was running really fine, before MESA/Xorg
Update last month, current version crashes
Product: vkd3d
Version: 1.4
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: vkd3d
Assignee: wine-bugs(a)winehq.org
Reporter: juergen.sauer(a)automatix.de
Distribution: ---
I was using dxvk-bin in Arch Linux.
[jojo@pc7 wotlk]$ cd /usr/share/dxvk/
[jojo@pc7 dxvk]$ ./setup_dxvk.sh install
This worked over years like a charm, rocksteady.
Since a month ago, I got:
[jojo@pc7 wotlk]$ wine Wow.exe
..
info: Game: Wow.exe
info: DXVK: v1.10.2
info: Built-in extension providers:
info: Win32 WSI
info: OpenVR
info: OpenXR
info: OpenVR: could not open registry key, status 2
info: OpenVR: Failed to locate module
info: Enabled instance extensions:
info: VK_KHR_get_surface_capabilities2
info: VK_KHR_surface
info: VK_KHR_win32_surface
terminate called after throwing an instance of 'dxvk::DxvkError'
abnormal program termination
wine-7.13 (Staging)
...
uninstalling dxvk-bin -> game works again,
but it runs sometimes in Wow Errors accordinf the OpenGL Stack.
You can reproduce on Arch Linux, current update, wine-staging, running Wow
WoW_3.3.5a_rising-gods.de. Client avaible via rising-gods.de
--
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=55131
Bug ID: 55131
Summary: Celeste FNA x86 Windows Game does not work on WOW64
Product: Wine
Version: 8.11
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: dofficialgman(a)gmail.com
Distribution: ---
Created attachment 74684
--> https://bugs.winehq.org/attachment.cgi?id=74684
backtrace when trying to boot the game
Specifically testing the FNA build of Celeste available on Itch.io but it is
available on other platforms as well https://mattmakesgames.itch.io/celeste
The game does not run on WOW64 (tested on Wine-8.10 and Wine-8.11) builds but
runs fine on the standard Wine-8.10 multiarch (32bit and 64bit linux
userspace).
A backtrace when trying to launch the game is attached.
--
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=54414
Bug ID: 54414
Summary: Window content corrupted after using scrollbars
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: maranbr(a)outlook.com
Distribution: ---
Created attachment 73975
--> https://bugs.winehq.org/attachment.cgi?id=73975
Window content after scroll
The window content gets completely corrupted after use scroll bars.
Tested on versions 4.x, 5.x, 6.x, 7.x and the last one available, the 8.0.
--
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=54785
Bug ID: 54785
Summary: ole32:compobj - test_CoWaitForMultipleHandles()
sometimes does not receive WM_USER on Windows
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: ole32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
ole32:compobj - test_CoWaitForMultipleHandles() sometimes does not receive
WM_USER on Windows. There are two places where this can happen:
compobj.c:2999: Test failed: expected message 1024, received none
and
compobj.c:3034: Test failed: expected message 1024, received none
See https://test.winehq.org/data/patterns.html#ole32:compobj
This failure impacts all Windows version but still only happens once every
other month on average:
* 2022-12-09 on fgtb-w10pro64-rx550-64
* 2023-01-24 on fgtb-w10pro64-rx550-64
* 2023-03-10 on w7u-pt-PT
* 2023-04-04 on w7u-de
* 2022-08-28 on w1064-tsign-32
This is a slightly different case because compobj received an unexpected
WM_DEVICECHANGE message instead of no message:
compobj.c:3000: Test failed: unexpected message 537
compobj.c:3034: Test failed: expected message 1024, received 537
compobj.c:3035: Test failed: unexpected message 1024
--
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.
http://bugs.winehq.org/show_bug.cgi?id=35336
Bug ID: 35336
Summary: HoMM 3: Horn of the Abyss launcher freezes on the game
update (Mono issue)
Product: Wine
Version: 1.7.10
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: minor
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: winebugs140(a)gmail.com
Classification: Unclassified
How to reproduce: open HotA_launcher.exe and then click on Update HotA. If you
try to cancel the update or there will be no updates available, the application
freezes.
With 'winetricks dotnet30' the launcher works fine, so it looks like a problem
with Mono.
You DON'T NEED Heroes of Might & Magic 3 to test this, you can open the
launcher of this unofficial expansion without downloading the original game.
There is nothing in the logs.
TESTED ON:
Ubuntu 13.04 and Mac OS X 10.9 Mavericks
--
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=54143
Bug ID: 54143
Summary: Chessbase 11 arrows draw too large
Product: Wine
Version: 8.0-rc1
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: gdiplus
Assignee: wine-bugs(a)winehq.org
Reporter: dav75uk(a)yahoo.co.uk
Distribution: ---
Created attachment 73675
--> https://bugs.winehq.org/attachment.cgi?id=73675
Picture of arrow on wine8.0-rc1
When arrows are drawn using Chessbase 11, they are too big. See attached
screenshot and log.
Compare with:
https://www.youtube.com/watch?v=xvJd97ZnHAk
At 4:58 an arrow is showing from g8 to f6 pointing to a knight that has just
moved. I've also set up this arrow on chessbase 11 with wine 8.0-rc1. Note
later chessbase draws arrows slightly different, so software like CBReader14
doesn't appear to be affecting by this issue.
On wine 8.0-rc1 in CB 11 the stem of the arrow looks approx in the right place.
It crosses f7/g7 (the squares occupied by pawns) at the right point. The tip of
the arrow is in the right place on the knight between the white on the mane and
the chin. On wine 7.22 the endcap square (some default catch in a switch
statement maybe) is being drawn which is not on native chessbase (thus the
arrow isn't meant to hide it). Finally the back of the arrow head is in the
wrong place (some scaling maybe?) which is making it too large. On wine 7.22
the back of the arrow is drawn from the right shoulder of the pawn on f7 (the
one nearest the king) to near (left of) the base of the one on g7. In the video
the arrow appears from under the base of the f7 pawn (almost but not quite
lined up horizontally the bishop on f8's cross right hand edge) to just inside
the corner of the square the knight is on.
--
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=51890
Bug ID: 51890
Summary: A lot more old games would be so much more usable if
wine's virtual desktop had proper resizing
Product: Wine-staging
Version: 6.18
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: enhancement
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: el(a)horse64.org
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ---
I have a really significant amount of older games around, none of which will
launch on this machine without wine's virtual desktop feature because on a
widescreen monitor, they determine there is no "expected" fullscreen resolution
available and crash.
Now I'd just use the virtual desktop, except it feels archaic and not very
usable: why is it that for a 800x600 game on a 800x600 virtual desktop, I can't
just maximize the virtual desktop window and get the virtual desktop SCALED UP
with proper letterboxing so I can play in some other way than a tiny window
with zero immersion and everything so small I can barely see it? Funnily enough
I can even resize the virtual desktop window except the resizing is fully
ignored and I just get black void with no scaling up all around with the game
stuck in the top-left, and the maximizing is blocked.
Scaling up (with automatic letterboxing), maximizing would seem like such
obvious features to make virtual desktop gaming infinitely less clumsy and
weird that I am a bit surprised it's not in there yet. Can it please be added??
--
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=55006
Bug ID: 55006
Summary: vbscript single line if else without else body fails
compilation
Product: Wine
Version: unspecified
Hardware: aarch64
OS: Mac OS X
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: vbscript
Assignee: wine-bugs(a)winehq.org
Reporter: francisdb(a)gmail.com
This is valid vbs when run with `cscript`
```
If x = 1 Then DoSomething() Else
```
wine vbscript fails with: "Compile error: Line: #, Character: #, Description
unavailable"
Workaround is changing the code to
```
If x = 1 Then DoSomething() Else:
```
or
```
If x = 1 Then DoSomething()
```
--
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=55496
Bug ID: 55496
Summary: World of Warships (12.7 update) - Graphical glitch -
Water texture and effects at wrong sea level.
Product: Wine
Version: 8.11
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: o.dierick(a)piezo-forte.be
Distribution: ---
Created attachment 75058
--> https://bugs.winehq.org/attachment.cgi?id=75058
Screenshots with glitch highlighted in red.
Hello,
Since the game update to 12.7, water textures and effects are rendered below
the sea level.
All objects are rendered at the same 'sea' level and the physics are respected,
but the water texture and effects are drawn below the sea surface, as if it was
painted at the bottom of a perfectly transparent sea, instead of the top.
I'm joining screenshots that show the issue. The glitches are highlighted with
red arrows.
On the first screenshot, the splash of the water drains are visibly shifted
below the ship in the port.
On the second screenshot, the space between the island in the distance and the
water texture below them is visible. Water trails from moving ships are shifted
below them.
On the third screenshot, the water trail from the player ship is shifted, as
are the splashes from artillery shells.
The fourth screenshot shows more shifted water trails and shells splashes, from
a dead player's observation camera (higher in the sky).
The height of the glitch is proportional to the distance of the camera zoom.
The farthest the camera is of the ship, the lower the water texture is drawn.
When the camera is zoomed to the closest, the water texture and effects are
nearly perfectly placed (it's still shifted by a small amount).
The glitch is easier to see when turning the camera around, as the water
texture doesn't match the ship position (because of perspective). The water
trails and splash effects do match the water texture position, but not their
respective objects. Objects matches their relative positions.
Note that on the screenshots, the horizon curve to the edge is magnified by my
ultra-wide resolution. Don't worry about the calculator on the first
screenshot. I had trouble getting a non-transparent screenshot of the Wine
full-screen window. After that capture, I found another way that didn't require
a non-full-screen window to be active.
Regards.
--
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=53371
Bug ID: 53371
Summary: 0024:fixme:ntdll:create_logical_proc_info stub
Product: Wine
Version: 7.12
Hardware: x86-64
OS: FreeBSD
Status: UNCONFIRMED
Severity: blocker
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: yklaxds(a)gmail.com
Created attachment 72755
--> https://bugs.winehq.org/attachment.cgi?id=72755
log
FreeBSD 13.1 release amd64
KDE plasma 5
emulators/wine-devel 7.12 not work at all.
--
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=55495
Bug ID: 55495
Summary: ntdll:threadpool - test_tp_wait() sometimes gets an
unexpected timeout in Wine
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: ntdll
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
ntdll:threadpool - test_tp_wait() sometimes gets an unexpected timeout in Wine:
threadpool.c:1715: Test failed: WaitForSingleObject returned 258
threadpool.c:1720: Test failed: expected info.userdata = 0, got 65536
threadpool.c:1729: Test failed: WaitForSingleObject returned 0
See See https://test.winehq.org/data/patterns.html#ntdll:threadpool
1715 & 1720: The timeout can also happen on Windows 8 and in that case the test
expects info.userdata to still be zero. But in Wine info.userdata still gets
set despite the timeout so the test fails. A hacky fix would be to expect the
correct behavior if (!broken(result == WAIT_TIMEOUT)) but it would be much
better to fix Wine's implementation.
Then the next WaitForSingleObject() does not time out which sounds a bit
similar to bug 55493.
The oldest known instance happened at the start of May and this seems to mostly
happen on the GitLab CI:
* 2023-07-28 MR!3441 (only the last two failures?)
* 2023-06-01 MR!2951 (only the last two failures?)
* 2023-05-31 fg-deb64-t32
* 2023-05-24 gitlab-debian-32
* 2023-05-02 MR!2734
--
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=55493
Bug ID: 55493
Summary: ntdll:threadpool - test_tp_timer() sometimes fails in
Wine
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: ntdll
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
ntdll:threadpool - test_tp_timer() sometimes fails in Wine:
threadpool.c:1439: Test failed: WaitForSingleObject returned 0
threadpool.c:1441: Test failed: WaitForSingleObject returned 258
See https://test.winehq.org/data/patterns.html#ntdll:threadpool
So instead of getting a timeout then a success, the test first gets an
unexpected WaitForSingleObject() success and then a timeout. That means it's
not a simple issue of the test running too slow.
There are only three known instances so far:
* 2023-08-23 MR!3621
* 2023-07-03 MR!3218
* 2023-06-09 fg-deb64-t32
--
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.