Bugs in 3.2.6

Hi,

we noticed some problems with the recent VASSAL version (PC, W7 x64, Java 1.7.021).

After loading a module and connecting to the server, there is no way to create a room to play. Theere is simply no place to write down the name of a new room, it is simply not there. My friends had the same problem and hence we were not able to play.
Sometimes I could solve the problem by loading another module where I could suddenly create a new room, then go back to the original module where to option was suddenly available.

And something else: sometimes I have 4 server to choose from (Vassal jabber, legacy, p2p client and p2p host), sometimes the p2p client option is missing.

Any ideas what may cause these problems?

Cheers.

Thus spake Seraph:

Hi,

we noticed some problems with the recent VASSAL version (PC, W7 x64,
Java 1.7.021).

After loading a module and connecting to the server, there is no way to
create a room to play. Theere is simply no place to write down the name
of a new room, it is simply not there. My friends had the same problem
and hence we were not able to play.
Sometimes I could solve the problem by loading another module where I
could suddenly create a new room, then go back to the original module
where to option was suddenly available.

And something else: sometimes I have 4 server to choose from (Vassal
jabber, legacy, p2p client and p2p host), sometimes the p2p client
option is missing.

Any ideas what may cause these problems?

I think you’re making a mistake, but I can’t guess what it is from
what you’ve said. Could you post a screenshot of the problem?


J.

The p2p client and p2p host options where removed and replaced with a single p2p network option in version 3.2.4 (ish). If you the p2p client option sometimes there and sometimes not, then it is because you are sometimes running an older version and sometimes running a newer version of Vassal.

The option to create a new room does not exis in the new version of the p2p Network server, make sure you are all selecting the Vassal Legacy server.

Hi,

here are 2 screenshots.

fotos.gmx.net/ui/external/vd2z8 … ZbXiA33001

It’s all in the 3.2.6 Client … and two of my friends experience exactly the same problem.

Cheers.

Thus spake Seraph:

Hi,

here are 2 screenshots.

fotos.gmx.net/ui/external/vd2z8 … ZbXiA33001[1]

It’s all in the 3.2.6 Client … and two of my friends experience
exactly the same problem.

Either you don’t have “VASSAL Legacy Server” selected, or you have
the server window so small that the layout can’t fit the field where
you specify the name of the game room.


J.

It is the Legacy Server, double checked. And even if I open the server window for full screen … nothing.

I think it has something to do with the p2p server window layout (without the “new game”).
In my opinion the VASSAL doesn’t change the window layout for the legacy server (although it is selected) and keeps the p2p layout.
Changing back and forth between legacy server and p2p shows this problem.
I can try to make a screen cast of this, if needed.

Thus spake Seraph:

It is the Legacy Server, double checked. And even if I open the server
window for full screen … nothing.

I think it has something to do with the p2p server window layout
(without the “new game”).

It looks like the New Game field isn’t shown if you start with the P2P
server selected and then switch to the legacy server.

File a bug report for this in our tracker.


J.

I’ve got this one:

Bug 10217 - Lose New Room selection field when changing from P2P to VASSAL server

Brent.

Thus spake Brent Easton:

I’ve got this one:

Bug 10217 - Lose New Room selection field when changing from P2P to
VASSAL server

Fixed in trunk@8471. Try 3.2.7-svn8471:

vassalengine.sourceforge.net/builds/


J.