https://bugs.winehq.org/show_bug.cgi?id=43133
Bug ID: 43133
Summary: The Witcher 3: ambient occlusion distortions
Product: Wine
Version: 2.9
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: directx-d3d
Assignee: wine-bugs(a)winehq.org
Reporter: shtetldik(a)gmail.com
Distribution: ---
Created attachment 58341
--> https://bugs.winehq.org/attachment.cgi?id=58341
The Witcher 3: SSAO (ambient occlution) distortion
When running The Witcher 3 with ambient occlusion on, there are various visual
artifacts appearing.
With SSAO, there is black dotted mesh, and with HBAO+ there are running black
vertical lines.
See attached screenshots.
Game version: GOG, 1.31.
System: Debian testing, x86_64.
Graphics: AMD RX 480: AMD POLARIS10 (DRM 3.8.0 / 4.9.0-3-amd64, LLVM 3.9.1),
Mesa 17.1.0-devel (git-af73acca2b).
Resolution: 1920x1200.
Settings: Max settings for all graphics, except Nvidia hairworks is off.
--
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=43786
Bug ID: 43786
Summary: The Witcher 3: textures disappear in some places when
you move
Product: Wine
Version: 2.17
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: directx-d3d
Assignee: wine-bugs(a)winehq.org
Reporter: shtetldik(a)gmail.com
Distribution: ---
Created attachment 59299
--> https://bugs.winehq.org/attachment.cgi?id=59299
The Witcher 3: Velen cave save with disappearing texture
In some areas when you move, textures toggle, disappearing and appearing back.
But they don't leave a transparent area, but rather just untextured surface
when that happens. So I'm not sure if it's the same as other missing texture
bugs or not.
I attach a save in Velen cave where that happens, as well as a video capture of
that texture toggling.
Graphics:
OpenGL renderer string: AMD Radeon (TM) RX 480 Graphics (POLARIS10 / DRM 3.15.0
/ 4.12.0-2-amd64, LLVM 5.0.0)
OpenGL core profile version string: 4.5 (Core Profile) Mesa 17.3.0-devel
(git-3e54493265)
--
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=43861
Bug ID: 43861
Summary: The Witcher: Movement problems
Product: WineHQ.org
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: www-unknown
Assignee: wine-bugs(a)winehq.org
Reporter: const1993(a)gmail.com
Distribution: ---
The movement keys do not work right away, the character can continue to run for
another 15 seconds after I stop moving
--
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=50722
Bug ID: 50722
Summary: State of Decay 2: Juggernaut Edition icons rendering
is wrong with OpenGL renderer
Product: Wine
Version: 6.2
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: directx-d3d
Assignee: wine-bugs(a)winehq.org
Reporter: andrey.goosev(a)gmail.com
Distribution: ---
Created attachment 69472
--> https://bugs.winehq.org/attachment.cgi?id=69472
example
wine-6.2-320-gee4e33ed9ac
--
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=42953
Bug ID: 42953
Summary: ffxiv dx11 fixme:d3d11:d3d11_device_CreateBlendState
Per-rendertarget blend not implemented.
Product: Wine
Version: 2.7
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: ssbkm(a)icloud.com
Distribution: ---
unhandled dx11
--
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=30400
Bug #: 30400
Summary: Final Fantasy 7 in the first fight scene
Product: Wine
Version: 1.5.1
Platform: x86
URL: http://download.cnet.com/Final-Fantasy-VII-demo/3000-7
538_4-10020419.html
OS/Version: Linux
Status: NEW
Keywords: download
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: austinenglish(a)gmail.com
Classification: Unclassified
Created attachment 39739
--> http://bugs.winehq.org/attachment.cgi?id=39739
terminal output
Bug 9220 is fixed, so this is the next crash.
Get the game from
http://download.cnet.com/Final-Fantasy-VII-demo/3000-7538_4-10020419.html
austin@aw21 ~ $ sha1sum ff7demo.zip
79a555cd1874410a93952486e511bb8492e82a56 ff7demo.zip
unzip/run. Bug 9220 would crash it once Cloud swung his sword. This no longer
happens, the fight scene starts, then about 15 seconds later => crash.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
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=54517
Bug ID: 54517
Summary: riched20:editor - KDE? Clipboard interference causes
test_EM_SETUNDOLIMIT() failures
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: richedit
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
riched20:editor - KDE? Clipboard interference causes test_EM_SETUNDOLIMIT()
failures:
editor.c:3667: Test failed: EM_SETUNDOLIMIT didn't allow the first undo with
UNDOLIMIT set to 2
editor.c:3670: Test failed: EM_SETUNDOLIMIT didn't allow a second undo with
UNDOLIMIT set to 2
See https://test.winehq.org/data/patterns.html#riched20:editor
These failures mostly happen on my desktop, fg-deb64, though they did happen a
few times on on master and lastestmaster (sic) too (latestmaster did not have
that issue).
* My desktop is Debian 11 + KDE.
* master and lastestmaster are Linux Mint 21 (desktop environment unknown)
On my desktop, whenever Wine modifies the clipboard, some non-Wine process
accesses it and sometimes causes the clipboard content to be lost. Whether that
has an impact on the tests depends on whether the test is done with the
clipboard content by the time that access happens, i.e. there is a race
condition.
test_EM_SETUNDOLIMIT() does multiple pastes in a row (101 + 3), each of which
accesses the clipboard, which leaves time for that other process to cause the
clipboard content to be lost. This results in some pastes not happening so that
there are fewer pastes to undo than expected. Hence the failures above.
The test could be modified to check the length of the text field as a way to
verify that it got the expected number of successful pastes. If not, it could
either limit undos to however many pastes succeeded, or redo a copy plus more
pastes to reach the target number.
But I don't remember losing the clipboard content outside of Wine. Of course,
unlike Wine's tests I never perform hundreds of copy/pastes per second so maybe
that's why. Anyway, there may be something wrong in Wine and then fixing that
would be a better approach.
Or it may be a bug in some other component on my desktop that mishandles the
clipboard.
Also, even if the clipboard content is not lost, the WM_PASTE handling does a
simple OpenClipboard() which would fail if winex11 is already accessing it to
handle a query from some other process in the system. That seems too fragile
and would also cause missing undos. I don't know how Windows behaves in that
case though : Does the WM_PASTE simply fail? Is the OpenClipboard() operation
repeated indefinitely? Just a few times?
--
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=54007
Bug ID: 54007
Summary: in kde plasma fullscreen videogames cause gap between
taskbar and bottom edge of the screen
Product: Wine-staging
Version: 7.22
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: HarlanStaggs(a)gmail.com
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ---
Created attachment 73586
--> https://bugs.winehq.org/attachment.cgi?id=73586
this is how it looks with and without launched game
characteristics:
Operating System: Nobara Linux 36
KDE Plasma Version: 5.26.3
KDE Frameworks Version: 5.100.0
Qt Version: 5.15.7
Kernel Version: 6.0.10-201.fc36.x86_64 (64-bit)
Graphics Platform: X11
how to reproduce:
1) launch some fullscreen videogame (personally i do it with lutris from
flathub, maybe its important)
2) alt+tab to another non-fullscreen window
3) put cursor in bottom edge of the screen
4) try to switch windows with mouse wheel
5) notice small (several pixels height) gap between bottom edge of the screen
and taskbar, and also between taskbar and current non-fullscreen window in
focus.
6) close fullscreen videogame
7) everything is normal, taskbar is adjacent to the bottom edge of the screen
without gaps
this started to happen after update to wine-7.22 (Staging), i've never seen
this before, so i assume this bug occurs in this particular version.
--
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=54854
Bug ID: 54854
Summary: Locking the KDE screen causes user32:win to fail
systematically
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: user32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
Locking the KDE screen causes user32:win to fail systematically.
Specifically it gets failures in test_nonclient_area():
win.c:1581: Test failed: Got unexpected color 0xc0c0c0.
win.c:1581: Test failed: Got unexpected color 0xc0c0c0.
win.c:1581: Test failed: Got unexpected color 0xc0c0c0.
win.c:1581: Test failed: Got unexpected color 0xc0c0c0.
win.c:1581: Test failed: Got unexpected color 0xc0c0c0.
win.c:1581: Test failed: Got unexpected color 0xc0c0c0.
win.c:1581: Test failed: Got unexpected color 0xc0c0c0.
win.c:1581: Test failed: Got unexpected color 0xc0c0c0.
win.c:1581: Test failed: Got unexpected color 0xc0c0c0.
win.c:1581: Test failed: Got unexpected color 0xc0c0c0.
win.c:1581: Test failed: Got unexpected color 0xc0c0c0.
win.c:1581: Test failed: Got unexpected color 0xc0c0c0.
in test_activateapp():
win.c:11013: Test failed: Expected foreground window 0, got 00FE0060
win.c:11019: Test failed: Expected foreground window 002D0142, got 00FE0060
win.c:11082: Test marked todo: Expected WM_ACTIVATEAPP(0), did not receive it.
and in test_topmost():
win.c:11683: Test failed: 01ED0126: expected prev 005D00BE, got 00000000
win.c:11697: Test failed: hwnd should NOT be topmost
win.c:11699: Test failed: 01ED0126: expected NOT topmost
win.c:11643: Test failed: 1: hwnd 01ED0126 is still topmost
win.c:11724: Test marked todo: owner should be topmost
win.c:11727: Test marked todo: hwnd2 should be topmost
win.c:11750: Test marked todo: hwnd should NOT be topmost
win.c:11764: Test marked todo: hwnd should NOT be topmost
win.c:11805: Test marked todo: hwnd should be topmost
win.c:11807: Test succeeded inside todo block: child should be topmost
win.c:11809: Test marked todo: child2 should be topmost
win.c:11810: Test failed: grandchild should be topmost
win.c:11818: Test failed: child should NOT be topmost
win.c:11821: Test succeeded inside todo block: grandchild should NOT be topmost
win.c:11824: Test failed: 0007012A: expected NOT topmost
win.c:11643: Test succeeded inside todo block: 5: hwnd 01070060 is still
topmost
[... more todos ...]
See https://test.winehq.org/data/patterns.html#user32:win
Only my development desktop runs the Wine tests in KDE and I normally avoid
locking the screen when doing so. But it is quite remarkable that only three
tests units have an issue with this configuration: this one, comctl32:tooltips
(bug 54582) and user32:input (bug 54583).
--
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=54853
Bug ID: 54853
Summary: Locking the KDE screen causes user32:input to fail
systematically
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: user32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
Locking the KDE screen causes user32:input to fail systematically.
Specifically it gets failures in test_rawinput():
input.c:2918: Test marked flaky: 4: unexpected WM_MOUSEMOVE message
input.c:2929: Test failed: 4: Unexpected cursor movement
input.c:2929: Test failed: 5: Unexpected cursor movement
input.c:2929: Test failed: 6: Unexpected cursor movement
input.c:2502: Test marked todo: Expected wparam 1, got 0
input.c:2929: Test failed: 7: Unexpected cursor movement
input.c:2929: Test failed: 8: Unexpected cursor movement
input.c:2918: Test marked flaky: 9: unexpected WM_MOUSEMOVE message
input.c:2645: Test marked flaky: 9: foreground process expected WM_MOUSEMOVE
message
input.c:2929: Test failed: 9: Unexpected cursor movement
input.c:2502: Test marked todo: Expected wparam 1, got 0
input.c:2645: Test marked flaky: 10: foreground process expected WM_MOUSEMOVE
message
input.c:2929: Test failed: 10: Unexpected cursor movement
input.c:2502: Test marked todo: Expected wparam 1, got 0
input.c:2645: Test marked flaky: 11: foreground process expected WM_MOUSEMOVE
message
input.c:2929: Test failed: 11: Unexpected cursor movement
input.c:2645: Test marked flaky: 12: foreground process expected WM_MOUSEMOVE
message
input.c:2929: Test failed: 12: Unexpected cursor movement
input.c:2921: Test marked todo: 13: expected WM_INPUT message
input.c:2929: Test failed: 13: Unexpected cursor movement
input.c:2929: Test failed: 14: Unexpected cursor movement
input.c:2929: Test failed: 15: Unexpected cursor movement
input.c:2929: Test failed: 16: Unexpected cursor movement
and in test_GetMouseMovePointsEx_process():
input.c:1730: Test failed: expected to get 64 mouse move points but got -1
input.c:1741: Test failed: expected to get 64 mouse move points but got -1
input.c:1787: Test marked todo: expected to get -1 mouse move points but got 64
input.c:1788: Test marked todo: expected ERROR_ACCESS_DENIED got -559038737
See https://test.winehq.org/data/patterns.html#user32:input
Only my development desktop runs the Wine tests in KDE and I normally avoid
locking the screen when doing so. But it is quite remarkable that only three
tests units have an issue with this configuration: this one, comctl32:tooltips
and user32:win.
--
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.