https://bugs.winehq.org/show_bug.cgi?id=46609
Bug ID: 46609
Summary: openbor: executable freezes while loading game (Marvel
Infinity War)
Product: Packaging
Version: unspecified
Hardware: x86-64
OS: Mac OS X
Status: UNCONFIRMED
Severity: blocker
Priority: P2
Component: wine-packages
Assignee: wine-bugs(a)winehq.org
Reporter: cardogar(a)hotmail.com
CC: michael(a)fds-team.de, sebastian(a)fds-team.de
Created attachment 63509
--> https://bugs.winehq.org/attachment.cgi?id=63509
Log file
When running the openbor game Marvel Infinity War the wine-preloder freezes
(not responding).
Game can be downloaded here http://www.zvitor.com.br/Downloads/miw_v1.2.rar
Attached console output.
Games constructed with different openbor engine versions work.
--
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=52837
Bug ID: 52837
Summary: The text cannot be displayed normally in the "小K直播姬"
software
Product: Wine
Version: 7.6
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: 3238998313(a)qq.com
Distribution: ---
Created attachment 72232
--> https://bugs.winehq.org/attachment.cgi?id=72232
The log output from the terminal (the action is recorded).
Run "Little K Live Ji" on the 7.6 version of the development branch, and the
expected version of WineD3D is 1.2.
The packages for Winehq are packaged by the distribution ArchLinux. See the log
file for details. The official website of the software is
https://yunboai.com/liverc; you can also get a complete copy of the software
from here: https://www.123pan.com/s/lgeRVv-zauHd, password: wine.
I looked at the output and everything seems to be working fine until line 1578,
after doing the login it opens a new process and reports back and forth
warnings and errors for d3d11, some modules and WineD3D.
The main thing that affects my continued use of the software is that in this
new process it barely displays text properly and is mostly blank. According to
the information, the software cannot be run directly after the d3dx11 bug patch
is applied by Winetricks.
Main output: MESA-INTEL: warning: Performance support disabled, consider sysctl
dev.i915.perf_stream_paranoid=0
This software has not been tested in versions prior to 7.6.
--
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=41163
Bug ID: 41163
Summary: Minimum memory for Nvidia GTX 1060 should be 3GB
Product: Wine
Version: 1.9.16
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: trivial
Priority: P2
Component: directx-d3d
Assignee: wine-bugs(a)winehq.org
Reporter: markk(a)clara.co.uk
Distribution: ---
In dlls/wined3d/directx.c a comment says
"The amount of video memory stored in the gpu description table is the minimum
amount of video memory "found on a board containing a specific GPU."
The line for Nvidia GTX 1060:
{HW_VENDOR_NVIDIA, CARD_NVIDIA_GEFORCE_GTX1060, "NVIDIA GeForce GTX
1060", DRIVER_NVIDIA_GEFORCE8, 6144},
6144 should probably be changed to 3072, since a 3GB version of the GTX 1060
(with slightly cut-down GPU) has been announced:
http://www.eurogamer.net/articles/digitalfoundry-2016-nvidia-unveils-cut-do…
Either that, or a separate entry for the 3GB model should be added.
Also, in dlls/wined3d/wined3d_private.h is the PCI ID for the GTX 1060:
CARD_NVIDIA_GEFORCE_GTX1060 = 0x1c03,
Nvidia uses 0x1C02 for the 3GB GTX 1060, according to the Windows driver INF
file:
NVIDIA_DEV.1C02.8438.19DA = "NVIDIA GeForce GTX 1060 3GB"
NVIDIA_DEV.1C03.9438.19DA = "NVIDIA GeForce GTX 1060 6GB"
--
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=50661
Bug ID: 50661
Summary: LibvirtTool: Automatically create Windows snapshots
with test signing turned on
Product: Wine-Testbot
Version: unspecified
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: unknown
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
Having test configurations with test signing turned on would be useful:
https://www.winehq.org/pipermail/wine-devel/2020-October/175882.html
There is now one such Windows 10 configuration, w1064_tsign, which was created
manually.
But to generalize this LibvirtTool should know how to turn on test signing
before creating live snapshots. Fortunately this seems pretty simple: just run
"bcdedit /set testsigning on" and reboot. So it should be possible to add that
in Revert().
--
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=44728
Bug ID: 44728
Summary: Bad windows version detection with python module
"platform"
Product: Wine
Version: 3.3
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: gillg02(a)hotmail.com
Distribution: ---
If you use a python script (for exemple built-in into an installer) wich use
native module "platform" to detect OS platform and version, you could have a
bad version number regarding your wine config.
Here, an extract of native "platform.py" file (python 3.5), and the line wich
cause this issue + a test to patch it temporarly.
def win32_ver(release='', version='', csd='', ptype=''):
try:
from sys import getwindowsversion
except ImportError:
return release, version, csd, ptype
try:
from winreg import OpenKeyEx, QueryValueEx, CloseKey,
HKEY_LOCAL_MACHINE
except ImportError:
from _winreg import OpenKeyEx, QueryValueEx, CloseKey,
HKEY_LOCAL_MACHINE
winver = getwindowsversion()
maj, min, build = winver._platform_version or winver[:3]
########## Begin PATCH for WineHQ ############
maj, min, build = winver[:3]
########## End PATCH for WineHQ ############
version = '{0}.{1}.{2}'.format(maj, min, build)
release = (_WIN32_CLIENT_RELEASES.get((maj, min)) or
_WIN32_CLIENT_RELEASES.get((maj, None)) or
release)
For a win10 configured, see dumps below :
winver._platform_version => (5, 1, 2600)
winver[:3] => (10, 0, 15063)
I don't know exactly why, but somwhere in windows confs or dlls something is
wrong.
For information, getwindowsversion() seems to be a wrapper of Win function
GetVersionEx()
--
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=31387
Bug #: 31387
Summary: Helicopter's tail prop is sometimes partly black in
GTAIV
Product: Wine
Version: 1.5.9
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: directx-d3d
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: b7.10110111(a)gmail.com
Classification: Unclassified
Created attachment 41247
--> http://bugs.winehq.org/attachment.cgi?id=41247
Screenshot
This bug is similar to bug 21197, but this particular thing wasn't fixed by the
commit which did fix that bug. See the screenshot. Symptoms are the same - one
of the propeller blades is black with black pixels around.
How to reproduce once in the game:
1. Find/spawn Police Maverick helicopter
2. Get inside it
3. Take off to be about 10 m above ground
4. Press 'S' and hold it so that helicopter punches the ground
5. See the artifact appear
--
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=52777
Bug ID: 52777
Summary: Ghost Recon Advanced Warfighter 2 does not render
shadows
Product: Wine
Version: 7.5
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: directx-d3d
Assignee: wine-bugs(a)winehq.org
Reporter: cmartinez2985(a)gmail.com
Distribution: ---
Shadows in GRAW2 (and GRAW1 which is the same engine) do not render at all, no
matter the selection.
I am running Arch Linux using a Radeon 5700XT on mesa-git 22.1 drivers. The
game uses DX9. Please let me know what I can attach to reproduce the issue.
Side note: this also occurs with DXVK but I've tested with a fresh WINE prefix
without DXVK. The shadows DO render running on Windows 11. This old bug might
have more info: 38015
--
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=41464
Bug ID: 41464
Summary: Quake live sound latency
Product: Wine
Version: 1.9.19
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: directx-dsound
Assignee: wine-bugs(a)winehq.org
Reporter: cosiekvfj(a)o2.pl
Distribution: ---
Hi. I measured sound latency(from fire button to gauntlet noise)(audacity) and
it's about >160ms. For that fast paced game it's to much. Even after tweaking
s_mixprestep and alsa buffer it's still to much.
Soundbackend Alsa
Linux GA-MA790X-DS4 4.6.7-1-MANJARO #1 SMP PREEMPT Tue Aug 16 19:20:55 UTC 2016
x86_64 GNU/Linux
--
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=25173
Summary: No sound in menus/game play in Call Of Duty : Black
Ops
Product: Wine
Version: 1.3.7
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: directx-dsound
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: oneofone(a)gmail.com
Created an attachment (id=31938)
--> (http://bugs.winehq.org/attachment.cgi?id=31938)
WINEDEBUG=+dsound
It's not http://bugs.winehq.org/show_bug.cgi?id=16942 as far as I can tell, I
tried everything.
Clean prefix, winver=windows7, disabled mmdevapi.
When I tried native dsound I lost the sound in the cut scenes.
--
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.