MfaktX Controller (Windows)

[Mini-Geek]

Originally Posted by Mini-Geek

I can add that. The thought had crossed my mind, but I wasn't sure if it'd be used so I hadn't done it yet.

Hm...maybe it should only automatically scroll down again if it was scrolled to the bottom when the new line came in. I'll see if I can improve this. I had based it off of the Windows command window, which does a similar thing.

These are added. The scrolling can still be a bit wonky, but it's much improved. If you want to scroll around, select and copy text, etc. and avoid all weird behavior, check the Select Mode box.

Originally Posted by Xyzzy

FWIW, we have tested the screensaver option with both the DPMS screensaver (in the "Power Options" control panel) and with the "blank" screensaver (in the "Personalization" control panel) and neither worked.

We are using Windows 7, if that helps.

That sounds exactly like my setup, but it works for me. I've made tweaks to that process recently (most recently in the build where I added the startup speed option), and I know I fixed a bug where it would go back to Medium when it switches from the Blank screensaver to the DPMS "screensaver" (screen off). If you were using an older build, upgrade and let me know if anything changes.

Originally Posted by Xyzzy

Finally, since you can detect that an instance is running, is it safe to assume that you can detect other things running? If you can, could you implement a "PauseWhileRunning" option?

It never hurts to ask!

Seems like I should be able to. I'll let you know when it's done, or I've decided it's unfeasible (for now).

Originally Posted by Xyzzy

Christmas List:
Option to start at a particular speed.
Option for "PauseWhileRunning".
Option to show which GPU is being used in the window and/or title bar.
Option to specify a font for the console output.

The startup speed option has been added.

For the third, What exactly were you thinking would be shown? E.g. "GTX 560" (GPU model), "0" (the device number), something else? A simple way to implement this would be to add an option to set a string that I'll show in the app, so you could call them anything you like and I don't have to worry about determining what makes sense.
Would anyone running multiple instances always specify the device number with -d? I'm not sure how you were able to get it to work in two directories before you noticed the arguments option. I could look for the -d x option in the arguments and show that device number.

There's also now a font option.

[Mini-Geek]

Originally Posted by Mini-Geek

Seems like I should be able to. I'll let you know when it's done, or I've decided it's unfeasible (for now).

PauseWhileRunning has been added. Let me know how you like it.

[Xyzzy]

Update:

We are using the original build and the screensaver part works. We perhaps did not give it enough time before. When we resumed working on the computer and looked at the screen buffer it showed the program switched from fast to medium.



As for the card description, a variable that the user can specify will be fine. We just need a way to be able to tell which window is which card.

We will download the newest version to try all the cool stuff!

Thanks for the awesome work!

[Xyzzy]

I'm not sure how you were able to get it to work in two directories before you noticed the arguments option.

R. Heinlein once said, "Never underestimate the power of human stupidity."

[Mini-Geek]

Originally Posted by Xyzzy

Update:

We are using the original build and the screensaver part works. We perhaps did not give it enough time before. When we resumed working on the computer and looked at the screen buffer it showed the program switched from fast to medium.

Ok, good. It should have started switching within half a second, (at default settings) but it does switch so fast that it can be easy enough to not notice what's really going on without looking closely. Especially with scrolling issues possibly making you look at the wrong spot. Anyway, if you have more problems, try to let me know the circumstances (e.g. what combo of screensaver/powersaving do you have enabled, and what was active at the time).

Originally Posted by Xyzzy

As for the card description, a variable that the user can specify will be fine. We just need a way to be able to tell which window is which card.

Ok, I've added that.

Originally Posted by Xyzzy

We will download the newest version to try all the cool stuff!

Thanks for the awesome work!

You're welcome.

[Xyzzy]

Latest report:

The screensaver definitely works now, and very quickly. (Is there a lot of overhead to poll every half second?)

The option to stop the screen buffer to view the output works perfectly. We set ours to 10,000 lines and so far there is no problem. Being able to scroll back is just awesome.

The user-specified string to identify cards works well. If we had the option to tweak the window title name to just say the string and the speed then we would be able to tell the status of the cards from the task bar. Right now the program name takes up a little more than half of the button so we can see the user string if we keep it short. But, this is really not that important.

Since "PauseWhileRunning" works, would a "SlowWhileRunning" option be viable?

[Mini-Geek]

Originally Posted by Xyzzy

The screensaver definitely works now, and very quickly. (Is there a lot of overhead to poll every half second?)

AFAIK there is not. Early in development I had accidentally set the interval at 3 milliseconds, and the app still used no noticeable resources (0% CPU time, totally responsive). I've since added a second call that's done each time (to check if the DPMS screensaver is off), so it might have more overhead than it did at that time, but hopefully not much worse.

Originally Posted by Xyzzy

The user-specified string to identify cards works well. If we had the option to tweak the window title name to just say the string and the speed then we would be able to tell the status of the cards from the task bar. Right now the program name takes up a little more than half of the button so we can see the user string if we keep it short. But, this is really not that important.

I'll move the "MfaktX Controller" part to the end (like every other program does...apparently I should look for conventions like that ). I'll try to see whether the instance id before or after the status would work better.

Originally Posted by Xyzzy

Since "PauseWhileRunning" works, would a "SlowWhileRunning" option be viable?

I knew that was coming. Shouldn't be too hard.

I'll be getting to these tonight, most likely.

[Mini-Geek]

Originally Posted by Mini-Geek

AFAIK there is not. Early in development I had accidentally set the interval at 3 milliseconds, and the app still used no noticeable resources (0% CPU time, totally responsive). I've since added a second call that's done each time (to check if the DPMS screensaver is off), so it might have more overhead than it did at that time, but hopefully not much worse.

Still not noticeable, even at 1 ms.
From running some simple speed tests, the idle check can run around 1.3 million times in a second - so even at 1 ms, it's nothing. The pause/slow check, however, can run about 800 times per second. Still insignificant at 500 ms intervals, but enough that I've decided that should have a configurable interval (and the other doesn't really need it).

Originally Posted by Mini-Geek

I'll move the "MfaktX Controller" part to the end (like every other program does...apparently I should look for conventions like that ). I'll try to see whether the instance id before or after the status would work better.

I knew that was coming. Shouldn't be too hard.

I'll be getting to these tonight, most likely.

I've made these changes.

[Xyzzy]

[Xyzzy]

We just tested the new version. It works perfectly.

With three profiles we are able to let our primary GPU run all of the time.

Fast = Screensaver on. (GPUSieveSize=128/GPUSieveProcessSize=8)
Medium = Normal computer usage, with no lag, ever. (GPUSieveSize=32/GPUSieveProcessSize=8)
Slow = Gaming at 60FPS with vertical sync on. (GPUSieveSize=4/GPUSieveProcessSize=8)

The taskbar title reordering is perfect as well.

[kracker]

Looks interesting. Will have to try it out later