It is currently March 29th, 2024, 3:45 pm

Monstercat Visualizer not working after Windows 10 October Update

Get help with creating, editing & fixing problems with skins
Krepre
Posts: 6
Joined: March 14th, 2019, 8:03 am

Monstercat Visualizer not working after Windows 10 October Update

Post by Krepre »

Title.

After updating from The October Update (Build 1809) things worked well expect with the Monstercat Visualizer.
I loaded it then Rainmeter froze, I couldn't do anything about it expect of Ending the task in Task Manager.

I'm using the 2.0.2 version of Monstercat visualizer, I also used different versions of the visualizer all of them crashed/froze

Rainmeter Version 4.2
rxtd
Posts: 100
Joined: April 30th, 2017, 11:51 am

Re: Monstercat Visualizer not working after Windows 10 October Update

Post by rxtd »

Can you check if it freezes without AudioLevel plugin?

In my (probably outdated) version of the skin there is a [MeasureAudio] section in the middle of visualizer.ini file. Try to place a semicolon in the beginning of Measure=Plugin line in this section.
Will it still hang after loading?
Krepre
Posts: 6
Joined: March 14th, 2019, 8:03 am

Re: Monstercat Visualizer not working after Windows 10 October Update

Post by Krepre »

Thanks for the quick reply.

I did as you said and when I loaded it it worked! (Thought it took a few moments to load up)

Also the CPU usage when up to 20% for some reason
Last edited by Krepre on March 14th, 2019, 9:27 am, edited 3 times in total.
Krepre
Posts: 6
Joined: March 14th, 2019, 8:03 am

Re: Monstercat Visualizer not working after Windows 10 October Update

Post by Krepre »

Edit: the Rainmeter client itself is also lagging, like really lagging, it takes about 2-6 seconds to register clicks

When unloading the visualizer the CPU usage goes down to normal then Rainmeter responds well.
rxtd
Posts: 100
Joined: April 30th, 2017, 11:51 am

Re: Monstercat Visualizer not working after Windows 10 October Update

Post by rxtd »

Krepre wrote: March 14th, 2019, 9:20 am
Interesting.
Unfortunately, this doesn't really solve your problem: you have just completely disabled visualization.

AudioLevel has an infinite loop if something takes too much time. It's very easy to get with bad FFTSize and FFTOverlap options, but if you have high CPU load even without visualization that's probably not the case.

1) Is it solely Monstercat Visualizer skin that causes high CPU load? OK, I see your second post.
2) Have you tried other visualizers? Do they have same issue?
Last edited by rxtd on March 14th, 2019, 9:37 am, edited 1 time in total.
rxtd
Posts: 100
Joined: April 30th, 2017, 11:51 am

Re: Monstercat Visualizer not working after Windows 10 October Update

Post by rxtd »

Also.
What CPU do you have?
Is it possible that that update turned on Meltdown workaround? It could cause similar issues, although I don't really believe it.
Krepre
Posts: 6
Joined: March 14th, 2019, 8:03 am

Re: Monstercat Visualizer not working after Windows 10 October Update

Post by Krepre »

I have tried other visualiers like Frost and Foundation of Colors, they all work perfectly well

As for my CPU it's Intel® Core™ i7 820QM

Details about my laptop: https://www.asus.com/Laptops/ROG-G73Jh/
Krepre
Posts: 6
Joined: March 14th, 2019, 8:03 am

Re: Monstercat Visualizer not working after Windows 10 October Update

Post by Krepre »

So hey.....

It turns out that I didn't install update KB4482887, which fixes "performance problems and severe mouse lag" (Article 2), and also there was this .NET update : https://imgur.com/a/V87MiTy .

Sorry for all of the time I have wasted, and thank you for the support.

Sources :
https://www.techspot.com/news/79177-windows-update-fixes-bug-caused-graphics-mouse-performance.html
https://hothardware.com/news/microsoft-patches-windows-10-to-fix-performance-robbing-cumulative-update
Krepre
Posts: 6
Joined: March 14th, 2019, 8:03 am

Re: Monstercat Visualizer not working after Windows 10 October Update

Post by Krepre »

After installing these updates, the visualizer works like normal now. Settling at around 6%-12% CPU load

So maybe its the .NET update or the KB4489899 update? But then again it's all fixed now and thank you for your support