https://bugs.winehq.org/show_bug.cgi?id=46218
Bug ID: 46218
Summary: World of Warcraft A streaming error has occurred.
(WOW51900322) - wine-staging
Product: Wine-staging
Version: 3.21
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: o.dierick(a)piezo-forte.be
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ---
World of Warcraft kicks the player back to the login screen with the error "A
streaming error has occurred. (WOW51900322)" a few seconds after choosing a
character and entering the game world.
The issue has been reported on the AppDB, WineHQ forums and eu/us blizzard
forums. The issue affects Linux players only.
See the How-to / Notes section of
https://appdb.winehq.org/objectManager.php?sClass=version&iId=36961
The workaround is to remove and replace the Cache directory in Program Files
(x86)\World of Warcraft\ by a Windows copy of the cache.
I experience the issue since I upgraded to Debian 9 and got rid of bug 42874.
I made several tests and pin-pointed the issue to the creaturecache.wdb and
gameobjectcache.wdb in World of Warcraft\Cache\WDB\ being corrupt when created.
I compiled a custom wine version : plain wine 3.21 + staged patchset from bug
45349 (with its staging dependencies).
With that custom version the Cache files are NOT corrupt and the issue doesn't
happen.
The 64-bit client requires wine-staging (bug 45349).
I have no knowledge of the issue with 32 bit version of the client and can't
test it myself due to (abandoned) bug 43656.
If the bug is indeed a regression in wine-staging, I guess people using
wine-staging to run the 32 bit game client also have the issue.
I'm currently conducting a regression test in wine-staging to pin-point the
patchset that causes the wrong file creation.
--
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=32096
Bug #: 32096
Summary: drawStridedSlow can be more efficient
Product: Wine
Version: unspecified
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: enhancement
Priority: P2
Component: directx-d3d
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: guillaum.bouchard(a)gmail.com
Classification: Unclassified
Hi,
Recently I noticed that World of Warcaft is far more slow on d3d9 mode than
using the OpenGL mode on my computer (pentium 4 and geforce 5 fx).
Unfortunately the OpenGL mode is unusable since last WoW update (bug is inside
WoW, not wine)
D3D mode is slower because an important amount of the primitives are rendered
using drawStridedSlow (dlls/wined3d/drawprim.c) which generates a lot of opengl
call (here, 600K calls compared to 12K in OpenGL mode).
It appears that if the computer can handle vertex array (ie:
glDrawElements/glDrawArrays/gl[Vertex|Color|TexCoords|Fog]Pointer and
glClientActiveTexture) the number of openGL call can be dramatically reduced,
leading to an important increase in FPS (8 to 25 in important city in WoW).
On my computer, I hacked inside drawStritedSlow and I have only one issue, the
format of color is packed in BGRA, which is not compatible with the format
awaited by glColorPointer. This can be fixed using the extension
ARB_vertex_array_BGRA, which is unfortunately not available on my computer. I
solved this issue by looping over each vertex and building a custom array in
memory that I submitted to glColorPointer. I got approximately the same FPS
increase using this approach.
My conclusions here are that the fallback to drawStridedSlow is a bit extreme
and in most case unnecessary. In my configuration everything works except the
conversion from the d3d BGRA format for color in RGBA. This part can be easily
done in software to create a suitable color array. Also, I did not dig inside
the shader code of wined3d, but perhaps this conversion can be simply
implemented as a swizzle in the custom vertex shader. (am I right guessing that
wined3d does not uses the default shader of the fixed pipeline ?).
So this bug report is more a way of opening the discussion. I see many options
to improve the situation:
a) Tweak the heuristics which detects and fallbacks to drawStridedSlow. If
necessary implements the needed conversions in software. But this will not
generates OpenGL function call and will increase performance a bit
b) Tweak the vertex shader to do the conversion in the vertex shader, I think
it is our best option
c) Tweak drawStridedSlow to still rely on vertex array when possible (I have an
example of code which is doing this. I'm playing WoW with this since 3 days
without any issue and with a FPS increase of 200%). I don't think that honestly
it is the good idea.
d) do something else. Because I did not read anything else than the
drawStritedSlow function, I may have missed something important.
I'm motivated to help in the DX -> GL code. I'm a skilled C and GL coder, I
don't know DX, but can learn enough. Thank you for reading.
--
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=46550
Bug ID: 46550
Summary: Please clean up filever.exe
Product: Wine-staging
Version: 4.0-rc6
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: ToddAndMargo(a)zoho.com
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ---
$ rpm -qa wine-core
wine-core-4.0-0.5.rc6.fc29.i686
wine-core-4.0-0.5.rc6.fc29.x86_64
Would you please clean up filever.exe (from Windows 7)
$ wine /home/linuxutil/filever.exe
000b:fixme:winediag:start_process Wine Staging 4.0-rc6 is a testing version
containing experimental patches.
000b:fixme:winediag:start_process Please mention your exact version when filing
bug reports on winehq.org.
0011:fixme:module:load_dll Loader redirect from L"uxtheme.dll" to
L"uxtheme-gtk.dll"
0011:fixme:uxthemegtk:load_gtk3_libs Wine cannot find the libgtk-3.so.0
library.
0014:fixme:module:load_dll Loader redirect from L"uxtheme.dll" to
L"uxtheme-gtk.dll"
0014:fixme:uxthemegtk:load_gtk3_libs Wine cannot find the libgtk-3.so.0
library.
0014:fixme:heap:RtlSetHeapInformation (nil) 1 (nil) 0 stub
0014:fixme:process:SetProcessDEPPolicy (1): stub
0014:fixme:heap:RtlSetHeapInformation (nil) 1 (nil) 0 stub
000d:fixme:module:load_dll Loader redirect from L"uxtheme.dll" to
L"uxtheme-gtk.dll"
000d:fixme:uxthemegtk:load_gtk3_libs Wine cannot find the libgtk-3.so.0
library.
001f:fixme:module:load_dll Loader redirect from L"uxtheme.dll" to
L"uxtheme-gtk.dll"
001f:fixme:uxthemegtk:load_gtk3_libs Wine cannot find the libgtk-3.so.0
library.
001f:fixme:heap:RtlSetHeapInformation (nil) 1 (nil) 0 stub
0023:fixme:nls:GetThreadPreferredUILanguages 00000034, 0x9cf5e8, 0x9cf658
0x9cf5f0
0023:fixme:nls:get_dummy_preferred_ui_language (0x34 0x9cf5e8 0x9cf658
0x9cf5f0) returning a dummy value (current locale)
000b:fixme:module:load_dll Loader redirect from L"uxtheme.dll" to
L"uxtheme-gtk.dll"
000b:fixme:uxthemegtk:load_gtk3_libs Wine cannot find the libgtk-3.so.0
library.
Prints file version information.
Z:\home\linuxutil\filever.exe [/S] [/V] [/E] [/X] [/B] [/A] [/D]
[[drive:][path][filename]]
/S Displays files in specified directory and all subdirectories.
/V List verbose version information if available.
/E List executables only.
/X Displays short names generated for non-8dot3 file names.
/B Uses bare format (no dir listing).
/A Don't display file attributes.
/D Don't display file date and time.
--
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=46389
Bug ID: 46389
Summary: valgrind errors in loader when loading a dll
Product: Wine
Version: 4.0-rc4
Hardware: x86
OS: Linux
Status: NEW
Keywords: download, source, testcase, valgrind
Severity: major
Priority: P2
Component: loader
Assignee: wine-bugs(a)winehq.org
Reporter: austinenglish(a)gmail.com
Distribution: ---
Split off from bug 36095
k
Seems I was mistaken, (at least) one of these is still present (I didn't
realize it was in the 'always ignore' rather than the 'to be fixed' category):
==29772== 32 bytes in 1 blocks are possibly lost in loss record 101 of 360
==29772== at 0x7BC48394: notify_alloc (heap.c:260)
==29772== by 0x7BC4B8B8: RtlAllocateHeap (heap.c:1726)
==29772== by 0x7BC6E013: RtlAnsiStringToUnicodeString (rtlstr.c:696)
==29772== by 0x7BC6E078: RtlCreateUnicodeStringFromAsciiz (rtlstr.c:303)
==29772== by 0x7BC54377: init_load_order (loadorder.c:252)
==29772== by 0x7BC548B9: get_load_order (loadorder.c:439)
==29772== by 0x7BC51F63: load_dll (loader.c:2519)
==29772== by 0x7BC53148: LdrLoadDll (loader.c:2599)
==29772== by 0x7B455BBE: load_library (module.c:975)
==29772== by 0x7B455CA0: LoadLibraryExW (module.c:1035)
==29772== by 0x7B46450D: __wine_kernel_init (process.c:1436)
==29772== by 0x7BC53E4E: __wine_process_init (loader.c:3585)
==29772== by 0x4045776: wine_init (loader.c:996)
==29772== by 0x7C000F9D: main (main.c:228)
==29772==
--
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=35360
Bug ID: 35360
Summary: Crimson3: crashes when dragging symbol on design
screen
Product: Wine
Version: 1.7.10
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: sammyizimmy(a)gmail.com
Classification: Unclassified
Created attachment 47167
--> http://bugs.winehq.org/attachment.cgi?id=47167
crash backtrace
Wine crashes when I drag a symbol from the palette to the design screen
in Crimson 3.0 build 548.001
--
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=46382
Bug ID: 46382
Summary: Prevents application from opening:line 223 in file
\GraphicsDisplayM.cpp
Product: Wine
Version: unspecified
Hardware: x86
OS: Mac OS X
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: nathanh1804(a)gmail.com
Created attachment 63138
--> https://bugs.winehq.org/attachment.cgi?id=63138
traceback
Prevents application from opening on startup. Files unedited.
APP: Deltarune [Deltarune.com]
--
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=46525
Bug ID: 46525
Summary: can brows or open files from host / filesystem even if
winecfg configure only drive c:
Product: Wine
Version: 4.0
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: gamiljydcome(a)gmail.com
Distribution: ---
winecfg just configure dirve c: without any other drives to run some app, which
still can brows and open files from host / filessystem.
that's not a good news,i hope limit some app only access files from configured
drives c: d: etc just like a sandbox.
docker+wine can make a sanbox but its not what i want.
--
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=34075
Bug #: 34075
Summary: Mouse must be held down to be visible
Product: Wine
Version: 1.6-rc3
Platform: Other
OS/Version: Mac OS X
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: winemac.drv
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: ipickert55(a)gmail.com
Classification: Unclassified
Created attachment 45302
--> http://bugs.winehq.org/attachment.cgi?id=45302
Wine Log of starting steam and playing the game
I believe that this is a regression, however, i have no clue how to run a
regression test on a mac so I am just submitting this bug. It looks like this
bug had been solved in X11, so I think that this is related to the macdriver.
--
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=46360
Bug ID: 46360
Summary: wine+dxvk black game window switch back to vtx from
vt7
Product: Wine
Version: 3.21
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: gamiljydcome(a)gmail.com
Distribution: ---
OS: debian9 stable kernel 4.18
GPU: intel+nvdia
Driver: mesa 18.2 + intel modesetting + nvidia driver
Wine version: x86_64 bit wine-staging 3.21 precompiled binary
DXVK version: 0.94
i start another xserver from another tty such as vt2 but not default vt7 so can
use nvidia as primary video card, launch dx11 game with wine+dxvk then switch
back to vt7 and switch back again, the game window totally black never restore.
from vtx run glxgeas or wine dx11 game with buildin dlls, or wine dx9 game with
native or buildin d3dx9_xx.dll, switch between vtx-vt7 the glxgeas or game
window restore quickly without any errors.
if from vt7 run DISPLAY=:1 glxgeas or wine dx11 game.exe with buildin dlls, its
fine, switch vts fine.
if run DISPLAY=:1 with wine+dxvk failed to launch game exe with dxvk error:
D3D11CoreCreateDevice: Failed to create D3D11 device.
its not dxvk bug like the author said. so maybe its about wine (vulkan part)?
--
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.