Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

It is possible to build the newest semaphores, before they are available... #2202

Closed
DorpsGek opened this issue Aug 6, 2008 · 3 comments
Closed

It is possible to build the newest semaphores, before they are available... #2202

DorpsGek opened this issue Aug 6, 2008 · 3 comments
Labels
component: interface This is an interface issue flyspray This issue is imported from FlySpray (https://bugs.openttd.org/)

Comments

@DorpsGek
Copy link
Member

DorpsGek commented Aug 6, 2008

RAMMAR opened the ticket and wrote:

This bug is not affecting on the game process itself (except appearance)... I've found it by chance...
It is possible to build the newest semaphores/signals, before they are available...
This bug don't need a save game, because this screenshot shows how to do it...
First: you need to have a straight line of the tracks, then you need some angled tracks at the end of the straight line. Second: you need to build an old (as it's only available for now) semaphore (its direction isn't important) on the angled track next to first square of the straight line of the tracks. Third: you need to start to build semaphores as line (over this straight line of the tracks) from this old semaphore. Fourth: and you have it - the line of the newest semaphores...

Attachments

Reported version: 0.6.2
Operating system: All

This issue was imported from FlySpray: https://bugs.openttd.org/task/2202
@DorpsGek
Copy link
Member Author

DorpsGek commented Aug 6, 2008

Yexo wrote:

There isn't something like 'availability' of signals. You can either change the patch setting or just press control while building the signal.

This comment was imported from FlySpray: https://bugs.openttd.org/task/2202#comment4554

@DorpsGek
Copy link
Member Author

DorpsGek commented Aug 6, 2008

RAMMAR wrote:

Another example:
Some tests have shown, that this bug is not working everytime... I didn't used "Ctrl" (BTW, thanks for this feature, I havn't know it before) and havn't changed date (1975 year as default) of appearance of the newest signals...

Attachments

This comment was imported from FlySpray: https://bugs.openttd.org/task/2202#comment4556

@DorpsGek
Copy link
Member Author

DorpsGek commented Aug 7, 2008

Rubidium closed the ticket.

Reason for closing: Fixed

In r14013.

This comment was imported from FlySpray: https://bugs.openttd.org/task/2202

@DorpsGek DorpsGek closed this as completed Aug 7, 2008
@DorpsGek DorpsGek added component: interface This is an interface issue flyspray This issue is imported from FlySpray (https://bugs.openttd.org/) bug labels Apr 6, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
component: interface This is an interface issue flyspray This issue is imported from FlySpray (https://bugs.openttd.org/)
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@DorpsGek