Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cursor: mousepointer flickers when moving the mouse #6319

Closed
DorpsGek opened this issue Jun 14, 2015 · 2 comments
Closed

Cursor: mousepointer flickers when moving the mouse #6319

DorpsGek opened this issue Jun 14, 2015 · 2 comments

Comments

@DorpsGek
Copy link

@DorpsGek DorpsGek commented Jun 14, 2015

3dmaxb00n opened the ticket and wrote:

Hi,

I noticed the following Problem since V1.4.2. Do not know, if it existet in earlier versions. I do not know, if it affects other OS.

When moving the mouse around, the cursor flickers. The strength varies from barely visible to invisible. This effect is heavier, when the game is paused. When unpaused, the cursor flickers but remains visible enough. I explained the problem in the forum here: https://www.tt-forums.net/viewtopic.php?t=71149# p1129732.

I have a Logitech g500 mouse with 4400dpi and 500 signals per second. If I lower the values, the flicker is less heavy. With standard office mouse types, the problem is gone. If I connect my G500 to my Laptop and play the game there, the flicker effect appears. I do not have other mice to test.

Hope this gets fixed.

Attachments

Reported version: 1.5.1
Operating system: Windows


This issue was imported from FlySpray: https://bugs.openttd.org/task/6319
@DorpsGek
Copy link
Author

@DorpsGek DorpsGek commented Jun 17, 2015

3dmaxb00n wrote:

Sorry for confusing you but I have to correct a fact I gave you.

I retried lowering the values for the g500 but the mouse still flickers very heavily when moving. Even on 200dpi and 125 signals per second (lowest values for g500).


This comment was imported from FlySpray: https://bugs.openttd.org/task/6319#comment13976
@TrueBrain
Copy link
Member

@TrueBrain TrueBrain commented Apr 11, 2018

3 years later. No other reports. Sorry, going to close the ticket. Feel free to reopen if you feel it is just.

@TrueBrain TrueBrain closed this Apr 11, 2018
TrueBrain added a commit to TrueBrain/OpenTTD that referenced this issue Feb 22, 2021
… frame

When we clip the region that is only been redrawn, something
weird happens on Windows. When pushing 60 frames per second on a
60Hz monitor, it appears that the clipped region is often shown
of another frame, instead of the current.

Examples of this are:
- pause the game, move your mouse to the left, and at the right
  speed it totally disappears.
- fast aircrafts seem to be in several places at once, weirdly
  lagging behind.
- in title screen, moving your mouse gives you the idea it is
  jumping places, instead of smooth movements.

In the end, if you do nothing, everything is correct, so it is
eventually consistent. Just when we are firing many BitBlt in
a clipped region, the in-between is not.

What goes wrong exactly, I honestly do not know. On every frame
that we push to the DC is a mouse painted, but visually it
sometimes appears like it is not. Recording with external software
shows it really is there.
It is also not our eyes playing tricks on us, as the first example
makes it really clear the mouse pointer really is not painted.

And to be clear, with the mouse this is easiest reproduceable,
as high-speed objects are influences by this most. But this happens
for all movement that redraws small regions.

Either way, not using clipped regions resolves the issue completely,
and there appears to be little to no penalty (I failed to measure
any impact of drawing the full screen). So better have a good game
than fast code, I guess?
@michicc michicc reopened this Feb 22, 2021
@TrueBrain TrueBrain closed this in 78d96da Feb 22, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants