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=39532
Bug ID: 39532
Summary: Assassin's Creed Unity doesn't run
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: directx-d3dx10
Assignee: wine-bugs(a)winehq.org
Reporter: anakin.cs(a)gmail.com
Distribution: ---
Created attachment 52679
--> https://bugs.winehq.org/attachment.cgi?id=52679
terminal log
I've been trying to run Assassin's Creed Unity from Uplay on my laptop, both on
the Intel card and Nvidia card (with primusrun), and I always get the following
error message (translated from French):
"Can't launch the game. Your video card doesn't support DirectX 11 or the video
drivers need to be updated."
My video card is an Nvidia Geforce 850M.
Attached is the terminal output after trying to launch the game.
--
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=39652
Bug ID: 39652
Summary: Battlefield 2142 Demo fails to start - full DirectX
9.0c installer resolves problem
Product: Wine
Version: 1.8-rc1
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: bob.mt.wya(a)gmail.com
Distribution: ---
Created attachment 52853
--> https://bugs.winehq.org/attachment.cgi?id=52853
battlefield_2142_demo_backtrace
Download from:
http://www.gamershell.com/download_15855.shtml
Installation of the Battlefield 2142 Demo (aka training video simulator 2015)
in clean 32-bit Wineprefix.
Launching game without any winetricks verbs, etc. results in the attached
backtrace and console logs.
Executing:
winetricks directx9
and removing all the Wine library overrides allows the game demo to
successfully launch, display a training video and reach the main login screen
(as it can get - due to the shutdown, last year, of the Gamespy Master
Servers).
I haven't been able to successfully launch the game by installing the
individual components of the DirectX9 installer. I did attempt to do this in a
clean 32-bit Wineprefix.
--
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=21806
Summary: Star Wars Empire at War: Demo crashes during battles
Product: Wine
Version: 1.1.39
Platform: x86-64
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: gaming4jc2(a)yahoo.com
Created an attachment (id=26385)
--> (http://bugs.winehq.org/attachment.cgi?id=26385)
Tutorial 1 debugs, pagefaults, backtraces...
This seems to affect the game any time you are going into battle. At the
loading screen the game will issue a exception.
You have two choices, retry or cancel. I've provided a backtrace log that
results from each selection - as well as the game's built debugger log.
For anyone wishing to confirm, just try Tutorial 1. It will crash in under
2mins. The other tutorials may crash too, but not nearly as often since there's
not many battles to load. I was using the Demo CD I got in a promo.
--
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=40045
Bug ID: 40045
Summary: Thinking Worlds Player: Direct3D 9 application doesn't
display anything
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: directx-d3dx9
Assignee: wine-bugs(a)winehq.org
Reporter: zionnimchuk(a)gmail.com
Distribution: ---
Created attachment 53508
--> https://bugs.winehq.org/attachment.cgi?id=53508
Verbose error log warn+all
Wine runs the application, gets no significant errors, but nothing shows up. I
have to force quit (Ctrl-C) the application to close it.
Tested operating systems: 64-bit Arch Linux, 64-bit Ubuntu 15.10
Wine versions tested: 1.9.2, 1.9.1 (from Arch Linux package)
I initially posted this as a forum post. You can see it here:
https://forum.winehq.org/viewtopic.php?f=8&t=26045
Error log (normal output):
fixme:win:EnumDisplayDevicesW ((null),0,0x32f724,0x00000000), stub!
fixme:console:CONSOLE_DefaultHandler Terminating process 8 on event
If you look at the more verbose error log, you can see, on line 295-298 it
says:
warn:d3d_surface:surface_init Creating a lockable surface with a POOL of
DEFAULT, that doesn't specify DYNAMIC usage.
warn:d3d9:d3d9_swapchain_QueryInterface {580ca87e-1d3c-4d54-991d-b7d3e3c298ce}
not implemented, returning E_NOINTERFACE.
warn:d3d9:d3d9_swapchain_QueryInterface {580ca87e-1d3c-4d54-991d-b7d3e3c298ce}
not implemented, returning E_NOINTERFACE.
warn:d3d9:d3d9_device_QueryInterface {580ca87e-1d3c-4d54-991d-b7d3e3c298ce} not
implemented, returning E_NOINTERFACE.
Which I think is the problem.
You can view the verbose error log (warn+all) here:
http://paste.scratchbook.ch/view/ec9a60dc (same as attachment)
--
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.
http://bugs.winehq.org/show_bug.cgi?id=23124
Summary: Philippine English locale defaults to wrong SUBLANG
Product: Wine
Version: unspecified
Platform: All
OS/Version: All
Status: NEW
Keywords: download, source
Severity: trivial
Priority: P4
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: kennybobs(a)o2.co.uk
I understand that following 1.2 .po file are going to be used, so this should
be easier to resolve then.
Philippine English follows American English rules, but currently defaults to
pick up SUBLANG_NEUTRAL which is British English. It should be picking up
SUBLANG_DEFAULT for American English.
I'm not sure if this can be changed before the introduction of .po files but
it's not urgent.
http://en.wikipedia.org/wiki/Philippine_English
--
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=44863
Bug ID: 44863
Summary: Performance regression in Prince of Persia 3D
Product: Wine
Version: unspecified
Hardware: x86
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: directx-d3d
Assignee: wine-bugs(a)winehq.org
Reporter: stefan(a)codeweavers.com
Distribution: ---
Prince of Persia 3D's performance went from perfectly smooth to about 0.5 fps.
I suspect 0b92a6fba7a6e60c6ff1a3729a3b21019c2df0ce is to blame, but I have not
run a regression test yet.
The problem is that the game creates a rather large (2MB)
D3DVBCAPS_SYSTEMMEMORY, maps it (the entire buffer due to API limitations),
writes a handful of vertices and draws a handful of vertices. Currently wined3d
uploads the entire 2MB, evicts the sysmem copy and downloads it from the GPU
every map / unmap / draw cycle.
The most obvious performance fix is not to create a VBO. Doing this restores
the performance, but questions remain.
On startup, the game writes "NetImmerse D3DDriver Info: Hardware supports
system memory textures" and "NetImmerse D3DDriver Info: No AGP support
detected". The first info seems wrong, so it is possible that the game enters a
codepath it does not choose on Windows.
Not creating a VBO is not an option on Core Contexts, so I investigated what's
going wrong with the PBO codepath on. First of all, evicting the sysmem copy
seems like a bad choice. It happens because ddraw buffers are not marked
dynamic. We may want to chance this. The game uses d3d3, so there's no
DDLOCK_DISCARDCONTENTS. The game passes DDLOCK_WAIT | DDLOCK_WRITEONLY to
IDirect3DVertexBuffer::Lock.
Commenting out the eviction call improves performance quite a bit, but it is
still noticeably slow. wined3d_buffer_map maps through heap_memory instead of
glMapBuffer because of the "(flags & WINED3D_MAP_WRITE) && !(flags &
(WINED3D_MAP_NOOVERWRITE | WINED3D_MAP_DISCARD))" condition.
Removing this condition uses glMapBuffer, but does not improve performance. It
seems the large glMapBuffer is still slow, at least on OSX with legacy
contexts.
So there are a few questions that need to be answered:
*) Is the game using a broken codepath?
*) Write tests for sysmem buffers
*) Consider making all d3d3 buffers dynamic
*) Test if the glMapBuffer path is fast on Linux
*) Investigate if Core Contexts + GL_ARB_buffer_storage help on OSX.
--
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=44315
Bug ID: 44315
Summary: Guild Wars 2 - Slow Performance since Wine 2.1
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: jonfarr87(a)gmail.com
Distribution: Mint
Created attachment 60162
--> https://bugs.winehq.org/attachment.cgi?id=60162
Screenshot showing performance between old and newer Wine versions.
Wine 2.0 (with Staging patches) was the last version to run this game at a good
performance, From 2.1 up to 3.0rc5 it results in a major framerate loss in
every aspect of the game. The staging versions (up to 2.21) perform the same as
"non staging" Wine.
While no other of my tested games were affected, it looks as if something in
CSMT was changed and affected this particular title. I've tested this across
multiple system configurations and the results are always the same.
Considering how much this game struggles to maintain a playable framerate, a
loss of 15-25 frames (depending on the situation) is a bit excessive.
Screenshot attached, showing the frames difference in an instanced area of game
where the performance can easily be used as a "benchmark".
Tests have been performed on 3 systems:
Ryzen 1700X
16GB DDR4 2800MHZ Ram
Nvidia GTX 1060 / v384.98 Drivers
-------------------------------------------
i5-4590
8GB DDR3 Ram
Nvidia GTX 960 / 384.98 Drivers
-------------------------------------------
i5-2400
8GB DDR3 Ram
Nvidia GTX 760 / 375.66 Drivers
--
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.