View Single Post
Old 01-25-18, 02:37 AM   #19
BarracudaUAK
Captain
 
Join Date: Apr 2016
Posts: 520
Downloads: 31
Uploads: 0


Default

Quote:
Originally Posted by Blackjack174 View Post
FYI:
.msg<Main>: 0xaaaa0002=FOCUS_RECEIVED (0x63000020, 0)
.msg<Main>: 0xaaaa0001=FOCUS_LOST (0x63000020, 0)
.msg<Main>: 0xaaaa0002=FOCUS_RECEIVED (0x63000007, 0)
.msg<Main>: 0xaaaa0001=FOCUS_LOST (0x63000007, 0)
.msg<Main>: 0xaaaa0002=FOCUS_RECEIVED (0x63000006, 0)
.msg<Main>: 0xaaaa0001=FOCUS_LOST (0x63000006, 0)
.msg<Main>: 0xaaaa0002=FOCUS_RECEIVED (0x63000005, 0)
.msg<Main>: 0xaaaa0001=FOCUS_LOST (0x63000005, 0)
.msg<Main>: 0xaaaa0002=FOCUS_RECEIVED (0x63000004, 0)
.msg<Main>: 0xaaaa0001=FOCUS_LOST (0x63000004, 0)

these are in fact messages from the "Main" application that gets dumped to the linux console, when hovering and focusing on UI elements in the sh3 menu, these are NOT errors.

As I have the flickering too with AMDGPU driver I tested my intel onboard driver (which worked fine with sh3 some month back), and I have no flickering / errors there.

Intel drivers for my HD4600 card now support exactly the same OPENGL levels as AMDGPU , so there should be a bug in AMDGPU driver (that incidentally is now used by AMDGPU Pro proprietary driver), I will try to revert to older mesa drivers and dissect and report this issue to the mesa developers if possible.

Hope that does not count as necroposting here (sorry), but this thread actually turns up first when searching for the problem...

cheers.


I just logged back in and noticed your post....


What I posted as errors, did not show up on the older wine/driver versions.
I start all of my games through a terminal strictly so I will have a clue if something goes "not to plan".

They messages START after the game starts flickering, and only after.
Until I move the mouse and the flickering starts, I will see no messages of this kind.

Hence the reason I concluded that they were "errors".


I keep meaning to file a bug report, but life has once again been really busy...

Also, just a note to anyone else that happens upon this thread,
I'm running Fedora 27, kernel 4.14.13, wine 2.20 staging
and it is still flickering.


I just updated to 4.14.14, so I'll check again next time I reboot.

Barracuda
BarracudaUAK is offline   Reply With Quote