https://bugs.winehq.org/show_bug.cgi?id=56317
Bug ID: 56317
Summary: Falcon BMS 4.37 crashes on start (not fully
implemented d3dx:D3DX11CreateTextureFromFileA)
Product: Wine
Version: 9.1
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: d3d
Assignee: wine-bugs(a)winehq.org
Reporter: xeno(a)x-s.com.pl
Distribution: ---
Created attachment 76046
--> https://bugs.winehq.org/attachment.cgi?id=76046
Launch log
Falcon 4 BMS 4.37 startup never goes further than splashscreen. If launched
from terminal following error messagee can be found:
0124:fixme:d3dx:D3DX11CreateTextureFromFileA device 00000000012F4298, filename
"E:\\Falcon_BMS_4.37/Data/Engine/Textures/Default.dds", load_info
0000000000000000, pump 0000000000000000, texture 00000000367CC0D0, hresult
0000000000000000 stub.
Steps to reproduce (in fresh Win64 bit prefix):
- install DXVK
- install original Falcon 4 (needed by Falcon BMS installer to proceed due
legal agreement)
- install Falcon BMS 4.37 with without optional DirectX installation (here
Falcon BMS 4.37.3 full installer was used)
- launch main Falcon binary
env WINEPREFIX="/home/Xeno/.local/share/wineprefixes/<your_prefix_name>"
wine <path_to_BMS-dir>/Bin/x64/Falcon\ BMS.exe
Expected result:
Game shows main UI screen after splashscreen and intro are displayed.
Actual result:
Game loading is stuck at splashscreen terminal output is spammed with error
messages.
Known workaround: once d3dx11_43 external library is installed game launches
properly
--
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=53428
Bug ID: 53428
Summary: 18ae96e5fb causes deadlocking on nvidia hardware
Product: Wine
Version: 7.13
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: d3d
Assignee: wine-bugs(a)winehq.org
Reporter: hibbsncc1701(a)gmail.com
Distribution: ---
This bug is split from Bug #53372. Testing in that bug (See Zeb's comment:
https://bugs.winehq.org/show_bug.cgi?id=53372#c9) reveals that commit
18ae96e5fb3cbbd53f1a022ba81203de6b431228 causes deadlocking to occur in some
programs on Nvidia hardware.
Reverting the patch does fix it, but obviously that is not ideal. As per Zeb's
request I've created this bug.
--
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=49667
Bug ID: 49667
Summary: user32-rawinput-mouse: can't use other programs
normally while running Elite Dangerous
Product: Wine-staging
Version: 5.14
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: kolAflash(a)kolahilft.de
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ---
This is mouse bug is analogous to this keyboard bug:
https://bugs.winehq.org/show_bug.cgi?id=48419
When user32-rawinput-mouse is being used, it's problematic to click onto other
X11 windows while a "Elite Dangerous" is running.
In detail:
1. configure "virtual desktop" mode via winecfg
2. Start EliteDangerous in Wine
3. Open a view inside EliteDangerous where every mouseclick (independent of
cursor position) will have an effect (e.g. cockpit mode -> mouse-1 fires
weapon)
4. switch to another X11 window (e.g. Firefox)
5. click onto something
When clicking in Firefox, the click also get send into the game. So e.g. the
primary weapon gets fired in the game.
Alternatively, the cursor can also positioned over an ingame button (e.g. in
the main menu). Then get another window into foreground without moving the
mouse (e.g. alt-tab) and then click. This will trigger the ingame button over
which the cursor lasted before switching windows.
Workaround:
./patches/patchinstall.sh DESTDIR=../wine-5.14 --all -W user32-rawinput-mouse
-W user32-rawinput-mouse-experimental -W user32-rawinput-hid
(user32-rawinput-mouse-experimental and user32-rawinput-hid depend on
user32-rawinput-mouse)
For more details, please see:
https://bugs.winehq.org/show_bug.cgi?id=48419#c5
--
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=44613
Bug ID: 44613
Summary: Stronghold 2 Deluxe fails to compile shaders on
startup with builtin d2dx9_27.dll
Product: Wine
Version: 2.21
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: directx-d3dx9
Assignee: wine-bugs(a)winehq.org
Reporter: alexander-winehq(a)xmine128.tk
Distribution: ---
Created attachment 60601
--> https://bugs.winehq.org/attachment.cgi?id=60601
WINE console output
Summary
=======
Stronghold 2 works perfectly when placing a native d3dx9_27.dll in
$WINEPREFIX/dosdevices/c:/windows/syswow64
or by running `winetricks d3dx9_27` (the override done by winetricks is not
needed).
However when starting the game without the library present it will show many
dialog box with shader compilation errors, before crashing (see attachment 2
for a selection).
A few examples:
* Error: Unable to open include file ../PhongShader.fx
Warning: Unmatched #if/#endif at end of file
Error: Unexpected end of file during preprocessing
Error: syntax error
* Error: Unable to open include file ../PhongShader.fx
* Error: Unable to open include file ../LifeStudioHeadLighting.fx
Error: Unable to open include file ../TransformState.fx
Finally the error message “Failed to load shared effects parameter file.
Rendering may appear incorrect.” is displayed and the game segfaults.
Meanwhile a bunch of fixmes will be logged to the console (see attachement 1).
Steps to reproduce
==================
Full game
---------
1. Install Stronghold 2 v1.0 German from ISO-image of the retail CDs
2. Download and install the [v1.4 “Deluxe”
patch](http://www.4players.de/4players.php/download_info/Downloads/Download/46369/Stronghold_2/Patch_14.html)
3. Apply NoCD crack if you don't actually have a CD drive (like me)
4. Start game
The Stronghold 2 Demo is not affected unfortunately.
--
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=56414
Bug ID: 56414
Summary: Cannot run SketchWow with Wine on Linux Mint 21.3
Product: Wine
Version: 6.0.3
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: thirdspacedavid(a)gmail.com
Distribution: ---
Created attachment 76177
--> https://bugs.winehq.org/attachment.cgi?id=76177
Backtrace for SketchWow
I am trying to run SketchWow on my new Linux Mint 21.3 system with Cinnamon. It
seems to install okay, but it give an error when I try to run it. I have tried
to upgrade to Wine 9, but I have not been able to get the repository to work
yet. I am attaching the backtrace file
--
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=56383
Bug ID: 56383
Summary: d3d11_device_CheckFormatSupport does not support
D3D11_FORMAT_SUPPORT_DISPLAY
Product: Wine
Version: 9.3
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: d3d
Assignee: wine-bugs(a)winehq.org
Reporter: madewokherd(a)gmail.com
Distribution: ---
FNA3D 24.02 is broken in Wine because it checks for the
D3D11_FORMAT_SUPPORT_DISPLAY flag, even for formats that should always work,
and Wine's implementation doesn't return that flag. Found when merging FNA
updates into Wine Mono. FNA3D 24.03 added a work-around for this, but they'd
like to remove it when Wine is fixed.
Wine already has a test for this with a todo in check_format_support.
See also: https://github.com/FNA-XNA/FNA3D/issues/199
--
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=56415
Bug ID: 56415
Summary: Some apps will break window decorations on kde plasma
6
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: winex11.drv
Assignee: wine-bugs(a)winehq.org
Reporter: dandraghas(a)gmail.com
Distribution: ---
Created attachment 76178
--> https://bugs.winehq.org/attachment.cgi?id=76178
Satisfactory running through wine
After plasma 6 is released some apps(particularly games) will break buttons on
window decorations
tested:
GPU-Z
Rockstar games launcher
Overwatch 2
Satisfactory
each app has different steps to reproduce that, on satisfactory it happens the
moment you launch it, on other ones you need to launch and then close it,
others like overwatch 2 it can occur randomly
Operating System: Arch Linux
KDE Plasma Version: 6.0.1
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2
Kernel Version: 6.7.9-zen1-1-zen (64-bit)
Graphics Platform: Wayland
Processors: 8 × Intel® Core™ i3-10100F CPU @ 3.60GHz
Memory: 15.5 GiB of RAM
Graphics Processor: NVIDIA GeForce GTX 1050 Ti/PCIe/SSE2
Manufacturer: ASUS
--
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=56412
Bug ID: 56412
Summary: cslol-manager Failed to find kernel32 ptr CreateFileA
Product: Wine
Version: 9.3
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: kernel32
Assignee: wine-bugs(a)winehq.org
Reporter: Deresiant(a)protonmail.ch
Distribution: ---
Created attachment 76174
--> https://bugs.winehq.org/attachment.cgi?id=76174
WINEDEBUG=+seh,warn+all wine cslol-manager.exe
cslol-manager fails to patch custom skin into game, saying "Failed to find
kernel32 ptr CreateFileA"
I press "run" in the program after line 201 in the winelog.txt
It pauses for a moment at line 497 in the winelog.txt before failing and
displaying an error.
The error the program displays is at this line:
https://github.com/LeagueToolkit/cslol-manager/blob/86ba488aa5a8b92bc3a25c6…
--
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=45780
Bug ID: 45780
Summary: Zeplin installer does not start
Product: Wine
Version: 3.15
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: blocker
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: rpeccolo(a)pratura.io
Distribution: ---
Created attachment 62236
--> https://bugs.winehq.org/attachment.cgi?id=62236
console output when trying to install zeplin
doing wine zeplin-installer does not 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=56388
Bug ID: 56388
Summary: Regression: Fullscreen apps show on wrong monitor and
don't respond to mouse events properly
Product: Wine
Version: 9.0
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: fabien(a)cournoyer.club
Distribution: ---
Created attachment 76135
--> https://bugs.winehq.org/attachment.cgi?id=76135
Video showing the bug.
I don't have anything more to say. Using Steam Proton 9.0 to run a fullscreen
app doesn't open it on the default screen for some reason. Though, the mouse
works perfectly fine. Trying to fullscreen it on the right screen, I can't use
mouse properly... In this case,it seems that only the left section is really
working. Probably since I have a 1080p main screen and a 768p secondary display
on the left, thinking it's 1080p fullscreen on the left 768p screen? It's realy
weird.
In the video, i go, starting fullscreen on the main screen:
Windowed
Go on the left display (notice the change in size)
Go back to the main display
This is really frustrating...
--
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.