[Bug 59599] New: bug in wow64 some for 32-bit games with AMD integrated (660m) and discrete Nvidia graphics (RTX 4050 laptop)

[WineHQ Bugzilla]

http://bugs.winehq.org/show_bug.cgi?id=59599

            Bug ID: 59599
           Summary: bug in wow64 some for 32-bit games with AMD integrated
                    (660m) and discrete Nvidia graphics (RTX 4050 laptop)
           Product: Wine
           Version: 11.5
          Hardware: x86-64
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: -unknown
          Assignee: [e-mail]
          Reporter: [e-mail]
      Distribution: ---

I have fedora 43 installed and use lutris to install and manage my windows
32-bit games (ranging windows 95 era to XP era and dos games)

when I install the latest winehq-staging from your fedora 42/43 repos, some
windows XP era 32-bit games install but runs weird or not at all. for example
when I try play "alter ego" from 2010.

The game installs but when choosing the to use the Nvidia graphics - it say
video mode not supported.
When the AMD i-gpu, it loads, the background load but no 3d models shows at
all, only way to fix is to set the games options shader level to 0 instead of 2
(only those options for them) changing this option for Nvidia graphic does
nothing to fix the problem.

however when install an older winehq-staging from your fedora 39/40 repos and
try again everything work with this game and actually allows to create 32-bit
prefix (fedora 39 repo not fedora 40) repo) but it breaks 64-bit compatibly
because of broken dependencies with libavcodec.so.60, libavformat.so.60 &
libavutil.so.58 as fedora 43 use newer versions and symlinking the files do not
work.

using the winehq-staging from your fedora 41 repo - produces a black screen
when game is started.

is the way to update version in fedora 39/40 repos use to updated
libavcodec.so.61, libavformat.so.61 & libavutil.so.59 or let the latest version
able to fully create 32-bit prefixes (also allow older 16-bit compatibly) and
not solely use wow64 mode because it doesn't work for everything

-- 
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.