Yeah, so this worked fine with my laptop last night. I also got it working on my desktop by importing my reg settings from my laptop and deleting the .maptool folder in my user directory.
sorry dude. I don't know now, fixed it with a warhammer
I really don't play with the settings, so I would guess defaults, plus playing with player reveal enabled and disabled.
Perhaps you and I are talking different languages here( I am not exactly the best with words sometimes), so I will try to be a bit more clear. When you go to File->Start Server, a dialog window appears where you put in your GM name, password, etc as well as a number of check boxes and a drop-down list or two. The important part here is knowing exactly what each and every one of those checkboxes was set or not set to.
Those 8(or so) checkboxes drastically change the behavior of MapTool, and how player(ie, those who are logged into the server from another MapTool client and logged in as a player instead of GM) actions affect what is shown on the screen. THAT is what I was trying to get from you. Even though you have it "fixed" you don't know why it's fixed and thus could encounter the same issue again, so I after offering to help, I would like to truly help you resolve the issue and that means(if you will let me) making sure you understand why it was "broken"(ie, not working the way you thought it should.) You did mention "defaults" but honestly, I have been using MapTool so darn long, I have no idea what(if any) the defaults for those checkboxes are, which is why I asked you to explicitly tell me....
by "I tried player expose and that did'nt work either", I assume that means you started a second instance of MapTool, connected to your server as a player, you as the GM gave the second "player" ownership of a PC token that has sight configured, and started the Server with the option "Allow players to reveal vision" = checked, and then attempted to reveal FOW from the player client MapTool instance, either
- with CNTL+I OR
- via moving said PC token AND your server setting "Players reveal FOW on movement" = checked(or whatever it's called)
If you are doing this all from a single MapTool instance, in which case you ARE the GM, no matter what, then there is only one answer... but I will wait to tell you that once I hear back from you on the other questions I asked.
correct, except what wasn't working was the auto expose on movement and the only currently visible (which made everything go dark for the player) expose (with control I) and last path worked fine.
Thanks for your replies.
Now... not counting the check boxes when you start a server, there is another "setting" that deals with exposing movements. This is in the Preferences (Edit->Preferences), on the Application Tab in the section named "Map Visuals" with a label of "Auto-Expose fog on token movement (GM Only)". Up until about 2 years ago, THIS was the only setting that controlled if movement exposed FOW. However, the GM had no control on this since this is a per client setting.
Soooooo.... I changed the label to add the (GM Only)" part, changed the Start Server Dialog and added the "Auto reveal on Movement" checkbox as a CHILD of "Players can reveal vision"(by child, I mean that if "Players can reveal vision" is NOT checked, then "Auto reveal on Movement" would also be OFF. However, if "Players can reveal vision" IS checked, the GM still has the option to either allow or disallow movement to perform the reveal.
Now, the preference "Auto-Expose fog on token movement (GM Only)" only works if it is checked AND the MapTool instance IS hosting a server(in which case you are always the GM) OR when you Connect to a server and sign in with a GM role.