FreeOrion

When it comes to bugs, this one is the biggest problem for me:

https://github.com/freeorion/freeorion/issues/676

Hi defaultuser,

I posted a reply to the thread for the linked issue, so that the information is less scattered.

Yes, I have seen it. This was originally just a reminder in the bug discussion that there is one that for a few souls is a game-breaker.

defaultuser wrote:This was originally just a reminder in the bug discussion that there is one that for a few souls is a game-breaker.

Unfortunately I fear it's more than just a few souls who suffer from this bug. Systems with Intel integrated graphics aren't exactly a rare, exotic setup.

However, unless one of the devs (who is capable of troubleshooting the code parts in question) is able to reliably reproduce that buggy behaviour, chances of fixing this are slim...

I could get set up to build and I am a software engineer, but trouble-shooting graphics is likely not going to be a "shallow dive".

defaultuser wrote:trouble-shooting graphics is likely not going to be a "shallow dive".

Your assessment is very likely spot on. Which is why it would be ideal if one of the devs familiar with the GG code could reproduce and troubleshoot that issue.

However, if you could get set up to build you could try to narrow down which commit introduced the issue, that would probably help a lot I guess (Geoff?). Probably going to be a thoroughly tedious git bisect operation, but might be worth it.

Given that many people in many applications has or have had problems of mouse disappearance and screen flickering in Windows as well as Linux (many distributions) with Intel Integrated Graphics, might it be that the problem was introduced by some version of the GPU graphics or some of the libraries used in FO?

In this thread, I have documented some data I have accumulated:

http://www.freeorion.org/forum/viewtopi ... =25&t=9768

It's possible that analysis of windows that cause the mouse to disappear and those that don't could provide some insight.

I will take a look at getting set up for build, but I make no promises. I had planned to do that AR (after retirement) which has been stretching on a bit as there are things I want to finish up at work and personally before I "pull the plug".

I have a new windows 10 machine and don't have any of these problems.
Would info about my box to compare to one that has problems be helpful?
I'll be happy to oblige.

Vezzra wrote:

defaultuser wrote:This was originally just a reminder in the bug discussion that there is one that for a few souls is a game-breaker.

Unfortunately I fear it's more than just a few souls who suffer from this bug. Systems with Intel integrated graphics aren't exactly a rare, exotic setup.

However, unless one of the devs (who is capable of troubleshooting the code parts in question) is able to reliably reproduce that buggy behaviour, chances of fixing this are slim...

I do not have Intel integrated graphics.

EricF wrote:I do not have Intel integrated graphics.

Me neither. It's in Intel drivers where the issue lies.