Updating rivatuner Free webcam recorded sex chat videos
So I update my drivers to the new Nvidia drivers this morning (353.06, GTX 670 FTW) and now Riva Tuner is 100% for sure, not working.
I can't lock my frames anymore nor does the FPS counter show up.
But as soon as you start them, the aquasuite will crash or not work anymore.
Riva Tuner is a x32 application while aquasuite works as x64 and Windows itself already prevents x32 applications to mess around with x64 stuff. NET application as been compiled with the flag "prefer 32 bit" set to disabled.
In the end the the problem is how Riva Tuner as x32 application tries to hook into the x64 aquasuite.
We can not tell if it is Riva Tuner that does something wrong here or if it is Microsoft that must have changed something with the . What we know for sure: we can not fix it; it must be done by Riva Tuner oder Microsoft.
Click on it, and on the right menu of RTSS, under where it says "Application Detection Level", choose "NONE". More specifically RTSS (Riva Tuner Statistics Server). Go to the Input Mapper directory: C:\Program Files (x86)\DSDCS\Input Mapper Add Input Now that you see it in the left panel.
I think this started after the latest Windows10 Creators update.
The current workaround is to put the aquasuite to the exception list of Riva Tuner so it will not trigger the aquasuite anymore.
Those who have the problem that the Aqua Computer service does not start automatically anymore: just reinstall the aquasuite (keep old data) so that the service will be reinstalled too and the problem is gone.
It seems that with the Creators update something in this direction has been changed, extended or whatever and is causing the crash. The default value for this flag is enabled so you will not see problem with most other . Using 32 bit or no GPU acceleration is no solution because data-intense stuff like the charts or logging would see a clear performance drop.
We were able to track down the problem to its root with a test setup that uses Windows 10 64 Bit with Creators Update (Build 15063) and Riva Tuner Statistic Server 6.6.0 or the current 6.7.0 Beta 1 with the profile set to Low/Medium/High. We have done a small hello world demo app to verify this problem with different compiler settings: WPF 64 Bit application (Default Renderer, uses GPU acceleration) = Crash WPF 64 Bit application (Software Renderer, no GPU acceleration) = works WPF 32 Bit application = works (since Riva Tuner is also x32) Windows Forms 64 Bit application (no GPU acceleration) = works Windows Forms 32 Bit application (no GPU acceleration) = works For those who want to give it a try.
And there was no problem with the ISO's that came out early, they're exactly the same as what got released today. Sorry I didn't post this earlier, but I came back to post and I noticed you locked my thread when I first reported the issue. But you can post what's below in the INPUT Mapper news feed so everyone can see it: The problem is with MSI Afterburner and RTSS. Click the big button at the bottom-left corner to add a new program. Mustafa wrote: Hi, the problem was never with Input Mapper or with the Creator's Update.