https://bugs.winehq.org/show_bug.cgi?id=51266
Bug ID: 51266
Summary: S.T.A.L.K.E.R. Anomaly 1.5.1: AI Targeting Is Broken
Product: Wine
Version: 6.10
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: jpreston0(a)yahoo.com
Distribution: ---
Version of application:
1.5.1 from
https://www.moddb.com/mods/stalker-anomaly/downloads/stalker-anomaly-151
Wine versions tested:
Wine-staging 6.9
Wine-staging 6.10 from 3 sources: Fedora repos, WineHQ repos, TkG
Synopsis:
Starting in Wine 6.10, most of the AI in S.T.A.L.K.E.R. Anomaly are incapable
of targeting other NPCs or the player and NPCs are unable to fire their weapons
at a target. The player is still able to perform normal functions. Game's
console (~) doesn't show anything unusual when compared between 6.9 and 6.10.
Of the three sources of 6.10 tested: one from the Fedora repos, one from the
WineHQ Fedora repos, and a Wine with additional patches, all three exhibited
the same behavior.
Video of issue in 6.10:
https://streamable.com/cm5io0
Zombified NPCs don't target and fire at the player, only move to the last
position of the player if they make noise or injure them. Zombies don't melee
the player, simply continually walk into the player. NPCs aren't shooting the
zombifieds or zombies. Enemy NPCs run away and don't fire at the player. The
only functioning AI is the bloodsucker which is still partially broken and
takes several seconds to acknowledge the player is there. The issue is
intermittent, sometimes a single AI will begin working after several seconds.
However after relaunching the game the behavior will change and they may stop
working.
Video of what is the normal outcome in 6.9 and previous versions:
https://streamable.com/vcktk4
S.T.A.L.K.E.R. Anomaly is free and standalone so can be tested easily. Only
requires d3dx11_43, d3dcompiler_43, and d3dx9 to run, with dxvk to get
acceptable framerates. Debug mode can be entered by launching the game with
-dbg and hitting numpad 0 to enter flycam, enter to teleport player to camera
position. There's an unrelated Wine issue with the game crashing when opening
the options menu, so set resolution with the launcher if needed.
I haven't tested if this issue also happens in the base S.T.A.L.K.E.R. games or
other mods. And yes, I don't have any mods to Anomaly installed.
As for debug logs, I have no idea where to start.
--
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=51214
Bug ID: 51214
Summary: rundll.exe and winoldap.mod crash
Product: Wine
Version: 6.9
Hardware: x86-64
OS: Linux
Status: NEW
Keywords: regression, source, win16
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: z.figura12(a)gmail.com
Distribution: ---
When run directly (e.g. `wine rundll.exe`, `wine winoldap.mod`) or when
launched via WinExec.
Both seem to crash the same way. It looks like wine is trying to execute the
fake executable.
Obviously a regression; I'll start working on a bisect if it's not already
obvious what the solution is.
--
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=21259
Summary: Visual C++ 2005 Trial build hangs on first run after a
reboot
Product: Wine
Version: 1.1.35
Platform: x86
OS/Version: Linux
Status: NEW
Keywords: download, testcase
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: dank(a)kegel.com
Created an attachment (id=25560)
--> (http://bugs.winehq.org/attachment.cgi?id=25560)
Shell script to download an example project, install Visual C++ 2005 trial, and
build the project.
Visual C++ can build projects from the commandline with
devenv projectname.sln /build Debug
but oddly, the first time you try this on Wine, it hangs.
^C and rerunning fixes it. After the ^C, you can see
mspdbsrv.exe -start -spawn
running, so evidently the first run spawned the
pdb service but then stumbled trying to connect to it;
the second run connected fine.
I'll attach a canned script that reproduces the problem from scratch.
--
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=49395
Bug ID: 49395
Summary: Altium Designer 20 crashes with E_NOINTERFACE
apparently from CreateDxgiSurfaceRenderTarget
Product: Wine
Version: 5.10
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: d2d
Assignee: wine-bugs(a)winehq.org
Reporter: me+wine(a)shane.sh
Distribution: ---
Created attachment 67463
--> https://bugs.winehq.org/attachment.cgi?id=67463
Crash log from Altium
I'm trying to get Altium Designer 20 running in wine. I'm using wine-staging
5.10 with the msxml6 and dotnet461 winetricks. The winetricks are necessary to
get the application to start, and wine-staging because it includes a fix for
https://bugs.winehq.org/show_bug.cgi?id=46568. I'm also using the patch from
https://bugs.winehq.org/show_bug.cgi?id=49379.
The crash log from Altium indicates says that the C# function
SharpDX.Direct2D1.Factory.CreateDxgiSurfaceRenderTarget received a HRESULT of
E_NOINTERFACE. I don't understand how FFI works in C#, but SharpDX is
open-source and
https://github.com/sharpdx/SharpDX/blob/master/Source/SharpDX.Direct2D1/Map…
and
https://github.com/sharpdx/SharpDX/blob/master/Source/SharpDX.Direct2D1/Ren…
seem like relevant parts of the code. Presumably though this just gets mapped
to d2d_factory_CreateDxgiSurfaceRenderTarget from dlls/d2d1/factory.c.
Also relevant is that the following shows up in STDERR when running wine at the
same time as the crash:
00c4:fixme:d2d:d2d_d3d_create_render_target Ignoring render target usage 0x2.
And d2d_d3d_create_render_target is indeed called at the end of
d2d_factory_CreateDxgiSurfaceRenderTarget, so it seems to get at least that
far.
But from reading the source of d2d_d3d_create_render_target, I don't see how it
could ever return E_NOINTERFACE without at least printing some additional
warnings, but I don't see any.
Any help would be greatly appreciated!
--
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=34045
Bug #: 34045
Summary: Gray Matter demo needs .NET Framework and DirectX for
launching
Product: Wine
Version: 1.6-rc5
Platform: x86
URL: http://www.fileplanet.com/217641/210000/fileinfo/Gray-
Matter-Demo
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: andrey.goosev(a)gmail.com
CC: andrey.goosev(a)gmail.com
Classification: Unclassified
Created attachment 45246
--> http://bugs.winehq.org/attachment.cgi?id=45246
config-log
Demo installs .NET Framework. No version showing. At the end of installation
has failed with that. I did installation manually from winetricks ver. 2.0 and
run config.exe
(see config log and pic)
I can't change the settings because of text in drop-down menus is missing.
Installation of Directx is solving this only partially.
--
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=51347
Bug ID: 51347
Summary: Installation for QQ cannot proceed
Product: Wine
Version: 6.11
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: amie1972(a)163.com
Distribution: ---
Installation for QQ cannot proceed because "安装路径无效,您没有权限在此位置写入数据”。
--
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=51278
Bug ID: 51278
Summary: wine packages for ubuntu have dependency glitch
Product: Wine
Version: 6.10
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: johnpgoodman(a)gmail.com
Distribution: ---
Created attachment 70162
--> https://bugs.winehq.org/attachment.cgi?id=70162
terminal output
Fresh kubuntu install then add backports ppa to update to latest kde then
install wine = fail due to dependency clash.
I'm not skilled in how apt works to give much more detail but terminal output
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=50793
Bug ID: 50793
Summary: Regression: Far Cry crashes on launch
Product: Wine
Version: 6.3
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: ntdll
Assignee: wine-bugs(a)winehq.org
Reporter: alasky(a)codeweavers.com
Distribution: ---
Far Cry (running through Steam, steam app id:13520) crashes on launch with the
latest wine master (9107f591d3d73a3b4040db2e13ef51d9846591c9 from 20210309). I
ran a git bisect which blamed the following commit:
e341d1f695311725752c287057f6c6ab60fdf2a3
ntdll: Restore all non-volatile i386 registers in syscall dispatcher
I reverted the commit on the latest wine tip (which was messy and I had to
resolve a conflict, so treat with mild suspicion), and confirmed that the Far
Cry crash on launch was fixed with the commit reverted.
Attached is a +tid,+seh log of the crash on the latest wine master.
--
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=50506
Bug ID: 50506
Summary: Do not receive WM_INPUT messages for game controllers
registered with RegisterRawInputDevices
Product: Wine
Version: 6.0
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: blocker
Priority: P2
Component: user32
Assignee: wine-bugs(a)winehq.org
Reporter: lunarlambda(a)gmail.com
Distribution: ---
I am using RegisterRawInputDevices with HID_USAGE_PAGE_GENERIC,
HID_USAGE_GENERIC_JOYSTICK, and HID_USAGE_GENERIC_GAMEPAD.
My controller (Nintendo Switch Pro Controller) shows up in joy.cpl, and input
works.
The controller shows up in GetRawInputDeviceList, I can query it with
GetRawInputDeviceInfo, and opening it and getting the product name via
HidD_GetProductString also works.
However, my window simply never receives any WM_INPUT messages.
If I register a keyboard instead (HID_USAGE_GENERIC_KEYBOARD), using the same
code, I do get WM_INPUT messages.
I was hopeful that this had been fixed in 6.0, but I was looking through
dlls/user32/rawinput.c, but I cannot find anything indicative of a lack of
support.
--
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=33421
Bug #: 33421
Summary: Cypress PSoCCreator Installer fails with "You have
insufficient privileges to run CyInstaller..."
Product: Wine
Version: unspecified
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: terry(a)maximatcher.com
Classification: Unclassified
wine-1.5.28-114-g60faef8
PSoCCreatorSetup_2.2_cp5.exe
wine runs the extractor, starts the PSoCCreator InstallShield Wizard, then
throws the error window with "You have insufficient privileges to run
CyInstaller. Please contact you(sic) administrator. CyInstaller will now exit"
--
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.