So we played a session 3 weeks ago and explored a large cave system. Exposed a lot of the map (server was set to individual fog of war), saved the campaign and called it a night.
We played again on Friday and when we all got in...all of the revealed fog was "re-fogged", for all the player tokens. All we could see was the area that our tokens sight could see, nothing revealed that had already been exposed in the previous session.
This is the 2nd or 3rd time this has happened. I thought all the fog stuff was stored at the token level, so why does it seem to be re-setting?
Running Maptool 1.4.0.5
Fog resetting between sessions
Moderators: dorpond, trevor, Azhrei
Forum rules
Posting now open to all registered forum users.
Posting now open to all registered forum users.
Re: Fog resetting between sessions
During the last FOW update and optimization this behavior was introduced. Because the data was stored on a it would cause lag if not cleared. I think they clear FOW data on restart. I'm not sure, but if you turn off individual views and let it be stored on the server then it will carry over between sessions. This is mostly speculation on my part but someone who actually did the coding like jagged may know better.
Downloads:
- Notepad++ MapTool addon
- RPEdit details (v1.3)
- Coding Tips: Modularity and Design
- Videos: Macro Writing Tools
Re: Fog resetting between sessions
Ugh, turn off individual views? Then all the players can see what everyone has revealed? That seems like a step backwards, since I really don't want the "Normal" vision human to be able to see what the "Darkvision" Dwarf has revealed.
Am I not understanding that right?
Am I not understanding that right?
Re: Fog resetting between sessions
Yes, they'll be able to see exposed pieces of the map but not tokens that they couldn't normally see.
Downloads:
- Notepad++ MapTool addon
- RPEdit details (v1.3)
- Coding Tips: Modularity and Design
- Videos: Macro Writing Tools
Re: Fog resetting between sessions
Thanks for the clarification AM, at least I can stop trying to chase down, "What did I do to cause this???" issues...
- JamzTheMan
- Great Wyrm
- Posts: 1872
- Joined: Mon May 10, 2010 12:59 pm
- Location: Chicagoland
- Contact:
Re: Fog resetting between sessions
FYI, I was able to replicate this in 1.3b91 so it's been this way for at least that long if not longer...
The server does remember the revealed FoW if you just uncheck "Use Individual FOW" and still get individual "views" for each token, perhaps that will work for you?
The server does remember the revealed FoW if you just uncheck "Use Individual FOW" and still get individual "views" for each token, perhaps that will work for you?
-Jamz
____________________
Custom MapTool 1.4.x.x Fork: maptool.nerps.net
Custom TokenTool 2.0 Fork: tokentool.nerps.net
More information here: MapTool Nerps! Fork
____________________
Custom MapTool 1.4.x.x Fork: maptool.nerps.net
Custom TokenTool 2.0 Fork: tokentool.nerps.net
More information here: MapTool Nerps! Fork
- Full Bleed
- Demigod
- Posts: 4736
- Joined: Sun Feb 25, 2007 11:53 am
- Location: FL
Re: Fog resetting between sessions
If this is indeed the case, it's not a good solution.aliasmask wrote:During the last FOW update and optimization this behavior was introduced. Because the data was stored on a it would cause lag if not cleared. I think they clear FOW data on restart. I'm not sure, but if you turn off individual views and let it be stored on the server then it will carry over between sessions. This is mostly speculation on my part but someone who actually did the coding like jagged may know better.
There should be a simple way to look at the FoW information stored on a token... and be able to clear it individually at the same place. That way if people are having performance issues, they can look and see about when it starts to happen and clear it. It might even be nice to be able to set a few options:
1) A warning for when the individual FoW on a token reaches a certain size.
2) An auto-clear threshold.
3) How about a way to have it start clearing earlier FoW data first at a certain threshold so that it keeps a relatively static amount of individual FoW data and the token only "forgets" older FoW instead of forcing users to "clear all"?
Maptool is the Millennium Falcon of VTT's -- "She may not look like much, but she's got it where it counts."
Re: Fog resetting between sessions
Jamz, will bounce that option of our group next time we play. Most maps, its not that relevant, since you get through them in a single session...which may be why I hadn't noticed this, all this time. Its just the bigger, multi session maps that matter.
Full Bleed, agreed, would be nice to have other solutions.
Full Bleed, agreed, would be nice to have other solutions.
Re: Fog resetting between sessions
These two are options, with a caveat. The slowdown (based on performance profiling that I did a long time ago) is in a Java library routine that is beyond the reach of application code. There's no good way to predict when there will be a slowdown because it isn't based on the "amount" of FOW on a given token, it's based on the shape of the aggregate FOW of all tokens. The issue is that there's a single shape that records the exposed area for the FOW for each token. Those shapes are then merged together to create an overall area that is exposed. That shape becomes so complicated -- with combinations of straight and curved edges -- that the Area object in the Java library gets bogged down processing the clipping region.Full Bleed wrote:1) A warning for when the individual FoW on a token reaches a certain size.
2) An auto-clear threshold.
The above is very much YMMV because I had trouble generating repeatable instances of the problem. A slight change to the FOW on one token could cause abrupt and significant changes in the shape of the overlaid FOW, thus having drastic results on the processing time.
There is only a single shape stored on the token so there's no way to store individual time stamps -- "earlier" can never be determined.3) How about a way to have it start clearing earlier FoW data first at a certain threshold so that it keeps a relatively static amount of individual FoW data and the token only "forgets" older FoW instead of forcing users to "clear all"?
The vision system that Craig has planned will allow for entirely new FOW to be calculated on the fly for every token and it will be faster than the existing system (based on some benchmarks of his). We just need to get it implemented...
- Full Bleed
- Demigod
- Posts: 4736
- Joined: Sun Feb 25, 2007 11:53 am
- Location: FL
Re: Fog resetting between sessions
There is no way to pull the timing on the exposure at the end of the FoW render?Azhrei wrote: There's no good way to predict when there will be a slowdown because it isn't based on the "amount" of FOW on a given token, it's based on the shape of the aggregate FOW of all tokens.
Interesting. I can see how shapes could get very complicated very quickly (particularly with irregular VBL). But it's too bad it can't be generating multiple "shapes" and then exposing them in series so that you *could* remove earlier exposures.There is only a single shape stored on the token so there's no way to store individual time stamps -- "earlier" can never be determined.
Even if, for example, every token had a maximum of 4 FoW shapes to render if would probably help significantly.
My guess is that this feature would be pretty far down the list at this point... but it would be nice.The vision system that Craig has planned will allow for entirely new FOW to be calculated on the fly for every token and it will be faster than the existing system (based on some benchmarks of his). We just need to get it implemented...
I, personally, shun Individual FoW due to the inconsistency. It's a nice idea, but not worth the potential performance issues it can cause.
Maptool is the Millennium Falcon of VTT's -- "She may not look like much, but she's got it where it counts."