bridgewater-brunel.me.uk - Simutrans-Experimental - Pak128.Britain-Ex 0.9.0

[ӔO]

I probably need to add an express line from nutish to chilwick for there to be some improvement at nutish.

---

On second look, the pax want to go to...

Eveford - ACM
Islingham - ACM
Monkinghall - wlindley
Brownton - ACM
Birningcaster - ACM
Berryden - ACM
Peachhampton - ACM

etc...

So not really my network that is crowded.

---

Some testing, and I think you can do around 120 vehicle replacements at once without slowing down the server.

P.S. Is electricity working again, or should it still be kept offline?

[jamespetts]

The problem seemed not to be with electricity after all, so you should be able to reconnect everything. If things go wrong after you do, we shall know what caused the problems.

[asaphxiix]

yes, there are more pax wanting to go to the yellow isles now than there were before - but still more than those, many tens of thousands want to go to featheringfield, chilwick, yerlhall, arlsmouth, jarhall, trunkwick, kisden etc.

and those heading to the isles, well, they're not gonna swim the way

edit: just remembered that those poor pax are actually likely to swim the way.... I'd help with the mass-killing, but I have no access to ACM.

[ӔO]

The pax don't actually want to go to chilwick etc., but instead those destinations are the result of them bouncing back to nutish and trying to find another route to their destinations.

They would be less inclined to head to nutish, if the east island was well connected to the north islands.

[asaphxiix]

I see. Well, still, it'd be best to come up with a solution for that, since it's been going on for a very long time now, and isn't expected to improve.

We should name those islands somehow.... What city is on the eastern island? I will try to improve the connections.

[asaphxiix]

nutish is all clear now, and the game is running almost as fast as a local game

but I'm getting the desyncs again.

The electricity after all?
It be noted that I was getting some desyncs last night as well, but played very little, and it was very slow then, so I thought the desyncs were on account of that, and anyway, there weren't so many - but now it's pretty instant (can be a minute though).

maybe it's the bus replacing, though there doesn't seem to be the hiatus of restarting.

[ӔO]

I cleared out nutish, but they are now building up at yerlden, hatingford, templeley and trunkington and a few other places.

Actually, all the pax I am clearing out, I dump at hatingford and templeley.

---

if you replace most of your horse depots with diesel depots, you should be able to replace 300 or more vehicles at once. It seems like the replacer is inconsistent in sending vehicles to depots to get them replaced with another power type.

[jamespetts]

if you replace most of your horse depots with diesel depots, you should be able to replace 300 or more vehicles at once. It seems like the replacer is inconsistent in sending vehicles to depots to get them replaced with another power type.

I have been working on fixing this to-day, as it happens, although this won't be deployed until the next major release.

[ӔO]

that's great to hear!


I can't wait for the next major upgrade. It seems like I can't keep pace with the ever increasing number of pax.

[asaphxiix]

just me not able to play these days?

[jamespetts]

When you say that you're not able to play, can you be more specific?

[asaphxiix]

sorry! I mean because of desyncs - can't stay connected for more than a minute or two...

[jamespetts]

Is anyone else having this problem?

[ӔO]

out of 5 tries, I get maybe 3 or 4 quick desyncs, but can stay connected for quite a while after that.

[jamespetts]

Asaph - is this the same experience that you have?

[asaphxiix]

trying now. It's true that I wasn't very persistent

aeo, do you reopen your client between attempts?

[ӔO]

yes, I reopen after 3 attempts

[asaphxiix]

and the first attempt is usually protocol error?
Also sometimes no response.

I've been connected for a few minutes now, on the fourth attempt I think, after prot. error, desync, and no response.

[ӔO]

I get, roughly, 1 in 10 for protocol error. The rest are desyncs.

[Felix]

I usually also get an immediate dsync when trying to connect. With a faster computer, I was sometimes able to connect. With my regular machine, I was never able to play in the last days.

[asaphxiix]

For me, persistence was helpful - quite stable now, except the usual first of the month desyncs.

[jamespetts]

Felix - sorry that you are having trouble. Are you still unable to connect? May I ask - what is the specification of the computer with which you can and the specification of the computer with which you cannot connect?

[Felix]

I still get an immediate desync. The weaker computer is an old Macbook Pro with a Core 2 duo T7600 and 2 GB RAM running Linux (Gentoo, 32 bit). The faster one has a i5 CPU and 8 GB RAM also running Linux (Kubuntu, 64 bit). I compiled simutrans experimental myself based in the sources from git.

[jamespetts]

May I ask - which branch did you use? Have you tried using the official Linux binary?

[Felix]

I am using the master branch.

[jamespetts]

Have you tried the official binaries?

[Felix]

I just gave it a try with the official 32-bit Linux binary. Sadly, I get the same behavior.

[jamespetts]

Hmm. How many times do you try to reconnect?

[asaphxiix]

there's much desynching when two players are connected.

[ӔO]

yes, it seems like two players cannot stay connected for any significant amount of time.

[Felix]

@jamespetts: I usually tried to connect between two and four times.

[jamespetts]

Hmm - sorry everyone for all the difficulties. I shall have to look into this in some detail when I get a chance. It might take a fair while, though.

[Felix]

Don't worry, and take your time. As the server runs the bleeding edge of experimental, I surely did not expect the game to run without issues at all times. Anyway, thanks for your effort!

[ӔO]

Just FYI, I tried the server game on an i3-3217U with 4GB of RAM (popular in ultrabooks) and the game is right at the limits of what the CPU can handle.

[ӔO]

Lindley lines was liquidated. I'm not entirely sure why, since it looked like it was going fine for a while, despite the refunds. I wasn't even there when it was liquidated, so I have, practically, no idea what happened.