Imarok

I have a working patch for that since some months, but implementing it properly would need a gamesetup rewrite and that takes much time and is difficult...

I also thought that. Imho the big ones fit better

Uh, they were different?

Seems like you are right and autobuild is broken. @Itms

Have you changed the model? The basket now looks quite smaller...

Does anything speak against giving the women's baskets a base? That looks a bit strange:

Which map?

What should the colored stuff inside the trough represent? I guess those white towels should be in playercolor? Btw what about laying some riding equipment (saddle or saddle cloth, or whatever mauryans used to sit on horses) over one of the fence gates? (As like someone is going to make his horse ready...)

Hmm, I can't reproduce that. Maybe you have a replay, where you reproduced it? Could you elaborate that? I don't get what you mean.

Which type of games are you talking about? (The network architecture heavily depends on the game genre)

I guess GNOME is the issue. (I have the same problem using Ubuntu gnome. Using 0ad in full screen "fixes" the issue) @Grugnas Ubuntu Gnome or Ubuntu?

Thx for updating

Yes

Nice idea. (Maybe it should be triggered on phase up or so...)

Stop asking. Now everyone knows about this issue. So either fix it yourself, wait until someone fixes it or propose a concrete solution...

Could you complete the wiki entry? (It's free to edit...)

@wowgetoffyourcellphone is right, there are other texture bugs remaining:

Of course I've heard about it, but I couldn't find a reliable source backing that up ;P

It seems like the persian farmstead has some bug/mistake in it's texture: As you can see, the bricks the cart lays on are purely in player color. @Enrique@LordGood

I'd guess the time is, uhmm ... just now? Try it out

Can you reproduce that issue? When does it appear? Which units are selected in that moment? When does it work correctly?

Sure. What about: When an autobuild fails, Vulcan only applies the first new commit and then tries building, if that succeeds it tries the next one. By that, Vulcan finds out the commit which fails and than could notify the committee the same way, as it does, when a Linux post commit test/build fails. (Alternatively we could yous bisecting)

We can feel lucky to have at least some testing...

Sure, but we could let Vulcan find out which commit broke the windows autobuild and then post it somewhere or send a mail

No, Vulcan failed with building the autobuild because of that.