OpenTTD 12.0 - How To Enable All Signals

[kamnet]

As of OpenTTD 12.0, only Path-Based Signals (PBS) and Block Signals are enabled by default in order to make it easier for new players to get started and learn.

Many experienced players are more familiar with the other types of signals available, and are now confused by the missing signals. Here are the steps you will need to follow in order to re-enable them.

1. In the main screen of the game, click on "settings"
2. Change the category to "Expert (show all settings)".
3. Open the "Company" menu.
4. Change the "Show signal types" setting to "Show all settings".

https://i.redd.it/tpxr8btn30u71.png

Now block signals should be activated in the game. Credit to Steam user Parabellum for writing this up!

If you would like to learn more about advanced signaling, visit the OpenTTD Manual:
https://wiki.openttd.org/en/Manual/Signals

There is also a detailed video tutorial available:
https://www.youtube.com/watch?v=1kcgylFM3y4

[RAMChYLD]

Getting the old Train signal systems back

After upgrading to the new version 12.0, I noticed that trains are just outright broken. They keep getting stuck and gridlock. The signals that allow bidirectional signalling are no longer there. How do I get the old system back?

[Vermilicious]

Maybe it's the default disabling of block signals? Search the options for signals.

[parabellum]

@devs
most importantly: Thank You for keeping openttd up to date for such a long time. iam playing transport tycoon since the 90s and you keep it alive for all of us.

I share RAMChYLDs view on keeping block signals on by standard settings.
i believe that TT was also so succesful because beginning for new players was as easy as possible, with more complexity later in game if you then chose to have that.

@RAMChYLDs
- in the main screen of the game, click on "settings"
- change the category to "expert (show all settings)"
- open the "company"-menu
- change the "Show signal types" setting to "show all settings.

Now block signals should be activated in the game.

[2TallTyler]

Block signals are less effective than path signals, and bidirectional block signals are a recipe for stuck trains. Perhaps you're using one-way path signals where regular path signals (which can be passed in the "wrong" direction) should be used?

[RAMChYLD]

Well, here's the thing. Block signals factors a lot into a playstyle I'm developing. To wit:

- On stations with multiple platforms, the station has a shared depot on it's end.
- Each platform only goes to one other platform on another station. No trains share lines.
- To turn around, the train is expected to go the other station, go into another depot at the end of the line, and turn there.

Now, owing to the shared depot, with only path signals, the trains behave very strangely, as if their AI/pathfinding is broken. They'd fill into the first available platform and not go to the correct platform that will take them to the correct destination. This results in a deadlock because the first train will pull into the first available platform, fill up, and go on it's way. Trouble starts when the second train then pulls out of the depot and also into the first platform instead of the correct platform and starts filling up. When the train that is returning from the right platform tries to pull in, both trains lock up facing each other. Nevermind the third train in the depot that is meant for yet another platform not moving at all until the deadlock is manually resolved.

Originally posted by parabellum:

@RAMChYLD

Noted with thanks.

[2TallTyler]

That's...an unusual style of designing stations and signalling. But you can enable the full signal menu and use block signals as you like.

[RAMChYLD]

I acknowledge that it's an unorthodox playstyle, but I find that it gives me quite a trouble free experience. I only came to the idea a few days ago, while watching the demo on the main menu while half-asleep. Prior to that I've experimented with shared lines and platforms with no success, and developed a convoluted system of loops, multiple tracks and branching. This is pretty much the result of me trying to streamline the system.

[Schwarzenegger]

muiyo bom

[Nebgama]

As a new player i would say its counter intuitive disabling things like this by default. Because i am following this guide atm https://www.youtube.com/watch?v=oAm5JiXVP2Q&list=PLX9TPVcxrORP8EOLYBgnhzxK6VbncNil7&index=11
Trying to following along realizing early on that i don't have the same amount of signals as him like as soon as he open the signals pane early in the video early. Then spending 5-10 minutes trying to figure out why which breaks the concentration of following something while learning. Because now i have to go and turn this back on.

imo the last thing someone new needs is to interrupt a learning process because they are not sure why something is different to the teachers. For all i knew he was using a mod or some setting from some abstract GRF.

[Beef]

I've been an OpenTTD (and OG TTD) fan for several years but, I haven't played in a while. I can't get the old signals to work in this version. I've enabled them in the advanced signals and they show up in the toolbar, but I can't place them in the world.

I don't know the names of the signals, I just remember the keystrokes. I put down a signal, change it to one-way by clicking on it again to cycle through, then in my stations I use the (block?) signals by ctrl+clicking to change them. They look different now and my trains don't seem to respect the one-way signals. I haven't been able to tell if the block signals are working correctly yet.

How do I get them to work again?

[^#^SmisekPaja^#^]

thanks

[[1eRoc]_Bolo]

lol

[Strange]

This is now wrong. The "All Signals" is no longer under company.
You can find it under "Interface>Construction>Show Signal types" and then change it to All Signals.

I'm not sure when it changed or why this is still pinned with wrong information.

[2TallTyler]

@Strange We did some reorganization of the Settings menu in OpenTTD 14: https://github.com/OpenTTD/OpenTTD/pull/11683

I will unpin this thread, since the change in OpenTTD 12 is now two years old.

[Mike]

This thread was quite old before the recent post, so we're locking it to prevent confusion.