witchbottles
Forum Guru
This, PLEASE fix the double HIP on DTO boards? My eyes are just not that good anymore!!!Really looking forward to the improved acq management and the fix on hip rotated Guns
Thanks everybody!!
This, PLEASE fix the double HIP on DTO boards? My eyes are just not that good anymore!!!Really looking forward to the improved acq management and the fix on hip rotated Guns
Thanks everybody!!
Seconded, just read David's ideas on linking counters as a generalised solution to acquisition - great idea!Really looking forward to the improved acq management and the fix on hip rotated Guns
Thanks everybody!!
Honestly, I am never watching what happens to the black border on the last object I was working with because I am focused on the new item I just left-clicked on, so that I never seem to realize that the previous one is still selected. I can say with certainty that the Shift key is not involved. Usually, before I do a right-click operation, I select the next object I want to manipulate with a left click. That should be enough to de-select the previous item, shouldn't it?Maybe it's a Windows thing, but when I right-click the turn marker, the selection box goes away from the counter and onto to Phase Tracker (I can see the black border disappear from one and go to the other). You're seeing the black border stay on the counter AND go onto the Phase Tracker when you right-click the Phase Tracker?
David and others,
it seems the information-bleeding-from-counters-in-a-stack bug will not fixed in 6.4. Could David or someone working with VASL comment on this?
You can read more about the bug in here:
http://www.gamesquad.com/forums/index.php?threads/bug-information-bleeding-from-counters-in-a-stack.128388/
Thanks.
Someone's obviously not following the election that closely.Draggable overlays. It is an election year afterall. I can dream.
Probably you are right about the simplest fix being the reduction of the vertical offset.The tricky part is obtaining consensus on how this should work; we've kind of backed into "design by committee." I think most players like to see the counters underneath. On the flip side it does provide some free recon.
I think the simplest "fix" for this would be to reduce the vertical offset on the stacks.
View attachment 241
Something wrong with the idea of "undo the change that made it happen"? The problem came out of the blue in the last release. Send it back to the blue.The tricky part is obtaining consensus on how this should work
I don't have a clue about vasl counters but I did stay at a Holiday Inn last nightSomeone's obviously not following the election that closely.
I'd love to see this as well. The first step would be to mock up an overlay as a counter ala draggable overlays, where each orientation is a different layer. Do you know anyone who's good with counters??? Hint. Hint.
It works in a sense that you cannot see the information from the counters anymore, but then it's really hard to see the size of the stacks anymore, which lowers the usability of VASL quite a bit. You have to hover around the stacks to see how big they are, and of course, if you don't have a LOS to an enemy stack, you would have to ask your opponent how big the stack is (unless it is concealed, of course).That counter offset looks like it would work for me.
Concur. I like the possibility to see stack sizes and I think the info gain by the current setup is overblown. Perhaps add this function but as an option for those concerned?It works in a sense that you cannot see the information from the counters anymore, but then it's really hard to see the size of the stacks anymore, which lowers the usability of VASL quite a bit. You have to hover around the stacks to see how big they are, and of course, if you don't have a LOS to an enemy stack, you would have to ask your opponent how big the stack is (unless it is concealed, of course).
Sorry, which option? If you mean counter offset, you can do it already by editing the VASL module. Just open VASSAL and then right-click on the VASL module, and from there:Concur. I like the possibility to see stack sizes and I think the info gain by the current setup is overblown. Perhaps add this function but as an option for those concerned?