![]() ![]() So I may, when I have some time, try the "preferred" method of debugging wine, but that will require some wading through dependencies for building from source with git.Looks good when there's actually light allowing you to see, the framerate isn't stumbling, textures aren't popping in, and screen tearing isn't happening.Ĭombat is a mess, puzzles are simplistic, camera location obscures the environment with Murphy's body, and it's often too dark to see anything. This had 2 effects, First and most noticeable, it prevents me from opening the application launcher (start menu for you "windows" types ).Ģnd, while it does not completely stop the flickering in SH4, it does reduce it some.īut most promising is it stops completely (I don't think it flickered at all) in SH3. So I followed the basic advice and I set the "focus stealing prevention" to "extreme". (I'm running KDE), and it was because the desktop manager was changing "focus" i.e. Things like this are what make me wait to confirm updates are working before I upgrade!īut, it is about that time, approximately X.8 -X.12 usually end up giving me some grief!Īlthough I haven't started the suggested path of using git to see if I can trace exactly what "broke", I have managed to nail down some 'possible' fixes to this without too much work.įirst, I went digging for any report of this before, apparently gnome desktop had a similar problem with something similar a few years ago. This wouldn't be the first time that I had a game stop working great (or at all) with Wine, and I just had to wait a few. Suggestion was to "set "Allow the window manager to control the windows." to disabled", but that didn't help. I found a bug were someone was having similar trouble with and older version of wine. Hmmmmm, I think I may have found something here. Gauges, dials, even the in game font textures, they are what is flickering in and out. They are both DX9 games, so something must be amiss related to SH4.Īlthough, on closer inspection, I'm not seeing "triangles" I'm seeing the various texture assets, sometimes distorted. Yes, it is, minimum requirements for ME2 were for a dual-core.Īlthough, as per my post in the PC hardware forum, it will raise all core's load when it runs, same as SH4. Mass Effect 2 is just flying with "CSMT" enabled. I'm still digging as to what the issue is.īut on the other hand, I'm playing some other games atm. So it looks to be a Wine issue with losing the "screen". So I started Steam and SH4 via the terminal, and this is what I keep getting. ![]() Tried with Vsync, Tried a 'standard' 4x3 resolution. I tried V2.8 and I get the same issue, I even went all the way back to a 4.8 kernel to see if it was the drivers. ![]() I upgraded to WINE 3.3, and Kernel 4.15.7 and the screen flickering stopped.īlackjack174 confirmed it was the Kernel, as he had the forethought to just upgrade one thing at a time!!! I finally got a few minutes to play, and all is going nuts.ĮDIT: It appears it was the Kernel. I just updated to 2.8 from the testing repo, I'm going to give it a try with the new version see if it imporves. Has anyone ever had this occur in Windows?Īny other Linux user having this with Wine 2.7? (With AMD or Nvidia?) None of my other games that I tried are having this issue. So I tried SH3, and I'm getting it there too. I tried both 32bit and 64bit environments, as well as with the LAA patch. It is random, and doesn't appear to be related to where the mouse is. Then I get minor flickering, start a "single mission" and as I move the mouse around playing, it gets to the point of half the screen has random triangles flickering in and out (for only a few frames). I know this has something to do with recent updates to WINE, as I've tried multiple different video driver (read: kernel) versions and I'm still getting it.Īll is good, until I start to move the mouse in the menu. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |