Instal Steam
login
|
bahasa
简体中文 (Tionghoa Sederhana)
繁體中文 (Tionghoa Tradisional)
日本語 (Bahasa Jepang)
한국어 (Bahasa Korea)
ไทย (Bahasa Thai)
Български (Bahasa Bulgaria)
Čeština (Bahasa Ceko)
Dansk (Bahasa Denmark)
Deutsch (Bahasa Jerman)
English (Bahasa Inggris)
Español - España (Bahasa Spanyol - Spanyol)
Español - Latinoamérica (Bahasa Spanyol - Amerika Latin)
Ελληνικά (Bahasa Yunani)
Français (Bahasa Prancis)
Italiano (Bahasa Italia)
Magyar (Bahasa Hungaria)
Nederlands (Bahasa Belanda)
Norsk (Bahasa Norwegia)
Polski (Bahasa Polandia)
Português (Portugis - Portugal)
Português-Brasil (Bahasa Portugis-Brasil)
Română (Bahasa Rumania)
Русский (Bahasa Rusia)
Suomi (Bahasa Finlandia)
Svenska (Bahasa Swedia)
Türkçe (Bahasa Turki)
Tiếng Việt (Bahasa Vietnam)
Українська (Bahasa Ukraina)
Laporkan kesalahan penerjemahan
Amazing but yeah this works, totally smooth now.
But after i stop pressing the wasd key's depending on how long the wasd key's were pressed like move forward's with w key for twelve second's il get a twelve second delay before the game register's the new input,
And when the wasd key's are pressed any other key's like prissing the left ctrl or 123 ect key's will have a input lag do to how long i was holding the w or asd key's,
This is with game graphic's setting's to there lowest setting and i have no option's to turn on/off the keyboard and mouse lighting option as it seem's to be disabled ingame,
As well as setting kill cam's to all off does not seem to help with the wasd input lag issue,
And i have tested it with setting the game graphic's setting's to all max with kill cam's all on and as long as i do not press/hold the wasd key's game seem's to run ok with only useing 22% to 23% of my cpu,
But if i press/hold the wasd key's il jump to 100% cpu usage with my computer tower screaming at me,
I dont think it is denuvo as i dont play multiplayer and have axis invasion set to off and iv even messt with game resolution/resolution scaling and game display mod/v-sync and there not the cause this is all i can think of at this time.
Probably to do with the implementation of the API. Its either got a fault/bug or wasnt handled in a way that lets it act appropriately, but at least we have an answer to the problem.