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

Re: Advice fixing #13683 (DirectX mouse overlay?)

by Christopher Thielen

Unfortunately, there is no reference to "ddraw7_GetCaps" or "GetCaps" anywhere in the 975 MB log. That confirms it isn't using overlays, right? This gog.com version uses nGlide to wrap the Glide API to DirectX calls - DX9 I believe, based on the requirements of nGlide (http://www.zeus-software.com/downloads/nglide) Not sure if this information helps. I re-ran the test case using Ken's suggestion of adding the 'warn' lines and the log went down to 35 MB. I uploaded a gzipped version to the bug report. The two lines I was wondering about still appear even with 'warn+ddraw,warn+d3d,warn+d3d_surface'. The surrounding log lines around the first of the two lines in question are simply repeats. A snippet of the logfile looks something like: fixme:d3d:wined3d_debug_location Unrecognized location flag(s) 0xfffffc00. fixme:d3d:wined3d_debug_location Unrecognized location flag(s) 0xfffffc00. fixme:d3d:wined3d_debug_location Unrecognized location flag(s) 0xfffffc00. fixme:d3d:wined3d_debug_location Unrecognized location flag(s) 0xfffffc00. fixme:d3d:wined3d_debug_location Unrecognized location flag(s) 0xfffffc00. fixme:d3d:wined3d_debug_location Unrecognized location flag(s) 0xfffffc00. fixme:d3d:wined3d_debug_location Unrecognized location flag(s) 0xfffffc00. fixme:d3d:wined3d_debug_location Unrecognized location flag(s) 0xfffffc00. fixme:d3d:wined3d_debug_location Unrecognized location flag(s) 0xfffffc00. fixme:d3d:wined3d_debug_location Unrecognized location flag(s) 0xfffffc00. fixme:d3d:wined3d_debug_location Unrecognized location flag(s) 0xfffffc00. The second line I'm curious about is a little more interesting and seems to occur in groups like this: warn:d3d:wined3d_get_adapter_display_mode Overriding format WINED3DFMT_B8G8R8X8_UNORM with stored format WINED3DFMT_B8G8R8A8_UNORM. fixme:d3d:debug_d3dusage Unrecognized usage flag(s) 0x10000000 fixme:d3d:debug_d3dusage Unrecognized usage flag(s) 0x10000000 fixme:d3d:debug_d3dusage Unrecognized usage flag(s) 0x10000000 fixme:d3d:debug_d3dusage Unrecognized usage flag(s) 0x10000000 fixme:d3d:debug_d3dusage Unrecognized usage flag(s) 0x10000000 fixme:d3d:debug_d3dusage Unrecognized usage flag(s) 0x10000000 fixme:d3d:debug_d3dusage Unrecognized usage flag(s) 0x10000000 (end of the Unrecognized usage flag(s) repeating - the line seems to appear 7 times each grouping) Given that these lines appear even with the 'warn' level increased, does anyone think they're significant? I could start reading some API docs and figure out what these unrecognized flags are if it sounds promising. - Christopher Thielen On 02/16/2014 01:48 AM, Ken Thomases wrote: > On Feb 16, 2014, at 3:06 AM, Christopher Thielen wrote: > >> No luck so far: I ran the application for about 30 seconds and generated a 975 MB log file but a case insensitive "overlay" appears not at all. > > To keep the log size down, you could try a warn+ddraw,warn+d3d,warn+d3d_surface log, instead. > > >> Since this missing secondary mouse cursor only appears during certain game states, one idea I had is to look at the 'fixme's in the log and see if any roughly correlate to when the cursor should be on-screen. This is assuming the log growth correlates to game-time, which it probably does with the exception of program start and stop. >> >> I don't know if that's the next best way to debug this but there are two fixme lines that come up a lot (hundreds and hundreds of times): >> >> fixme:d3d:wined3d_debug_location Unrecognized location flag(s) 0xfffffc00. > > The wined3d_debug_location() function is used in other tracing lines. So, to figure out what is affected by it, you would want to read the next line or two from the log. > >> fixme:d3d:debug_d3dusage Unrecognized usage flag(s) 0x10000000 > > Same here. > > These both may go away if you reduce the logging to just WARNs (and ERRs and FIXMEs which are enabled by default). It's possible they were only be generated by TRACEs. > > -Ken >

Feb. 16, 2014

(no subject)

by Jarkko Korpi

I had similar gifting idea before, we should use steam discount sales for gifting games for wine devs.

Feb. 16, 2014

Re: Gifting steam/gog games to Wine developers

by Stefan Dösinger

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Am 2014-02-16 17:59, schrieb Jerome Leclanche: > I was reading a bug which gave me an idea. I have a lot of unused > Steam gift links from duplicates in my Humble Bundle purchases. I'd > like to share those with whomever needs any of them to work on bugs > (or to Wine devs who want them, you guys more than deserve them). I like the idea. I won't make use of your offer personally though. Since I'm working for codeweavers and they're providing me with all the game licenses I need for my work on Wine I've never had any issues with getting access to games. Unfortunately there's also no shortage of bugs and work to be done :-\ . -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJTARJuAAoJEN0/YqbEcdMwmGgP+waL7zoMFqdRoguPmrimI1CI MCu0k/BlNx0ngyKcvCE8T5VQqWrf0ahWVMWkwVzvICTt+FDAzdGXhE6u9qUzB5mZ 5pFtwamPNAR6G9ajj7tv8UCd7vTSe9ARHKMGUDhsX/JWOllFci8bMdfFaordtuqy ZL4t0mA+AVZDwfodGnK/e9k0thSGUW14naTZpNTyOfO7ZnKGPLZw616kVa9pfj4r C9148Z8dYlqpVe775aDT7jIVlZWvx6YRKVYPtB+XwL/pH/K/dUIMjLQhMay9CoPS Km4SvKEHLPoSxGC6u2oLNl8lRuBmk25+kpCdyd856wgGTOCA5bKBgOLek2CAdC80 Q82WC5xRS+HtCgfBQQ90yyBEYKTKKkphGMT61B5dSv39CN1aBtUYPPLmmrywyRMi m3Cs7JjbbfAaICPUzaFWeFmgGu7vnAsTIIP6VJkPOA8PuFhxd9yqQqud9Vtow1pY 4qFOqN/xjvzVl+wbItIhVsl88gPpcyli/lNd4zePgOM1ZlUlIry8efj7TKZNPaXf zmx+nQBiKbEFvfT9mwQY66tz/taomaVEEh/bHgFOyWkexePlQDhe86zonARzfMa8 XNZq99/YU4H8lZOGOJIwthrMAMn8bLM0ryVwqu6JebQZLsM8fJB4p9cTiggVfDne 4NeLcvkbU+aThQlHwy/b =DdQR -----END PGP SIGNATURE-----

Feb. 16, 2014

Re: Gifting steam/gog games to Wine developers

by André Hentschel

Am 16.02.2014 17:59, schrieb Jerome Leclanche: > Hi list > > I was reading a bug which gave me an idea. > I have a lot of unused Steam gift links from duplicates in my Humble > Bundle purchases. I'd like to share those with whomever needs any of > them to work on bugs (or to Wine devs who want them, you guys more > than deserve them). > I'd like to set up a Wiki page containing a list of available games > and a point of contact to get it gifted, encouraging other Wine users > to do the same and have one more open method of contributing to the > project. > > Is this something that would interest anyone? Hi Jerome, I once was gifted an Humble Indi Bundle to work on a related Bug, and actually i just used it to fix the bug, not for playing :) So this kind of contribution really works. Thus i think your idea is really good. Sadly i have no time atm to work on such things i guess.

Feb. 16, 2014

Gifting steam/gog games to Wine developers

by Jerome Leclanche

Hi list I was reading a bug which gave me an idea. I have a lot of unused Steam gift links from duplicates in my Humble Bundle purchases. I'd like to share those with whomever needs any of them to work on bugs (or to Wine devs who want them, you guys more than deserve them). I'd like to set up a Wiki page containing a list of available games and a point of contact to get it gifted, encouraging other Wine users to do the same and have one more open method of contributing to the project. Is this something that would interest anyone? J. Leclanche

Feb. 16, 2014

Re: [PATCH 1/5] d3d9/tests: Clean up yuv_color_test.

by Stefan Dösinger

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Am 2014-02-14 20:24, schrieb Henri Verbeet: > On 13 February 2014 23:10, Stefan Dösinger <stefan(a)codeweavers.com> wrote: >> + * Unfortunately different implementations(Windows-NV and Mac-AMD tested) interpret some colors vastly >> + * differently, so we need a max diff of 18. */ > And actually, is there any chance the "vastly differently" here is > because of using BT.601 vs. BT.709 coefficients, or not including the > headroom/footroom scaling + offsets? Maybe, but I can't look into either driver. If I remember correctly I got the reference values from the GeForce 7 driver on Windows and our shader results match it pretty well (plus / minus 2 or something). Geforce 8+ cards on Windows are off pretty far, and the GL_APPLE_ycbcr_422 support on OSX deviated even more. I think we're also doing some things wrong with the coefficients in our shader. I read about a common pitfall when handling 8 bit integer chroma that I thought we're falling into, but I don't remember the details. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJTAN07AAoJEN0/YqbEcdMw1XkQAJIVxUs2cbTwrS5mTQo+DVWA THeFaWm10TbHKNqEZQZMdTjD3BgKsZ5PYNCpGirMlOeLZqMc71Z6IQ6AZLWJcI/o iT8JIZ4KOi3e95ggyCkWkPCnkD2oSq+WorRakgIFoIjrd56KPvPB1vD8DHwz7DA0 ybE1CdHWVyEEDO2LRDnSVI9gqGsWGo+8y4T5hW929KyMOkm8GG//T0NMdoddaJol W1mp2n8Qh3Xb1VP9rMSBHmqPAPC3a/ma/21oflOR/ywDgcofsBGA97tHOYPhWERo mf2G5o1Isv+pgoFz5J8cvvnMaGn7uESWJXGpzTKkDV/zbzqdOVelCC3qHmhP4Pe1 4HVQ+NegBeVORljkTbebCnh5KyfJXBt+9yfiWKW62xjjK3So17eKIYCHLKZQ/uKg pdK1KMseYuXKWAyYJi/4W+UsIBbhgS2yZKSQeuNVMmnTa7hdBG5fPzmL8XGx1jbB 13CzOVSZ7hASA1tZIcnjErUrl6rFkfunf8W3NZS8ExoD5sZ6noTt2kej4kpDyvy/ xt5qzovuN/HNets7D+P4F83hwtK9LgRVSpoxBFm1kR6/GVNQTNaGlXsNxsdlDzHY DVyC1Zgj7fD5LyU4qJ+tlNmTQlUMLxGS6WqNjZzL7vW7bf3l2bWF/DjsatCkb2v3 T1dtcM4ttsR/iqIcfGOs =el3W -----END PGP SIGNATURE-----

Feb. 16, 2014

Re: Advice fixing #13683 (DirectX mouse overlay?)

by Stefan Dösinger

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 There is another easy way to test if the game is using an overlay on Windows: Take a screenshot with the print key. If the mouse pointer shows up, it is *not* an overlay. If it does not show up, it might be an overlay or a user32 mouse pointer. Am 2014-02-16 10:06, schrieb Christopher Thielen: > No luck so far: I ran the application for about 30 seconds and > generated a 975 MB log file but a case insensitive "overlay" > appears not at all. If the game looks for overlay flags it may not even call any overlay-related function if it doesn't find the flags present. And there's no way to find out at which flags it looks, short of disassembling the game code. What you can do is looking for IDirectDraw::GetCaps calls (grep the log for ddraw7_GetCaps). If it does not call that it doesn't look at overlay capabilities and my theory is moot. If it does, you can try to add overlay capabilities and see if it starts calling IDirectDrawSurface::UpdateOverlay (look for ddraw_surface7_UpdateOverlay) and friends. Unfortunately there's not a one-button switch to fake overlay capabilities. You may have to look at a DDCAPS structure returned from Windows and add / remove capabilities from Wine's until they look more alike. I know that I looked into Setter 3's overlay mouse pointer and it was rather tricky to figure out what the game wanted. I think it needed a proper dwMinOverlayStretch and dwMaxOverlayStretch value set, among other things. Some hints to get you started: DDCAPS_OVERLAY, DDSCAPS_OVERLAY, dwMaxVisibleOverlays, dwMinOverlayStretch, etc. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJTANmdAAoJEN0/YqbEcdMw+ikP/AqVDKsTP55id74rRQFPrqdI fpZEpjz/Lqu12sZzPdLhK9zPPvsqhon3QyE+VPFrkBB4X0hlZ2vuWzVbjrd/XBLv au6HS3Os/KDMnpkYZlyE8JwdtaOqJOF8f2GdpUvpwZ4AruU9qgVqoKSjP358qa+Y Kl/e9hmdLZw6tDGlKVimfO9gp3up46JQm+o0jzXLSuEoNKGWMxQtXVVuTBfv30DJ hTcVdrCd/FBSvSTSS4+5R6Dj0VbcdM7DaJ3GJrtVs3hMyN0smkD6SbQ7KGq5c3Ds d/Z/Z/X2TcBpxM7UF2Qg/Vg08v0Yubkz5JAqNuHdaU3117Gd4UTfjevdCkTnhFiv 3JQmDKtNQZAq4V33CmGWabYtOddgJP0loD63GX/sMmPQeOJBCztsDN59dhXpCq5O QOZRz5bJEri5317yHbATlNST4mlqR5VpnYvJovNiMNSa4Om82Z8TXLuTisCRkeMr wuTxG45zuMmH/p5BNbuL9eoKhDGWlhm/m7LMv1nGWajnDTFvtXNpIJv8WKIZ7flR ik0+0ak0hSpkLYCrDoe62qv9tktP6L7g1/XBQhysxMCwxkVE/jU7nafYzFbC31bA 8ezCnHbwvVUYL1036nOIZEd0zjcRSHtHvuJgmmbEu4wgjgMBD/T7uL4/1N9NVVuD UZ0eZzT35qwUSkM1siOx =98Q8 -----END PGP SIGNATURE-----

Feb. 16, 2014

Re: Assorted spelling fixes

by Dmitry Timoshkov

Francois Gouget <fgouget(a)free.fr> wrote: > > It's more ambiguous for e.g. file or disk sizes where drive vendors > > often use 1000 based units, > > <offtopic> > > And it's getting even more confusing. Some time ago I bought a 60 GB SSD > which was really 60 * 1024 * 1024 KB. That makes sense since SSDs are > after all more like DIMMS than hard drives. But more recently I bought a > 240 GB SSD which turned out to be 240,000,000 KB. > > So for SSDs there's no telling what GB means anymore :-( That's been always a trick HDD vendors were playing for decades to fool the users, and it has nothing todo with the actual mening of those abbrevations. -- Dmitry.

Feb. 16, 2014

Re: configure: Add import library for xmllite.

by Dmitry Timoshkov

Henri Verbeet <hverbeet(a)gmail.com> wrote: > On 14 February 2014 08:23, Dmitry Timoshkov <dmitry(a)baikal.ru> wrote: > > -WINE_CONFIG_DLL(xmllite) > > +WINE_CONFIG_DLL(xmllite,,[implib]) > That's auto-generated by make_makefiles from Makefile.in. Just a bit of clarification: does that mean that an import library gets added once a Wine component (dll or an application) start to require it and somebody adds a dependency to Makefile.in? If that's the case what should 3rd party users of winelib do when they compile their code and it fails to link because of a missing import library? Shouldn't they be always available if PSDK provides one? -- Dmitry.

Feb. 16, 2014

Re: Assorted spelling fixes

by Francois Gouget

On Sun, 16 Feb 2014, Henri Verbeet wrote: [...] > It's more ambiguous for e.g. file or disk sizes where drive vendors > often use 1000 based units, <offtopic> And it's getting even more confusing. Some time ago I bought a 60 GB SSD which was really 60 * 1024 * 1024 KB. That makes sense since SSDs are after all more like DIMMS than hard drives. But more recently I bought a 240 GB SSD which turned out to be 240,000,000 KB. So for SSDs there's no telling what GB means anymore :-( </offtopic> -- Francois Gouget <fgouget(a)free.fr> http://fgouget.free.fr/ 145 = 1! + 4! + 5!

Feb. 16, 2014