Star Wars: Armada - Vassal module version 4.2.0

By Green Knight, in Star Wars: Armada

Do the vlog files from 3.6 do not work on 3.7? The program is asking if it should open the file, but i can cannot go through the steps to restore the fleet. Do i have to redo the fleets again in 3.7?

Nevermind. I had two vlogs (one as backup). One worked, the other did not.

Edited by Tokra
26 minutes ago, Tokra said:

Do the vlog files from 3.6 do not work on 3.7? The program is asking if it should open the file, but i can cannot go through the steps to restore the fleet. Do i have to redo the fleets again in 3.7?

Nevermind. I had two vlogs (one as backup). One worked, the other did not.

Old vlogs will work in new versions. You'll get a warning, but that's all.

I cover this in tutorial no. 7. Or maybe no. 8.

Couple of new tutorials added:

No. 9 is about additional vassal/module features

No. 10 is about using the module to support your CC games

Bug Report, @Green Knight .

Haven't gotten a chance to do much investigation into the cause yet, but I picked up a new bug in the transition from 3.6 -> 3.7 that hard locks the Armada module. When it happens, it won't accept input in any field of any screen in the SWA module, either keyboard or mouse; to include interacting with the windows (closing, minimizing). I have to kill it from the OS and reopen the module.

I think it might be associated with the die roller, because it seemed to always happen either right after I'd rolled, or right before I saw what my opponent had rolled. (Sorry about that game, @Matt Antilles . :( )

3.6 seems to be stable, though, so I'm pretty sure it's something in the module itself, not Vassal. It doesn't seem to leak outside Vassal--or at least outside the JRE--because it doesn't have any impact systemwide (eating up resources, memory leak, nothing like that). It happened fairly frequently... I'd say maybe one out of every 2 or 3 die rolls.

I am, of course, running it on Linux, but I would be surprised if this sort of an issue was platform-specific, particularly in a Java application.

I'll post back when I get a chance if I can pin down what exactly is causing it.

59 minutes ago, Ardaedhel said:

Bug Report, @Green Knight .

Haven't gotten a chance to do much investigation into the cause yet, but I picked up a new bug in the transition from 3.6 -> 3.7 that hard locks the Armada module. When it happens, it won't accept input in any field of any screen in the SWA module, either keyboard or mouse; to include interacting with the windows (closing, minimizing). I have to kill it from the OS and reopen the module.

I think it might be associated with the die roller, because it seemed to always happen either right after I'd rolled, or right before I saw what my opponent had rolled. (Sorry about that game, @Matt Antilles . :( )

3.6 seems to be stable, though, so I'm pretty sure it's something in the module itself, not Vassal. It doesn't seem to leak outside Vassal--or at least outside the JRE--because it doesn't have any impact systemwide (eating up resources, memory leak, nothing like that). It happened fairly frequently... I'd say maybe one out of every 2 or 3 die rolls.

I am, of course, running it on Linux, but I would be surprised if this sort of an issue was platform-specific, particularly in a Java application.

I'll post back when I get a chance if I can pin down what exactly is causing it.

Keep me posted.

Can't say I've noticed anything similar.

However, the dice roller is very complex to begin with. Maybe the addition of more sounds pushed it over the edge. For some systems at least?

I also found an issue, though it may just have been caused by me. I tried copying the graphics pack in, but when I did so the cards for X-Wing, B-Wing, and Jan Orrs, even though they were present in the graphics pack, couldn't be found, apparently, and thus were not displayed. Given that those three specifically are in my fleet, I have a suspicion that it was something I did, but then again the ship and upgrade cards worked perfectly fine, so I have no idea what I did wrong. . . any ideas?

I've noticed that sometimes ship dial reveal isnt showing up in the log. About once a game. I've been watching too many games.

@Green Knight Feature Request : Can we have it so that grav wells only show up to distance 3? Would make distinguishing multiple ones much easier if their 4s and 5s don't overlap and make it a puzzle.

Thank you :)

On 4/4/2017 at 2:48 PM, Visovics said:

@Green Knight Feature Request : Can we have it so that grav wells only show up to distance 3? Would make distinguishing multiple ones much easier if their 4s and 5s don't overlap and make it a puzzle.

Thank you :)

I'll put it on my consider list for the 380 update.

On 4/3/2017 at 10:51 AM, Ginkapo said:

I've noticed that sometimes ship dial reveal isnt showing up in the log. About once a game. I've been watching too many games.

Could that be players accidentally using CTRL + Q Look at top command instead of CTRL + R Reveal command?

The former doesn't trigger a report, the latter does.

On 4/3/2017 at 10:28 AM, NobodyInParticular said:

I also found an issue, though it may just have been caused by me. I tried copying the graphics pack in, but when I did so the cards for X-Wing, B-Wing, and Jan Orrs, even though they were present in the graphics pack, couldn't be found, apparently, and thus were not displayed. Given that those three specifically are in my fleet, I have a suspicion that it was something I did, but then again the ship and upgrade cards worked perfectly fine, so I have no idea what I did wrong. . . any ideas?

That sounds odd.

If those squads were not part of the graphics pack - and they are - you'd still see the untexted versions, as they would not have been overwritten.

So I'm thinking this is something else entirely. Not sure what.

On 4/3/2017 at 5:51 AM, Ardaedhel said:

Bug Report, @Green Knight .

Haven't gotten a chance to do much investigation into the cause yet, but I picked up a new bug in the transition from 3.6 -> 3.7 that hard locks the Armada module. When it happens, it won't accept input in any field of any screen in the SWA module, either keyboard or mouse; to include interacting with the windows (closing, minimizing). I have to kill it from the OS and reopen the module.

I think it might be associated with the die roller, because it seemed to always happen either right after I'd rolled, or right before I saw what my opponent had rolled. (Sorry about that game, @Matt Antilles . :( )

3.6 seems to be stable, though, so I'm pretty sure it's something in the module itself, not Vassal. It doesn't seem to leak outside Vassal--or at least outside the JRE--because it doesn't have any impact systemwide (eating up resources, memory leak, nothing like that). It happened fairly frequently... I'd say maybe one out of every 2 or 3 die rolls.

I am, of course, running it on Linux, but I would be surprised if this sort of an issue was platform-specific, particularly in a Java application.

I'll post back when I get a chance if I can pin down what exactly is causing it.

Not sure if it's the same bug, but I've had the module freeze a couple of times, always when discarding a defense token. Maybe for as long as 30 seconds.

2 hours ago, Green Knight said:

Not sure if it's the same bug, but I've had the module freeze a couple of times, always when discarding a defense token. Maybe for as long as 30 seconds.

Possibly related, though I do know that I wasn't interacting with defense tokens when mine happened.

On 4/2/2017 at 10:51 PM, Ardaedhel said:

Bug Report, @Green Knight .

Haven't gotten a chance to do much investigation into the cause yet, but I picked up a new bug in the transition from 3.6 -> 3.7 that hard locks the Armada module. When it happens, it won't accept input in any field of any screen in the SWA module, either keyboard or mouse; to include interacting with the windows (closing, minimizing). I have to kill it from the OS and reopen the module.

I think it might be associated with the die roller, because it seemed to always happen either right after I'd rolled, or right before I saw what my opponent had rolled. (Sorry about that game, @Matt Antilles . :( )

3.6 seems to be stable, though, so I'm pretty sure it's something in the module itself, not Vassal. It doesn't seem to leak outside Vassal--or at least outside the JRE--because it doesn't have any impact systemwide (eating up resources, memory leak, nothing like that). It happened fairly frequently... I'd say maybe one out of every 2 or 3 die rolls.

I am, of course, running it on Linux, but I would be surprised if this sort of an issue was platform-specific, particularly in a Java application.

I'll post back when I get a chance if I can pin down what exactly is causing it.

<Cough> Linux <Cough>

QFL

(quoted for laughs)

I make jokes because I love linux, but don't use it enough. I have debated changing off of M$ at home to Linux just because Ubuntu would run so much better on my aging hardware. When I have my beer with Ard, I will discuss this change over further.....

2 hours ago, moodswing5537 said:

<Cough> Linux <Cough>

<Cough> JRE <Cough>

3 hours ago, Ardaedhel said:

<Cough> JRE <Cough>

That's reason alone to go to linux....

Hi there, I have a question, I see no text on any cards. I've installed the module as the tutorial says... did that 3 times. Still have no text on any cards. I see a graphic pack V3, but how do I install it ?

Thanks.

1 hour ago, xenosfear said:

Hi there, I have a question, I see no text on any cards. I've installed the module as the tutorial says... did that 3 times. Still have no text on any cards. I see a graphic pack V3, but how do I install it ?

Thanks.

That's normal and is done for legal reasons. You should have the card title but no text. If there is no title text, then that is a major problem.

You'll need to find card text from some other source of you don't have the cards with you.

2 hours ago, xenosfear said:

Hi there, I have a question, I see no text on any cards. I've installed the module as the tutorial says... did that 3 times. Still have no text on any cards. I see a graphic pack V3, but how do I install it ?

Thanks.

To install the graphics pack follow Green Knight's tutorial #5 here .

Question to Vassal users (and others):

Would it be useful to have some "how to play Armada" tutorials based off Vassal? Or is it safe to assume than anyone playing on Vassal is fairly skilled in terms of rules and whatnot?

2 hours ago, Green Knight said:

Question to Vassal users (and others):

Would it be useful to have some "how to play Armada" tutorials based off Vassal? Or is it safe to assume than anyone playing on Vassal is fairly skilled in terms of rules and whatnot?

I think it could be useful

Just a quick w6 heads up:

I've got everything that's been spoiled in the Quasar article in the next build.

As soon as the Hammerhead article is up I'll release a new module version.

By necessity it will NOT include the correct firing arcs (that will have to wait until I have the actual models in hand), but mockups based on whatever ship most closely resembles the new one (looks like I'll be using the Vic as a standing for the Quasar, for example).

47 minutes ago, Green Knight said:

Just a quick w6 heads up:

I've got everything that's been spoiled in the Quasar article in the next build.

As soon as the Hammerhead article is up I'll release a new module version.

By necessity it will NOT include the correct firing arcs (that will have to wait until I have the actual models in hand), but mockups based on whatever ship most closely resembles the new one (looks like I'll be using the Vic as a standing for the Quasar, for example).

If only it had come before the tournament ... :(