TripleA Needs Your Help - Call for 2.0 Beta Testers

SilverBullet

@LaFayette ok

beelee

@LaFayette
I agree. Just thinking we've reached the point where at least idk what else to test

cuda418

Hello everyone, I just downloaded the beta. Two issues right away...

When loading a save game it doesn't remember human/cpu players. After you select them it loads ok. Be nice if it remembered like older versions so you could return to a game later without having to remember.
1941 AA50 map, playing as Japan. Round 1. Attempting to move the transports in seazone 61 to the Philippines. They start loaded in the game. The transports move but the troops remain in seazone 61. This is only the case for the preloaded transports, I used Germanys transport with no issue.

Cernel

@cuda418 I believe bug reports in here are not wanted (they are wanted in the proper bug tracker).

@cuda418 said in TripleA Needs Your Help - Call for 2.0 Beta Testers:

1941 AA50 map, playing as Japan. Round 1. Attempting to move the transports in seazone 61 to the Philippines. They start loaded in the game. The transports move but the troops remain in seazone 61. This is only the case for the preloaded transports, I used Germanys transport with no issue.

Works for me using 18843. So, maybe this is a very recent problem, if you just downloaded the latest.

cuda418

Oh, my bad. I dont have github and all that so I will just let it be and hope someone else catches the bugs and go back to using the older versions.

LaFayette

FWIW it's quick @cuda418 to create a github.com account; the bug report should be easy as it asks you the questions we need and you wont' have to worry about us endlessly asking the those same questions back to you. Submitting bug reports certainly is not zero effort, it's a balance of gathering the information we'll always want/need and keeping it easy.

LaFayette

There are a good number of items to test:

map downloads
engine preferences
game technologies
battle rules (with some emphasis on subs and retreat)
carrier rules
play by email
play by forum
dice roller
multiplayer games (can be done by hosting locally and connecting to the same game locally again; does not require a bot per-say)
any/all lobby functionality, join the lobby multiple times, leave lobby with one window, test out slaps, status updates
all file menu options and menu items.

Hopefully going forward we'll get back to releasing more frequently, one to two times a month until we decide to do a 3.0; In part because it's been such a long time since we did testing and so many changes, pretty much everything needs to be re-tested by hand, which is just a giant effort (hence the frequent releases makes this easier on all)

LaFayette

Good to see the in-game report function being used. For this group, please comment on any such issues created so we can know who to talk to and get to fixes sooner. Some of these errors we'll be interested to know more details to get at a fix.

SilverBullet

@LaFayette ive been having trouble starting a domination solo game.

LaFayette

@SilverBullet please use this form:
https://github.com/triplea-game/triplea/issues/new?assignees=&labels=Pre-Release+Problem&template=prerelease_problem.md&title=

include as much detail as you can so we can have as good of an idea of what you are doing and seeing.

SilverBullet

@LaFayette didnt the ingame report work?

LaFayette

It does, but does not say who it's from, what the impact is, where it's being seen. We get only a code location and the error message that something happened.

SilverBullet

@SilverBullet all i was doing was trying to start a new domination game and it gave me an error, i used in game report, and it acted like it accepted it

SilverBullet

@LaFayette impact was it didnt launch,lol

LaFayette

@SilverBullet it did, but it's without context for us. If you can find it and comment, would be helpful.

LaFayette

In part, also do not want this thread to start discussing all details of every prerelease problem. We've fixed over 25, and we have about 5 that are active. Please consider what it would be like if we had to talk everyone through all of those, technical discussions as well, all in the same thread. No way we could track it all and keep it straight. Hence why I mentioned if you cut a problem report, to find it, comment on it, and we can ask questions that will help us figure out what a good fix is, and we'll have a place where we can discuss between ourselves what a fix should be.

SilverBullet

@LaFayette where do i look to find it? here or github? oh snap, i cant even load a revised game without getting that same error message. i did yesterday, no problem.

Cernel

Has the "Show Comment Log" feature been removed from TripleA, in 2.0 (meaning the ability to add user comments in game history)?

LaFayette

@SilverBullet https://github.com/triplea-game/triplea/issues

FYI: When you create an in-game error report, it gives you the link to the bug report that is created.

@Cernel no, not removed. Specific questions/issues, let's address them in github issues please.

LaFayette

Why are beta testers asked to create bug reports directly and not report issues here?

The bug report has all all the questions that we need for each bug report. Not including the answers will lead to us asking those questions. Asking about all such things in this one forum thread will be overwhelming.
Each bug needs its own tracking. We need to know that every single one is fixed, can't let one slip through on page 4.
Each bug has a separate conversation, first details if we have any trouble seeing the problem. Sometimes a bug will need a developer conversation on how to fix the code before we can actually proceed. Some of those conversations are lengthy. Adding a few pages here to discuss one fix will drown out other conversation.
We need to keep testing moving, can't stay focused on one topic, we want a rapid fire gatling gun of bug reports here.

FWIW, the bug report form is really minimal, has the essential questions and then a few less, and should take a fraction of the time it does to do any level of thorough beta testing.