To everyone... sorry I haven't been around. The best way to find me is posting in the HFM Google Group.
http://groups.google.com/group/hfm-net
bollix47 wrote:EDIT: Managed to get past the above by installing mono 2.4 from:
http://directhex.mfgames.com/hardy.html
It's still a little fragile .... e.g. if I click on any of clients 9 thru 12(sorted by ETA) the program immediately closes .... doesn't do that for clients 1 thru 8. Anyway, at least it now does come up and I was able to import the clients from FahMon and the bonus is being calculated on the a3 and bigadv a2 clients which is what I was looking for.
Yeah, Mono just doesn't "work" like the .NET Framework. I'm going to be buying a package soon that will allow me to test and debug directly on Mono/Linux right from Visual Studio. This should go a long way in making Mono/Linux support better in future releases.
Have you tried Mono 2.6? It was released recently. Alas, I haven't had time. One of the fixes on the list was much improved DataGridView support, which is the control HFM uses to display clients... so I'm crossing my fingers.
patonb wrote:Nathan_P wrote:
They haven't been listed on Psummary yet
If it wasn't, then explain why fahmon had it all correctly? Took 3hrs for it to come out in hfm after fahmon displayed it.
bruce wrote:The psummary data is updated dynamically so if a project is available for a while and then the server goes down or for some other reason the project is suspended, the data will no longer appear on-line. I think that FahMon stores the information locally so it keeps it even after the project has finished. (HFM may or may not do the same thing.) In any case, you won't have the information in HFM unless you update the data at a time when the project is showing in psummary.
HFM does cache Project information. Please see the following post in the HFM Google Group.
http://groups.google.com/group/hfm-net/ ... d6577853e#
AZBrandon wrote:Thanks ChasR, once I got a new WU, it was back to reporting all information again. Seems to be something that may work or fail based on WU, but hey - good to hear the developer still updates the code. It seemed like fahmon was pretty much abandoned at this point.
Zagen30 wrote:Forgive me if this has been mentioned before- I did look to see if anyone else had reported it and didn't find anything.
HFM can get confused if the client starts up and tries to send a previously completed WU. For instance, earlier today my GPU client wouldn't send a WU, and this is what happened when I started the client up next:
The 5767 was the one that had already been completed, and the client was working on the 5781. HFM thought that the client was doing a 5767, and as such the PPD calculation was way off (of course, since the low 5780's aren't in the psummary, it now tells me I'm getting 0 PPD, but that's not HFM's fault). I unfortunately didn't get a screenshot.
*EDIT*
After checking the Google group Harlam has, it seems he already knows about this bug.
To AZBrandon and Zagen30...
HFM parses out much the entire FAHlog file on refresh, and when it does it tries to determine the boundries of where WUs begin. This is a tough chore as you can see and a much more "detailed" approach than any other application has taken as I think most others just parse out the end of the FAHlog file. There are so many variations to the logs and it's unpredictable at times. I'd have to say that users run into this kind of issue 1 out of 100 times. So no, it's not perfect. All I can do is fix situations when they are brought to my attention. Next time you have one of these issues, please send me your log files (harlam357 at gmail dot com). I'm going to implement a feature that will make send me logs for errant clients somewhat automatic, but it's going to take some time.
Thanks for that log snippet Zagen30. I'll fix that issue and add it to my test suite. To be honest, I've never seen the client try to autosend at that juncture. So yes, in that case, at that point in the log, HFM captures the first "Project: " string it sees and it thinks that is the Project.
P5-133XL wrote:There is something wrong with the psummery for p5781. They all give me 1M+ PPD in hfm.net. Theoretically it could be a HFM.net issue, but it doesn't happen with any other projects, so I'm assuming that the problem is with Psummery rather than HFM.net.
I had another user have this issue with his GPUs. He said he had some faulty information from the psummary. Not sure if the psummary was actually gunked for a short period or what was going on. If you're still having the issue can you check the benchmarks for the project in question and see if the k factor value is greater than 0.
Otherwise, please see this post in the HFM Google Group and try replacing the ProjectInfo.tab file manually.
http://groups.google.com/group/hfm-net/ ... d6577853e#
