wine-devel November 2014

wine-devel@winehq.org

48 participants
175 discussions

Re: wined3d: Add NVIDIA Geforce GT 750M to supported device list.
by Jonas Maebe 21 Nov '14

21 Nov '14

FWIW, I have such an NVIDIA Geforce GT 750M card (under OS X 10.9.5) and Crossover 13.2 returned 768MB of vram for it. Crossover 14/14.0.1 returns 128MB instead, which resulted in a number of games suddenly crashing because they ran out of VRAM. This issue was quickly diagnosed by the helpful Codeweavers support person, and resolved by adding the registry entry to override the video memory size. Looking at the current source code, I assume that's because shader_arb_get_caps() can set the shader_caps->vs_version maximally to 3, while d3d_level_from_caps() will only return WINED3D_D3D_LEVEL_10 for shader_caps->vs_version==4. As a result, d3d_level_from_caps now returns WINED3D_D3D_LEVEL_9_SM3, which is translated for an unknown NVidia card into CARD_NVIDIA_GEFORCE_6800. That one is indeed defined as having 128MB of VRAM.

5 13

Re: [PATCH 5/5] d3d8: Only one fullscreen swapchain is allowed.
by Marvin 21 Nov '14

21 Nov '14

Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at https://testbot.winehq.org/JobDetails.pl?Key=10398 Your paranoid android. === w8 (32 bit device) === device.c:1222: Test failed: TestCooperativeLevel failed, hr 0x88760868. device.c:1267: Test failed: Reset failed, hr 0x88760868. device.c:1269: Test failed: TestCooperativeLevel failed, hr 0x88760869. device.c:1273: Test failed: Got unexpected value 0 for D3DRS_LIGHTING. device.c:1280: Test failed: D3DVIEWPORT->X = 10, expected 0. device.c:1281: Test failed: D3DVIEWPORT->Y = 20, expected 0. device.c:1282: Test failed: D3DVIEWPORT->Width = 400, expected 800. device.c:1283: Test failed: D3DVIEWPORT->Height = 300, expected 600. device.c:1284: Test failed: D3DVIEWPORT->MinZ = 2.00000003e-001, expected 0. device.c:1285: Test failed: D3DVIEWPORT->MaxZ = 3.00000012e-001, expected 1. device.c:1290: Test failed: Screen width is 640, expected 800. device.c:1291: Test failed: Screen height is 480, expected 600. device.c:1297: Test failed: Back buffer width is 640, expected 800. device.c:1299: Test failed: Back buffer height is 480, expected 600. device.c:1329: Test failed: Screen width is 640, expected 1024. device.c:1330: Test failed: Screen height is 480, expected 768. device.c:2517: Test failed: Expected message 0x7e for window 0, but didn't receive it. device.c:2522: Test failed: The focus window is active. device.c:2530: Test failed: Got unexpected hr 0x88760869. device.c:2536: Test failed: Got unexpect screen size 800x600. device.c:2551: Test failed: Expected message 0x47 for window 0, but didn't receive it, i=1. device.c:2560: Test failed: Got unexpect screen size 800x600. device.c:2573: Test failed: Expected message 0x7e for window 0, but didn't receive it. device.c:2580: Test failed: Got unexpect width 640. device.c:2581: Test failed: Got unexpect height 480.

1 0

Re: [PATCH 4/5] d3d8/tests: Fix test_cursor().
by Marvin 21 Nov '14

21 Nov '14

Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at https://testbot.winehq.org/JobDetails.pl?Key=10397 Your paranoid android. === w8 (32 bit device) === device.c:1186: Test failed: TestCooperativeLevel failed, hr 0x88760868. device.c:1231: Test failed: Reset failed, hr 0x88760868. device.c:1233: Test failed: TestCooperativeLevel failed, hr 0x88760869. device.c:1237: Test failed: Got unexpected value 0 for D3DRS_LIGHTING. device.c:1244: Test failed: D3DVIEWPORT->X = 10, expected 0. device.c:1245: Test failed: D3DVIEWPORT->Y = 20, expected 0. device.c:1246: Test failed: D3DVIEWPORT->Width = 400, expected 800. device.c:1247: Test failed: D3DVIEWPORT->Height = 300, expected 600. device.c:1248: Test failed: D3DVIEWPORT->MinZ = 2.00000003e-001, expected 0. device.c:1249: Test failed: D3DVIEWPORT->MaxZ = 3.00000012e-001, expected 1. device.c:1254: Test failed: Screen width is 640, expected 800. device.c:1255: Test failed: Screen height is 480, expected 600. device.c:1261: Test failed: Back buffer width is 640, expected 800. device.c:1263: Test failed: Back buffer height is 480, expected 600. device.c:1293: Test failed: Screen width is 640, expected 1024. device.c:1294: Test failed: Screen height is 480, expected 768. device.c:2481: Test failed: Expected message 0x7e for window 0, but didn't receive it. device.c:2486: Test failed: The focus window is active. device.c:2494: Test failed: Got unexpected hr 0x88760869. device.c:2500: Test failed: Got unexpect screen size 800x600. device.c:2515: Test failed: Expected message 0x47 for window 0, but didn't receive it, i=1. device.c:2524: Test failed: Got unexpect screen size 800x600. device.c:2537: Test failed: Expected message 0x7e for window 0, but didn't receive it. device.c:2544: Test failed: Got unexpect width 640. device.c:2545: Test failed: Got unexpect height 480.

1 0

Re: gdiplus:GdipDrawImagePointsRect has a nosie vertical line output after resampled
by Vincent Povirk 21 Nov '14

21 Nov '14

This will break in cases where the destination area (defined by points) is not a rectangle. On Fri, Nov 21, 2014 at 8:32 AM, 刘昌辉 <liuchanghui(a)linuxdeepin.com> wrote: > > > >

1 0

Re: [PATCH 4/5] wined3d: Don't minimize hidden Windows.
by Henri Verbeet 21 Nov '14

21 Nov '14

On 19 November 2014 20:13, Stefan Dösinger <stefan(a)codeweavers.com> wrote: > @@ -2189,6 +2189,13 @@ static LRESULT CALLBACK test_proc(HWND hwnd, UINT message, WPARAM wparam, LPARAM > } > } > > + if (unexpected_messages) > + { > + const struct message *i; > + for (i = unexpected_messages; i->message; i++) > + ok(i->message != message, "Got unexpected message %x on window %p.\n", message, hwnd); Note that putting the ok() in test_proc() makes it hard to find the actual test that failed.

2 1

Re: shell32/tests: Fix a copy and paste error (PVS-Studio)
by Marvin 20 Nov '14

20 Nov '14

2 1

Re: [2/2] ws2_32: Implement returning the proper time with SO_CONNECT_TIME.
by Bruno Jesus 20 Nov '14

20 Nov '14

On Thu, Nov 20, 2014 at 10:27 AM, Sebastian Lackner <sebastian(a)fds-team.de> wrote: > Based on a patch by Erich Hoover. > > To avoid calculations on the client-side, the server sends the connect time as relative (negative) value. > Needs tools/make_requests. Hi, Sebastian. Thanks for taking care of this, but actually I'm thinking by doing this in a different way. I'm thinking about moving SO_CONNECT_TIME, SO_SNDBUF and SO_RECVBUF to the server with some new server message or the one Erich created for the WSAIoctl. By doing it this way we can fix not only this bug but also https://bugs.winehq.org/show_bug.cgi?id=8606 where we can store the pretended SO_SNDBUF value and return to the client when asked. Some other messages could also be done there like SO_EXCLUSIVEADDR, SO_DEBUG and others that require only memory to store/retrieve the value. This would also help for SO_ACCEPTCONN which is bugged in OSX due to a kernel problem. Not sure if my approach would be accepted anyway. Best wishes, Bruno

2 6

Re: [PATCH 1/2] Add tests for calling ShowWindow(SW_HIDE) on a hidden window.
by Marvin 20 Nov '14

20 Nov '14

2 1

Re: [PATCH] explorer: Fix copy_path_string() when an unnecessary \ follow the path.
by Huw Davies 20 Nov '14

20 Nov '14

On Thu, Nov 20, 2014 at 08:29:17PM +0800, Jactry Zeng wrote: > @@ -639,6 +640,11 @@ static int copy_path_string(LPWSTR target, LPWSTR source) > while (*source && *source != ',') target[i++] = *source++; > target[i] = 0; > } > + > + last = strlenW(target) - 1; > + if (target[0] && target[last] == '\\') > + target[last] = 0; > + > return i; > } You probably want PathRemoveBackslashW() Huw.

2 1

Re: [PATCH] winex11.drv: call XRRSetScreenSize when changing resolution
by Stefan Dösinger 20 Nov '14

20 Nov '14

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 11/20/14 13:11, Mark Harmstone wrote: > This changes xrandr12_set_current_mode so it behaves the same way > as xrandr does in 1.2 mode (e.g, `xrandr --output HDMI-0 --crtc 0 > --mode 640x480`). Before XRRSetCrtcConfig is called, the CRTC is > temporarily disabled, then XRRSetScreenSize is called. > (XRRSetCrtcConfig will fail if the CRTC isn't disabled first.) I've experimented with this a few weeks ago, and it drastically improves the usability of fullscreen applications on Metacity-based window managers. Unfortunately I'm afraid it is not quite that simple. It breaks KDE (may be a bug) and it breaks multi-monitor setups. Testing on Windows (sorry, I did not write formal tests) shows that in single monitor setups the virtual screen size is adjusted to match the monitor's resolution when the resolution is changed. So the change is correct in single monitor setups, but needs tests. In multi-monitor setups the virtual screen size is changed too, but it still takes both monitors into account. E.g. you had two monitors at 1920x1080, where one is to the right of the other. So you have a virtual screen of 3840x1080. If you change the res of the left monitor to 640x480 you get a virtual screen size of 2560x1080. I hackily "fixed" the Nvidia panning bug by replacing crtc_info->x and crtc_info->y in pXRRSetCrtcConfig with 0, 0. That way the mode set succeeds and the CRTC is positioned correctly. The direct3d mouse grab takes care of the mouse moving outside the window, but only after clicking in the window once. The d3d grab is incorrect though as far as I can see. Windows doesn't grab the mouse in fullscreen d3d games in dual monitor setups. Passing an offset of 0, 0 to pXRRSetCrtcConfig may be the correct thing to do. It seems that the content of crtc_info->x and crtc_info->y depends on the mouse pointer location, which would be an odd thing for a mode change to depend on. May be an Nvidia bug. Finally, there is a bug in all window managers forked from Metacity. If the new resolution is smaller in width or height than half the virtual screen size (= old resolution for single-monitor setups) then the WM places the window incorrectly. xwininfo reports where the window *should* be - at 0x0-WxH. But the real display location is something different, depending on the exact incarnation of the WM. In Unity it is shifted by 64x64 (unity bar I guess) and stretched to the virtual screen size. In MATE I think the window is centered. I suspect this is caused by the window positioning logic breaking. I have not been able to isolate the bug in the window manager code yet. All in all I'm afraid we have a number of different bugs to fix in all Metacity forks, Wine, the Nvidia driver and maybe KDE. Fwiw, KDE and FVWM place fullscreen windows properly. MATE and Unity also adjust their title bars and window maximization to match the new CRTC size, not the screen size. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJUbeMbAAoJEN0/YqbEcdMwutAP/jWwKCaDNL0OzaWoQhVM8+XN fmshL9cSYha3jVnJ8TJU92ch/7NcFsnGFL0dAEFz1bZqpM9lHwqapdjhqP7PUI0r yIpRNoBR+UjeX46zQ1oIbcib2UpXhm0YZQ0x45DaaUGvVDFGSs0d2Oo4nulDJFx+ DkEdSxe9p403rc6S2nfWHROaUmT3v/stYs9nN+A+YuBleYZwJz+e+MknElTBiboo RcIWnOICDksJ08oEhWaMxNDLtQstMYp0cuRtPNeB3jCWxRP00xsgXgZ2uAigSrrI OPcLgQ5jq3MFDdHorgz7pM3aOa5YvouFxt1OsCsbyekSovBJMj4WaB0QHmqOxPUQ 2LQzS9TMsR0CJYl6hdsykB6c8Gdqdcc8Gv+SoLUn7FjUckvXi6cgnN+XnXTFBQT2 ah6S59gVYxwvb4IVdvYuAL/AvN3tlfR6rOkw/U3Z16u0KHa2C0SQRSK8ohuFabzS SMq2VEq4Cspub3nYCSOSSFZvmUKxlHdyQPPfXEpFEfBQaM40CnsfqN/7vfchj0dQ jAExC4Z1PGvFJFqVnTFaxZ3eIOPBDIBOTgkDK14gWaxrZoGySTJtDe6513iLBsQv 75JZxcfl5VZbzIfYuUcVjvXoWyr4gqeOSJhe/oEITpd5UwEAZabcvJ/yIH8s3u0T tliUU3UuYOfzLsP7jLP2 =eGIQ -----END PGP SIGNATURE-----

1 0

← Newer
1
2
3
4
5
6
7
8
...
18
Older →

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-devel November 2014