Anonymous | Login | Signup for a new account | 2024-04-20 00:05 UTC |
My View | View Issues | Change Log | Roadmap | Zandronum Issue Support Ranking | Rules | My Account |
View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] | ||||||||
ID | Project | Category | View Status | Date Submitted | Last Update | ||||
0003793 | Zandronum | [All Projects] Bug | public | 2020-05-29 00:47 | 2024-02-29 06:23 | ||||
Reporter | Soul | ||||||||
Assigned To | |||||||||
Priority | normal | Severity | major | Reproducibility | always | ||||
Status | closed | Resolution | no change required | ||||||
Platform | OS | Microsoft Windows 10 | OS Version | ||||||
Product Version | 3.1-beta | ||||||||
Target Version | Fixed in Version | ||||||||
Summary | 0003793: Mouse has forced smoothening/acceleration on Software renderer | ||||||||
Description | The mouse in 3.1 beta works good on OpenGL, thanks to the fix in 0003314. However, on the Software renderer, it still appears to function the same as 3.0, which is the behavior seen when setting smooth_mouse to 1 in spite of it being turned off. This might be caused by Windows 10's forced mouse acceleration on apps that don't utilize certain types of fullscreen. Odamex had this same problem before, and that was fixed by implementing a new type of fullscreen. | ||||||||
Steps To Reproduce | It's probably easiest to reproduce this problem if one's PC specs and Zandro config are similar to my own, which are: - OS: Windows 10 - GPU: GeForce GTX 970 - CPU: Intel Core i7-3770 - FPS: uncapped - Resolution: 1920 x 1080 (still happens in other resolutions though) | ||||||||
Attached Files | |||||||||
Notes | |
(0021526) Leonard (developer) 2020-08-05 23:16 |
Have you made sure that you don't have the m_filter CVar enabled? What about VSync? If so, could you test both the newest GZDoom and 1.8.6 and confirm if the issue is present? Of course, make sure smooth_mouse/m_filter/vsync are all disabled. |
(0021529) Soul (reporter) 2020-08-10 01:13 |
The note I posted before was in response to a different bug, so I deleted it. Weirdly enough, I can't seem to reproduce this problem anymore. I haven't changed anything in my settings, so perhaps Windows itself fixed this problem on a more recent update. |
(0023106) Ru5tK1ng (updater) 2024-02-29 06:23 |
Reopen ticket if you have any updates on your end. |
This issue is already marked as resolved. If you feel that is not the case, please reopen it and explain why. |
|
Supporters: | No one explicitly supports this issue yet. |
Opponents: | No one explicitly opposes this issue yet. |
Issue History | |||
Date Modified | Username | Field | Change |
2020-05-29 00:47 | Soul | New Issue | |
2020-08-05 23:16 | Leonard | Note Added: 0021526 | |
2020-08-05 23:16 | Leonard | Status | new => feedback |
2020-08-10 01:08 | Soul | Note Added: 0021528 | |
2020-08-10 01:08 | Soul | Status | feedback => new |
2020-08-10 01:08 | Soul | Note Deleted: 0021528 | |
2020-08-10 01:13 | Soul | Note Added: 0021529 | |
2024-02-29 06:23 | Ru5tK1ng | Note Added: 0023106 | |
2024-02-29 06:23 | Ru5tK1ng | Status | new => closed |
2024-02-29 06:23 | Ru5tK1ng | Resolution | open => no change required |
Copyright © 2000 - 2024 MantisBT Team |