Most times the program freezes up and crashes while trying to move them or when merging it thinks for an inordinately long time and most times Windows gives up on it and prompts to close the program. Other times it moves fine, but when I change the zoom level to better align the tiles it freezes. I am having to manual merge through layers because the auto-merging doesn't seem to work well at all, usually skipping every session in the Game Map folder and prompting to manual merge. It appears to be the layers window and associated functions that is causing these particular freezes.
I'll check if i can find the reason for that.
Also a few general performance issues. My main map is 34k+ tiles, so I can understand the long initial loads, though one would think it would load faster being on an SSD. Once loaded, rendering while zooming takes a horribly long time; 30+ seconds sometimes to get all the tiles rendered per zoom level. If I try to scroll through several zoom levels it is likely to stop responding and crash. At max zoom out, I am only using 1.5-1.6GB out of 14+GB available.
Biggest map i personally tried was around 20k tiles. I'll do some testing with bigger maps to find the problems.
Another question: Does SessionWatcher also require the Amber Client? I can't seem to get it to work with bdew's.
Yes, it should work with all clients. SessionWatcher uses the Game-Map-Directory Setting. It will watch that Directory and check for Changes.
The Amber Map Directory is a Settings specific to PlayerTracker.
Some suggestions :
Layers should always center themselves at or near 0,0 rather than oddly positioning all over the Main Map.
When choosing a directory for layers, it should default to the Game Map directory. Having to drill down every time gets really tiring.
Will do.
You might consider pre-rendered Zoom levels vs generating them on demand, similar to TP Map Tool. TP Map Tool loads the map instantly and there is no slow progressive loading as what happens here. I also use under 200MB with the TP tool, as opposed to the 1.6Gigs mentioned above (not that I am hurting for memory or anything). Oddly TP Map Tool eats up nearly 30% processor time on a 4-core i5-3570k even when just sitting there doing nothing, so it isn't exactly Nirvana, itself.
Yeah, i guess the crashes are also because of the RAM-Usage. So I'll try to improve that.
EDITI am having to manual merge through layers because the auto-merging doesn't seem to work well at all, usually skipping every session in the Game Map folder and prompting to manual merge.
Can you check the Logfile for the reasons why it couldn't auto-merge?
Not a biggie, just thought I should let you know.