2.6 Testing (Report 2.6 problems here)

LaFayette

Updates:

the game not actually closing on exit should be fixed now. Before people would have seen this as TripleA continuing to run in the process list even though they clicked 'exit program' (and the window closed). Now the game should drop off the process list.
there was a recent performance improvement that removed an unnecessary scan of installed maps when rendering territory effect images
map skins were put behind the 'beta features' flag. That flag can be toggled on or off in the preferences window 'test' tab. Map skins remain mostly broken in 2.6 & how to install or download them is undocumented.

In the meantime I think maybe skin support can be brought back with a few more days work. If it turns out to be a lot more than that then it could make sense to shift focus to just releasing 2.6 without skin support.

Otherwise, the list of things left to do is here: https://github.com/triplea-game/triplea/projects/25

TheDog

@lafayette
To Do, Map Tags for each map and their ratings and era code?

LaFayette

@thedog Yes, though that is a data entry task after 2.6 is launched. We could get a head start with the prerelease data and I could copy that data to prod when we launch 2.6

In either case I will need the set of tag names and respective tag values to enter in database before we can 'tag' maps.

LaFayette

@ubernaut , moving only the truck, I do not see the problem you posted.

ubernaut

@lafayette not really sure how the inner working of the engine work but perhaps it has something to do anything that has changed in regards to however rails work? it seems as if it's treating the truck like a train when it's loaded if you control click to set way points you can force it to work as it should.

LaFayette

@ubernaut Moving only the train, with 2.6, I do not need to control click, it moves the 2 territory spaces.

test.tsvg

ubernaut

@lafayette there is no rail on that territory so i'm not sure what you are saying bc the train cannot follow the correct path the truck should

LaFayette

@ubernaut same with material loaded onto truck, observing movement of 2 spaces directly to target territory.

ubernaut

@lafayette i don't get it i thought you said you were also seeing the problem

LaFayette

@ubernaut At this point please be 100% specific about the problem. I'm only going off the screenshot, i do not know which units you have selected.

I am not aware that you're selecting, please clarify exactly what you are selecting.

ubernaut

@lafayette truck + material

LaFayette

@ubernaut thanks, yah, not seeing it.

ubernaut

@lafayette well if you want i can screen share with you or something

LaFayette

@ubernaut please start by posting a save.

ubernaut

@lafayette weird i just tried to replicate it twice maybe it's already been fixed somehow in the prerelease i'm using ¯\_(ツ)_/¯

TheDog

https://github.com/triplea-game/triplea/releases/tag/2.6.33.8af5587ac3

The above version causes this error before the 1st turn completes

.
On this map and crashes TripleA
https://triplea-game.org/map/ww2-oil-and-snow-2nd-edition/

It also causes the same error on this unpublishing map
The Shogun Advanced

All versions after the above version cause the same error
This version and before
https://github.com/triplea-game/triplea/releases/tag/2.6.13%4057528d46ee
do not have this error.

Also raised on Github
https://github.com/triplea-game/triplea/issues/10417

Myrd

There's been lots of recent changes so I think it would be great if more folks could test the latest 2.6 prerelease for any problems.

TheDog

@myrd
One reason for the poor uptake in testing is the 2.6 map download servers dont work.
So players have to

download a map with 2.5
play/test in 2.6
link that with 2.6 unzipping problems

=too many hurdles.

4 months ago this was posted;
https://forums.triplea-game.org/topic/3109/unable-to-download-maps-in-2-6-535

see post 10
LaFayette said
Map downloads are now dependent on the server and database to be operational. The database server on the prerelease server keeps crashing. It is currently crashed and probably has been for a bit now (before I was manually turning it back on every now and then).

Second, we also have disk space issues. That could be causing the DB to halt. Second, there might be something in the deployment that is killing the database.

Myrd

@thedog Yea, I did notice that.

I'm not sure why each version uses separate download servers. Why can't 2.6 just use the 2.5 servers?

beelee

yea i still can't use it. wtf lol