Small Grey Dot Dead Centre of Pieces

Technical Support & Bugs
1

Hi there

I’m noticing a small, grey dot which appears in the middle of all of the game pieces of all of the modules that I run (mainly hexgrid type wargames). This may just be an idiosyncrasy of Vassal that we all have to live with? Apologies if this issue is know or has been dealt with before - I did search ‘small grey dot’ but nothing came up.

I’m running a well-specced MacBook Pro 13" with the latest version of Vassal.

I hope someone out there understands what this is.

Best wishes.

Don

2

could you give us a picture showing it as well as which module you are seeing
this in?

From: yangtze yangtze2000@yahoo.com
To: messages@vassalengine.org
Sent: Thu, July 26, 2012 12:05:55 PM
Subject: [messages] [Technical Support & Bugs] Small Grey Dot Dead Centre of
Pieces

Hi there

I’m noticing a small, grey dot which appears in the middle of all of the
game pieces of all of the modules that I run (mainly hexgrid type
wargames). This may just be an idiosyncrasy of Vassal that we all have
to live with? Apologies if this issue is know or has been dealt with
before - I did search ‘small grey dot’ but nothing came up.

I’m running a well-specced MacBook Pro 13" with the latest version of
Vassal.

I hope someone out there understands what this is.

Best wishes.

Don

Read this topic online here:
https://forum.vassalengine.org/t/small-grey-dot-dead-centre-of-pieces/5139/1

3
4

Apologies, I’ll have to give a mediafire link to the pic. It’s a free download:

http://www.mediafire.com/?tie08iha7j1j0d8

I see this effect in every module, including Stalin’s War.

Don

5

Thus spake yangtze:

mediafire.com/?tie08iha7j1j0d8

I checked Stalin’s War. The dots are caused by the Movement Trail trait.
In particular, they disappear when “Trails start visible?” is unchecked,
but that appears also to have the effect of disabling movement trails
altogether when there’s no key command defined.

It’s unclear to me what the right thing to do here is.

–
J.

6

Thanks for looking. Hopefully the issue will be solved in a future update?

7

Thus spake yangtze:

Thanks for looking. Hopefully the issue will be solved in a future
update?

What’s not clear to me is whether this is our bug or a module bug.
Anyone else care to comment?

–
J.

8

Never used the Movement Trail myself, but maybe leaving “Trails start visible” unchecked but fixing the engine so that trails do show up even with no key command defined is the ideal solution?

9

Thus spake barbanera:

“uckelman” wrote:

Thus spake yangtze:

mediafire.com/?tie08iha7j1j0d8[1]

I checked Stalin’s War. The dots are caused by the Movement Trail
trait.
In particular, they disappear when “Trails start visible?” is
unchecked,
but that appears also to have the effect of disabling movement trails
altogether when there’s no key command defined.

It’s unclear to me what the right thing to do here is.

–
J.

Never used the Movement Trail myself, but maybe leaving “Trails start
visible” unchecked but fixing the engine so that trails do show up even
with no key command defined is the ideal solution?

[1] mediafire.com/?tie08iha7j1j0d8

This turned out to be a bug in the way line segments were drawn. There
was no check of whether the final point in the points list is the same
as the current location of the piece, which resulted in a zero-length
(but not zero-width) line segment being drawn at the location of each
unmoved piece.

This bug has existed as long as the Movement Trail trait has. It’s
amazing to me that no one told us about it before.

Try 3.1.20-svn8234:

vassalengine.org/~uckelman/builds/

–
J.