February 2014 - Wine-bugs - list.winehq.org

[Bug 12388] New: Commandos 3: read_from_framebuffer_texture error ( glCopyTexSubImage2D)
by wine-bugs＠winehq.org 04 Apr '14

04 Apr '14

http://bugs.winehq.org/show_bug.cgi?id=12388 Summary: Commandos 3: read_from_framebuffer_texture error (glCopyTexSubImage2D) Product: Wine Version: CVS/GIT Platform: PC URL: http://www.eidosinteractive.com/downloads/search.html?gm id=143 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d AssignedTo: wine-bugs(a)winehq.org ReportedBy: alexd4(a)inbox.lv Created an attachment (id=11888) --> (http://bugs.winehq.org/attachment.cgi?id=11888) screenshot with problem In one of game levels (in the demo, you get into it by selecting central europe campaign in menu) there are bad rendering errors. The moment you get to that screen, console is filled with message fixme:d3d_surface:read_from_framebuffer_texture >>>>>>>>>>>>>>>>> GL_INVALID_OPERATION (0x502) from glCopyTexSubImage2D @ surface.c / 914 Which must be the reason of this problem. This also happens with PBO extension and P8 texture support reporting disabled in directx.c. -- 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.

1 11

[Bug 25780] New: MS WORKS can't find licence terms
by wine-bugs＠winehq.org 04 Apr '14

04 Apr '14

http://bugs.winehq.org/show_bug.cgi?id=25780 Summary: MS WORKS can't find licence terms Product: Wine Version: 1.2.2 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: jpxsat(a)gmail.com MS WORKS, the "light" office suite from microsoft(R) shows a message that says "can't show licence terms from microsoft software. Licence terms must show y be accepted before be able to use MS WORKS. To show licence terms, reinstall WORKS" This message should not exist. After this message, the application closes. There are some reports of having overrule it by winetricks (see appdb) but should be a way to get it to work. -- 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.

1 10

[Bug 21576] New: Touch screen loses calibration when in full screen mode - specifically AtomixMP3.exe
by wine-bugs＠winehq.org 04 Apr '14

04 Apr '14

http://bugs.winehq.org/show_bug.cgi?id=21576 Summary: Touch screen loses calibration when in full screen mode - specifically AtomixMP3.exe Product: Wine Version: 1.1.33 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: newmaniax(a)gmail.com When running AtomixMP3, and other WINE apps, in full screen mode the touchscreen goes way out of calibration, which is important for this program specifically and how i use it. In un-maximised mode it works fine. If it helps this program will not operate at all (display to be used anyway) in full screen mode in VirtualBox, but again fine when in un-maximised mode. A demo version is available here fore testing: http://dl.dropbox.com/u/1640537/Link%20to%20Atomixmp3.exe I have searched various forums and have fond no clue towards a solution. ie, I have no idea if it's a bug or something that is easily configurable. I have played with WINE config settings and screen resolutions with no success. I tried changing my x screen resolution to 800 x 600 (normally 1680 x 1050) and noted that the calibration is the SAME as the WINE app in full screen mode, with the pointer very biased towards the left side of the screen. Please advise, would love touch screen to work properly in full screen mode. Thanks, Sincerely, Guy Newman -- 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.

1 5

[Bug 29875] New: MS Works 9 can't install (infinite waiting for estimating time)
by wine-bugs＠winehq.org 04 Apr '14

04 Apr '14

http://bugs.winehq.org/show_bug.cgi?id=29875 Bug #: 29875 Summary: MS Works 9 can't install (infinite waiting for estimating time) Product: Wine Version: 1.3.37 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: jpxsat(a)gmail.com Classification: Unclassified Created attachment 38831 --> http://bugs.winehq.org/attachment.cgi?id=38831 Terminal Output Install crashes after estimating time to install. I'm adding terminal output. -- 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.

1 15

[Bug 35678] New: Defiance patcher crashes on start (gdiplus/GdipDrawImagePointsRect)
by wine-bugs＠winehq.org 04 Apr '14

04 Apr '14

https://bugs.winehq.org/show_bug.cgi?id=35678 Bug ID: 35678 Summary: Defiance patcher crashes on start (gdiplus/GdipDrawImagePointsRect) Product: Wine Version: 1.1.13 Hardware: x86 URL: http://www.defiance.com/en/my-ego/profile/pc-free-tria l/ OS: Linux Status: NEW Keywords: download Severity: normal Priority: P2 Component: gdiplus Assignee: wine-bugs(a)winehq.org Reporter: austinenglish(a)gmail.com Backtrace: =>0 0x7e5541e4 GdipDrawImagePointsRect+0xe14(graphics=<is not available>, image=<is not available>, points=<is not available>, count=<is not available>, srcx=<is not available>, srcy=<is not available>, srcwidth=<is not available>, srcheight=<is not available>, srcUnit=<is not available>, imageAttributes=<is not available>, callback=<is not available>, callbackData=<is not available>) [/home/austin/wine-git/dlls/gdiplus/graphics.c:2943] in gdiplus (0x0033bf68) 1 0x7e555432 GdipDrawImageRectRectI+0x181(graphics=<is not available>, image=<is not available>, dstx=<is not available>, dsty=<is not available>, dstwidth=<is not available>, dstheight=<is not available>, srcx=<is not available>, srcy=<is not available>, srcwidth=<is not available>, srcheight=<is not available>, srcUnit=<is not available>, imageAttributes=<is not available>, callback=<is not available>, callbackData=<is not available>) [/home/austin/wine-git/dlls/gdiplus/graphics.c:3130] in gdiplus (0x0033c038) Appears to only happen on first run. -- 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.

1 14

[Bug 35550] New: Horizon (Steam Game) - Crashes after hitting play in launcher
by wine-bugs＠winehq.org 04 Apr '14

04 Apr '14

http://bugs.winehq.org/show_bug.cgi?id=35550 Bug ID: 35550 Summary: Horizon (Steam Game) - Crashes after hitting play in launcher Product: Wine Version: 1.7.11 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: msvcp Assignee: wine-bugs(a)winehq.org Reporter: jmelton116(a)gmail.com Classification: Unclassified Created attachment 47470 --> http://bugs.winehq.org/attachment.cgi?id=47470 Backtrace generated upon crash Game crashes immediately after hitting the play button in the launcher menu which is launched by Steam when you press play in the library. It fails with the following error Unhandled exception: unimplemented function msvcp100.dll.?_Random_device(a)tr1@std@@YAIXZ called in 32-bit code (0x7b83b52e). -- 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.

1 7

[Bug 27625] New: Panzer General 3D Demo: second scenario fails to load
by wine-bugs＠winehq.org 04 Apr '14

04 Apr '14

http://bugs.winehq.org/show_bug.cgi?id=27625 Summary: Panzer General 3D Demo: second scenario fails to load Product: Wine Version: 1.3.22 Platform: x86 URL: http://www.download.com/Panzer-General-III-Scorched-Ea rth-updated-demo/3000-7562_4-10048808.html OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: robert.munteanu(a)gmail.com After winning the first scenario in the demo loading the second scenario does not work. The loading screen simply hangs. I can provide a savegame if it would speed up testing. -- 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.

1 6

[Bug 31079] New: Fatal error during Stronghold Crusader Demo installation
by wine-bugs＠winehq.org 04 Apr '14

04 Apr '14

http://bugs.winehq.org/show_bug.cgi?id=31079 Bug #: 31079 Summary: Fatal error during Stronghold Crusader Demo installation Product: Wine Version: 1.2.3 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: maikwagner(a)yahoo.com Classification: Unclassified Created attachment 40798 --> http://bugs.winehq.org/attachment.cgi?id=40798 Console output of Stronghold Crusader Demo Hi everyone, I would like to report that I had some issues installing "Stronghold Crusader" demo which I got from: http://www.giga.de/spiele/stronghold-crusader/downloading/?id=2670&post_id=… During the installation a fatal error comes up but installation continues as normal when I close the error window. Thought I let you know. I have attached my console output. OS is CentOS 6.2 Another thing which could be of interest is, that the demo link in the AppDB is pointing nowhere. Appdb entry is: http://appdb.winehq.org/objectManager.php?sClass=version&iId=3993 Regards, Maik -- 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.

1 6

[Bug 19269] New: Distant impostors does not work in Lord of the Rings Online
by wine-bugs＠winehq.org 04 Apr '14

04 Apr '14

http://bugs.winehq.org/show_bug.cgi?id=19269 Summary: Distant impostors does not work in Lord of the Rings Online Product: Wine Version: 1.1.25 Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d AssignedTo: wine-bugs(a)winehq.org ReportedBy: eric.ladner(a)gmail.com The "distant impostors" setting has no effect. The way it implements distant impostors, I believe, is substituting a flat 2d texture for 3d objects that are very far from the camera, giving more detail to the landscape without having to render 20 million polys for the trees. See http://www.codeweavers.com/compatibility/browse/group/?app_parent=4029;foru… (second post from the top) for screen shots comparing LotRO running on Wine and Windows and the difference "distant impostors" makes. I've verified that it doesn't work on 1.1.24 and 1.1.25 (although 1.1.25 crashed a lot for me on LotRO for some reason and I had to revert back to 1.1.24). I'd be happy to provide any extra debugging info if any would be helpful. -- 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.

1 22

[Bug 35112] New: L.A. Noire 1.3 (Steam version) fails to start, claiming "DX94: Graphics card capabilities are below the minimum specifications." (wined3d clamps device caps MaxVertexIndex to 0xFFFFF)
by wine-bugs＠winehq.org 04 Apr '14

04 Apr '14

http://bugs.winehq.org/show_bug.cgi?id=35112 Bug ID: 35112 Summary: L.A. Noire 1.3 (Steam version) fails to start, claiming "DX94: Graphics card capabilities are below the minimum specifications." (wined3d clamps device caps MaxVertexIndex to 0xFFFFF) Product: Wine Version: 1.7.8 Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: focht(a)gmx.net Classification: Unclassified Hello folks, now with bug 35109 fixed the game runs into next problem. After the main process 'LANoire.exe' has started an error dialog window is shown, stating: "Error: DX94: Graphics card capabilities are below the minimum specifications." It was actually a bit of pain to diagnose/debug because of several processes involved which are (re)started in sequence with the actual timing being important. There are only very small time windows for attaching debuggers, if you miss them -> boom (avoid 'auto' debugging of childs from parent). Additionally, these processes are a mixture of native binaries, .NET binaries and mixed-mode binaries somewhat complicating diagnosis further (unmanaged code with various managed code transitions in the same process). Relevant part of trace log, showing processes involved: NOTE: Don't redirect to files located within Steam folder to avoid unnecessarily triggering the directory watcher thread(s). --- snip --- $ WINEDEBUG=+tid,+seh,+loaddll,+process,+msvcrt,+d3d9,+relay wine ./steam.exe -applaunch 110800 >>~/Downloads/trace.txt 2>&1 ... 0024:trace:process:__wine_kernel_init starting process name=L"C:\\Program Files\\Steam\\steam.exe" argv[0]=L"C:\\Program Files\\Steam\\steam.exe" ... 0024:Call KERNEL32.CreateProcessW(00b1ed88 L"C:\\Program Files\\Steam\\steamerrorreporter.exe",00000000,00000000,00000000,00000000,00000000,00000000,00b1edf0 L"C:\\Program Files\\Steam",0033f4e8,0033f52c) ret=10001121 ... 0024:trace:process:create_process_impl starting L"C:\\Program Files\\Steam\\steamerrorreporter.exe" as Win32 binary (0x400000-0x436000, arch 014c) ... 0024:trace:process:create_process_impl started process pid 0025 tid 0026 ... 003f:Call KERNEL32.CreateProcessW(02a54a40 L"C:\\Program Files\\Steam\\steamapps\\common\\L.A.Noire\\LanLauncher.exe",02a54f50 L"\"C:\\Program Files\\Steam\\steamapps\\common\\L.A.Noire\\LanLauncher.exe\"",00000000,00000000,00000000,00000004,00000000,02978818 L"C:\\Program Files\\Steam\\steamapps\\common\\L.A.Noire",06dcb588,06dcb604) ret=381ec242 ... 003f:trace:process:create_process_impl starting L"C:\\Program Files\\Steam\\steamapps\\common\\L.A.Noire\\LanLauncher.exe" as Win32 binary (0x400000-0x514000, arch 014c) ... 003f:trace:process:create_process_impl started process pid 0056 tid 0057 ... 0057:Call KERNEL32.CreateProcessW(00000000,0033de68 L"C:\\Program Files\\Steam\\steamapps\\common\\L.A.Noire\\LANPatcher.exe",00000000,00000000,00000000,00000404,00000000,044c8b88 L"C:\\Program Files\\Steam\\steamapps\\common\\L.A.Noire",0033d520,0033d510) ret=100416f7 ... 0057:trace:process:create_process_impl starting L"C:\\Program Files\\Steam\\steamapps\\common\\L.A.Noire\\LANPatcher.exe" as Win32 binary (0x400000-0x4ae000, arch 014c) ... 0057:trace:process:create_process_impl started process pid 005b tid 005c ... 005c:Call KERNEL32.CreateProcessW(00000000,0033dd18 L"C:\\Program Files\\Steam\\steamapps\\common\\L.A.Noire\\LANLauncher.exe -SkipPatchCheck",00000000,00000000,00000000,00000404,00000000,04497e78 L"C:\\Program Files\\Steam\\steamapps\\common",0033d3d0,0033d3c0) ret=100416f7 ... 005c:trace:process:create_process_impl starting L"C:\\Program Files\\Steam\\steamapps\\common\\L.A.Noire\\LANLauncher.exe" as Win32 binary (0x400000-0x514000, arch 014c) ... 005c:trace:process:create_process_impl started process pid 0066 tid 0067 0067:Call KERNEL32.CreateProcessW(00000000,0033d8b8 L"C:\\Program Files\\Steam\\steamapps\\common\\L.A.Noire\\LANoire.exe -windowed -parentIsLauncher",00000000,00000000,00000000,00000404,00000000,04531618 L"C:\\Program Files\\Steam\\steamapps\\common\\L.A.Noire",0033cf70,0033cf60) ret=100416f7 ... 0067:trace:process:create_process_impl starting L"C:\\Program Files\\Steam\\steamapps\\common\\L.A.Noire\\LANoire.exe" as Win32 binary (0x400000-0x184f000, arch 014c) ... 0067:trace:process:create_process_impl started process pid 0026 tid 0025 0067:Call KERNEL32.CreateProcessW(00000000,0033d8b8 L"C:\\Program Files\\Steam\\steamapps\\common\\L.A.Noire\\LANLauncher.exe -SplashScreen Loading",00000000,00000000,00000000,00000404,00000000,00000000,0033cf70,0033cf60) ret=100416f7 ... 0067:trace:process:create_process_impl starting L"C:\\Program Files\\Steam\\steamapps\\common\\L.A.Noire\\LANLauncher.exe" as Win32 binary (0x400000-0x514000, arch 014c) ... 0067:trace:process:create_process_impl started process pid 004b tid 004d ... 0064:fixme:advapi:CreateProcessAsUserW 0x44c L"C:\\Program Files\\Rockstar Games\\Social Club\\renderer.exe" L"\"C:\\Program Files\\Rockstar Games\\Social Club\\renderer.exe\" --type=renderer --disable-logging --disable-desktop-notifications --disable-speech-input --enable-accelerated-compositing --lang=en-US --channel=38.0F96F300.97936503 /prefetch:3" (nil) (nil) 0 0x0100040c (nil) (null) 0x322ae14c 0x322ae134 - semi- stub ... 0064:trace:process:create_process_impl started process pid 006a tid 006b ... --- snip --- After dumping, rebuilding and analysing the main executable + trace log for some hours I finally deduced the place where the problem originated. The d3d calls from trace log are register indirect calls which requires a debugger to identify the actual call site at run time. Additionally some of them are hooked at through Steam gameoverlay renderer. --- snip --- ... 0025:trace:d3d9:d3d9_device_GetDeviceCaps iface 0x32977c18, caps 0x332a74. 0025:Call ntdll.RtlAllocateHeap(00110000,00000008,0000017c) ret=f687fa1f 0025:Ret ntdll.RtlAllocateHeap() retval=32fe6448 ret=f687fa1f 0025:Call wined3d.wined3d_mutex_lock() ret=f687fa55 0025:Ret wined3d.wined3d_mutex_lock() retval=00000000 ret=f687fa55 0025:Call wined3d.wined3d_device_get_device_caps(328e2cb8,32fe6448) ret=f687fa6a 0025:Ret wined3d.wined3d_device_get_device_caps() retval=00000000 ret=f687fa6a 0025:Call wined3d.wined3d_mutex_unlock() ret=f687fa72 0025:Ret wined3d.wined3d_mutex_unlock() retval=00000000 ret=f687fa72 0025:Call ntdll.RtlFreeHeap(00110000,00000000,32fe6448) ret=f687ff1c 0025:Ret ntdll.RtlFreeHeap() retval=00000001 ret=f687ff1c 0025:trace:d3d9:d3d9_GetAdapterDisplayMode iface 0x32977990, adapter 0, mode 0x332a64. 0025:Call wined3d.wined3d_mutex_lock() ret=f688af86 0025:Ret wined3d.wined3d_mutex_lock() retval=00000000 ret=f688af86 0025:Call wined3d.wined3d_get_adapter_display_mode(328d9f38,00000000,003329fc,00000000) ret=f688afac 0025:Call user32.EnumDisplaySettingsExW(328dcdf0 L"\\\\.\\DISPLAY1",ffffffff,00332860,00000000) ret=f66ba608 0025:Call winex11.drv.EnumDisplaySettingsEx(328dcdf0,ffffffff,00332860,00000000) ret=7ed181c2 0025:Ret winex11.drv.EnumDisplaySettingsEx() retval=00000001 ret=7ed181c2 0025:Ret user32.EnumDisplaySettingsExW() retval=00000001 ret=f66ba608 0025:Ret wined3d.wined3d_get_adapter_display_mode() retval=00000000 ret=f688afac 0025:Call wined3d.wined3d_mutex_unlock() ret=f688afb5 0025:Ret wined3d.wined3d_mutex_unlock() retval=00000000 ret=f688afb5 0025:trace:d3d9:d3d9_CheckDeviceFormat iface 0x32977990, adapter 0, device_type 0x1, adapter_format 0x16, usage 0x1, resource_type 0x1, format 0x4c4c554e. 0025:Call wined3d.wined3d_mutex_lock() ret=f688b1b6 0025:Ret wined3d.wined3d_mutex_lock() retval=00000000 ret=f688b1b6 0025:Call wined3d.wined3d_check_device_format(328d9f38,00000000,00000001,00000073,00000001,00000001,4c4c554e) ret=f688b202 0025:Ret wined3d.wined3d_check_device_format() retval=00000000 ret=f688b202 0025:Call wined3d.wined3d_mutex_unlock() ret=f688b20b 0025:Ret wined3d.wined3d_mutex_unlock() retval=00000000 ret=f688b20b 0025:trace:d3d9:d3d9_CheckDeviceFormat iface 0x32977990, adapter 0, device_type 0x1, adapter_format 0x16, usage 0x2, resource_type 0x3, format 0x5a544e49. 0025:Call wined3d.wined3d_mutex_lock() ret=f688b1b6 0025:Ret wined3d.wined3d_mutex_lock() retval=00000000 ret=f688b1b6 0025:Call wined3d.wined3d_check_device_format(328d9f38,00000000,00000001,00000073,00000002,00000003,5a544e49) ret=f688b202 0025:Ret wined3d.wined3d_check_device_format() retval=00000000 ret=f688b202 0025:Call wined3d.wined3d_mutex_unlock() ret=f688b20b 0025:Ret wined3d.wined3d_mutex_unlock() retval=00000000 ret=f688b20b 0025:Call KERNEL32.GetLastError() ret=79e7a087 0025:Ret KERNEL32.GetLastError() retval=00000000 ret=79e7a087 ... <several transitions to managed code> ... <huge amount of unrelated trace messages later> ... 0073:Call user32.CreateWindowExW(00000200,0907369c L"WindowsForms10.EDIT.app.0.3ce0bb8",0906fedc L"DX94: Graphics card capabilities are below the minimum specifications.",560108c0,00000005,00000013,0000027d,00000015,00020184,00000000,00400000,00000000) ret=017edcbc --- snip --- The error dialog window is created from .NET code (windows form), along with some unusable callstack display (another bug). The actual reason for the problem is not visible in trace log, one has to analyse and step the disassembly. d3d9_device_GetDeviceCaps() returns D3D9 Device Caps structure. The engine code checks several caps struct members to decide if the card is 'good'. My card 'NVIDIA GeForce GT 425M' was not recognized (bug 35054) hence Wine's default choice was taken: 'Graphics Card: NVIDIA GeForce 8800 GTX'. The minimum video card requirements for this game (from website): "NVIDIA GeForce 8600 GT 512MB" ... so even with the default (incorrect) choice it should have been 'good'. Each time a requirement is not met the game internally assigns an error code 'DX<two-digit-code>' which is translated to a more or less generic error message. DirectX caps checks (in order): --- snip --- VertexShaderVersion my raw value: 0xFFFE0300 good value: >= 3.0 (masked out) failure: "DX92: Shadermodel 3.0 required" --- snip --- --- snip --- PixelShaderVersion my raw value: 0xFFFF0300 sanitized good value: >= 3.0 (masked out) failure: "DX93: Shadermodel 3.0 required") --- snip --- Now the important one ... --- snip --- MaxVertexIndex my raw value: 0xFFFFF good value: 0x555555 (5592405 decimal) failure: "DX94: Graphics card capabilities are below the minimum specifications." --- snip --- Wine uses a hard-coded default value. d3d9_device_GetDeviceCaps -> wined3d_device_get_device_caps -> wined3d_get_device_caps (filter_caps) Source: http://source.winehq.org/git/wine.git/blob/34ad4c7014c63a4b4f96f94ba4973831… --- snip --- 4100 HRESULT CDECL wined3d_get_device_caps(const struct wined3d *wined3d, UINT adapter_idx, 4101 enum wined3d_device_type device_type, WINED3DCAPS *caps) 4102 { ... 4441 caps->MaxAnisotropy = gl_info->limits.anisotropy; 4442 caps->MaxPointSize = gl_info->limits.pointsize_max; 4443 4444 caps->MaxPrimitiveCount = 0xfffff; /* For now set 2^20-1 which is used by most >=Geforce3/Radeon8500 cards */ 4445 caps->MaxVertexIndex = 0xfffff; 4446 caps->MaxStreams = MAX_STREAMS; 4447 caps->MaxStreamStride = 1024; ... --- snip --- Increasing the limit to 0x555555 made the game DirectX engine happy :) There were a few other dx caps checks following but those requirements were fulfilled by default. *** Interesting tidbit: There exists a kind of hack to overcome the failing dx caps check without modifying Wine code. During dumping/analysis of the main binary I found several 'goodies' -> semi-/undocumented command line parameters. One of them is '-disablecrashhandler'. You can pass it through launcher 'command line' options dialog. This basically skips the invocation of the .NET based error handler and lets the game engine code continue as if nothing happened. Having this kind of 'override' in actual code is usually disastrous. Due to the special way the requirement checks were coded this 'magically' works. Each invocation of error handler leads to a no-return 'continuation' like call. The next prerequisite check immediately follows the no-return call (without branches in between). Disabling the crash handler made the no-return calls basically a no-op hence letting the execution flow 'magically' continue. *** The game runs further until next problem ... looks like some wined3d volume texture/surface management thing (that area is currently being worked on). $ wine --version wine-1.7.8-200-gd566292 Regards -- 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.

1 9