TripleA Needs Your Help - Call for 2.0 Beta Testers

prastle

@LaFayette I will beat the drums slaps @beelee and a few others

beelee

@prastle
getting a slow start today. I'll dive in soon. Problem with being prepped up is all i do is eat, drink and clean lol

prastle

@beelee hehe

LaFayette

Please leave a quick comment if you get some testing in and do not find any problems. It would be useful to know if the recent lack of new issues is due a sheer lack of problems, or if we have yet to find them.

prastle

@LaFayette bit of playing and testing .. curious if the bad words section was also supposed to include numbers? since for example 88 did not seem to be accepted..

beelee

@LaFayette
I'll tyr the bot thingy now. forget it's git number but basically can't join bots. I'll post at git

prastle

@beelee Either way a simple ? to you bee do you think it is releasable as well? And work continues over time? It has my vote.

beelee

@prastle idk some stuff been fixed. Probably never get it all. FR it let it go we'll get more testers then

prastle

@beelee I agree

LaFayette

Any specific problems please raise as issues so we do not have to discuss all of them here. It's too much, it's like a tree with many branches, the threads are too much to follow from just a single trunk.

Regrettably users are not eager to upgrade. Probably the last 4 releases all had major problems we discovered after releasing. We need the testing effort, it really is painful. It's a legacy of TripleA that much of the code is not automatically tested so we are left trying to manually test what we can (which is actually not all that sufficient, but better than nothing). Hence, the testing effort/labor is really appreciated and helps out a lot!

SilverBullet

@LaFayette which one for mac users?

LaFayette

Mac OS download is the macos.dmg link

SilverBullet

@LaFayette ok, i am starting to nudge people over to the new lobby. i hope there will be enough open bots once the migration starts.

LaFayette

@SilverBullet some caution in doing so. The prerelease lobby is for those that really want to do testing and are going to be reporting any/all problems they see. We'll probably start to do the nudging of the full herd perhaps as early as this Sunday. For that we'll have a new production lobby up for them to join, the accounts created there would be permanent (and existing accounts hopefully cleanly migrated).

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.