Unable to change vision setting

[Norman Hammond]

It seems i'm unable to change the setting for vision anymore. I attempted this with a brand new fresh campaign/map and when i went to check vision it stays on Disable. If i do Set to Day or Set to Night the checkbox does not move nor do any of the settings change.

[Idle Ideas Inc.]

What version are you using? Please update to the latest version (1.14.2), if you haven't yet. Are you on Windows?

Thanks.

[Norman Hammond]

Sorry about the long delay on replying to this.

I'm on 1.16.5 and the problem still persists. I load my campaign file, and everything works. But as soon as i start a server the whole thing breaks, to the point not even copy paste controls seem to work either.

https://drive.google.com/file/d/1CAwFuag3mmkYs3LEd1OZUNW-6ruXYt9J/view?usp=sharing

Here's the file, it was too big to attach normally. On a side note the updater seems to have issues as well. It took me 3 tries with it crashing before i was able to update my mote to the latest verison using it. (this was after having done a nuke, re-install and download of 1.16 on the site just now and then wanting to update to the 1.16.5).

[Idle Ideas Inc.]

Sorry to hear this, Norman. Checking it out, I think it's a different issue. The toggle gets set but the fog doesn't render, yes? We've added some new features such as MELs and movable drawables, and it has impacted fog, inadvertently, the transparency of fact, to be exact. It gets drawn completely transparent, for "older" maps. This has been fixed. We'll issue an update soon.

We can't replicate any crashes though, what did you exactly do, after starting a server?

Thanks.

[Norman Hammond]

So the toggle doesn't get set either. Set to day, night, off, fog on/off, no matter what the menu shows as if i hadn't changed anything. I coudln't even copy/paste a token between maps.

These were my exact steps.

1. Load campaign file

2. Go to temple of mild doom map (i've tested this on undercrapt map as well, but just in case thats important as i ran into this when i went to start the server to begin testing vision blocking)

3. Confirm menu options (setting day/night, fog on/off) and copy paste work between maps.

4. Start server

5. Repeat steps 2. Menu doesn't update any changes (checkbox will not move from whatever option it was previously on). Attempt to copy/paste/delete token, none of it responds.

Now i will mention, i can still move, drag in to create new from the resource library, and delete objects on the map, so that seems to work, but copy/paste doesn't work, drawing won't work, map settings won't work

If it helps i've attached the server startup settings just on the off chance that has anything to do with it.

I checked the log viewer, but nothing appears when i attempt any of the fog of war or day/night stuff (checkmark won't move or turn on/off for anything).

I'm on windows 10 pro if that also helps. (i've attached a couple of pieces from the debug info).

I'd love to know what is different between our setups that we're getting 2 different results because i've been able to re-create this issue without fail every time (attempted 4 times now).

[Idle Ideas Inc.]

Thanks for the extra info. We were about to release an update, but will now need to reprocess it, after nailing the cause of this issue. The setting does not get set, due to a broken connection to the server. With the connection severed, notifications for all clients, including the origin, do not get to the recipients. The connection gets broken, due to an invalid/unsupported setting. We caught it on our end, because our router has UPnP disabled, which caused an error that broke the server connection. This has been fixed. 

Try simplifying your server startup, by toggling off items, until you see the vision toggle work. You'll be able to identify which setting is the culprit and report it to us. Hopefully, however, we got it fixed so you don't have to do that.

We experience no freezing, however. We suspect it's caused by your low memory settings, fairly large maps with VBL, and path finding enabled. Path finding, is an expensive operation that is best done on well-made maps that constrain the working area, and an ample amount of memory for leg room. Pile on individual FoW, then it will strain the rendering process. We suggest to adjust the server policy on path finding, to be active only for maps you plan on using them on. Turn it off, when not used. Thinking about it, we'll probably amend the map model, so that users can define path finding, on a map to map basis. Not on this release though.

[Idle Ideas Inc.]

The update is out. Hopefully most, if not all, these issues were addressed. Do let us know :)

[Norman Hammond]

So far so good. Though i will note i'm getting some performance issues on one of the maps (undercrapt) if i use vision on it.

If i turn off the "lights" rendering toggle this is fixed. This was an issue before that i remember was fixed, but it seems to be a problem again. (i upped the memory to 4 gigs and stack thread stack to 8 on the launcher, forgot to reset those when i re-installed.)

[Idle Ideas Inc.]

Good to hear.

It's not likely, however, that a performance issue has re-occurred due to the same reasons. It's more likely that something new is causing this, though you can try and go over the vision-related threads in this forum, for some insight. Try to reset fog, and/or recreating tokens/light sources, as well.

Your thread stack size is too high. Mote uses a lot less than MT, so try knocking it down, until you get to a minimum. Stack size is really only important for executing Motescript, due to the recursive nature of its inherited parser. If you aren't aware of it yet, this value sets the size of every thread that runs in the application. There are a lot of those, ranging from dozens, to potentially even hundreds, at a given time. 

[Norman Hammond]

Ok, i'll try that out, i had the stack size that high due to some particularly large macros utilized within maptools.

[Norman Hammond]

Ok, so that helped a bit, but i did run into a new issue.

While running a session we ran into an....interesting issue.

For some reason while people were connecting to the server we had some initial issues, first we had to fix a bunch of macros (i made a separate issue for that), but this resulted in the strangest error ever.

1. I restarted the server so everyone could get the updated campaign macros

2. Players then started using said campaign macros.

3. One player somehow, not certain how, but they were still calling the old macros....which caused that map to crash. I couldn't touch any tokens, and i was forced to swap to a different map. But i couldn't swap back to the old map ever.

4. I restarted the server, issue happened again.

We had 4 people connected, and only 1 person got this, and we can't track down what they remotely did differently to somehow get old campaign macros. The only thing we can really narrow down here is they set their maptools directory in mote's launcher, and no one else bothered to, but i don't see how that should be related considering its campaign macros, not global macros (and i checked over and over to make sure they weren't using global macros).

[Idle Ideas Inc.]

sounds like a synchronization issue. that one player  didn't finish getting the update, or never got it (i think it's the former). he then pushed the old state to the others, which may have caused everything to go south.

we'll look into it, but I suggest, for now, do not use verbose campaign macros. instead, put such macros on libraries and only use campaign macros as triggers/calls.

[Norman Hammond]

So we've tried using the program again and i swear the issue pops up once the 3rd person connects we start getting massive de-sync issues. Which is bad considering we're usually working with 7 or 8 people in maptools.

Our most recent one was a player started making macros on their token, and about a minute later it removed it from them. I could still see it until i un-impersonated/re-impersonated about 4 times at which point the macro was gone on my end also.

Then another player modifier their token image. This resulted in my whole program locking up saying it couldn't access the resource. I attempted to fix it, but instead it compounded the issue where when i reset their character image it only updated on their end and instead it force updated back to the problem image on my end and extra froze the server.

[Idle Ideas Inc.]

Sorry to only see this now. Not much time left to work on these projects right now.

Is it possible to have a copy of your campaign file? We'll need it to hunt down the culprit of this sync issue. Thanks.

On Monday, May 28, 2018 at 3:29:54 AM UTC+8, Norman Hammond wrote:

So we've tried using the program again and i swear the issue pops up once the 3rd person connects we start getting massive de-sync issues. Which is bad considering we're usually working with 7 or 8 people in maptools.th