LOS buttons suddenly unavailable

[Robin Reeve]

Hi all,
Strange bug here.
Using VASSAL 3.5.8/VASL 6.6.2.
The LOS buttons and functions worked well, but now the buttons are shaded and unusable...



Any clue to solve this problem?

Thanks in advance for the answers.

 

[Robin Reeve]

Autosolve : I relaunched VASL and the buttons work.
I think it bugged when I tried LOS while the "Turn on/off the highlighting of broken units/weapons" was on.
Even after when I toggled that button off, the LOS buttons didn't work.

 

[DougRim]

This is not a bug. I have deliberately programmed the los buttons to disable once your opponent selects one of the buttons. Once your opponent stops los checking, your buttons will turn themselves back on.

Let me know if you are seeing any different behaviour.

The reason for this was to try and prevent los checking from freezing the game, which appeared to happen if both players clicked the los button at the same time. Not every time but often enough. I have not received any bug reports about los freezing since 6.6.2 was released so I am hopeful that disabling the buttons has solved that problem.

The disabling should not happen on your local machine. It will only effect your opponent's device. And can only be cleared by the person who initiated the los check closing out the los engine (by left clicking on the map), which will then enable the buttons on their opponent's machine.

 

[Robin Reeve]

Doug,
Thanks for the explanations, but I don't think that they apply to my situation.
I was not online, only playing solo.

 

[DougRim]

Doug,
Thanks for the explanations, but I don't think that they apply to my situation.
I was not online, only playing solo.

Well there is no other way for this to happen so I don't know what to tell you.

You might revert to 3.5.5 as that is the VASSAL version I used to build VASL6.6.2. I cannot replicate your problem using 6.6.2/3.5.5. Perhaps there is a change in VASSAL3.5.6 + that is allowing the buttons to be disabled.

You could also create a log file and triggers this to happen and then send me the log file. That may help me figure out how this is happening. At present, I have no idea.

 

[Robin Reeve]

Thanks Doug !
The problem only occurred once.
I didn't make a logfile, unfortunately.