I fixed a [URL="https://github.com/Mini-Geek/mfaktx-controller/issues/9"]bug[/URL] and released a new version. As always, available at [url]https://github.com/Mini-Geek/mfaktx-controller[/url]

We have had your program go AFK but we have not mentioned it yet.

One instance is set to never change speed. It runs fine.

One instance is set to change speeds based on both conditionals and it changes speeds all of the time, for DPMS, gaming and general browsing. This instance, after a few days (Or cycles?) will get stuck on a speed and will not allow us to stop it or change the speed. (We kill it in the task manager.)

It only happens after several days so we are okay with rebooting occasionally.

The program still rocks and is the only way we can use the computer and do GPU work the way we want to.

:bow:

[QUOTE=Xyzzy;339362]One instance is set to change speeds based on both conditionals and it changes speeds all of the time, for DPMS, gaming and general browsing. This instance, after a few days (Or cycles?) will get stuck on a speed and will not allow us to stop it or change the speed. (We kill it in the task manager.)

It only happens after several days so we are okay with rebooting occasionally.[/QUOTE]

Hm, I've never seen this behavior. When it's stuck, how does the instance look (a screenshot would be good)? If you try to press the buttons (including the X to close), what happens? Does it still update the output log text? Are you using separate mfaktc exe names with a MaxInstances value of 1 on each?

[QUOTE]When it's stuck, how does the instance look (a screenshot would be good)?[/quote]We will get a screen shot the next time it happens.

[quote]If you try to press the buttons (including the X to close), what happens?[/quote]Sometimes the buttons do not respond and sometimes it throws up an error about the max number of instances. If the "X" in the window corner closes the controller, the card continues to run and we have to kill the actual executable. (In our case, "0.exe".)

[quote]Does it still update the output log text?[/quote]Yes.

[quote]Are you using separate mfaktc exe names with a MaxInstances value of 1 on each?[/QUOTE]Yes.

:bow:

When it's frozen, if you kill your mfaktc instance (0.exe) with the task manager, does the controller recover? (When running normally, it handles it well: the status changes to "Stopped" and you can start it again manually.)

Do you know what it was doing when it freezes? E.g. was it switching speeds, dealing with pause and/or slow while running apps running/opening/closing, running unattended, etc.? How much memory and CPU time does the controller use when it freezes, and how does that compare to the controller that always runs?

I don't really know what's up with this...a rather strange problem.

Here is a benign example. The Titan card is running at "Fast" even though we just came out of DPMS mode and it should be at "Medium". The display shows that no speed is selected, but the various buttons did respond when clicked.

[QUOTE=Xyzzy;339524]Here is a benign example. The Titan card is running at "Fast" even though we just came out of DPMS mode and it should be at "Medium". The display shows that no speed is selected, but the various buttons did respond when clicked.[/QUOTE]

I'd noticed and (AFAIK) fixed, on Apr 19, the bug that makes it show "Running (Stopped)" as that screen shot shows. It's possible this is related to your freezing issue. Please update to the newest version (file's timestamp is on 5/5) and see if the problem is fixed.

Thanks!

:bow:

Mini-Geek,

Looks like an excellent utility. Great job.

What is the [I]PropertyChanged[/I] namespace you are referencing in the [I]Controller.cs[/I], if you do not mind me asking?

If that is where you implement the [I]ImplementPropertyChanged[/I] attribute, that seems to be missing from the project on GitHub…

Thank you

[QUOTE=TObject;340022]Mini-Geek,

Looks like an excellent utility. Great job.

What is the [I]PropertyChanged[/I] namespace you are referencing in the [I]Controller.cs[/I], if you do not mind me asking?

If that is where you implement the [I]ImplementPropertyChanged[/I] attribute, that seems to be missing from the project on GitHub…

Thank you[/QUOTE]

That comes from an external dependency, PropertyChanged.Fody. I had hoped it would automagically work, but apparently not. I've now added links on the readme at github: [url]https://github.com/Mini-Geek/mfaktx-controller[/url]

FWIW, the obscure errors we had with your program have stopped since we updated to the latest version.

:bow: