Azinctus wrote:MAC OS X 10.6.6, Java 1.6.0_22, Memory 1024MB Stack 2MB.
Thanks.
The campaigns listed in my Recent Campaigns menu date from December, I have renamed the large campaign (70MB or so), using save as, at least 5 times since then and opened from the Open choice dozens of times. Need anymore details?
Hm. This works fine for me on my similarly spec'd machine. I believe the RecentCampaigns menu is populated from a Java "Preference" which is stored under ~/Library/Java (could have the directory wrong though).
Edit: Okay, I found it. It's under
~/Library/Preferences and the filename is
com.apple.java.util.prefs.plist. That file is binary and you won't be able to directly view it, but double-clicking should bring up the PList editor. The key
mruCampaigns has the list of recently accessed campaigns. Without looking at the MT code, I can't think of any reason why yours wouldn't be saved...
I ran a session last night and ran into a few problems. The Individual Views broke down a few times. Players could suddenly see areas that had been exposed by other players. As in B.81
http://forums.rptools.net/viewtopic.php ... ow#p184880 I think using the teleport gates on the map may have played a role in that.
I'll look at the functions that the teleport gates use; that's probably the
Wiki: moveTokenToMap() function since I don't think there are any others that can move tokens between maps.
Another odd issue was that a player with a small light source (radius one) that revealed a single ring of partial hexes around their token, could move up the map, exposing darkness but not down. Map Tool wouldn't let the player drag the token one hex towards the bottom of the screen but would allow them to move one hex up. Weird, no? We first saw this issue when the Player was revealing only slightly more than half a hex in each direction but I increased the size of the light and that let the player move in any direction.
This might be related to the new algorithm for determining whether a token can be moved into a square based on the amount and position of the fog that covers that square. The algorithm for the square grid isn't overridden by the hex grid. That may be causing a false negative to be returned that says the token can't move there. I believe I have described the new/current algorithm on the forums already (maybe in reference to the problem depicted by lmarkus?) but I don't have a link handy. It's likely that the fact that hexes treat the center as the origin and squares treat the upper left corner as the origin could be causing the problem. I'll see if a simple shift of the origin might correct the problem well enough for the hex grid to make it work properly.
The final problem was with zoom. I'm not sure what I or, at one stage, one of my players did but we found ourselves 'lost' on the map. The zoom box showed a seven figure plus zoom percentage that randomyl shifted back and forth, while remaining too long to fit the box, and no amount of zooming in or out would bring the map back to a rational level of zoom.
So you didn't try just typing a new zoom level directly into the box?
I can't think of any reason why the zoom level would get so funky -- that's a very isolated variable that isn't written to except in specific circumstances.
When the player had this problem I used Force Players View to bring them back, but when I got it on my GM map I couldn't find a workaround. Opening a new map and returning didn't help, clicking on tokens in the Map Explorer or Initiative list didn't help. It was the end of a great session (these bugs didn't stop us having another great night with Map Tool) so I wasn't too bothered at the time, but I guess it was a serious flaw.
If/when it happens again, please use the Map menu and export the current map and post it here. There's enough information in the .rpmap file to debug a zoom factor problem, I believe.
Then try starting another MapTool and connecting as a GM. You should be able to force everyone again using that second instance.
On the Mac you won't be able to (easily) run a second instance. There's probably a way from the GUI, but I know from the command line you can enter
open -n MapTool-1.3.b84.app and it'll run it a second time. (Obviously you should substitute what version you're using.)
This is a large well used campaign with a mess of macros and this particular map has been the focus of our gaming for months. The FOW has been drawn and cleared a million times and the light settings changed many times too. The link above takes you to a cut down version of the campaign with just the relevant map, I've added more stuff to it since though. If an up to date version would be useful I can organise one and upload it.
How many different versions of MT have you used with this campaign file? For example, if the campaign started with b56 and you've loaded and saved it with 4 other versions (such as b59, b63, b66, and then b77) that might be useful to know.
I've added your list of stuff to my bug list. I'll let you know whether these will be fixed or whether there is simply a work-around to use until 1.4 is stable.
