Stuff to finish before release

el_matarife · Post by **el_matarife** » 14 May 2007, 11:26

Tobi wrote: The goal of weekly builds which are easily testable because they're linked to a lobby server is to provide (regression) testing of the engine. I'd be happy if at least 1 game is played with it every week, and if regressions found in that game are reported in the bug tracker.

This is a pretty sweet testing environment. I can see a bunch of people hopping on every week to run a test game or two. Could you make the weekly test versions use a different directory by default so it'll be harder to accidentally overwrite your "real" Spring install?

AF · Post by AF » 14 May 2007, 13:44

I'd suggest reccomending a time so that 100 people dont join fidn nobodys on, logoff *next user logs in a few minutes later* looks around nobodies there logs fof *next suer 5 minutes later* etc...

That way we have a chuink of people on at a common time so at least 1 game gets going because tbh there arent that many testers atm as it is.

I'd say around 8-10pm gmt for the best coverage fo europe and US. And then 12 noon gmt for anyone who cant make it.

Tobi · Post by **Tobi** » 14 May 2007, 13:56

Sounds like a good idea yeah.

Neddie · Post by **Neddie** » 14 May 2007, 20:21

I won't be able to help with this, but I'm keeping an eye on all.

Tobi · Post by **Tobi** » 20 May 2007, 10:15

I'll ditch netcode for 0.75, we really need release early release often more then new netcode TBH.

NOiZE · Post by **NOiZE** » 20 May 2007, 13:46

Tobi wrote:I'll ditch netcode for 0.75, we really need release early release often more then new netcode TBH.

we need both imo

but yeah a new release would be nice :)

AF · Post by AF » 21 May 2007, 01:53

AFLobby script incompatability with tasclient is fixed now.

smoth · Post by **smoth** » 21 May 2007, 03:25

Tobi wrote:I'll ditch netcode for 0.75, we really need release early release often more then new netcode TBH.

While I look forward to the expanded lua I am willing to wait another month if you can get the next version with net code, if it would take more then a month then I am happy with an earlier release.

Post by **trepan** » 21 May 2007, 04:30

fwiw: net code != resync

smoth · Post by **smoth** » 21 May 2007, 13:07

The net code is supposed to be easier for other devs to read, my thoughts were that we may have new devs show up that could help work on resync but ultimately, I am just one person I am sure everyone else cannot wait for the next version. Don't let me hold you up.

Tobi · Post by **Tobi** » 21 May 2007, 15:02

It is in a branch on SVN anyway, so if they want they could already help with it / build on it.

Tobi · Post by **Tobi** » 07 Jun 2007, 10:32

For reference (or fixing if you like

): these major bugs showed up in yesterday's test game:

GAIA team has a commander
Keyboard localisation is broken (again)
SLI is broken
Desyncing gives only one error instead of a continuous stream making it very easy to miss.

AF · Post by AF » 07 Jun 2007, 12:07

SLI? Are you sure thats spring and not the drivers?

Tobi · Post by **Tobi** » 07 Jun 2007, 12:15

It works fine with 0.74b3, doesn't work with test builds. (Renders one frame correct, one frame black, if I understood it correctly).

This suggests it's a Spring bug, unfortunately...

clericvash · Post by **clericvash** » 07 Jun 2007, 12:24

Well we have waited 7 months give or take since the last major release, lets just make sure it's a good one lads, if i could code anything but php i would lend a hand for sure.

Keep it up though guys! Great work!

Lippy · Post by **Lippy** » 07 Jun 2007, 14:56

Please don't forget http://spring.clan-sy.com/mantis/view.php?id=537. I personally would consider it a quite important bug, which should be easy to fix seeing it's only come up in the SVN, not 74b3

Pxtl · Post by **Pxtl** » 07 Jun 2007, 15:26

Tobi wrote:For reference (or fixing if you like ): these major bugs showed up in yesterday's test game:
GAIA team has a commander

Keyboard localisation is broken (again)

SLI is broken

Desyncing gives only one error instead of a continuous stream making it very easy to miss.

I suppose this is just a feature request, but until resync is completed, would it be possible just to have the system auto-kick the desynced players with a message?

Post by **jcnossen** » 07 Jun 2007, 16:18

Why would you want that... desynced games can still be fun and at least everyone can continue playing. And most of all everyone wins :)

Peet · Post by **Peet** » 07 Jun 2007, 17:09

Tobi wrote:
Desyncing gives only one error instead of a continuous stream making it very easy to miss.

How about a flashing icon next to the player's name in the list?

SinbadEV · Post by **SinbadEV** » 07 Jun 2007, 18:18

or maybe hust have the last desync message stay at the top of the list

Spring RTS Engine

Stuff to finish before release