Topic: General call for testing

I'm trying out these changes right now. Recently I replayed the campaigns (to check if the translations i made for b19 were OK -- I'm happy to say they're not too horrible ), so I should be able to make some useful remarks.

Top

Quote

I had a look at these changes, all improvements work. Some remarks and other timing issues:

• bar01: Some of the now-delayed dialog windows (briefing_msg_{05,06,07}) still have "the story begins" as title.
• atl01: Objective for warehouse comes perhaps a bit early: depending on where player puts one it doesn't help at all for escaping the rising tide - I don't suppose that's a problem though. But it's possible to trigger this objective and get instructed to build horse farms before one has any farms.
• tut01:
  • After the tutor builds the first lumberjack's hut, maybe he/she should wait a bit longer before ordering the extra flag on the road, so it would be more obvious how slow transport is with that long road segment.
  • Showing the different ways to move the view: as soon as the view has moved (before I even release the arrow key/mouse button) a new objective is shown and the game saved, that doesn't go very smoothly (at least on the old machine I use).
  • Messages in a real game: it could take some time between the first and the second 'quarry empty' messages, maybe a bit awkward.
  • At the end, I think 10 seconds is too long before showing the conclusion, the player can take a look at their territory afterwards if they want.
• tut02: If for whatever reason the trainingcamp is finished first, dialogue flow is disrupted. F.e. celebration of 'strongest soldiers ever' comes too soon, and explanation of evasion comes after instruction to dismantle the sentry.
• tut04: When I first played this, I didn't immediately understand the tavern incident. Timing's better now, though still fast compared to the rest of Widelands.

While going over the tutorials/campaigns again, I noted a number of small possible refinements. Is there some place I can dump these? Bugtracker is maybe not the best place, it's not one single bug.

Top

Quote

stdh wrote:

• Messages in a real game: it could take some time between the first and the second 'quarry empty' messages, maybe a bit awkward.

I don't understand what change you are suggesting here - it only needs to work in the tutorial. We have 2 quarries, hence 2 messages (unlike waiting for 2 messages from the same quarry, which would be 30 minutes apart).

All other suggestions have been implemented, thanks a lot!

I am getting a crash in Tutorial 4 with the Tavern code now, I still have to look into that.

Busy indexing nil values

Top

Quote

It would be good if somebody could test the spritesheets branch, the code has already been approved.

https://github.com/gunchleoc/widelands/tree/spritesheet-generation

https://ci.appveyor.com/project/widelands-dev/widelands/builds/27577176

Barbarian Units that are using spritesheets:

• Flags
• Wood Hardener
• Carrier

Note that the idle carrier gets a black background when zoomed out - this is a proof-of-concept that the correct mipmap files are being generated and used. We'll delete that one before merging.

Busy indexing nil values

Top

Quote

I tested this now on my WIndows machine. I know again why I don't like Windows But everything is working normally.

Top

Quote