https://bugs.winehq.org/show_bug.cgi?id=46422
Bug ID: 46422
Summary: Kara no Shoujo does not enter fullscreen correctly
Product: Wine
Version: 4.0-rc4
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: zaplo00(a)mailfence.com
Distribution: ---
Created attachment 63193
--> https://bugs.winehq.org/attachment.cgi?id=63193
screenshot of the problem
See screenshot. Same thing happens in wine virtual desktop as well as in other
desktop environments.
OS: Arch Linux x86_64
Kernel: 4.19.9-arch1-1-ARCH
Uptime: 5 hours, 39 mins
Packages: 1453 (pacman)
Shell: bash 4.4.23
Resolution: 1920x1080, 1920x1080
DE: Cinnamon 4.0.8
WM: Mutter (Muffin)
WM Theme: cinnamon (Adwaita)
Theme: Adwaita [GTK2/3]
Icons: Adwaita [GTK2/3]
Terminal: mate-terminal
Terminal Font: Monospace 10
CPU: AMD Ryzen 7 1700 (16) @ 3.000GHz
GPU: NVIDIA GeForce GTX 1060 3GB
Memory: 2011MiB / 16036MiB
wine log:
0009:fixme:ddraw:DirectDrawEnumerateExA flags 0x00000006 not handled
0042:fixme:d3d:state_linepattern_w Setting line patterns is not supported in
OpenGL core contexts
--
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=55488
Bug ID: 55488
Summary: Finale 27 doesn't print SMuFL fonts
Product: Wine
Version: 7.0.2
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: wineps.drv
Assignee: wine-bugs(a)winehq.org
Reporter: davech(a)t-online.de
Distribution: ---
Finale 27 doesn't print glyphs from SMuFL fonts (https://www.smufl.org/) which
use glyphs in the Unicode private-use area from E000. Files using legacy fonts
(glyphs in the range 0000-00FF) print correctly, but SMuFL is the standard for
new files.
--
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=50577
Bug ID: 50577
Summary: Saya no Uta: hangs on RtlpWaitForCriticalSection
Product: Wine
Version: 6.0
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: ntdll
Assignee: wine-bugs(a)winehq.org
Reporter: pernegger(a)gmail.com
Distribution: ---
Created attachment 69251
--> https://bugs.winehq.org/attachment.cgi?id=69251
terminal output at default settings
Note: This is about the Japanese "Windows 10 compatible" release, not an
English localised one. There is no demo version, I'm afraid.
The game runs fine--until it hangs at:
012c:err:ntdll:RtlpWaitForCriticalSection section 103971A4 "?" wait timed out
in thread 012c, blocked by 0024, retrying (60 sec)
The hang may happen, after as little as 1 min, sometimes it's 10 min, and I
might have made it 20 min once. When it happens, it does not recover, the
message just repeats every once in a while.
I'm using the Ubuntu packages from the official winehq repo. Originally I tried
with wine-staging 6.0, then I went backwards version by version through
(wine-staging) 5.18, and finally now I'm on (wine-devel) 6.0 for this bug
report. No discernable difference either way. The run in the attached log
happened in a clean prefix (though I admit I may have forgotten to wipe the
prefix between some downgrades).
--
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=54074
Bug ID: 54074
Summary: ws2_32:sock - test_empty_recv() sometimes gets an
ERROR_IO_PENDING error in Wine
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: winsock
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
ws2_32:sock - test_empty_recv() sometimes gets an ERROR_IO_PENDING error in
Wine:
sock.c:12752: Test failed: got error 997
See https://test.winehq.org/data/patterns.html#ws2_32:sock
This happens about twice per month in the nightly WineTest runs but the first
known instance is on 2022-09-01 on debiant-wow32: there is no record of this
failure happening in the previous 3 months. So it is likely to be caused by
some commit in August.
This is also known to have happened in the GitLab CI environment which impacted
some merge requests (for instance MR!1561 and MR!1485).
--
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=51715
Bug ID: 51715
Summary: crypt32:chain fails on some AMD/Nvidia GPU machines
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: crypt32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
crypt32:chain has the same three failures on a set of Windows machines:
chain.c:3458: Test failed: chainCheck[31]: expected 3 elements, got 4
chain.c:4583: Test failed: simple_chain->cElement = 4
chain.c:4609: Test failed: got string GB, Greater Manchester, Salford, Comodo
CA Limited, AAA Certificate Services, expected US, New Jersey, Jersey City, The
USERTRUST Network, USERTrust RSA Certification Authority
https://test.winehq.org/data/patterns.html#comctl32:header
The only common point is that all these machines have an AMD or Nvidia GPU:
* cw-gtx560 Windows 8.1 Nvidia GTX560 driver 353.82
* cw-gtx560 Windows 10 1507 Nvidia GTX560 driver 391.35
* cw-rx460 Windows 10 1507 AMD RX460 driver 19.11.3
* fgtb-w10pro64 Windows 10 2009 AMD RX550 driver 20.11.3
* fgtb-w10pro64 Windows 10 21H1 AMD RX550 driver 21.8.2
* vn-w10pro Windows 10 21H1 AMD RX570 driver 20.10.35.02
But the failures don't happen whenever there is such a GPU: cw-gtx560-2009 has
the same 391.35 Nvidia driver as cw-gtx560-1507 version and yet does not have
these failures.
--
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=54424
Bug ID: 54424
Summary: user32:edit - test_dbcs_WM_CHAR() fails on Windows in
mixed locales
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:edit - test_dbcs_WM_CHAR() fails on Windows in mixed locales:
edit.c:3407: Test failed: W: got L"\02c6\00ea\201c", expected
L"\4e00\4e8c\4e09"
edit.c:3412: Test failed: W: got "?e\x81gn?O", expected "\x88\xea\x93\xf1\x8eO"
See https://test.winehq.org/data/patterns.html#user32:edit
The failures happen in the w10pro64-mx-MX test configuration. What's special
about it is that it uses a mix of locales:
SystemDefaultLCID 0411
UserDefaultLCID 040c
ThreadLocale 0411
SystemPreferredUILanguages 0412,0409
UserDefaultUILanguage 0412
ThreadUILanguage 0412
Country 231
ACP 932
The failures started happening with the commit that introduced the new tests:
commit cbe3a39b647e029df16faf1dcce2958f1ee418d0
Author: Akihiro Sagawa <sagawa.aki(a)gmail.com>
AuthorDate: Fri Jan 20 23:51:36 2023 +0900
user32/tests: Add DBCS WM_CHAR tests for edit control.
--
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=55405
Bug ID: 55405
Summary: FreeCommander crashing immediately after it starts,
when Windows version is set above Windows XP
Product: Wine
Version: 8.13
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: mywine(a)schiermeier-it.de
Distribution: ---
Created attachment 74965
--> https://bugs.winehq.org/attachment.cgi?id=74965
Console log from start of FreeCommander with Windows version set to v10
Installation of FreeCommander 32bit is working without any error.
When it should start it crashes. Depending on the version Windows is set to, it
behaves like this:
Windows XP: works
Windows 7: crash at the start with a stack overflow error, show in a message
box
Windows 10: a window came up and disappears immediately without any message
(box)
Console output for Windows 10 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=41662
Bug ID: 41662
Summary: Carmageddon (windows 95 version) flickering menus
(possible ddraw issue)
Product: Wine
Version: 1.9.22
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: aaronbpaden(a)gmail.com
Distribution: ---
Created attachment 56059
--> https://bugs.winehq.org/attachment.cgi?id=56059
log
AfteCarmageddonr playing a race in Carmadeddon and returning to the menus, the
tops and bottoms of the screen flicker with an image from the last race.
I'm on radeonsi and it could be a driver issue, but from the logs I think it's
a ddraw issue.
It's not a huge problem as far as Carmageddon is concerned, because the menu is
still fully visible and usable.
--
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=54026
Bug ID: 54026
Summary: user32:msg receives unexpected messages in the 49000+
range on w11pro64_nv
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 receives unexpected messages in the 49000+ range on w11pro64_nv:
msg.c:13518: Test failed: msg.message = 49667 instead of WM_TIMER
or
msg.c:13499: Test failed: msg.message = 49815 instead of WM_TIMER
or
msg.c:13549: Test failed: msg.message = 49663 instead of WM_TIMER
msg.c:13552: Test failed: msg.message = 275 instead of WM_USER + 1
msg.c:13554: Test failed: expected PeekMessage to return FALSE, got 1
msg.c:13564: Test failed: msg.message = 1025 instead of WM_TIMER
msg.c:13566: Test failed: msg.message = 275 instead of WM_USER
msg.c:13568: Test failed: expected PeekMessage to return FALSE, got 1
msg.c:13577: Test failed: msg.message = 1024 instead of WM_TIMER
msg.c:13579: Test failed: expected PeekMessage to return FALSE, got 1or
or
msg.c:13518: Test failed: msg.message = 49650 instead of WM_TIMER
msg.c:13521: Test failed: msg.message = 275 instead of WM_USER
msg.c:13523: Test failed: expected PeekMessage to return FALSE, got 1
msg.c:13534: Test failed: msg.message = 1024 instead of WM_TIMER
msg.c:13536: Test failed: expected PeekMessage to return FALSE, got 1
msg.c:13546: Test failed: msg.message = 275 instead of WM_USER
msg.c:13549: Test failed: msg.message = 1024 instead of WM_TIMER
or
msg.c:13499: Test failed: msg.message = 49668 instead of WM_TIMER
msg.c:13503: Test failed: msg.message = 49668 instead of WM_TIMER
See http://winetest.dolphin/data/patterns.html#user32:msg
Where:
275 == WM_TIMER
1024 == WM_USER
These failures don't happen on other w11pro64 test configurations so it is
likely that these messages are generated by some part of the NVIDIA driver
despite it being installed without its GUI precisely to avoid this type of
issue. So it seems the test will have to accommodate these extra messages
despite their value changing from one run to the next.
--
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=43081
Bug ID: 43081
Summary: Final Fantasy VII 2012: Buggy rendering of graphics
during fights and dialogs
Product: Wine
Version: 2.0.1
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: b33lzebob(a)googlemail.com
Distribution: ---
Created attachment 58266
--> https://bugs.winehq.org/attachment.cgi?id=58266
Archive including screenshots of this graphics bug, sed DLLs and terminal
output.
Strange display of character graphics during fights and dialogs (see
attachment).
System Information:
Wine version: 2.0.1
OS: Ubuntu Gnome 17.04 64bit
CPU: AMD® A4-3305m apu with radeon(tm) hd graphics × 2
GPU: ATI Radeon HD 6480 (Sumo2)
Things I've tried:
- update from Ubuntu Gnome 16.04 to 17.04 to provide form actual graphics
driver
- Added DDLs like described at https://appdb.winehq.org
/objectManager.php?sClass=version&iId=28519 via winetricks
- selected different versions of windows (Windows XP, 7, 8 & 10)
- installed steam- and non-stream-version of this 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.
http://bugs.winehq.org/show_bug.cgi?id=24559
Summary: Final Fantasy 7: error when installing 'Movie Player'
Product: Wine
Version: 1.3.3
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: leighmanthegreat(a)hotmail.com
Created an attachment (id=31005)
--> (http://bugs.winehq.org/attachment.cgi?id=31005)
Clicking 'Install MoviePlayer' option
Using Ubuntu 10.04
Final Fantasy 7 setup program gives you the option to 'Install Movie Player'
clicking this appears to fail with the error message
DirectShow Setup failed with error code: -2147023829
terminal log attached
--
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=53802
Bug ID: 53802
Summary: Steam - new Login UI renders as a black screen
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Mac OS X
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: gcenx83(a)gmail.com
Steams new reactlogin login has been rolled out to all users and at least on
macOS this renders as a black window.
To avoid this steam can be launched with the following launch command
-noreactlogin, this forces the older Login UI that renders correctly.
This occurs on brand a brand new wineprefix and installing steam via
winetricks.
--
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=55208
Bug ID: 55208
Summary: Array size expressions should not allow every possible
expression
Product: vkd3d
Version: 1.8
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: hlsl
Assignee: wine-bugs(a)winehq.org
Reporter: bunglehead(a)gmail.com
Distribution: ---
Sample shader would be:
float4 main() : sv_target
{
int x;
float a[(x = 2)];
return 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.
http://bugs.winehq.org/show_bug.cgi?id=33763
Bug #: 33763
Summary: Sacred 2 : HLSL shader parsing failed error with
built-in d3dcompiler_43
Product: Wine
Version: 1.6-rc1
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: directx-d3dx9
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: xvachon(a)gmail.com
CC: wine-bugs(a)winehq.org
Classification: Unclassified
Created attachment 44714
--> http://bugs.winehq.org/attachment.cgi?id=44714
log trace+d3dcompiler
Follow up of http://bugs.winehq.org/show_bug.cgi?id=25366#c9
Running Sacred 2 in a clean prefix without overrides in 1.6-rc1 results in a
crash. Using overrides d3dcompiler_43 (poor performance) or d3dx9_36 (better
performance) work around the issue. This bug is tagged to d3dcompiler_43
however because of this :
fixme:d3dx:D3DXLoadSurfaceFromMemory Unhandled filter 0x5.
err:d3dcompiler:compile_shader HLSL shader parsing failed.
wine: Unhandled page fault on read access to 0xca7fa113 at address 0x1134484
(thread 0009), starting debugger...
Attached a log trace+d3dcompiler which hopefully reveals meaningful details to
the devs..
--
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.
http://bugs.winehq.org/show_bug.cgi?id=36091
Bug ID: 36091
Summary: Project APT fails to compile vertex shader
Product: Wine
Version: 1.7.17
Hardware: x86
URL: http://www.desura.com/games/project-apt
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: directx-d3dx9
Assignee: wine-bugs(a)winehq.org
Reporter: madewokherd(a)gmail.com
Created attachment 48280
--> http://bugs.winehq.org/attachment.cgi?id=48280
d3dcompiler,tid log
When clicking "new game" in project apt, I get a message saying "FATAL ERROR in
Vertex Shader compilation". The console shows an error in compile_shader, and
messages in the d3dcompiler channel seem to match up with the details of the
game's error message.
--
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=54054
Bug ID: 54054
Summary: Rayman Origins has messed up rendering
Product: vkd3d
Version: 1.5
Hardware: x86-64
OS: Linux
Status: NEW
Severity: minor
Priority: P2
Component: vkd3d
Assignee: wine-bugs(a)winehq.org
Reporter: andrey.goosev(a)gmail.com
Distribution: ---
Created attachment 73607
--> https://bugs.winehq.org/attachment.cgi?id=73607
example
vkd3d:fixme:evaluate_array_dimension Unhandled type HLSL_IR_EXPR.
0218:err:d3dcompiler:D3DCompile2 Failed to compile shader, vkd3d result -4.
0218:err:d3dcompiler:D3DCompile2 Shader log:
0218:err:d3dcompiler:D3DCompile2 <anonymous>:39:16: E5008: Array size is
not a positive integer constant.
0218:err:d3dcompiler:D3DCompile2
0218:err:d3dcompiler:D3DCompile2 Shader log:
0218:err:d3dcompiler:D3DCompile2 <anonymous>:47:16: E5005: Function "tex2D"
is not defined.
0218:err:d3dcompiler:D3DCompile2
0218:err:d3dcompiler:D3DCompile2 Failed to compile shader, vkd3d result -4.
0218:err:d3dcompiler:D3DCompile2 Shader log:
0218:err:d3dcompiler:D3DCompile2 <anonymous>:166:18: E5005: Function "tan"
is not defined.
0218:err:d3dcompiler:D3DCompile2
vkd3d-1.5-93-g1b11b576
--
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=54484
Bug ID: 54484
Summary: Comma-separated variable declaration lists do no
handle dependent initializers within the same list
Product: vkd3d
Version: 1.6
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: hlsl
Assignee: wine-bugs(a)winehq.org
Reporter: bunglehead(a)gmail.com
Distribution: ---
Created attachment 74035
--> https://bugs.winehq.org/attachment.cgi?id=74035
test
See attached test. Currently it produces an error: E5005: Identifier "i" is not
declared.
This happens because earlier declared variables are not declared within the
context, so when occurred in following initializers they are treated as
NEW_IDENTIFIER, instead of VAR_IDENTIFIER. My understanding is that
declarations are added to the context after whole list is processed, and that
probably should change.
--
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=54647
Bug ID: 54647
Summary: Call of Juarez needs "log2" handling
Product: vkd3d
Version: 1.6
Hardware: x86-64
OS: Linux
Status: NEW
Severity: minor
Priority: P2
Component: hlsl
Assignee: wine-bugs(a)winehq.org
Reporter: andrey.goosev(a)gmail.com
Distribution: ---
0718:err:d3dcompiler:D3DCompile2 Failed to compile shader, vkd3d result -4.
0718:err:d3dcompiler:D3DCompile2 Shader log:
0718:err:d3dcompiler:D3DCompile2 <anonymous>:19:16: W5300: Implicit
truncation of vector type.
0718:err:d3dcompiler:D3DCompile2 <anonymous>:21:19: E5005: Function "log2"
is not defined.
1.6-195-g2880be64
--
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=54680
Bug ID: 54680
Summary: NewoAsteroids played with Dolphin emulator needs SM1
'round' support
Product: vkd3d
Version: 1.6
Hardware: x86-64
URL: https://dl.dolphin-emu.org/releases/dolphin-3.0-x64.ex
e
OS: Linux
Status: NEW
Keywords: download
Severity: normal
Priority: P2
Component: hlsl
Assignee: wine-bugs(a)winehq.org
Reporter: gijsvrm(a)gmail.com
Depends on: 34242
Distribution: ---
0110:err:d3dcompiler:D3DCompile2 <anonymous>:12:10: E5017: Aborting due to
not yet implemented feature: SM1 "round" expression.
NewoAsteroids: http://wiibrew.org/wiki/Newo_Asteroids
--
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=54700
Bug ID: 54700
Summary: Conspiracy's Clean Slate 64K demo crashes due to
missing 'fmod' handling
Product: vkd3d
Version: 1.6
Hardware: x86-64
URL: https://web.archive.org/web/20210807072016/https://con
spiracy.hu/files/cns%21cns-AMDfix.zip
OS: Linux
Status: NEW
Keywords: download
Severity: normal
Priority: P2
Component: hlsl
Assignee: wine-bugs(a)winehq.org
Reporter: gijsvrm(a)gmail.com
Depends on: 54679
Distribution: ---
0024:err:d3dcompiler:D3DCompile2 Failed to compile shader, vkd3d result -4.
0024:err:d3dcompiler:D3DCompile2 Shader log:
0024:err:d3dcompiler:D3DCompile2 <anonymous>:1:302: E5005: Function "fmod"
is not defined.
0024:err:d3dcompiler:D3DCompile2
wine: Unhandled page fault on read access to 00000000 at address 00607E90
(thread 0024), starting debugger...
--
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=54708
Bug ID: 54708
Summary: Renegade Ops needs Load() sampling index parameter
Product: vkd3d
Version: 1.6
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: hlsl
Assignee: wine-bugs(a)winehq.org
Reporter: andrey.goosev(a)gmail.com
Distribution: ---
0bb4:trace:d3dcompiler:D3DCompile data 0D67DEE0, data_size 370, filename
(null), defines 00000000, include 00000000, entrypoint "main", target "ps_4_0",
sflags 0, eflags 0, shader 0D67DEDC, error_messages 0D67DED8.
0bb4:trace:d3dcompiler:D3DCompile2 data 0D67DEE0, data_size 370, filename
(null), macros 00000000, include 00000000, entry_point "main", profile
"ps_4_0", flags 0, effect_flags 0, secondary_flags 0, secondary_data 00000000,
secondary_data_size 0, shader_blob 0D67DEDC, messages_blob 0D67DED8.
0bb4:err:d3dcompiler:D3DCompile2 Failed to compile shader, vkd3d result -5.
0bb4:err:d3dcompiler:D3DCompile2 Shader log:
0bb4:err:d3dcompiler:D3DCompile2 <anonymous>:6:121: E5017: Aborting due to
not yet implemented feature: Load() sampling index parameter.
0bb4:err:d3dcompiler:D3DCompile2 <anonymous>:6:149: E5000: syntax error,
unexpected '['
1.6-207-g4110f1e5
--
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=54736
Bug ID: 54736
Summary: MojoShader HLSL requires ternary operators
Product: vkd3d
Version: 1.7
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: hlsl
Assignee: wine-bugs(a)winehq.org
Reporter: flibitijibibo(a)gmail.com
Distribution: ---
A quick note before the report: Many thanks to the vkd3d team for their work on
the HLSL compiler, we have been using it as our Linux-native HLSL compiler for
FNA and as of 1.7 we have commercial games running with it! The FNA community
is very grateful for this work.
In testing games against the latest compiler, we found that one notable
hlsl_fixme was ternary operators:
https://gitlab.winehq.org/wine/vkd3d/-/blob/57d92a15cf93d9448f2deb91a8614f9…
MojoShader, our method for converting D3D9-era DXBC to other shader formats,
uses ternaries in a number of ways:
- cnd/cmp operations
- rsq/rcp operations (have to handle the division-by-zero case)
- Translating SV_IsFrontFace to an equivalent VFACE value
This can be tested with the Linux-native version of Terraria on Steam, using
the following process:
1. Download Terraria from the Steam client
2. Download https://fna.flibitijibibo.com/archive/fnalibs.tar.bz2, copy
lib64/libFNA3D.so.0 into Terraria's lib64 folder
3. Copy the following libraries into Terraria's lib64 folder:
- libdxvk_d3d11.so
- libdxvk_dxgi.so
- libvkd3d.so.1
- libvkd3d-shader.so.1
- libvkd3d-utils.so.1
As of writing, DXVK currently requires the latest development builds:
https://github.com/doitsujin/dxvk/actions/workflows/artifacts.yml?query=bra…
3. Run Terraria with /gldevice:D3D11 as a launch argument
With the vanilla binaries, you should be able to see the title screen and main
menu! However, the in-game screen will be mostly black, since compiling the
shaders with ternaries will fail. (Setting a breakpoint on hlsl_fixme is the
easiest way to catch the issue.)
When we intentionally break MojoShader to avoid ternaries, the game appears to
be okay, ignoring the whole "shader output is obviously incorrect" part:
https://twitter.com/flibitijibibo/status/1640136828433883139
--
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=54777
Bug ID: 54777
Summary: MojoShader HLSL requires 'any' intrinsic, for TEXKILL
Product: vkd3d
Version: 1.7
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: hlsl
Assignee: wine-bugs(a)winehq.org
Reporter: flibitijibibo(a)gmail.com
Distribution: ---
Created attachment 74274
--> https://bugs.winehq.org/attachment.cgi?id=74274
Random TMNT Pixel Shader
From MSDN:
https://learn.microsoft.com/en-us/windows/win32/direct3dhlsl/dx-graphics-hl…
Attached is some sample shader output from TMNT: Shredder's Revenge.
--
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=54786
Bug ID: 54786
Summary: Lethe - Episode One needs 'log' support
Product: vkd3d
Version: 1.7
Hardware: x86-64
OS: Linux
Status: NEW
Severity: minor
Priority: P2
Component: hlsl
Assignee: wine-bugs(a)winehq.org
Reporter: andrey.goosev(a)gmail.com
Distribution: ---
0254:err:d3dcompiler:D3DCompile2 Failed to compile shader, vkd3d result -5.
0254:err:d3dcompiler:D3DCompile2 Shader log:
0254:err:d3dcompiler:D3DCompile2 <anonymous>:336:8: E5017: Aborting due to
not yet implemented feature: Ternary operator.
0254:err:d3dcompiler:D3DCompile2 <anonymous>:372:8: E5017: Aborting due to
not yet implemented feature: Prioritize between multiple compatible function
overloads.
0254:err:d3dcompiler:D3DCompile2 <anonymous>:372:1: W5300: Implicit
truncation of vector type.
0254:err:d3dcompiler:D3DCompile2 <anonymous>:529:15: E5005: Function "log"
is not defined.
1.7-27-gd6d9aab3
--
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.