Vassal 3.2 Testers

Hello,

I am one of the administrators of a medium sized Warhammer 40k based community. We’re currently running a campaign based on Vassal and we’re all really excited for the release of version 3.2.

I would like to offer our services to help you test the new version if you’re willing. We have about 10 people using Vassal regularly (3-4 days a week per user average) and I would like to think we could give you some decent feedback.

If you’re interested, that would be awesome.

Tony “Apulo” Dellett
gothicwars.org/

Thus spake Apulo:

Hello,

I am one of the administrators of a medium sized Warhammer 40k based
community. We’re currently running a campaign based on Vassal and we’re
all really excited for the release of version 3.2.

I would like to offer our services to help you test the new version if
you’re willing. We have about 10 people using Vassal regularly (3-4 days
a week per user average) and I would like to think we could give you
some decent feedback.

If you’re interested, that would be awesome.

Would you like to test 3.2 development builds? You can find them
here:

vassalengine.org/~uckelman/builds/

We’d appreciate having feedback on them.


J.

Sure thing! I’ll post the link on our website.

We played a couple complete games with 3.2.0-svn8131 last night and everything was peachy. The only thing I noticed was a small cosmetic issue. When you expand the module window, the new game text box expands vertically so it ends up being very narrow and very tall.

Great work guys!

Thus spake Apulo:

We played a couple complete games with 3.2.0-svn8131 last night and
everything was peachy. The only thing I noticed was a small cosmetic
issue. When you expand the module window, the new game text box expands
vertically so it ends up being very narrow and very tall.

I don’t follow. Expand the module window how?


J.

I don’t follow. Expand the module window how?

When I play, I always maximize the module window and the “New Game” textbox expands oddly. Here is a screenshot:

As I said, a very minor cosmetic issue. I have found your development builds to be extremely stable so far :slight_smile:

FYI - Something is broken with this image: VASSAL-3.2.0-svn8137-windows.exe

I installed it on Windows 7. When I run VASSAL.exe it immediately terminates itself without having even launched the regular VASSAL window. So I reverted back to 3.2.0-svn7890, the last image that runs my module properly.

Thanks,
-Mark R.

I also had this issue yesterday. I rolled back to 3.2.0-svn8131.

Thus spake mroyer:

FYI - Something is broken with this image:
VASSAL-3.2.0-svn8137-windows.exe

I installed it on Windows 7. When I run VASSAL.exe it immediately
terminates itself without having even launched the regular VASSAL
window. So I reverted back to 3.2.0-svn7890, the last image that runs
my module properly.

Fixed in trunk@8146. (The problem was that I missed one of the two
places conf directory paths are stored when I was implementing RFE 1924.
It’s awful that we have to maintain these paths in two places, but
presently there’s no way around it.)

Try the svn8146 build.


J.

Okay, thanks. This latest build fixes that problem - it runs and will load my module.

However, the issue I reported in November persists:
viewtopic.php?f=5&t=4580&hilit=mroyer&start=15#p27135

I think, at that time, I ran into two bugs at once - an “Eeek! A Bug!” bug during splash-screen display that was fixed as part of bug number 4122 and a second, as yet diagnosed bug that was assumed to have been fixed as part of 4122 but wasn’t.

To recap the remaining issue:
When I load my unpublished module that has a VERY large map image, the hex grid is neither visible nor enabled. The playing-piece counters can be positioned anywhere and do not snap to the intended hex-grid. The last version of VASSAL that worked properly for my module regarding hex-grid display was 3.2.0-svn7890.

I’ve reported it as bug 4428.

Thanks for all your help,
-Mark R.

-Mark R.

I actually have a question about using a private Jabber server.

I have Jabber installed on our server with multi-user conferencing enabled. However when I try to use that with 3.2, it does not connect. What authentication is Vassal trying to use with jabber? It connects to the server but is unable to authenticate.

Thus spake mroyer:

Okay, thanks. This latest build fixes that problem - it runs and will
load my module.

However, the issue I reported in November persists:
viewtopic.php?f=5&t=4580&hilit=mroyer&start=15#p27135[1]

I think, at that time, I ran into two bugs at once - an “Eeek! A Bug!”
bug during splash-screen display that was fixed as part of bug number
4122 and a second, as yet diagnosed bug that was assumed to have been
fixed as part of 4122 but wasn’t.

No, the bug you’re seeing is exactly the one in 4122. 4122 hasn’t been
fixed.

To recap the remaining issue:
When I load my unpublished module that has a VERY large map image, the
hex grid is neither visible nor enabled. The playing-piece counters can
be positioned anywhere and do not snap to the intended hex-grid. The
last version of VASSAL that worked properly for my module regarding
hex-grid display was 3.2.0-svn7890.

I’ve been trying to get Pieter to look at this bug for some time now.


J.

Thus spake Apulo:

I actually have a question about using a private Jabber server.

I have Jabber installed on our server with multi-user conferencing
enabled. However when I try to use that with 3.2, it does not connect.
What authentication is Vassal trying to use with jabber? It connects to
the server but is unable to authenticate.

Sorry, I don’t know. You’d have to look at the source.


J.

Trying 3.2-8146, and two things to note:

The problems with the hex grid definitely exist in the F&E module. Looks to be a scaling issue. By the time you hit the bottom of the map, it’s about two hexes off.

Second, 3.2 will error when trying to load the Pegasus Bridge map (PB) for VASL. The bug tracker should have gotten a report from me where I mentioned I was trying to load an old file. I went back and determined that starting a new game with that map errors as well. Everything’s fine with that map in 3.1.19.

Thus spake Rindis:

Trying 3.2-8146, and two things to note:

The problems with the hex grid definitely exist in the F&E module. Looks
to be a scaling issue. By the time you hit the bottom of the map, it’s
about two hexes off.

Try the build labeled svn8170-8169. Is the hex alignment problem solved
there?

Second, 3.2 will error when trying to load the Pegasus Bridge map (PB)
for VASL. The bug tracker should have gotten a report from me where I
mentioned I was trying to load an old file. I went back and determined
that starting a new game with that map errors as well. Everything’s fine
with that map in 3.1.19.

Could you track down the bug number for me?


J.

Thus spake Apulo:

I don’t follow. Expand the module window how?

When I play, I always maximize the module window and the “New Game”
textbox expands oddly. Here is a screenshot:

Thanks for pointing this out. Problems like this make VASSAL look
unprofessional.

This problem is due to Java’s built-in layout managers being almost
totally useless for creating proper layouts—it would be charitable to
describe them as toys— and the fact that a lot of VASSAL has not been
converted to use a proper constraint-based layout manager yet.

I coverted the server pane to use MigLayout. Try resizing the server
pane in various ways in svn8171 or later, and let me know if it behaves
satisfactorily.


J.

I have no idea how to do that. :stuck_out_tongue: (Haven’t ever gone into the bug system, so I’m not even sure where it is.)

Ah ha. The Tracker link at the top. Took me a while to find my way around (didn’t know that my email address was in the body of the bug. So the Pegasus Bridge map error bug is:

vassalengine.org/tracker/sho … gi?id=4448

Thus spake Rindis:

Ah ha. The Tracker link at the top. Took me a while to find my way
around (didn’t know that my email address was in the body of the bug.
So the Pegasus Bridge map error bug is:

[1] vassalengine.org/tracker/sho … gi?id=4448

This bug is already fixed in the development version of VASL, which
Lance Leung is working on.


J.

Just tested this, and it looks good in 8170-8169.

James