Demo bug - invalid action marker

[Loops]

I've been having a lot of fun with the demo, but I just ran into a significant issue with an invalid action marker showing up, which on reflection I think I may have seen affecting computer shots too.

The attached screenshots pretty much tell the story:
- my Trehourt is distance 11 from the Wellesley, and has its port broadside facing
- the game gives me a distance "1" action marker on the Wellesley, which when clicked fires the Trehourt's starboard broadside
- curiously, the action marker remains and can be clicked again and again to fire 0 gun broadsides (incidentally, this is how I came by the screenshots - I didn't stop to think about it the first time around)
- I am confident the first shot when the guns were loaded actually did do range 1 damage (notice the missing mast?), which makes it a pretty powerful effect when it occurs.

- Loops

[Loops]

For what it's worth, the bug is fairly easy to reproduce - it seems to be solely dependent on the geometry of the ships. Specifically, distance 11 with the enemy ship at the extreme edge of the firing arc will cause it. This would be fairly exploitable in MP, so I hope it's addressed eventually.

- Loops

[Loops]

Ran into a separate issue with crew added to a ship of mine between scenarios in the campaign not showing up for assignment. As the screenshot shows, the available crew in the top display exceeds the total amount in the assignment panel. I don't think there can be valid reason for this. The total in the assignment panel is stuck at the same amount from the end of the previous scenario.

I'm thinking that the fact that this ship struck its colors in the previous scenario but was never captured may have contributed to this problem, since adding crew has worked fine for me in many other situations.

- Loops

[Andrew Lonon]

Loops:

Excellent Reporting, and even better timing! I have just about everything ‘in place’ for the update (still some work to do, but looking good) and its time for major bug fixes. I want to role as many fixes into the update as possable so they get fully tested in the rigmarole. So – here are the open issues that I will be fixing from this thread, restated to make sure I understand the situation:

1) Distance 11 is Represented as Distance ‘1’ but, the firing double-check disqualifies the shot as too far, allowing the whole process can be repeated, luckily with no loaded guns. But the double-check does not catch the original shot – so the ship does range 1 damage. Nice: ‘Good one Andrew.’

2) Crew on struck but not captured friendly ships after Campaign Advance.

Thanks again for your effort & keep playing Salvo!

[Loops]

That looks great Andrew - thanks for your response. I spend my days developing software (albeit of a much less entertaining variety), so I'm fully sympathetic to the myriad ways issues can sneak in.

I've played the demo through and through, and I'm now anxiously awaiting delivery the full game. The level of effort you are still putting into the game and the support you have provided through this forum were major deciding factors for me.

- Loops

[Loops]

Following up on (2) - the crew issue - I just had it happen to me again, this time on a non-struck friendly and a struck/uncaptured friendly at the same time. However, I have now figured out a work-around: if you dump all the crew into idle and switch on Auto allocation, then the AI will assign out all the crew you should have a couple rounds later. Oh, and I'm now using the full release, so it's not just a demo issue.

I'm wondering if the problem isn't more User-allocation related, which I always have set on all my ships. I can't stand how Auto allocation prefers full gun crews over adequate sailing - changing speed or tacking when you need to is a heck of a lot more important than making sure every gun in broadside fires IMHO.

- Loops