News:

Want to praise Simutrans?
Your feedback is important for us ;D.

Recent posts

#1
Quote from: prissi on Today at 01:12:29 PMWhat is the logic of adding the no route passengers only to one stop and not all stops in the catchment point (line 1959)?
The logic has not changed; GCC just did complain about the loop being run at most once, and judging by the comment on the line directly above, this was probably intentional (?)
#2
Simutrans Help Center / Re: Weird- but maybe intended ...
Last post by emirkir - Today at 02:14:42 PM
Ah, okay. Thanks for answering!

I will watch it more closely, otherwise build another station, thank you for your help!
#3
Thank you. What is the logic of adding the no route passengers only to one stop and not all stops in the catchment point (line 1959)? They could potentially travel from any of them.

It will certainly change the number of no_route passengers in normal games.
#4
Should hopefully be fixed in r11902.
#5
Bug Reports / Re: [r11900] City growth can b...
Last post by prissi - Today at 12:32:14 AM
Check 11901
#6
Simutrans Help Center / Re: Weird- but maybe intended ...
Last post by prissi - Yesterday at 11:54:28 PM
Usually this happens if the steel mill is delivered by more than one coal mine. The second coal mine will send also some coal for the other stell mill, if it has a contract for that mill.

The only way to avoid taht would be seperate stations for drop off of the coal.
#7
The general names would be used in the same way as in Standard - if there are no streetnames available then it will use the general names.
#8
Simutrans Help Center / Weird- but maybe intended beha...
Last post by emirkir - Yesterday at 11:18:06 PM
Hello,

It's been a while since I played Simutrans. But here I am again. Since it's been so long, I might have forgotten core game mechanics. I cannot wrap my head around the following issue...

I have set up this cargo train line:

WEST STEEL MILL ------ COAL PLANT ------ EAST STEEL MILL

The train bounces between the two steel mills with coal from the middle station. Here's the "issue":
The train has 100% load with coal, then drops it off at the west steel mill (all fun and games). Then it goes back to the coal plant, gets 100% coal and drops it off at the east steel mill. But here, it starts to load coal from the steel mill (to like 50%?) to move back to the other plant. Why? So it starts loading some coal, not all 100%, but a little - to move it to the other steel mill.

Is this intended behaviour or am I doing something wrong. The line is simple, without any signals or other stuff - just rail and stations.

To clear things up: I only want the train to drop off coal at the steel mills - not pick up directly after dropping off.

Thanks for your time in advance!
#9
That is some very interesting research - thank you for that. I am wondering in the circumstances how the general names might work in the circumstances - what was the behaviour in the patch for when these would be selected?
#10
Quote from: cousjath on Yesterday at 02:48:47 PMMy reasoning was that bus stops are all named with something as well as the name of the place, even if it is the only stop in the village; i.e. Upperbackwatersthwaite Red Lion, Lowerbackwatersthwaite Post Office. Since I create more bus stops than train stations I prefer the default behaviour being like that, it is easier for me to decide to delete part of a name than stick a street name in later. Even train stations in large cities got extra description when first built, i.e. Manchester Liverpool Road.

I agree with this reasoning. In Extended, railway stations are usually built after road and water halts.

That's partly a chronological necessity: if you start from 1750 you can't build passenger railways for another 57 years anyway. And a name like "Bigtown Central" doesn't really fit an 18th century waggonway halt.

And even if you start at a later date, building a railway line without a(n omni)bus or stagecoach network to feed it passengers is a very risky endeavour in Extended's paksets, so experienced players almost invariably build a road network first and that's what they tell newbies to do.

Quote from: jamespetts on March 15, 2026, 04:26:40 PMThe first (or only) railway station in a town is not called "Bigtown Pied Pigeon Street". It's just called "Bigtown". The second station is similarly likely to have a generic name ("Bigtown Central", "Bigtown Road", etc.). Only when the town has lots of different stops and stations do people start having to be more creative with the names (typically using the names of the roads or other nearby features).

This would have been rational and it's how stations are named today, but it wasn't what happened in 19th century Britain. Look at the very first announcement of the Liverpool and Manchester Railway, the first ever scheduled, inter-city passenger railway (open in a new tab if it's too small to read here):



In the very first paragraph, the termini are immediately identified by street names, "Crown-street" and "Liverpool-road". That's repeated in the Omnibus timetables: the Manchester routes don't terminate at "Manchester station" but at "Liverpool-road station". In the railway timetable proper, the minor stops include "Bury Lane", "Top of Sutton Incline", and other very specific halts.

And this quickly passed into wider usage.E.g. this is from Thomas Roscoe's Book of the Grand Junction Railway, published in 1839:



You can see that Lime Street station, opened only three years before, is already referred to using that name. The only time the book uses "Liverpool Station" rather than Lime Street station is in the label of an illustration, and the index uses "Lime Street Station", not "Liverpool Station". In this screenshot, you can also see a mention of Wavertree Lane, a halt which opened right from the start of the line.

I wonder whether perhaps this pattern of using street names is because the railway stations weren't seen in isolation, but in the context of the existing networks of stagecoach and omnibus stations, which is exactly the same behaviour that would take place in Simutrans if this pull request is accepted.