Latest Posts

Topic: Build 20

GunChleoc
Avatar
Joined: 2013-10-07, 15:56
Posts: 2628
Ranking
One Elder of Players
Location: RenderedRect
Posted at: 2018-10-27, 12:03

Thanks for the detailed bug report. Debugging desyncs is tricky, and currently nobody active on the team has any experience with it.

We do have a wiki page on it though: https://wl.widelands.org/wiki/DebuggingDesyncs/


Busy indexing nil values

Top Quote
stonerl
Avatar
Joined: 2018-07-30, 00:03
Posts: 100
Ranking
Likes to be here
Location: Earth
Posted at: 2018-10-27, 13:40

Just a minor question do the commandline options work the same on windows as they do on macOS and Linux?


Top Quote
GunChleoc
Avatar
Joined: 2013-10-07, 15:56
Posts: 2628
Ranking
One Elder of Players
Location: RenderedRect
Posted at: 2018-10-27, 15:39

Yes. The only difference is that log output gets written to C:\Users\<username>\.widelands\stdout.txt instead of being printed to console.


Busy indexing nil values

Top Quote
WorldSavior
Avatar
Joined: 2016-10-15, 04:10
Posts: 819
Ranking
One Elder of Players
Location: GER
Posted at: 2018-10-27, 18:34

Another problem is that almost every replay stops at some point, and then they cannot be continued, so you can watch only the beginnings of the matches.


“It's a threat to our planet to believe that someone else will save it.” - Robert Swan

Top Quote
stonerl
Avatar
Joined: 2018-07-30, 00:03
Posts: 100
Ranking
Likes to be here
Location: Earth
Posted at: 2018-10-27, 18:45

WorldSavior wrote:

Another problem is that almost every replay stops at some point, and then they cannot be continued, so you can watch only the beginnings of the matches.

I ran into the same issue. That's also a desync. At least that's what the commandline reports:

REPLAY: Lost synchronization at time 910200
I have: 31cc2400c98213244f817257c9f77e1d
Replay has: 35834365bf28a8d3e50a880deb60cc09

So there seems to something fundamentally broken.

Edited: 2018-10-27, 18:53
Top Quote
stdh
Avatar
Joined: 2013-08-04, 22:05
Posts: 31
Ranking
Pry about Widelands
Posted at: 2018-11-05, 19:45

How far along are we in the release process? If I'm not mistaking, only important bugs will be fixed and translations are still open. After the list of 'build20-rc1'-tagged bugs dries up, we have two more weeks to work on translations and then it's time for the RC. Is that right?

I know it's hard to tell, but can anyone give a reasonable estimate how long it would take before the last such bug is squashed?


Top Quote
GunChleoc
Avatar
Joined: 2013-10-07, 15:56
Posts: 2628
Ranking
One Elder of Players
Location: RenderedRect
Posted at: 2018-11-06, 19:57

At the rate we're currently going, at least two weeks until we've fixed the bugs, maybe even longer.


Busy indexing nil values

Top Quote
stonerl
Avatar
Joined: 2018-07-30, 00:03
Posts: 100
Ranking
Likes to be here
Location: Earth
Posted at: 2018-11-06, 23:54

Just out of curiosity, is bunny bot still running? Travis and Appveyor are very quiet..


Top Quote
GunChleoc
Avatar
Joined: 2013-10-07, 15:56
Posts: 2628
Ranking
One Elder of Players
Location: RenderedRect
Posted at: 2018-11-07, 11:25

Nope, I have already pinged SirVer to reboot it.


Busy indexing nil values

Top Quote
stonerl
Avatar
Joined: 2018-07-30, 00:03
Posts: 100
Ranking
Likes to be here
Location: Earth
Posted at: 2018-11-07, 15:22

Before I file a bug report, I noticed that the Appveyor builds install to Users\Username\AppData\Local\Widelands

Instead of ProgramFiles\Widelands or ProgramFiles (x86)\Widelands


Top Quote