TOME Metrics: ~v1.10 RELEASE~

[nehal]

I'd be interested to see analytics on Necromancers using my addon, so I can figure out what talents are in need of improvement.

http://te4.org/games/addons/tome/eternaldarkness

I haven't forgotten about this, just been busy working to get prepped to hopefully get a public build here shortly. If that delays much longer, I'll run this for you.

[nehal]

RELEASE

Things are settled and I've been given the green light to go ahead and let people start playing with this!

You can download the latest version at http://efbnet.com/tome/TOMEMetrics-1.01.zip (MD5: 1327FEA3443AB9BB90C20AF0B22B8A12)

Things you might want to know:
-This should run on any modern version of Windows that has the .NET 4.5 Framework installed, which you can get from Microsoft here: http://www.microsoft.com/en-us/download ... x?id=30653
-This will not work with Mono for Linux folks - the Mono project has decided not to implement the WPF UI Framework I'm using. Making a more portable version is a future project!
-You can find your API Credentials by going to your 'My Account' page on te4.org and looking under the API tab
-Directions on Getting Started can be found in-application via the Help button

Known Issues:
-As of v1.01(this one) TOMEMetrics still operates completely from memory. This means it is *fast* to parse large sets of characterdata but is memory-limited. I've tested with sample sets just above 5000 characters and feel like it could probably handle sets three to four times as large, but at some point it is guaranteed to crash when it runs out of memory in the 32-bit memoryspace.
-As such it is highly recommended that you keep your dataparsing logically limited. 5000 characters is every winner since 1.0, for example. But pulling every Archmage ever played, living or dead, at all levels, will probably both take a long time to download AND not be parseable at this time.
-If you can crash it like this please let me know how many characters you're operating with
-A CharacterSet/Storage Management tool will be built into the application in the future, for the time being you can do this yourself by closing TOMEMetrics and renaming the /storage directory to save, but not let the application use, a specific set of characters.

-The API that TOMEMetrics uses is rate-limited by te4.org - While testing says this should not be a problem, if you do seem to hit this limit please let me know. Automated handling of this should be done within a couple of days and I'll post a new build to make sure this is permanently not-a-problem. But I didn't want to hold up the release for a probably-not-a-problem!

Comments, Questions, and Feedback are all super welcome and the About menu in-application has a contact link. You can also contact me via the forums or IRC.

[nehal]

As a heads-up, I am aware of a bug affecting some users on smaller monitors, where the interface does not scale properly and instead ends up either falling off the screen or having sections compacted and overlaid.

I hope to have a fix and a new build up in the next day or two to resolve this, unfortunately I am quite busy away from my development system today.

As an explanation: I developed the interface to have a standard resolution that fit reasonably on my 1920x1080 monitor. Before release, I did add in some code that checks to see if a user has a lower resolution monitor and, if so, scales down the interface appropriately. I tested this on my machine by changing resolutions down to 1280x720. However, for some reason the same logic that checks resolution on my monitor just fine doesn't appear to catch properly on some other monitors and I'm doing my best to investigate and resolve.

[Marson]

I'm on 1920x1080 and it does the same, though I did set my font DPI to 130%. I tried setting the exe properties to ignore high-DPI scaling. That usually works for 32-bit programs (though I then have to deal with small fonts), but that didn't have an impact in this case.

http://kynosarges.org/WindowsDpi.html

[nehal]

Release 1.02

Download here: http://efbnet.com/tome/TOMEMetrics-1.02.zip

I'm incrementing the version because holy hell it's got a bunch of under-the-hood-you'll-never-see-it improvements to the UI.

Also I think the resolution thing is fixed. Please report if it's not.

[nehal]

Just a bump for weekly update news.

Next version is doing a lot of core rewriting for performance's sake before I start worrying too much about big new features(and there are a few planned). Right now it's getting memory usage under control and ensuring that doing so doesn't affect speed too much. I'm predicting the next version should require 1-10% of the memory that 1.02 does when handling the same set of characters!

I'm going to try and target next weekend for the release.

[Sradac]

I think the Creep problem is expectations vs execution. I remember when I went to first play Creep it sounded really cool. Stealthy afflicted? Murder from the shadows? Its like a Doomed...that uses daggers...and has even more darkness stuff! Sounds neat!

And then the actual gameplay was kind of .... meh. Just didnt find it fun. Addon devs have to make early choices interesting. Creeps might get really awesome at high levels but when I played Creep I just felt like a gimped shadowblade. Why wouldn't I just play a shadowblade? I think resource management was the biggest issue on Creep maybe? It's been a while since I played but I seem to remember there being some short-ranged talent to generate Hate that had to be used from Stealth but it also broke Stealth?

Like I said its been a while, I just remember Creep never "wow'd" me. Vector was very cool. The storm based one was cool. Most of your classes were really awesome I was just let down by Creep

[nehal]

Release 1.10

Download here: http://efbnet.com/tome/TOMEMetrics-1.10.7z

1.10's primary change is that it uses index-based analysis. Rather than attempting to hold all stored characters in-memory it keeps an index of relevant detail about all stored characters, and uses this index to decide what to read-from-disk and analyze when Filtering. This decrease memory usage enormously:

Using the same set of data(2918 Characters from 1.2.2)
1.02's Private Set is: 295mb (after loading from disk)
1.10's Private Set is: 107mb (with the index built)

Put into perspective, 1.02 *without loading characters* takes up 106MB.

[Wolls]

I cannot get 1.10 to run. It loads but popup "TOMEMetrics has stopped working" .. with one option to close the program. I'm using Windows Vista. I'm guessing it works for other people?

1.02 runs fine. Good work.

[nehal]

I cannot get 1.10 to run. It loads but popup "TOMEMetrics has stopped working" .. with one option to close the program. I'm using Windows Vista. I'm guessing it works for other people?

1.02 runs fine. Good work.

Can you please get me a copy of your tmet.log file? Either post it here or attach it, or PM it to me. I'd love to figure out why this doesn't work for you and help you resolve it.

[Wolls]

Tome 1.10 tmet.log

20141008221334 Starting ResizeContent()
20141008221334 Window Desires: 1041.6 x 836.8
20141008221334 Windows Reporting WorkArea as: 1024 x 792
20141008221334 Resize Event Passed. New Size = 1041.6 x 836.8
20141008221334 Calculated necessary scaling as: 0.578666666666667
20141008221334 Starting ResizeContent()
20141008221334 Window Desires: 1041.6 x 578.666666666667
20141008221334 Windows Reporting WorkArea as: 1024 x 792
20141008221334 Resize Event Passed. New Size = 1041.6 x 578.666666666667
20141008221334 Calculated necessary scaling as: 0.578666666666667
20141008221334 Starting ResizeContent()
20141008221334 Window Desires: 1041.6 x 578.666666666667
20141008221334 Windows Reporting WorkArea as: 1024 x 792
20141008221334 No Resize Event passed. Ignoring upscaling, checking for need to downscale.
20141008221334 Calculated necessary scaling as: 0.578666666666667


I check the 1.02 log and the resize event does pass there. Any way to force a size or? When I fail, the program shuts down. That's the only thing that jumps out to me.

[nehal]

Interesting. Anything in system Event Viewer?

I'll work on getting a 1.11 up soon with more detailed logging to track down errors. Can you tell me exactly what you're doing that crashes?

Does it crash as soon as you start the program? Does it crash if you try to interact with it? After clicking a specific button?