I have noticed a serious difference in speed between the 32-bit and 64-bit versions of Java. Since I made sure I only have 64-bit java on my pc the games I run are much smoother (use maptools version 1.4.0.5).

I can try to get the debug information but the laptop belongs to a friend of mine. Since i don't plan on seeing him until next game, I will ask him via Facebook to get a copy of it and send it my way so I can post it here. His schedule is pretty full though so there may be a wait for the information.

There used to be multiple bats to run... it's easy enough to create a custom bat though. I usually create custom bats for my players catered to their systems and OS. One size does not tend to fit all.

How do I create a custom .bat?

I heard back from the player last night. He hasn't had time to look at it.

And while I don't know exactly what he has on his computer as far as settings and software, I do know that it is slightly better than the laptop I was using. The short version of the story is that I bought 2 laptops, one for me and one for my wife that were very similar. Both Dell Studios but after a long period of not using mine, I sold it to him. My wife kept hers and now that we are using Maptool again, I dusted it off and updated everything for my use.

My wife's laptop is almost identical but it only has 2GB of RAM instead of 4GB. Aside from the difference in memory and screen size, everything else is the same so now I'm scratching my head trying to figure out why a 4GB setup would have trouble running Maptool when the 2GB setup doesn't seem to have any issues at all.

Edit: I looked at some of your other posts Full Bleed and found the mt.cfg file. Mine is set to 512 with StackSize+2. So if that is the issue on his laptop, it must be set lower than that.

Edit: I looked at some of your other posts Full Bleed and found the mt.cfg file. Mine is set to 512 with StackSize+2. So if that is the issue on his laptop, it must be set lower than that.

Yeah, he could be using the default 256 which always causes problem for people.

I would take yours up to 1024 with a 4 stack.

And you can put his at 2048 with a 4 stack.

Make sure you BOTH are using 64 bit java. This is the most important bit. Verify this in his Gather Debug (don't take his word for it... a lot of people think they're using 64 bit java when they aren't.)

_________________Maptool is the Millennium Falcon of VTT's -- "She may not look like much, but she's got it where it counts."

Well we played another session yesterday and I've got some good news and bad news.

I double checked his system and he is runnin 64-bit Java with Maptool 1.4.05 with a MaxMem of 2048 and Stack Size 4. I am running MaxMem 1024 and Stack Size 4.

The server was setup with players being able to reveal Fog of War and Individual Vision for each token but not individual Fog of War.

We started playing and less than 10 minutes into the game, there was the issue with lag. It was so bad that he couldn't move any of the player tokens on his computer. And we spent about 30 minutes troubleshooting it without any progress but then there was a breakthrough! He turned off the Snap to Grid on his token and it could move freely without any noticeable lag. So we played the rest of the game with Snap to Grid off.

As the group moved through the cavern, their individual light sources revealed the FoW just as I had hoped it would but I'm not sure if that was Auto-Reveal (since it had been checked on the Server setup) or if the player was revealing the area manually when he stopped. I seem to recall back in the day that Snap to Grid had to be on to auto-reveal FoW but now I'm wondering if that has changed in some of the more recent Maptool updates.

The server was setup with players being able to reveal Fog of War and Individual Vision for each token but not individual Fog of War.

We started playing and less than 10 minutes into the game, there was the issue with lag. It was so bad that he couldn't move any of the player tokens on his computer. And we spent about 30 minutes troubleshooting it without any progress but then there was a breakthrough! He turned off the Snap to Grid on his token and it could move freely without any noticeable lag. So we played the rest of the game with Snap to Grid off.

As the group moved through the cavern, their individual light sources revealed the FoW just as I had hoped it would but I'm not sure if that was Auto-Reveal (since it had been checked on the Server setup) or if the player was revealing the area manually when he stopped. I seem to recall back in the day that Snap to Grid had to be on to auto-reveal FoW but now I'm wondering if that has changed in some of the more recent Maptool updates.

Well, a couple things possibly going on here...

You use two settings that I don't use so one is likely to be causing the problem:

1) Players can Reveal Vision1A) Auto Reveal on Move...

I'd guess it's the auto reveal... I reveal FoW using Ctrl-I or a macro on my GM sheet using Wiki: exposeFOW(). Doing manual reveals probably greatly reduces the number of reveals since many times it just isn't necessary or people might pickup and drop their token 3 or 4 times a move (doing 3-4 exposures when 1 would have sufficed.)

I don't know why turning off snap to grid fixed your problem unless doing so reset the token's FoW... a dev more familiar with that might have an answer.

_________________Maptool is the Millennium Falcon of VTT's -- "She may not look like much, but she's got it where it counts."

I spoke with the player about an hour ago and he was revealing the FoW manually. It's an "okay" workaround for the cavern map but I'm hoping that we can use the auto-reveal on future maps. I guess my next step is to reach out to the Devs and see if they know what's going on.

The best thing you can do is go back to your original settings and see if it happens again. If so, tell us your exact server settings and post a copy of the campaign file along with memory settings and # clients connected.

Obviously if we can recreate this outside of your live game, that would be helpful. We may not be able to get you a full fix but there's a lot of experienced players here that could suggest changes to server settings/fow/lights to alleviate some of the pain.

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot post attachments in this forum