https://bugs.winehq.org/show_bug.cgi?id=53213
Bug ID: 53213
Summary: d3d11:d3d11 - test_texture() fails in the TestBot VMs
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: directx-d3d
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
d3d11:d3d11 - test_texture() fails in the TestBot VMs:
d3d11.c:9837: Test failed: Test 60: Got unexpected color 0xff0000ff at (0, 0).
d3d11.c:9837: Test failed: Test 60: Got unexpected color 0xff00ffff at (1, 0).
d3d11.c:9837: Test failed: Test 60: Got unexpected color 0xff00ff00 at (2, 0).
d3d11.c:9837: Test failed: Test 60: Got unexpected color 0xffffff00 at (3, 0).
d3d11.c:9837: Test failed: Test 60: Got unexpected color 0xffff0000 at (0, 1).
d3d11.c:9837: Test failed: Test 60: Got unexpected color 0xffff00ff at (1, 1).
d3d11.c:9837: Test failed: Test 60: Got unexpected color 0xff000000 at (2, 1).
d3d11.c:9837: Test failed: Test 60: Got unexpected color 0xff7f7f7f at (3, 1).
d3d11.c:9837: Test failed: Test 60: Got unexpected color 0xffffffff at (0, 2).
d3d11.c:9837: Test failed: Test 60: Got unexpected color 0xffffffff at (1, 2).
d3d11.c:9837: Test failed: Test 60: Got unexpected color 0xffffffff at (2, 2).
d3d11.c:9837: Test failed: Test 60: Got unexpected color 0xff000000 at (3, 2).
d3d11.c:9837: Test failed: Test 60: Got unexpected color 0xffffffff at (0, 3).
d3d11.c:9837: Test failed: Test 60: Got unexpected color 0xff000000 at (2, 3).
d3d11.c:9837: Test failed: Test 60: Got unexpected color 0xff000000 at (3, 3).
https://test.winehq.org/data/patterns.html#d3d11:d3d11
These failures don't happen on my box which has an Intel graphics card instead
of QEmu's QXL graphics card.
Note also that these failures still happen on my debian11 VM which has a single
monitor instead of the TestBot VMs' multi-monitor setup.
So this seems to be related to the VMs QXL GPU.
Note that despite being systematic these failures could cause false positives
(see bug 53212).
--
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=54780
Bug ID: 54780
Summary: UndertaleModTool display regression since wine-staging
8.4
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: minor
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: janbidler00(a)protonmail.com
Distribution: ---
Created attachment 74277
--> https://bugs.winehq.org/attachment.cgi?id=74277
Display bug
Starting from wine-staging 5.4 UndertaleModTool has corrupted display at boot.
This did not happen on wine-staging 5.3 and earlier.
The corrupted display can be fixed temporarily by clicking on any item in the
Menubar (i.e. "File").
Happens both on a clean prefix and when upgrading.
Issue is specific to wine-staging; wine-development has crashes going back all
the way to wine-7.0 if not earlier and I didn't test it with wine-stable.
Attached is an image of the display bug.
The UndertaleModTool version can be found here (I used the asset
"UndertaleModTool_v0.5.0.0.zip"):
https://github.com/krzys-h/UndertaleModTool/releases/tag/0.5.0.0
Using Arch Linux. The wine-staging were gotten from here:
https://archive.archlinux.org/packages/w/wine-staging/
--
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=54519
Bug ID: 54519
Summary: d3d9:visual - test_mipmap_upload() fails on AMD and
Nvidia GPUs
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_mipmap_upload() fails on AMD and Nvidia GPUs.
This impacts three VMs:
fgtb-w10pro64_rx550 (AMD RX550):
visual.c:27986: Test failed: pool 0x2: level 0: Got unexpected color
0x00000000.
visual.c:27986: Test failed: pool 0x2: level 1: Got unexpected color
0x00000000.
visual.c:27986: Test failed: pool 0x2: level 2: Got unexpected color
0x00000000.
visual.c:27986: Test failed: pool 0x2: level 3: Got unexpected color
0x00000000.
visual.c:27986: Test failed: pool 0x2: level 4: Got unexpected color
0x00000000.
visual.c:27986: Test failed: pool 0x2: level 5: Got unexpected color
0x00000000.
w11pro64_amd (AMD RX660):
visual.c:404: Test failed: pool 0x2: level 0: Got hr 0x80004005.
visual.c:27986: Test failed: pool 0x2: level 0: Got unexpected color
0x00ff0000.
visual.c:404: Test failed: pool 0x2: level 1: Got hr 0x80004005.
visual.c:27986: Test failed: pool 0x2: level 1: Got unexpected color
0x00ff0000.
visual.c:404: Test failed: pool 0x2: level 2: Got hr 0x80004005.
visual.c:27986: Test failed: pool 0x2: level 2: Got unexpected color
0x00ff0000.
visual.c:404: Test failed: pool 0x2: level 3: Got hr 0x80004005.
visual.c:27986: Test failed: pool 0x2: level 3: Got unexpected color
0x00ff0000.
visual.c:404: Test failed: pool 0x2: level 4: Got hr 0x80004005.
visual.c:27986: Test failed: pool 0x2: level 4: Got unexpected color
0x00ff0000.
visual.c:404: Test failed: pool 0x2: level 5: Got hr 0x80004005.
visual.c:27986: Test failed: pool 0x2: level 5: Got unexpected color
0x00ff0000.
w11pro64_nv (NVIDIA RTX3050):
visual.c:195: pool 0x2: level 0: Can't create an offscreen plain surface to
read the render target data, hr 0x80004005.
visual.c:27986: Test failed: pool 0x2: level 0: Got unexpected color
0x00adbeef.
visual.c:27986: Test failed: pool 0x2: level 1: Got unexpected color
0x00000000.
visual.c:195: pool 0x2: level 2: Can't create an offscreen plain surface to
read the render target data, hr 0x80004005.
visual.c:27986: Test failed: pool 0x2: level 2: Got unexpected color
0x00adbeef.
visual.c:195: pool 0x2: level 3: Can't create an offscreen plain surface to
read the render target data, hr 0x80004005.
visual.c:27986: Test failed: pool 0x2: level 3: Got unexpected color
0x00adbeef.
visual.c:195: pool 0x2: level 4: Can't create an offscreen plain surface to
read the render target data, hr 0x80004005.
visual.c:27986: Test failed: pool 0x2: level 4: Got unexpected color
0x00adbeef.
visual.c:195: pool 0x2: level 5: Can't create an offscreen plain surface to
read the render target data, hr 0x80004005.
visual.c:27986: Test failed: pool 0x2: level 5: Got unexpected color
0x00adbeef.
See https://test.winehq.org/data/patterns.html#d3d9:visual
These failures all started on 2023-01-06 and a bisect shows that, on all three
machines, they started with the commit below:
commit 2954d3e4a23025657740fb178ddbe110890c0cc8
Author: Zebediah Figura <zfigura(a)codeweavers.com>
Date: Tue Dec 20 17:43:39 2022 -0600
d3d9/tests: Test uploading the whole mipmap chain in one map.
Signed-off-by: Zebediah Figura <zfigura(a)codeweavers.com>
--
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=54399
Bug ID: 54399
Summary: d3d11:d3d11 - test_vertex_formats() fails on Windows
11 + AMD
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
d3d11:d3d11 - test_vertex_formats() fails on Windows 11 + AMD:
d3d11.c:34906: Test failed: Format 0x58: Got {3.96078438e-001, 2.62745112e-001,
1.29411772e-001, 1.42236653e-019}, expected {3.96078438e-001, 2.62745112e-001,
1.29411772e-001, 1.00000000e+000} at (0, 0), sub-resource 0.
See w11pro64-amd in https://test.winehq.org/data/patterns.html#d3d11:d3d11
The failures started on 2023-01-24, that is on the date the test was added by
this commit:
commit dc19f5c517af5d04bebb4f26bd79220b02f1ba64
Author: Zebediah Figura <zfigura(a)codeweavers.com>
AuthorDate: Wed Jan 11 19:25:11 2023 -0600
d3d11/tests: Add a basic test for vertex formats.
--
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=55679
Bug ID: 55679
Summary: warframe doesn't start in experimental wow64 mode
Product: Wine
Version: 8.16
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: pmargeti34(a)gmail.com
Distribution: ---
Created attachment 75201
--> https://bugs.winehq.org/attachment.cgi?id=75201
warframe doesn't start in experimental wow64 mode
Game launcher fails to run properly, it spawns it's own error dialog which
offers to send crash related data to Digital Extremes. Attached is the output
of launching it from the terminal.
--
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=55608
Bug ID: 55608
Summary: NAM won't open on new update
Product: Wine
Version: 8.16
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: zardivorku(a)gufum.com
Distribution: ---
Created attachment 75145
--> https://bugs.winehq.org/attachment.cgi?id=75145
Log Report
https://github.com/sdatkinson/NeuralAmpModelerPlugin/releases
On latest wine staging update NAM crashes, didn't happen before on prior
update.
Linux Mint Cinnamon
--
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=55316
Bug ID: 55316
Summary: d3d10core:d3d10core fails systematically on
w11pro64-amd
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
d3d10core:d3d10core fails systematically on w11pro64-amd:
test_pipeline_statistics_query():
d3d10core.c:4922: Test failed: Got unexpected GSInvocations count: 2.
d3d10core.c:4941: Test failed: Got unexpected GSInvocations count: 2.
test_sample_c_lz():
d3d10core.c:8553: Test failed: Got 1.00000000e+000, expected 0.00000000e+000 at
(100, 100), sub-resource 0.
d3d10core.c:8553: Test failed: Got 1.00000000e+000, expected 0.00000000e+000 at
(100, 100), sub-resource 0.
See https://test.winehq.org/data/patterns.html#d3d10core:d3d10core
These failures have been happening forever and are specific to the Windows 11 +
AMD RX6600 configuration. In particular they never happened on
fgtbw10pro64_rx550 (Windows 10 + AMD RX550). Also, except for 2023-05-10 to
2023-05-12 (3 days) they are present in all nightlies.
--
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=53218
Bug ID: 53218
Summary: d3d10core:d3d10core - test_uint_shader_instructions()
fails in the TestBot VMs
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: directx-d3d
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
d3d10core:d3d10core - test_uint_shader_instructions() fails in the TestBot VMs:
d3d10core.c:13215: Test failed: Got {0x80000000, 0x00000000, 0x00000000,
0x00000000}, expected {0x00000000, 0xffffffff, 0x00000000, 0x00000000} at (0,
0), sub-resource 0.
d3d10core.c:13215: Test failed: Got {0x00000000, 0x80000000, 0x00000000,
0x00000000}, expected {0xffffffff, 0x00000000, 0x00000000, 0x00000000} at (0,
0), sub-resource 0.
d3d10core.c:13215: Test failed: Got {0xffffffff, 0x00000001, 0x00000000,
0x00000000}, expected {0x00000000, 0x00000001, 0x00000000, 0x00000000} at (0,
0), sub-resource 0.
d3d10core.c:13215: Test failed: Got {0x00000001, 0xffffffff, 0x00000000,
0x00000000}, expected {0x00000001, 0x00000000, 0x00000000, 0x00000000} at (0,
0), sub-resource 0.
https://test.winehq.org/data/patterns.html#d3d10core:d3d10core
These failures:
* Don't happen on Debian 11 + Intel / KDE
* Happen on Debian 11 + QXL + single-monitor
* Happen on Debian 11 + QXL + multi-monitor
* Happen on Debian Testing + QXL + multi-monitor (it actually has a couple
extra)
So they are probably related to QXL.
Note that despite being systematic these failures could cause false positives
due to the test multi-threading (see bug 53212).
--
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=53522
Bug ID: 53522
Summary: Need for Speed III: joystick doesn't work after evdev
removal
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: dinput
Assignee: wine-bugs(a)winehq.org
Reporter: DirtY.iCE.hu(a)gmail.com
CC: rbernon(a)codeweavers.com
Regression SHA1: adfee25b45af8160848f94fdb24279d63d5f91f4
Distribution: Gentoo
Created attachment 72888
--> https://bugs.winehq.org/attachment.cgi?id=72888
WINEDEBUG=+dinput, ds4 usb, overriden, nfs3 demo with git master wine
I decided to try NFS3 after some time and realized that joystick no longer
works with newer releases. Git bisect lead me to commit
adfee25b45af8160848f94fdb24279d63d5f91f4, where the evdev and js backends were
removed. With the new backend, in NFS3 deadzone calibration screen, all axes
are at constant 0, and it doesn't respond to any keypress either. I've tried it
with DualShock 4 (both usb and bt), DS3 (only usb), and some noname cheap
controller, the same results. Interestingly, in joy.cpl the joysticks do work,
I've tried to click on override to move the controller from the xinput to the
non-xinput list, but no change. I also have no force-feedback support with the
new backend.
Tested it with the retail version of nfs3 and also with this patch, the results
are the same: https://veg.by/en/projects/nfs3/
Also tested it with the demo version and the latest git
(bfc73b0b80a1da2b137b5da4a2fcf530ee3a9d7d), same results.
1. Download demo from here: https://archive.org/details/nfs3_demo
2. Create a new 32-bit wine prefix (I've only compiled a 32-bit wine)
3. In winecfg, set windows compatibility to 98 (otherwise the install refuses
to start), go to drives and add a (fake) cdrom device (otherwise setup refuses
to start), and probably you should set a virtual desktop (the game likes to
mess with your resolution)
4. Run setup.exe (it will throw a registry error but still installs the game)
5. Start the game with taskset: `taskset -c 0 path/to/wine nfs3demo -d3d0` (the
game crashes/freezes if run on multicore cpu)
6. After the race countdown, press esc, controls, and try to bind some keys or
click on dead zone to see axes values.
I'm attaching a log with WINEDEBUG=+dinput and overridden joystick on joy.cpl.
--
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.