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

Advanced (pre)signalling #1644

Closed
DorpsGek opened this issue Jan 11, 2008 · 3 comments
Closed

Advanced (pre)signalling #1644

DorpsGek opened this issue Jan 11, 2008 · 3 comments
Labels
component: pathfinder This issue is related to Pathfinder flyspray This issue is imported from FlySpray (https://bugs.openttd.org/)

Comments

@DorpsGek
Copy link
Member

Fragster opened the ticket and wrote:

On vacations, I did cleaning and came across to my old university notes. There was a notebook with the course of microelectronics and logic chips. And I thought: in fact signal block - is a logic element with a Multiple Inputs(Exit|Combo presignals) and 1 Output(Entrance presignal). But we have only 1 type of elements - «or».

But in my outlines of a further 3 were like: «and», «or-not», «and-not».

If we would have additional types of input and combo presignals, which are consistent with these types of logical elements that could build a very effective (in size and speed) at the station entrances and exits and at the complex lunctions.

I propose to refer to these types presignals in attaches.
This leaves only add these types in code and add them to process. I think it will not take much coding. If developers interested in my proposal , I can draw the rest sprites.

Attachments

Reported version: trunk
Operating system: All


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

Fragster wrote:

I think, that it would be great alternative for PBS, which is very unrealistic


This comment was imported from FlySpray: https://bugs.openttd.org/task/1644#comment3223

@DorpsGek
Copy link
Member Author

Alberth wrote:

A requirement for introducing new signal types is to allow construction of better track layout, not possible with current signals.
Please show how these additional signal types help.

(eg or-not would give red if no train is in a block. The 'red' signal however prevents a train to enter such a block, so effectively we have a block where no train can move into.)


This comment was imported from FlySpray: https://bugs.openttd.org/task/1644#comment4766

@DorpsGek
Copy link
Member Author

andythenorth closed the ticket.

Reason for closing: Won't implement

Flyspray clean up: more than 5 years old, and not obvious what should be done with this next, so closing. If this offends, discuss with andythenorth in irc. Thanks.


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

@DorpsGek DorpsGek added component: pathfinder This issue is related to Pathfinder flyspray This issue is imported from FlySpray (https://bugs.openttd.org/) enhancement labels Apr 6, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component: pathfinder This issue is related to Pathfinder flyspray This issue is imported from FlySpray (https://bugs.openttd.org/)
Projects
None yet
Development

No branches or pull requests

1 participant