Closed ArkiOriginal closed 4 years ago
The game in it's current state is worse than unplayable since the framedrops can get even more agressive than high and unstable ping even in a single 10 minute long deathmatch.
But looks like the stuttering in beta build is high i was tested it on both OS Ubuntu and Windows and game works much better on Ubuntu now
On Windows performance is a bit worse i dont know maybe CS GO and my anti virus program because on Ubuntu i dont use any anti virus software
GDAMSIx86.dll is from Anti Virus DiscordHook.dll is from discord MessageBus.dll is probably from Nvidia
Made an alternative account for testing purposes. (same settings in-game, same launch options, same autoexec)
Reinstalled stuff
No instabilities, only occasional ping spikes and packet loss (might be cause by my own connection).
Tested:
Did the same tests with revalidated files (no invalid files this time??) -> no instabilities.
Scrap that, after 3rd hour of testing the framerate tanked and I got an average of 80fps in a in-game benchmark comapred to ~300 on the stable build.
Hello @santeri0200, @ZeroYamaoka, per "We’ve made adjustments to the 1.37.6.0-rc1 beta to address performance issues. This change is now live for users opted into the beta." at https://twitter.com/CSGO/status/1277422264862953472, please retest this issue.
No performance issues found.
While researching other reasons for the issue downloaded 451.48-desktop-win10-64bit-international-whql.exe (which seems to be hidden because of reasons) instead of 451.48-desktop-win10-64bit-international-dch-whql.exe and noticed a performance uplift and removed a weird fps cap that capped fps to 330 unless the gpu was able to push over 500? Might be completely different issue, need more investigating on different hardware.
Can @ZeroYamaoka confirm the update working for them?
I tested on Bot Deathmatch and i didnt find any performance issues (On Windows)
Thanks for retesting, closing.
Your system information
Please describe your issue in as much detail as possible:
Steps for reproducing this issue:
Additionally
User controlled software running while testing: