|
|
SUBSIM: The Web's #1 resource for all submarine & naval simulations since 1997
|
SUBSIM: The Web's #1 resource for all submarine & naval simulations since 1997 |
|
|
06-01-17, 07:47 PM
|
#1 |
|
CTD - it's not just a job
Join Date: May 2016
Location: One hour from Music City USA!
Posts: 10,098
Downloads: 451
Uploads: 2
|
There's an "Anti-Aliasing" (or is it one of those "-tropic" things??) setting, along with volumetric fog and a few other thingies in the game. Would they make any difference? I don't know if you have to re-start the game after changing those settings or not.
__________________
"...and bollocks to the naysayers" - Jimbuna |
|
|
|
06-28-17, 03:00 AM
|
#2 |
|
Captain
 Join Date: Apr 2016
Posts: 520
Downloads: 33
Uploads: 0
|
Just thought I would update on this....
Although 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... First, I went digging for any report of this before, apparently gnome desktop had a similar problem with something similar a few years ago... (I'm running KDE), and it was because the desktop manager was changing "focus" i.e. selecting other windows... So I followed the basic advice and I set the "focus stealing prevention" to "extreme". This had 2 effects, First and most noticeable, it prevents me from opening the application launcher (start menu for you "windows" types   ).2nd, while it does not completely stop the flickering in SH4, it does reduce it some. But most promising is it stops completely (I don't think it flickered at all) in SH3. 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.... Barracuda |
|
|
|
|
06-28-17, 04:46 AM
|
#3 |
|
Growing Old Disgracefully
 Join Date: Dec 2012
Location: Hythe - Southampton
Posts: 9,609
Downloads: 1133
Uploads: 0
|
Hi guys
SH4.exe compatibility mode. Ticking the box to 'Override High DPI Scaling' does this male any difference? Peter
__________________
LSH3-2015 <> TUTORIALS <> ALL YOU NEED TO KNOW <> ALL IN ONE PLACE SH4 <> TUTORIALS <> HOW TO DO IT <> INFORMATION <> DOWNLOAD LINKS SH5 <> TUTORIALS <> HOW TO DO IT <> INFORMATION <> DOWNLOAD LINKS Always Here To Help A Fellow 'Subber' | Need An Answer to A Question Just Send Me A PM |
|
|
|
|
06-28-17, 06:39 PM
|
#4 |
|
Captain
Join Date: Apr 2016
Posts: 520
Downloads: 33
Uploads: 0
|
I just read the thread about text size posted by blackhawk70, any chance that your post was meant for that thread?
No such option in Linux... Currently I'm running it with "emulate a virtual desktop" of 1024x768 in WINE, so I can read the errors as they show up in the terminal window... But I did check for such an option in game as well, no dice.... And I'm running WINE 2.10 as of my last post...  Although, I think with all of the post about issues with SH4 recently, I may be better off running it through WINE than most running it through Windows...  Barracuda |
|
|
|
|
01-07-18, 11:33 AM
|
#5 |
|
Swabbie
 Join Date: Mar 2010
Posts: 7
Downloads: 11
Uploads: 0
|
Intel with MESA still works fine
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. 
|
|
|
|
|
01-25-18, 02:37 AM
|
#6 | |
|
Captain
Join Date: Apr 2016
Posts: 520
Downloads: 33
Uploads: 0
|
Quote:
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 |
|
|
|
|
|
01-26-18, 01:29 PM
|
#7 |
|
Swabbie
Join Date: Mar 2010
Posts: 7
Downloads: 11
Uploads: 0
|
Mesa bugtracker
I filed a bug some while ago , but so far no reaction yet:
https://bugs.freedesktop.org/show_bug.cgi?id=104549 I inlucded an apitrace so developers can "replay" opengl commands and debug what is going wrong. Incidentely I retested sh3 on my intel integrated graphics , no artefacts there exactly as I remember  , so should be an AMDGPU issue , even replaying the trace on intel looks ok too.
|
|
|
|
 |
|
|
Hybrid Mode
