Skip to content
This repository has been archived by the owner on Apr 17, 2022. It is now read-only.

Cursors rapidly alternate between default pointer & selection/action cursors #4450

Closed
wzdev-ci opened this issue Jul 19, 2016 · 11 comments
Closed

Comments

@wzdev-ci
Copy link
Contributor

resolution_fixed type_bug | by xShadow421x


When you select any unit/s (droid), the cursor then doesn't seem to know to only use the cursor icon specific for whatever you're about to do with that/those unit/s.
For example, if you select a truck unit and try to build something, the cursor flickers between the "image_cursor_default.png" and the "image_cursor_build.png". This includes anything else unit related from selecting a spot in the world to move, selecting targets, and anything in between. I've also noticed it happens when manually moving the camera's position and the cursor tries changing to the related arrow icons. This seems to happen in these cases only and the cursor is not affected when making selections in any menus.
Notes:
• Unit type & configuration doesn't matter.
• This is a clean install
• Mods are not involved or don't affect the cursor behavior differently
• Happens regardless of gametype
• Happens regardless of cursor style (Colored Cursors ON or OFF)
• Tested on two PC's with different specs and OS's (Windows 7/10 & Linux)
• Using current build 3.2.0

If possible I'll upload a small video demonstrating it happen.
Otherwise I'll have the file & the ability to record should someone want or need it and we'll figure it out from there.


Issue migrated from trac:4450 at 2022-04-16 12:33:09 -0700

@wzdev-ci
Copy link
Contributor Author

xShadow421x uploaded file vlc-record-2016-07-20.mp4 (4506.5 KiB)

Recorded video of cursor bug

@wzdev-ci
Copy link
Contributor Author

Per changed blocking which not transferred by tractive

@wzdev-ci
Copy link
Contributor Author

Per changed blockedby which not transferred by tractive

@wzdev-ci
Copy link
Contributor Author

Per commented


That is odd. I cannot reproduce that.

@wzdev-ci
Copy link
Contributor Author

xShadow421x commented


Figures; it would be one of those kind of glitches...

Unfortunately I wasn't around to test the betas for 3.2 and I vaguely recall reading about how the master branch was involved, so was 3.2 built separately or on top of 3.1.5? Because this does not happen in 3.1.5 & previous versions, if that helps narrow it down even slightly.

@wzdev-ci
Copy link
Contributor Author

wzdev-ci commented Jul 20, 2016

xShadow421x commented


Replying to Warzone2100/old-trac-import#4450 (comment:1):

That is odd. I cannot reproduce that.

Sorry about the extra comment. I failed to notice the reply buttons; unless this ended up being a separate comment anyway...

Right, so after trying multiple things I've found that this issue occurs when VSync is turned OFF, but with VSync ON, the issue goes away. However, the issue persists on my laptop PC regardless though, but I'm not worried about it functioning there. Just thought I'd mention it since a lot of people play on laptops & low-end hardware in general.

@wzdev-ci
Copy link
Contributor Author

Cyp <cyp@...> changed status from new to closed

@wzdev-ci
Copy link
Contributor Author

Cyp <cyp@...> changed owner from `` to Cyp <cyp@wz2100.net>

@wzdev-ci
Copy link
Contributor Author

Cyp <cyp@...> changed resolution from `` to fixed

@wzdev-ci
Copy link
Contributor Author

Cyp <cyp@...> commented


In Warzone2100/warzone2100@ec3eb89:

#CommitTicketReference repository="" revision="ec3eb89550752db7098952af6aa79b20d4bfc9de"
Don't let the cursor flicker.

Hard to reproduce, probably depends on hardware and/or vsync.

Fixes #4450.

@wzdev-ci
Copy link
Contributor Author

wzdev-ci commented Jul 21, 2016

xShadow421x commented


Replying to Warzone2100/old-trac-import#4450 (comment:4):

In Warzone2100/warzone2100@ec3eb89:

#CommitTicketReference repository="" revision="ec3eb89550752db7098952af6aa79b20d4bfc9de"
Don't let the cursor flicker.

Hard to reproduce, probably depends on hardware and/or vsync.

Fixes #4450.

Assuming the warzone2100-master-x-x-x.exe from [​http://buildbot.wz2100.net/files/] has these changes implemented, I can confirm that they seem to resolve the issue in all conditions I've tested, and for both PC's that I use.
Thank you for taking the time to look into this!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant