https://bugs.winehq.org/show_bug.cgi?id=53197
Bug ID: 53197
Summary: Shogun Total War 2 needs
d3dx11_42.dll.D3DX11LoadTextureFromTexture.
Product: Wine
Version: 7.11
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: directx-d3d
Assignee: wine-bugs(a)winehq.org
Reporter: hibbsncc1701(a)gmail.com
Distribution: ---
With both wined3d and dxvk, Shogun Total War 2 generates the following in
DirectX 11 mode (on both 32bit native and WoW64 prefixes) before reaching the
game's main menu:
---Log output---
d3d call failed (0x80004001) : unspecified
0100:fixme:d3dx:D3DX11GetImageInfoFromMemory src_data 046FE756, src_data_size
5592532, pump 00000000, img_info 0055CBD0, hresult 00000000 stub!
d3d call failed (0x80004001) : unspecified
0100:fixme:d3dx:D3DX11GetImageInfoFromMemory src_data 046F3D2A, src_data_size
5592532, pump 00000000, img_info 0055CBD0, hresult 00000000 stub!
d3d call failed (0x80004001) : unspecified
0100:fixme:d3dx:D3DX11GetImageInfoFromMemory src_data 046FEA86, src_data_size
5592532, pump 00000000, img_info 0055CBD0, hresult 00000000 stub!
d3d call failed (0x80004001) : unspecified
0100:fixme:d3dx:D3DX11GetImageInfoFromMemory src_data 046F405A, src_data_size
5592532, pump 00000000, img_info 0055CBD0, hresult 00000000 stub!
d3d call failed (0x80004001) : unspecified
wine: Call from 7B0122F6 to unimplemented function
d3dx11_42.dll.D3DX11LoadTextureFromTexture, aborting
0100:fixme:faultrep:ReportFault 0055C6B8 0x0 stub
wine: Unimplemented function d3dx11_42.dll.D3DX11LoadTextureFromTexture called
at address 7B0122F6 (thread 0100), starting debugger...
---Log output---
As a workaround, the game can be played in DirectX 9 mode.
--
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=49674
Bug ID: 49674
Summary: Feature Request: Restoring previous resolution upon an
app crashing
Product: Wine
Version: unspecified
Hardware: Other
OS: other
Status: UNCONFIRMED
Severity: enhancement
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: s.maddox(a)lantizia.me.uk
So this has been a bit of a bug of mine with Wine for a while, but you may
think it's not really a problem Wine should deal with - which may be a fair
point.
But I couldn't find anything clearly asking for this as a feature request... so
lets see how well it fairs.
# The problem
Lets say you open up a Windows executable which changes your screens resolution
(e.g. a game) and it either...
a) freezes
b) is broken enough that its UI (if any appears) can't be used to nicely ask it
to quit
c) crashes and quits differently to how it'd normally do so upon user request
With a) and b) you likely need to kill that process, which ultimately leaves
you in the same situation as c).
But however it happens... you're likely to find your resolution now stuck to
whatever it set. If that is an incredibly low resolution (like 320x240 or
640x480)... then with the desktop environment of today (especially with HiDPI)
you're likely going to struggle finding the proper option to fix it. Worse you
might resort to a terminal (or switch TTY) and mess around with the xrandr
command for a stupid amount of time trying to find the names of screens and
such.
# Expected Behaviour
Well I'm not sure what actually does this. But in actual Windows (e.g Windows
10), when this same circumstance occurs... the resolution is always restored
back to what it was. This leaves me to believe that Windows itself has
something for this eventuality.
# Research
Well I've been searching around for solutions to this one for years and the
best I always come across... is someone saying you're better off with a script
(usually calling xrandr) mapped to a hot key or something for this eventuality.
Which is fine if the number of displays you've got connected and their
resolutions are always consistent... but often for laptop users moving between
docks and such - it isn't.
A quick chat on the #winehq IRC channel had someone mention that Proton can now
scale games to the resolution you're already using instead (when the app
requests a resolution change)... and pointed out these patches...
https://github.com/GloriousEggroll/proton-ge-custom/blob/master/patches/pro…https://github.com/GloriousEggroll/proton-ge-custom/blob/master/patches/pro…
That's fine, and it's a welcome feature. But I do wonder if this is a
universal fix for any request for any resolution change... regardless the age
(and compatibility with which version of Windows it was meant for) of the game
and the way it draws on the screen (e.g. SDL, OpenGL, DirectDraw, Vulkan,
etc...).
However it *may* give some hope for people wanting to run older windowed-mode
games from the early Win 3.1/95 era which refuse to be re-sized/re-scaled...
but that's a topic for another feature request :)
# Conclusion
I've not got any.
Should this be the job of Wine to restore the prior resolution if the app/game
fails to? Like Windows somehow does? Or is this something the OS (whatever
that may be, Linux/macOS or even Windows) should be doing separately from Wine
for any process?
Also if this is a dupe, feel free to mark it as such... I've looked and
couldn't find anything that is quite so specific - at least with the points
raised here.
Thoughts?
--
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=26407
Summary: Shadowgrounds Survivor crashes after viewing the map
Product: Wine
Version: 1.3.15
Platform: x86
URL: http://www.gamershell.com/download_23192.shtml
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: gyebro69(a)gmail.com
Created an attachment (id=33629)
--> (http://bugs.winehq.org/attachment.cgi?id=33629)
terminal output
In the game the crash always occurs when I switch back to normal mode after
viewing the map (by pressing <Tab>).
Sometimes the game "survives" 2-3 switches between the two modes but eventually
it will crash.
How to reproduce the problem in the demo:
1. Choose only Physx and Windows Media Codecs when the installer asks for it
(native d3dx9_36.dll will be placed in the game directory).
2. Start the game either by survivor.exe or with the launcher.
3. Choose <New Game> from the menu. When you gain control over your character
press <Tab> to switch to map mode then press <Tab> again to get back to normal
mode. This might need to be repeated 2-3 times. Sooner or later the game will
crash.
If I don't use the map mode, the game seems to be stable (I've played for about
30-40 minutes).
I can reproduce the crash with Wine-1.0.1, too.
The crash happens even if I lower the gfx details to the minimum and with
disabled audio.
When starting the game with WINEDEBUG=warn+heap (is that the correct syntax?)
the crash doesn't occur.
Fedora 14 x86
Nvidia GeForce 250 / driver 260.19.36
--
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=44625
Bug ID: 44625
Summary: Cybernoid 2 exits but x window drawing updates are
frozen
Product: Wine
Version: 3.2
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: dav75uk(a)yahoo.co.uk
Distribution: ---
You can get this game from
https://www.classic-retro-games.com/games/action/cybernoid-2--the-revenge-3…
When you quit the game, x windows no longer updates the screen - events are
being responded to though (you can click stuff then change to a terminal tty
and back and see the updates). The only way to get back to a sane system is
kill xwindows with ctrl alt backspace.
This is seen on opensuse 42.3 which uses xf86
--
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=31665
Bug #: 31665
Summary: Femap unexpected crash on rebuild database (or any
command that involves it i.e. import)
Product: Wine
Version: 1.5.12
Platform: x86-64
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: dark.schneider(a)iol.it
Classification: Unclassified
Created attachment 41633
--> http://bugs.winehq.org/attachment.cgi?id=41633
Backtrace of crash triggered by file->rebuild in femap 10.3 with wine 1.5.12
1) wine femap.exe
2) file->rebuild...
3) answer yes.
The crash happen with any action that implies a rebuild database by femap. I.e.
if you import a "large" bdf, lunching a rebuild is just a fast way to check if
the bug is present or not.
Wine version I tested without the bug (those are working):
1.0.1
1.1.29
1.3.6
Wine versions i tested with the bug (crash with similar backtrace to one
attached):
1.4.1-2 (from debian repo)
1.5.6-2 (from debian repo)
1.5.12
I have tested with both femap 10.2 and femap 10.3 and they share the same
problem with no difference (i.e. probably the code on their side did not
changed and if someone has an older version around it may show the same bug). I
have not tested Femap 10.3.1, but may show the same problem.
All of this is related to 32 bit version of femap and wine running on a AMD 64
bit system. I have no chance to test 32 bit on 32 bit.
The bug persist on another system with ati/amd video driver, tested with both
open source and closed opposed by this system that has closed source nvidia
blob. Due to this bug seems unrelated to the video rendering (e.g. the problem
with femap not redrawing automatically the gl window looks unrelated, if needed
I can post another bug for that, but it's minor glitch)
Best Regards,
Gabriele Dini Ciacci
P.S.
Unrelated practical thing that make it desirable to have a recent version of
wine working: With 1.5.6-2 and 1.5.12 the program is much faster (especially on
start-up and actually faster than on windows)
--
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=45358
Bug ID: 45358
Summary: AC Syndicate is completely broken
Product: Wine-staging
Version: 3.10
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: berillions(a)gmail.com
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: Debian
Created attachment 61658
--> https://bugs.winehq.org/attachment.cgi?id=61658
Graphic rendering completely broken
Hello,
With wine-3.10, it's possible to launch the game without crash.
Now, there is a very big issue with graphic rendering with wined3d. (see
screenshot)
In the output console, i have a lot of message about :
- "d3d_shader:shader_sm4_read_instruction_modifier Unhandled modifier
0xXXXXXXXX" - "err:d3d:wined3d_debug_callback 0x35451990:
"GL_INVALID_OPERATION in glGetUniformLocation(program not linked)""
- "fixme:d3d_shader:shader_glsl_dump_program_source ..."
- "fixme:d3d:context_bind_shader_resources Shader 0x34e90740 needs 34 samplers,
but only 32 are supported."
For Wine dev who want to reproduce the issue, you need wine-staging to avoid
the issue with UPlay (bug #35902) + Wine AND the issue with AC Syndicate +
Uplay with online mode (bug #45312)
Google drive link for the log :
https://drive.google.com/open?id=15Q2gY9uk_JohSwqlhwix9HK8BgUWCY5E
--
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=44009
Bug ID: 44009
Summary: Syberia Gog version: crash after cinematics
Product: Wine
Version: 2.20
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: legluondunet(a)free.fr
Distribution: ---
Created attachment 59671
--> https://bugs.winehq.org/attachment.cgi?id=59671
Syberia Gog wine 2.20 backtrace
Hello,
I just acquire the Syberia Gog version and it is impossible for me to play this
game on Linux with Wine. Happily the game was free.
How to reproduce:
Install Syberia Gog version
Launch the game, you can see cinematics but just when the menu appear the game
crash.
I joined you the terminal log/backtrace.
Config:
Ubuntu 17.10
Nvidia 384.90
--
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=25009
Summary: Password Memory 2010 - Titlebar color rendering error
Product: Wine
Version: 1.3.6
Platform: x86-64
OS/Version: Linux
Status: UNCONFIRMED
Severity: minor
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: rsflynn(a)gmail.com
Created an attachment (id=31694)
--> (http://bugs.winehq.org/attachment.cgi?id=31694)
Password Memory 2010 Screenshot
Password Memory 2010 v3.0.3
Download URL:
http://download.cnet.com/Password-Memory-2010/3000-18501_4-10770367.html
Titlebar is not rendered correctly. Half the title bar is in the application
default blue, the other half is black.
--
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.
http://bugs.winehq.org/show_bug.cgi?id=29417
Bug #: 29417
Summary: Mouse pointer laggy/slow in Dweebs and Dweebs 2
Product: Wine
Version: 1.3.35
Platform: x86-64
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: markk(a)clara.co.uk
Classification: Unclassified
This bug applies to the games Dweebs and Dweebs 2 by Mutation Software.
Demos can be downloaded from
http://www.tucows.com/preview/272853/DWEEBS-Platinum-Remix
and
http://www.tucows.com/preview/281667/DWEEBS-2-The-New-Breed
Download and run one of the demos. Click Setup. On the title screen the mouse
pointer is fine. However if you click Help, Credits or Exit, the pointer is
very "laggy" on those screens. In-game the pointer lags slightly, but less than
on the Help/Credits/Exit screens.
(Also, with earlier versions of the first Dweebs game -- I tested the one on
the Arcade Master CD published by eGames -- the pointer lags on the title
screen as well.)
I thought this problem might be the same as bug 29325, but it also occurs with
Wine 1.3.31.
--
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.
http://bugs.winehq.org/show_bug.cgi?id=27745
Summary: Racer is unplayable
Product: Wine
Version: 1.3.24
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: bugmenot123456(a)mailinator.com
Created an attachment (id=35498)
--> (http://bugs.winehq.org/attachment.cgi?id=35498)
Output of racer under wine-1.3.24
Racer used to work fine with wine-1.3.14. Somewhere between version 1.3.14 and
1.3.17 it stopped working. Now racer infinitely loops with following error
after pressing "Race" button:
RNetwork: waiting for connecting id response...
RNetwork: out of loop, client connected: 0, id 0 (objectIDbatch=-640664278)
RNetwork: connect attempt failed; be persistent (try 1)
enet_host_connect; out of (1) peers
** Error: QNClient:Connect(); failed to create enet peer; out of connections
Link to the program: http://racer.nl/download/racer0655.zip
--
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.