I’ve hit some snags working with the HeroStats memory scanner, so I’ve started doing the next best thing – building my own based on their code.  I’m working in a different programming language than HeroStats was developed in, but I’m definitely making progress.  I’m already accessing CoH’s memory and have a very fast search algorithm locating specific data within it.  Time to start pegging down the locations of specific bits of data now…

I left the LCD code running all day today – about 10 hours straight – and didn’t see any negative side effects.  No memory leaks or escalating CPU usage.

So far, pretty happy with the new drawing routines.  Time to start jamming some CoH data into it.  I think I’ll still piggyback HeroStats in that regard.

So it turns out that Logitech had made some pretty significant changes to their LCD SDK in order to accomodate people with multiple displays, G19 QVGA screens, etc, and the .NET wrapper class I was using hasn’t been updated to take that into account.  I did a little digging, found an updated .NET wrapper, and got to work last night.  As of this morning, I’m outputting and animating on the LCD again, and reading the four buttons under the LCD successfully.

Of course, none of that has anything to do with interfacing with City of Heroes, but I wanted to get the hardware aspects over with first.  On the upside, writing to the LCD is taking significantly less memory and CPU time than it did in the old v1.8 series CoHLCD, and I believe even better than the optimized code I had in v2.0 Beta.  I’m sure it’ll chew up more memory once it starts polling City of Heroes, but at least the CPU time is almost negligible now.

Hey Gang, Duck L’Orange here.  I just wanted to let everyone know that the programming bug has finally bit me again, and I’ve started work on CoHLCD v3.  I was never really happy with Version 2.0 and its integrated LCD editor, which is why it never took off and saw the public eye.  Sadly, this means that hundreds of CoH players haven’t had access to CoHLCD.

I’m building v3 from the ground up, so don’t expect to see it tomorrow or anything… but it IS in the works.