Btw, what about 'VECTORS' and other switches? Maybe it would be better to have just one 'extra flags' field, so the GUI is independent from possible future phoenix changes/additions.

Regards

Yeah, VECTORS and BFI_INT.I thought they would be included in the HD58XX+ or whatever checkbox but when i put in VECTORS and BFI_INT after my specified aggression value my Mh/s got alot higher.But not nearly as fast as the standalone phoenix (300Mh/s vs 345Mh/s, a 5850 clocked @ 875/300).

But now I get the strange subscript error that many gets so I've left your Phoenix GUI for now.

Btw, what about 'VECTORS' and other switches? Maybe it would be better to have just one 'extra flags' field, so the GUI is independent from possible future phoenix changes/additions.

Regards

Yeah, VECTORS and BFI_INT.I thought they would be included in the HD58XX+ or whatever checkbox but when i put in VECTORS and BFI_INT after my specified aggression value my Mh/s got alot higher.But not nearly as fast as the standalone phoenix (300Mh/s vs 345Mh/s, a 5850 clocked @ 875/300).

But now I get the strange subscript error that many gets so I've left your Phoenix GUI for now.

Little bug I guess. When Stopping minning, then starting it again idle timer doesnt reseting too. Had to manually add 'platform=1', so it would be mice if u could add it permanently ( means ability to choose which platform)

Little bug I guess. When Stopping minning, then starting it again idle timer doesnt reseting too. Had to manually add 'platform=1', so it would be mice if u could add it permanently ( means ability to choose which platform)

Figured it out, apparently I was incrementing the same variable in a function that has that variable in it as argument (x1000).What do you mean by platform=1?

Uploading the fix soon. Also disabled the affinity thing, in case of only 1 core.

Also any chance to ability to display Hashrate as OSD (consumes much CPU on higher aggression for me) or somewhere in GUI window?

EDIT:

Maybe just instead of restarting miner it should close current one and start backup one if available ( or checkbox whenever switch if idle or restart). Then after specified time return to check if its working.

I've been trying out the 1.3a beta. It's about 3% slower on my Radeon HD 6870 with the same settings than running phoenix directly, but I'm not sure why. Also, it seems to go to sleep when my PC is running the screen saver. My reported hashrate from the server drops way down, and when I come back from screensaver the OSD reads "Restarting...". It's possible that the underlying phoenix bug is biting me. Perhaps the GUI doesn't properly detect idleness when the screensaver is running?

Try 1.3b, I fixed a couple unintended bugs.If you're using multiple graphics cards, it could be setting affinity all to the same core (if you used that), which could result in a little loss of performance.

Trying out the client now, so far I like it, the affinity setting is something I really like, and the backup option was just what I was looking for. One thing though is the OSD is always click-through for me no matter if I hit the button or try to alt-tab to the window or anything. I saw someone else had this problem but I didn't see any resolution, has anyone come up with anything for this?

Finally I was able to show the OSD, it was on the upper left corner of the desktop and I just moved it before clicking "Click Through" to lock it's position. So far working good! Thanks for this GUI! The restart option is very handy indeed! I will be testing it with a dual card system. Have just tested it with a single card. I get the same Mhash/sec with the console version.

P.S.Would there be a way to change the font color to like Green or White or Black or something? The red font is kind of hard to view . I know I may be asking too much but it would greatly help.

Finally I was able to show the OSD, it was on the upper left corner of the desktop and I just moved it before clicking "Click Through" to lock it's position. So far working good! Thanks for this GUI! The restart option is very handy indeed! I will be testing it with a dual card system. Have just tested it with a single card. I get the same Mhash/sec with the console version.

P.S.Would there be a way to change the font color to like Green or White or Black or something? The red font is kind of hard to view . I know I may be asking too much but it would greatly help.

Sure, it's an easy change:Go to line 51 in the source, should read "$pen=_gdiplus_pencreate(0xffed1c24,2)"Change the 0xffed1c24 to an RGB color you want.Recompile!

Finally I was able to show the OSD, it was on the upper left corner of the desktop and I just moved it before clicking "Click Through" to lock it's position. So far working good! Thanks for this GUI! The restart option is very handy indeed! I will be testing it with a dual card system. Have just tested it with a single card. I get the same Mhash/sec with the console version.

P.S.Would there be a way to change the font color to like Green or White or Black or something? The red font is kind of hard to view . I know I may be asking too much but it would greatly help.

Sure, it's an easy change:Go to line 51 in the source, should read "$pen=_gdiplus_pencreate(0xffed1c24,2)"Change the 0xffed1c24 to an RGB color you want.Recompile!

It seems phoenix.exe is launched with incorrect parameters (i.e. lacking a space) when fastloop is disabled. In Process Explorer on phoenix.exe (Properties > Image):phoenix -u http://user:pass@bitcoinpool.com:8332 -k poclbm VECTORS BFI_INT FASTLOOP=falseAGGRESSION=7 DEVICE=0 WORKSIZE=512 -q 2This probably causes both the fastloop and aggression settings to not be parsed. For some reason when launching like this (also when launched manually in a command-prompt), on my system the miner only uses up to 82% GPU and thus a lower hashrate.

EDIT:On second inspection it seems that FASTLOOP=false is still parsed even if another argument is directly attached to it, so only the aggression argument is ignored. Apparently my card needs fastloop to run at full-speed, so I should have just enabled it in the first place.