I haven’t ranted for a while and this seems like a perfect opportunity to do so. This time it’s for “always absolutely perfect” NVIDIA’s ForceWare drivers that everyone praises so much…
Quite some time ago, I’ve switched to Opera browser because everything else is quite frankly shit because of various things, but especially because of dumb ass GPU blacklisting which makes my AMD E-450 APU useless. But Opera allows disabling of this GPU blacklist and I get my HW acceleration back on that old but still perfectly capable APU. So I use Opera on all my systems now. And I’ve noticed that if you have Fast V-Sync or Adaptive V-Sync enabled globally, ALL videos in Opera browser will be all fucked up, stuttering, video shifting inside itself, flickering, annoying as fuck. I didn’t notice this before, because I was using Firefox where even with Fast V-Sync enabled, videos play fine. Just not on anything Chrome based, be it actual Chrome or Opera (and even Vivaldi). So, I’ve filled a bug report to NVIDIA. That was months ago and they still haven’t fixed their shit. I’ve tried as far back as drivers from January 2017 and they all have this fucking bug that for some reason no one else seems to have spotted. Apparently 90% of people don’t have a clue how cool Fast V-Sync is otherwise so they don’t even experience this shit. I use Fast V-Sync for all games because it removes tearing and has no input lag unlike normal V-Sync.
Here’s a kicker though. Windows 10, even though I’ve installed ancient drivers to try and solve an issue, it auto installed newer drivers on its own (Microsoft, stop fucking up with drivers without my fucking permission you utter twats). However, while I’m pissed at Microsoft for doing that, the drivers from May 1st 2017 version 382.05 that get auto installed by Win10 DON’T have this bug for some fucked up reason. It’s especially more fucked up because all the drivers after it from NVIDIA again have this retarded bug. So, why do ALL the drivers before and after ForceWare 382.05 have this stupid bug, but this one doesn’t? And more importantly, why the fuck NVIDIA hasn’t fixed it yet for months?
This shit is pissing me off so much I’m seriously considering just going to AMD with the RX Vega because NVIDIA apparently just doesn’t give a fuck if this crap can’t get fixed for months. Especially now that AMD has Enhanced Sync which is the same as Fast V-Sync. And hopefully with no such retarded issue… What good is all this awesome framerate and shit from NVIDIA if they fuck up basic shit like video playback in most widely used browser engine (Chrome) in connection with one of their most useful features for games? Aaargh
A lot of people will start to scratch their heads on why I’m writing about Battlefield 3 when Battlefield 4 has been out for ages and Battlefield 5 (Hardline) has been in production for ages. The reason for this blog entry is because it took me one and a half years to complete this game. Particularly because of this bug…
It’s a last mission in this game, filled with quite some button mashing sequences. And like all of them through the entire game, I did what I was expected to do. And it worked just fine. Quickly pressing the required buttons. And yet, I was continuously dying here. Over and over again, only in this mission. No matter what I’ve tried, no matter what guides I’ve checked, fail after fail.
And few days ago, I’ve again posted on TechPowerUp forums about it and one user gave a suggestion that my key bindings might be the cause of it. And guess what, he was right. LOL. The first of this kind in my entire 20+ years history of gaming, that’s why it hasn’t even crossed my mind…
Battlefield 3 has a nasty showstopper bug on this exact (and only) part of the entire game that prevents you from progressing further if you are not using default keyboard keys.
I’m the kind of odd retro geek who plays everything with arrow keys and buttons around them. So, arrow keys for movement, RShift for jumping and RCtrl for crouching. However, in this particular segment of the game, game is expecting SPACE button action and the JUMP action to be on the same physical button/key. And because they weren’t in my case, I was dying like suicidal maniac on a Groundhog Day.
I had to reset controls just to get past this train climbing part and after that, I could use my old key binds again. I have serious doubts that EA/DICE will fix this now, but if they are going to do it, that would be nice. It was a pretty good game and I’ll certainly play it again in the future…
If you happen to use a PC or laptop with Realtek driver and you’re “all of a sudden” getting massive CPU usage on process RtkNGUI64.exe, I have a solution for that. The reason for this problem is in registry entry related to SRS Labs which apparently supply certain audio enhancement solution to Realtek.
Deleting this registry entry results in massive CPU usage by the RtkNGUI64.exe process. The problem happens even faster if you use registry cleaners because the registry entry is in fact empty and most registry cleaners treat it as useless (empty) and delete it.
Solution was found by the user “cheshirecat179” on DELL Forums. I’ve just compiled the solution into a registry file that you just have to run by double clicking it (to import registry key into your registry) and then reboot your system. RtkNGUI64.exe should not be using any CPU after reboot.