https://bugs.winehq.org/show_bug.cgi?id=50379
Bug ID: 50379
Summary: The Witcher 3 has broken rendering with Vulkan
renderer
Product: Wine
Version: 6.0-rc3
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 68984
--> https://bugs.winehq.org/attachment.cgi?id=68984
example
In addition all bright parts are blinking.
--
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=50386
Bug ID: 50386
Summary: Sniper Elite V2 some objects aren't rendered with
Vulkan renderer
Product: Wine
Version: 6.0-rc3
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 68996
--> https://bugs.winehq.org/attachment.cgi?id=68996
examples
fixme:d3d:wined3d_context_vk_update_descriptors NULL constant buffer views not
implemented.
err:d3d:wined3d_context_vk_apply_draw_state Failed to update shader
descriptors.
err:d3d:adapter_vk_draw_primitive Failed to apply draw state.
wine-6.0-rc3-24-g3d2b4233288
--
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=48618
Bug ID: 48618
Summary: Wargaming.net Game Center shows black screen on launch
since Wine 5.0
Product: Wine
Version: 5.0
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: chris(a)cjwatts.com
Distribution: ---
Created attachment 66463
--> https://bugs.winehq.org/attachment.cgi?id=66463
Wine stdout log
Confirmed on two different Ubuntu 19.10 machines.
Able to launch World of Tanks directly without much issue, but the Game Center
is just a black screen.
Tried wine-stable 5.0 and wine-staging 5.1 with the same results.
--
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=50424
Bug ID: 50424
Summary: std::mutex crashes on creation
Product: Wine
Version: 4.12.1
Hardware: arm
OS: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: msvcp
Assignee: wine-bugs(a)winehq.org
Reporter: david.paradis(a)us.abb.com
Distribution: ---
Created attachment 69041
--> https://bugs.winehq.org/attachment.cgi?id=69041
Test Project File
I have spent the better half of the last month tracking down a crash in my
application related to the creation of the std::mutex object in my code. After
putting many debugging messages into the Wine code I have finally found what
the issue is. Here is what I have found:
1) In the dlls/msvcp90/msvcp_main.c:init_cxx_funcs() the code is calling
GetProcAddress() for the critical_section methods for ctor, dtor, lock, ... but
never checks to see if we found a valid address for the functions. Later on in
the _Mtx_init_in_situ() a call is made to the critical section ctor and throws
null pointer exceptions because the function pointer is null.
2) In the dlls/concrt140/concrt140.spec there are NO definitions for any ARM
architecture method exports. In the dlls/msvcp90/msvcp90.spec there are
definitions but they are missing in concrt library.
After playing with the concrt140.spec file I was able add the 5 critical
section method exports to the file and was able to verify that I can now create
a std::mutex object and call lock, unlock and other methods on it successfully.
At this point I have no idea how many other ARM methods are missing from the
concrt140.spec list, but the distribution package does not have ANY ARM
definitions in that file.
I am attaching a very simple test CPP file that I was using to verify that the
code is now working for my usage but not completely fixed. With the test code
and the shipping source code you will not get past the point of seeing the
second printf statement after creating the test class, it will crash on the
"test t1;" line.
Thank you
--
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=46709
Bug ID: 46709
Summary: VarFormatCurrency doesn't handle an already formatted
string.
Product: Wine
Version: 4.2
Hardware: x86
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: oleaut32
Assignee: wine-bugs(a)winehq.org
Reporter: leslie_alistair(a)hotmail.com
Distribution: ---
Split off from 46442.
When VarFormatCurrency is passed an already formatted string, eg $9.0, it
returns an error instead of a string.
--
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=30062
Bug #: 30062
Summary: Deer Hunter demo: unable to start a new game (map view
unusable)
Product: Wine
Version: 1.3.18
Platform: x86
URL: http://www.fileplanet.com/28105/20000/fileinfo/Deer-Hu
nter
OS/Version: Linux
Status: NEW
Keywords: download, regression
Severity: normal
Priority: P2
Component: directx-d3d
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: gyebro69(a)gmail.com
CC: hverbeet(a)gmail.com
Classification: Unclassified
Regression SHA1: 926dfc5c49dde8401732a943c1055ba6631bcc5c
Created attachment 39166
--> http://bugs.winehq.org/attachment.cgi?id=39166
terminal output
This bug applies to the first Deer Hunter game in the series, released in 1997.
The game requires Win98 mode to start, and I had to set up virtual desktop
mode.
Steps to reproduce the problem with the demo:
1. Install the demo.
2. Set Windows version to Win98 before launching the game. Start the demo with
DhDemo.exe.
3. In the menu click on <Start New Hunt>, <OK>, <Hunt Here>. Here comes the
problem:
- a map is shown with a crosshair in it. You should be able to change locations
by left-clicking anywhere on the map. This doesn't work: the mouse pointer
disappears when you click on the map.
- the lower part of the screen is missing (showing only a black bar). This is
where certain buttons are located (Hunt, Quit, Help).
- although the buttons at the bottom are missing, you can start a game by
pressing <Enter>. A loading screen is displayed, but the game never loads, it
is freezing with the loading screen.
The problem appeared in 1.3.18 and is still present in 1.4-rc6.
The result of the regression test:
926dfc5c49dde8401732a943c1055ba6631bcc5c is the first bad commit
commit 926dfc5c49dde8401732a943c1055ba6631bcc5c
Author: Henri Verbeet <hverbeet(a)codeweavers.com>
Date: Tue Apr 12 18:28:41 2011 +0200
wined3d: Merge the IWineD3DSwapChain::SetDestWindowOverride()
implementations.
:040000 040000 12437b369aadbbeb6de72ed285f2ced64a7c26b1
025f1e0265b689bf82dd954e1ceb33216af77386 M dlls
Fedora 16
Nvidia 250 / driver 290.10
X.Org X Server 1.11.4
--
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=47915
Bug ID: 47915
Summary: League of Legends 9.20: Crash after champ select
Product: Wine
Version: 4.17
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: mail+wine(a)m-reimer.de
Distribution: ---
Created attachment 65411
--> https://bugs.winehq.org/attachment.cgi?id=65411
Crash dump
Since updating to LoL 9.20 there is a new "crash after champ select" issue.
Probably this is the anticheat, again.
Would be great if some experienced developer could have a look at this.
I've attached my crash dump but the bug is really easy to reproduce. Just try
to open the "practice tool". Will crash immediately when the switch from client
to actual game should happen.
Maybe Andrew Wesie could have a look at this one? He did an remarkably great
job with fixing such things in the past!
--
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=50117
Bug ID: 50117
Summary: winedbg --gdb doesn't work
Product: Wine
Version: 5.18
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: winedbg
Assignee: wine-bugs(a)winehq.org
Reporter: tomsod-m(a)ya.ru
Distribution: ---
After updating wine, winedbg's GDB mode stopped working for me. Instead of
attaching to a program, it starts the program, then terminates itself. The
latest unaffected version is 5.17; 5.18 to 5.21 all have this bug. The default
mode of winedbg (without --gdb) works as expected, however.
Steps to reproduce: run e.g. "winedbg --gdb notepad.exe".
Expected behavior: winedbg stops at notepad's entry point and prompts for
commands.
Observed behavior: winedbg quits almost immediately, notepad runs freely.
--
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=49905
Bug ID: 49905
Summary: VbsEdit runs wscript.exe with unsupported switches /d
and /u
Product: Wine
Version: 5.18
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: wscript
Assignee: wine-bugs(a)winehq.org
Reporter: sloper42(a)yahoo.com
Distribution: ---
Created attachment 68266
--> https://bugs.winehq.org/attachment.cgi?id=68266
patch for wscript
In VbsEdit version 9.2139 from https://www.vbsedit.com/, when choosing "Start
Debugging with wscript", wscript.exe is called with unsupported options /d
(debug) and /u (unicode).
Therefore wscripts bail out and script is not executed.
Solution is to ignore these options.
--
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.