November 2015 - Wine-Bugs - list.winehq.org

[Bug 9435] New: MDI child window outside main window gives scrollbars
by wine-bugs＠winehq.org Nov. 27, 2015

Nov. 27, 2015

http://bugs.winehq.org/show_bug.cgi?id=9435 Summary: MDI child window outside main window gives scrollbars Product: Wine Version: CVS/GIT Platform: Other OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: wine-user AssignedTo: wine-bugs(a)winehq.org ReportedBy: peter(a)cendio.se In Wine, if you move a MDI child window outside the borders of the main window, you'll get scrollbars. This does not happen in Windows. This causes problems with some applications which creates MDI child windows that occupies the entire main window area. In this case, scroll windows appears, which obscures parts of the MDI child. Tested with Wine as of 2007-08-23, using http://www.cendio.se/~astrand/wine/11-mdi-scrollbar/mdi1.exe. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

1 29

[Bug 3952] GameGuard does not work in several applications
by wine-bugs＠winehq.org Nov. 27, 2015

Nov. 27, 2015

https://bugs.winehq.org/show_bug.cgi?id=3952 Anastasius Focht <focht(a)gmx.net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |clawild(a)hotmail.com --- Comment #74 from Anastasius Focht <focht(a)gmx.net> --- *** Bug 39037 has been marked as a duplicate of this bug. *** -- 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 0

[Bug 39684] New: e-Deklaracje: Crash while opening an form
by wine-bugs＠winehq.org Nov. 27, 2015

Nov. 27, 2015

https://bugs.winehq.org/show_bug.cgi?id=39684 Bug ID: 39684 Summary: e-Deklaracje: Crash while opening an form Product: Wine Version: 1.7.55 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: lukasz.wojnilowicz(a)gmail.com Distribution: --- Created attachment 52908 --> https://bugs.winehq.org/attachment.cgi?id=52908 Opening requested form Steps to reproduce: 1) remove ~/.wine 2) winetricks adobeair mspatcha 3) install Adobe Reader 10.1 PL 4) turn off protected mode by wine reg add "HKLM\\SOFTWARE\\Policies\\Adobe\\Acrobat Reader\\10.0\\FeatureLockDown" /v bProtectedMode /t REG_DWORD /d 0 /f 5) install e-DeklaracjeDesktop.air 6) start e-Deklaracje.exe 7) give your name 8) choose forms catalog (see 8. in attachment) 9) choose one of the forms (see 9. in attachment) 10) press open (see 10. in attachment) Behaviour: Separate window opens with circular progress bar and then Wine error window shows up. Expected behaviour: Requested form should appear in separate window ready to fill in. Additional info: 1) Adobe Reader https://ardownload2.adobe.com/pub/adobe/reader/win/10.x/10.1.0/pl_PL/AdbeRd… 2) WINETRICKS_VERSION=20151110 -- 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 3

[Bug 8051] Sims 2 demo exits prematurely
by wine-bugs＠winehq.org Nov. 27, 2015

Nov. 27, 2015

https://bugs.winehq.org/show_bug.cgi?id=8051 --- Comment #129 from swswine(a)gmail.com --- (In reply to Stefan Dösinger from comment #128) > Does it use a shader too, or just a vertex declaration? Both shader and vertex declaration. > It's probably easier to hook into > https://www.opengl.org/wiki/Transform_Feedback instead. Yes, sure, I see. -- 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 0

[Bug 8051] Sims 2 demo exits prematurely
by wine-bugs＠winehq.org Nov. 27, 2015

Nov. 27, 2015

https://bugs.winehq.org/show_bug.cgi?id=8051 --- Comment #128 from Stefan Dösinger <stefan(a)codeweavers.com> --- (In reply to swswine from comment #127) > At the first place ProcessVertecies does not understand VertexDeclaration > output buffer specification, while sims2 wants to use them and output buffer > has zero FVF code. Does it use a shader too, or just a vertex declaration? > I know it may sound very weird, but can't shader support in ProcessVertices > be done in a shorter way by just using application shader function in fixed > function GLSL pipeline in a way similar to how the normal application > shaders (without ProcessVertices) are used? It's possible, but has its own set of issues. E.g. what do you do if the game calls ProcessVertices two times with two different shaders (shader constants) and the same output buffer, and then draws the entire buffer with one draw call? What happens if one of the input buffers goes away or is modified between ProcessVertices and DrawPrimitive? The shader state, and in particular vertex shader constants and potential vertex textures, is pretty huge. Managing this gets complex fast... It's probably easier to hook into https://www.opengl.org/wiki/Transform_Feedback instead. -- 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 0

[Bug 8051] Sims 2 demo exits prematurely
by wine-bugs＠winehq.org Nov. 27, 2015

Nov. 27, 2015

https://bugs.winehq.org/show_bug.cgi?id=8051 --- Comment #127 from swswine(a)gmail.com --- (In reply to Stefan Dösinger from comment #125) > Our ProcessVertices so far only supports > very basic fixed function operations - just transformation, no lighting > support. For shader support we'll need to be able to interpret the shader on > the CPU, or maybe we can work with one of those OpenGL feedback extensions. At the first place ProcessVertecies does not understand VertexDeclaration output buffer specification, while sims2 wants to use them and output buffer has zero FVF code. I know it may sound very weird, but can't shader support in ProcessVertices be done in a shorter way by just using application shader function in fixed function GLSL pipeline in a way similar to how the normal application shaders (without ProcessVertices) are used? The user shader and input buffer references to the input buffer could be attached to the output buffer. Then VP shader code can be used as a function when output buffer is used. Such output buffer would be a sort of vertex shader closure :)) The Lock on such output buffer won't work, but Sims2 does not lock these buffers (as I can see from my logs), and overall it would be strange for the application to process vertices in its code after requesting shader processing (if mainly for debugging purposes maybe). -- 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 0

[Bug 21579] New: Yahoo Messenger 10 crash when opening IM window with a contact
by wine-bugs＠winehq.org Nov. 26, 2015

Nov. 26, 2015

http://bugs.winehq.org/show_bug.cgi?id=21579 Summary: Yahoo Messenger 10 crash when opening IM window with a contact Product: Wine Version: 1.1.37 Platform: x86 URL: http://rd.software.yahoo.com/msgr/10/msgr10us.exe OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: deun.support(a)gmail.com After installing client, it starts and I can log in without any issue. However, when attempting to open an IM window with a contact, the application systematically crashes with a page fault in one of its threads, but app stays stuck until I do a Ctrl+C in the shell from which I launched it. Not being sure about what leads to that page fault, I've attached a debug log with +user,+advapi,+ole just in case. I case also provide a +all log if there's not enough infos in that log. Tested on Ubuntu 9.04 x86 32bits. Bug occurs with identically with both wine 1.1.37 and 1.1.34. -- 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 33

[Bug 8051] Sims 2 demo exits prematurely
by wine-bugs＠winehq.org Nov. 26, 2015

Nov. 26, 2015

https://bugs.winehq.org/show_bug.cgi?id=8051 --- Comment #126 from swswine(a)gmail.com --- (In reply to Stefan Dösinger from comment #125) > (In reply to swswine from comment #124) > I noticed d3dx9 trying to create a shader validator interface, but so far it > has always been happy with the NULL return and just skipped validation. Are > you sure it really needs this? > Absolutely. It discards all the real shaders without that. The program is statically linked with a very old d3dx9, maybe newer versions are OK with Null valudator even if validation is requested. This one returns the error from d3dx9 shader linking function in this case (E_FAIL 0x80000405) > I wonder though if this stuff works on any modern Windows driver though. Google suggests that yes (at least windows 7, not sure about later). There are some tricks with game configuration files discussed in the forums though. But it is lkely mainly due to gorgeous configuration files which list all the graphic cards they know and has plenty specific feature configuration flags. -- 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 0

[Bug 8051] Sims 2 demo exits prematurely
by wine-bugs＠winehq.org Nov. 26, 2015

Nov. 26, 2015

https://bugs.winehq.org/show_bug.cgi?id=8051 Stefan Dösinger <stefan(a)codeweavers.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |stefan(a)codeweavers.com --- Comment #125 from Stefan Dösinger <stefan(a)codeweavers.com> --- (In reply to swswine from comment #124) > The reason is that Sims2 is using some shader compilaton function from d3dx > library (which has fancy static linkage in sims2 exe files, so no way to use > builtin d3dx.dll). That function requests undocumentated interface from d3d9 > through Direct3DShaderValidatorCreate9, and fails if it is not available. I noticed d3dx9 trying to create a shader validator interface, but so far it has always been happy with the NULL return and just skipped validation. Are you sure it really needs this? > After that, if shader model 3.0 is available, the model stops rendering at > all and the trace is full of indications of unsupported features. Not fully > supported ProcessVertices implementation goes first, then a few other things > like tangent, binormal and vertex blend indices vertex attributes, and some > more. These probably should be sorted out one by one. Horray. A game that actually needs ProcessVertices with shader support. This will be pretty nasty to implement. Our ProcessVertices so far only supports very basic fixed function operations - just transformation, no lighting support. For shader support we'll need to be able to interpret the shader on the CPU, or maybe we can work with one of those OpenGL feedback extensions. The other stuff is probably RHW vertices + Shader Model 3 shaders. This should be fixable with the fixed function vertex pipeline GLSL shader. I wonder though if this stuff works on any modern Windows driver though. We removed the tests that test the related functionality because we were getting broken behavior on newer drivers. (There are plenty of differences between those old tests and Sims 2 though. One being explicit SWVP, the other is that ProcessVertices + RHW draw is most likely different from just an RHW draw) -- 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 0

[Bug 8051] Sims 2 demo exits prematurely
by wine-bugs＠winehq.org Nov. 26, 2015

Nov. 26, 2015

https://bugs.winehq.org/show_bug.cgi?id=8051 --- Comment #124 from swswine(a)gmail.com --- Created attachment 52904 --> https://bugs.winehq.org/attachment.cgi?id=52904 Partial workaround to fix game start, models display and get a sensible trace I eventually tried to run Sims2 and make it work under Wine. It seems to be an interesting case of using various d3d9 features which are not implemented in Wine yet. Shader constants limit is just the first but not the least reason. I hope it is interesting to share what I found as actually previous discussion does not reveal what is actually wrong with Sims2 under wine. While I not yet succeded in making Sims2 fully work I found the major reason why rendering did not work without any indication what's wrong or not supported in the trace (after the trick similar to that from Comment #118). I am attaching the patch which partially fixes rendering for me but more important reveals actually unsupported features which the game is using. This patch by no means can be thought as a fix proposal for anything, but lets Sims2 run and draw models, and makes it usable for further testing and fixing. As noted in Comment #118 here, the crash on startup can be worked around by increasing the number of supported shader constants. The patch increases that constant at the first place and also increases number of constants in wined3d. Actually this workaround helps to run some other games involving 3d characters, but not this time. After applying just this the game starts but model is rendered in T pose and totally red (I am mainly running TS2BodyShop.exe to view how the model renders). At the same time wine trace does not show up any relevant problems. The reason is that Sims2 is using some shader compilaton function from d3dx library (which has fancy static linkage in sims2 exe files, so no way to use builtin d3dx.dll). That function requests undocumentated interface from d3d9 through Direct3DShaderValidatorCreate9, and fails if it is not available. Unlike some redundant constants initialization at startup, this problem does not show up as crash or something, the game just continues running and falls back to some most basic shaders which draw red models in T pose, without any visible errors. My patch adds a very dumb & dirty implementation of the undocumented validator interface which returns OK for all the requests and does the trick, the game starts to use real shaders. After that, if shader model 3.0 is available, the model stops rendering at all and the trace is full of indications of unsupported features. Not fully supported ProcessVertices implementation goes first, then a few other things like tangent, binormal and vertex blend indices vertex attributes, and some more. These probably should be sorted out one by one. The last thing that the patch does is hardcoding maximum shaders version to 2 (caps->VertexShaderVersion and caps->PixelShaderVersion in wined3d/directx.c). After that the model shows OK in model builder (with normal pose and texture). I also started the main game in tutorial mode (I do not know how to play it), and the model also showing OK in the beginning, but other glitches show up quickly when doing some actions in the house (the glitches are now accompanied by the informative trace output). So probably it is easier to fix the problems showing up in shader 2.0 model first as it likely has less missing features. It actually should be possible to limit shader model version within game configuration files (the google is full of discussions on how people fixing Sims2 on Windows through these). -- 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 0