Instalar Steam
iniciar sesión
|
idioma
简体中文 (Chino simplificado)
繁體中文 (Chino tradicional)
日本語 (Japonés)
한국어 (Coreano)
ไทย (Tailandés)
български (Búlgaro)
Čeština (Checo)
Dansk (Danés)
Deutsch (Alemán)
English (Inglés)
Español - España
Ελληνικά (Griego)
Français (Francés)
Italiano
Bahasa Indonesia (indonesio)
Magyar (Húngaro)
Nederlands (Holandés)
Norsk (Noruego)
Polski (Polaco)
Português (Portugués de Portugal)
Português - Brasil (Portugués - Brasil)
Română (Rumano)
Русский (Ruso)
Suomi (Finés)
Svenska (Sueco)
Türkçe (Turco)
Tiếng Việt (Vietnamita)
Українська (Ucraniano)
Informar de un error de traducción
Here is a list of things I've tried that do and do not cause the issue:
Things that cause the problem:
Things that do NOT cause the problem:
From this data, I surmise that the problem is within the game code that deals with button input from the mouse.
I’m running on Win10pro, I7 6700k, 1070 (417.71 drivers) 16 gigs DDR4 RAM.
I had to kill the game using keyboard via the Task Manager and even then the mouse control did not return to normal until a few minutes later.
It did this the first two times that I launched the game, but then it didn't on my third attempt.
I don't know if I had any of the beeping sound issues though. My speakers where turned off while I was playing around with this last night.
Not saying that this is in any way related, but I did notice that many of the .ogg audio files in maiden.grp have been replaced with .wav files. Could this possibly be a factor in any of this?
I've just tried this, and while I got the beeping sound at the beginning (when I was clicking away the start screens), it doesn't happen ingame, and I can turn off Vsync with no problems.
That alone likely is not a complete fix. I was playing in Software mode last night when I experienced this issue, and I was still in Software mode when the issue seemingly stopped (on my third attempt to play the new version). In fact, I hadn't made any settings changes at all between the time when it was not working and when it did begin to work.
1. Open the console with [Shift]+[KeyAboveTab] (usually ~/`)
2. Execute the command
Please let us know if there are any further issues. You may wish to look through your graphics driver's control panel to see what options are available for avoiding screen tearing with an uncapped framerate.
Excellent, thanks!
thank you dude!
How and how did this happen? Why did uncap frame rate solve this? It was solved in a previous "beta beta" and now is presentment!? Why?