wine-bugs August 2022

1 participants
2926 discussions

[Bug 42440] New: Jedi Knight Dark Forces II / DirectX7 3D acceleration issue

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=42440 Bug ID: 42440 Summary: Jedi Knight Dark Forces II /DirectX7 3D acceleration issue Product: Wine Version: 2.0 Hardware: x86 OS: Mac OS X Status: UNCONFIRMED Severity: normal Priority: P2 Component: winemac.drv Assignee: wine-bugs(a)winehq.org Reporter: kevincarrolldavis(a)gmail.com The game renders find when 3D acceleration is turned off within the games Display settings. When 3D Acceleration is turned on, the game is rendered with randomly-placed magenta-hue colored pixels. As mentioned in Bug #42439, this problem seemed fixed after commenting out the following line from the updateColorSpace function found in the dlls/winemac.drv/cocoa_window.m file: [self SetColorSpace:nil]; -- 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 year, 8 months

[Bug 48328] New: DarkForces 2 do not see available resolutions

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=48328 Bug ID: 48328 Summary: DarkForces 2 do not see available resolutions Product: Wine Version: 5.0-rc2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3dx9 Assignee: wine-bugs(a)winehq.org Reporter: axet(a)me.com Distribution: --- Created attachment 66054 --> https://bugs.winehq.org/attachment.cgi?id=66054 xrandr log Hello! I'm trying to run DarkForces 2, seems with recent updated game does not see all available resolutions. Ubuntu 19.10, ubuntu wine-4.0.2 and wine-develeopment-4.17 (screen stuck I do not see anything beside initial game screen, UI respond to mouse movements). Also I tried to install d3dx9, also I treid winehq repo with 4.0.3 and 5.0~rc2 - games does not see all resolutions. Only two available: 320x180 && 320x240. According to logs (WINEDEBUG=+xrandr and WINEDEBUG=+ddraw), all ok: 002a:trace:xrandr:X11DRV_XRandR_Init Found XRandR 1.6. 002a:trace:xrandr:xrandr12_init_modes CRTC 0: mode 0x48, 2880x1800+0+0. 002a:trace:xrandr:xrandr12_init_modes OUTPUT 0: name "eDP-1". 002a:trace:xrandr:xrandr12_init_modes Adding mode 0x48: 2880x1800@60. 002a:trace:xrandr:xrandr12_init_modes Adding mode 0x49: 2880x1620@60. 002a:trace:xrandr:xrandr12_init_modes Adding mode 0x4a: 2880x1620@60. 002a:trace:xrandr:xrandr12_init_modes Adding mode 0x4b: 2560x1600@60. and: 002b:trace:ddraw:ddraw7_EnumDisplayModes Enumerating 2880x1800x32 @0 002b:trace:ddraw:ddraw7_EnumDisplayModes Enumerating 2880x1620x32 @0 002b:trace:ddraw:ddraw7_EnumDisplayModes Enumerating 2560x1600x32 @0 -- 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 year, 8 months

[Bug 24308] New: Fullscreen fails for MechWarrior 4 games (Only one D3D device per DirectDraw object)

by wine-bugs＠winehq.org

http://bugs.winehq.org/show_bug.cgi?id=24308 Summary: Fullscreen fails for MechWarrior 4 games (Only one D3D device per DirectDraw object) Product: Wine Version: 1.3.2 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-ddraw AssignedTo: wine-bugs(a)winehq.org ReportedBy: georg298(a)gmx.de For all MechWarrior 4 games, fullscreen fails with message fixme:ddraw:d3d7_CreateDevice Only one Direct3D device per DirectDraw object supported. Obviously, the game falls back to window'ed mode, as static HRESULT WINAPI d3d7_CreateDevice(IDirect3D7 *iface, REFCLSID riid, IDirectDrawSurface7 *surface, IDirect3DDevice7 **device) returns DDERR_INVALIDPARAMS changing this behaviour (returning D3D_OK instead): if (ddraw->d3ddevice) { FIXME("Only one Direct3D device per DirectDraw object supported.\n"); LeaveCriticalSection(&ddraw_cs); return D3D_OK; // return DDERR_INVALIDPARAMS; } makes fullscreen work for these games. Probably it's not "legal" to return D3D_OK in this case, but maybe there is a real solution for this problem? -- 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 year, 8 months

[Bug 39421] New: Majesty Gold HD runs very slowly

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=39421 Bug ID: 39421 Summary: Majesty Gold HD runs very slowly Product: Wine Version: 1.7.52 Hardware: x86 OS: Mac OS X Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: jonas.bugzilla(a)gmail.com Created attachment 52535 --> https://bugs.winehq.org/attachment.cgi?id=52535 Clamp the glFlush rate in the Mac driver to 60Hz The game Majesty Gold HD (http://www.gog.com/game/majesty_gold_hd ) runs very slowly under Wine for me (Late 2013 iMac 21.5", quad 2.9GHz Core i5, GeForce GT 750M with 1GB GDDR5, OS X 10.9.5). There is an in-game slider to speed up the game, but it has no effect. The game is a DirectDraw 7 game. There are also some reports on Windows regarding this problem, but most people can solve it by telling the game to use DirectDraw for blitting (set BlitMode=1 in the MajXPrefs, or use the -useddblit command line parameter -- see http://forum.paradoxplaza.com/forum/index.php?threads/bug-fixes.601217/#pos… ) The game performs its drawing commands in the same thread that runs the game logic (I don't know whether anything else is even supported by by DirectDraw 7). From a trace I can see that game performs many small blits to update only the parts of the screen that have changed. Example from a trace: trace:ddraw:ddraw_surface7_Blt iface 0x16c160, dst_rect (0,0)-(24,38), src_surface 0x16c9c8, src_rect (0,0)-(24,38), flags 0x1000000, fx 0x0. [ repeats 8 times ] trace:ddraw:ddraw_surface7_Blt iface 0x16c160, dst_rect (864,661)-(1009,803), src_surface 0x16c9c8, src_rect (864,661)-(1009,803), flags 0x1000000, fx 0x0. trace:ddraw:ddraw_surface7_Blt iface 0x16c160, dst_rect (806,999)-(986,1080), src_surface 0x16c9c8, src_rect (806,999)-(986,1080), flags 0x1000000, fx 0x0. trace:ddraw:ddraw_surface7_Blt iface 0x16c160, dst_rect (1097,734)-(1277,914), src_surface 0x16c9c8, src_rect (1097,734)-(1277,914), flags 0x1000000, fx 0x0. trace:ddraw:ddraw_surface7_Blt iface 0x16c160, dst_rect (860,481)-(1040,661), src_surface 0x16c9c8, src_rect (860,481)-(1040,661), flags 0x1000000, fx 0x0. trace:ddraw:ddraw_surface7_Blt iface 0x16c160, dst_rect (860,481)-(1040,661), src_surface 0x16c9c8, src_rect (860,481)-(1040,661), flags 0x1000000, fx 0x0. trace:ddraw:ddraw_surface7_Blt iface 0x16c160, dst_rect (1354,797)-(1534,977), src_surface 0x16c9c8, src_rect (1354,797)-(1534,977), flags 0x1000000, fx 0x0. ... I think Wine, however, always flushes a complete new screen via OpenGL, as the game spends almost all of its time waiting for glFlush() to finish. I have verified that this is the case by applying the attached patch to the Mac driver code to unconditionally clamp the glFlush rate to 60Hz. This solves the speed issue, even at 1920x1080 (without the patch, the game is glacial even at 800x600). Obviously, the patch cannot be integrated in wine, since it occasionally discards the "last" blit to screen after a static scene change, leaving old data visible and no longer updating. I previously posted about this issue (a long time ago) on wine-dev: https://www.winehq.org/pipermail/wine-devel/2015-February/106625.html . To answer some questions/suggestions from the end of that thread: a) the SkipSingleBufferFlushes registry key does not help (my system supports the GL_APPLE_flush_render extension) b) related to Henri Verbeet's suggestion that it may be related to wine possibly not implementing asynchronous ddraw blits: it's true that wine does not support this, but OTOH the game does not ask for them either: it calls ddraw_surface7_Blt rather than ddraw_surface7_BltFast (BltFast is documented on MSDN as always being asynchronous), and it does not set the DDBLT_ASYNC flag The game offers a built-in ability to wait for vsync via its configuration file (set the VSync variable in $HOME/Documents/My Games/MajestyHD/MajXPrefs to "1"), but that only results in trace:ddraw:ddraw7_WaitForVerticalBlank iface 0x146750, flags 0x1, event 0x0. fixme:ddraw:ddraw7_WaitForVerticalBlank iface 0x146750, flags 0x1, event 0x0 stub! I'm also not sure whether it would help, but looking at the ddraw log (which I will also attach -- it's a trace+ddraw,trace+d3d_draw log), I think it may since often there are several blits between the vsync waits. Some possible approaches to tackle this issue may be: * handle small direct rects more efficiently * add support for waiting for VSync in ddraw There is a demo of an older version of the game, but it can only run in 640x480 and there is no way to adjust the game speed via an in-game slider, and at least on my system the difference with and without my patch is not very visible there (http://www.cyberlore.com/Majesty/demo.htm ) -- 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 year, 8 months

[Bug 45533] New: Puyo Puyo Tetris (Steam) - Game crashes on startup

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=45533 Bug ID: 45533 Summary: Puyo Puyo Tetris (Steam) - Game crashes on startup Product: Wine Version: 3.13 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: sirmentio123(a)gmail.com Distribution: --- Created attachment 61934 --> https://bugs.winehq.org/attachment.cgi?id=61934 These logs are made from the moment I launch steam through the wine prefix to when the application crashes and when I close it/steam itself out The program crashes upon launch in the Steam version. win64 was required in order to play. This was tested obviously with the Steam version and I'm not sure if it's the same for the one from the SEGA store. As far as I know. Using the staging version of 3.13 Ubuntu 18.04 x86 64 Nvidia driver 390 X.Org X Server 1.19.6 -- 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 year, 8 months

[Bug 52208] New: WSCGetApplicationCategory does not exist

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=52208 Bug ID: 52208 Summary: WSCGetApplicationCategory does not exist Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winsock Assignee: wine-bugs(a)winehq.org Reporter: euloanty(a)live.com Distribution: --- wine malus wine: Call from 7BC2B310 to unimplemented function WS2_32.dll.WSCGetApplicationCategory, aborting This software could not run. https://getmalus.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.

1 year, 8 months

[Bug 49817] New: d3d9: Crashes on invalid opengl context with disabled csmt in IDirect3DDevice9Ex_CreateOffscreenPlainSurface

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=49817 Bug ID: 49817 Summary: d3d9: Crashes on invalid opengl context with disabled csmt in IDirect3DDevice9Ex_CreateOffscreenPlainSurface Product: Wine Version: 5.17 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: piotr.caban(a)gmail.com Distribution: --- Created attachment 68148 --> https://bugs.winehq.org/attachment.cgi?id=68148 test that shows invalid error handling on invalid opengl context The simplest way to reproduce the crash is (I was only testing it running 32-bit process): - disable csmt - run the test with WINEDEBUG=warn+heap (to guarantee the crash) The test destroys window/hdc used by current gl context. After that it's not possible to restore previous context in Direct3DCreate9Ex. It also leads to a crash when deleting "destroyed" context in IDirect3DDevice9Ex_CreateOffscreenPlainSurface. -- 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 year, 8 months

[Bug 36869] New: Chronology under wine-mono fails to start

by wine-bugs＠winehq.org

http://bugs.winehq.org/show_bug.cgi?id=36869 Bug ID: 36869 Summary: Chronology under wine-mono fails to start Product: Wine Version: 1.7.21 Hardware: x86 URL: http://store.steampowered.com/app/269330/ OS: Linux Status: NEW Severity: normal Priority: P2 Component: mscoree Assignee: wine-bugs(a)winehq.org Reporter: madewokherd(a)gmail.com Chronology fails to start and consumes 100% of a CPU when run under wine-mono until killed. Based on a log with WINE_MONO_TRACE=wrapper, the only thing it does is call Steamworks.NativeMethods:SteamAPI_InitSafe, which is a cdecl function with no arguments. That function then endlessly throws breakpoint exceptions. InitSafe is a cdecl function with no arguments returning signed char. I have no idea how we could be screwing this up. -- 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 year, 8 months

[Bug 39761] New: MDK (MDKDEM95.EXE) graphics not drawn

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=39761 Bug ID: 39761 Summary: MDK (MDKDEM95.EXE) graphics not drawn Product: Wine Version: 1.8-rc3 Hardware: x86 OS: Mac OS X Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: jeffz(a)jeffz.name Tested on OSX 10.9.5. http://jeffz.name/mdkdemo_repack.tar.bz2 winecfg virtual desktop set to 640x480 cd ~/.wine/drive_c && tar xf ~/mdkdemo_repack.tar.bz2 && cd mdkdemo_repack wine MDKDEM95.EXE The game loads (as can be heard by the sounds after hitting enter a few times) but nothing is ever drawn. There should be intro credits, main menu and gameplay. Confirmed that this bug does not happen on Windows 7. It works fine there. Note: bug #39760 deals with the D3D version of the demo. -- 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 year, 8 months

[Bug 53596] New: Day of the Tentacle remastered crashes randomly

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=53596 Bug ID: 53596 Summary: Day of the Tentacle remastered crashes randomly Product: Wine Version: 7.7 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: kohen.d(a)gmail.com Distribution: --- Created attachment 72985 --> https://bugs.winehq.org/attachment.cgi?id=72985 backtrace from winedbg The app crashes randomly, usually after > 1h play, but happens when loading as well (unfortunately it overwritten my save that crashes quickly). It crashes on a read violation. Tested it with Win 7 32Bit bottle -- 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 year, 8 months

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

wine-bugs August 2022