Article View: alt.games.microprose.transport-tyc
Article #28042A Couple of Locomotion Questions
From: Mike Humberston
Date: Thu, 21 Oct 2004 19:10
Date: Thu, 21 Oct 2004 19:10
21 lines
1571 bytes
1571 bytes
I'm sorry to start yet another thread about Locomotion. I have two questions. Two things that bug me about Transport Tycoon are: 1. the dire track-laying algorithm that the computer controlled companies use. 2. the over simplistic routing algorithm which causes trains to easily get lost on complex networks. So my questions are, for Locomotion, has Chris Sawyer bothered to take some time to research and implement algorithms which: 1. result in sensible computer controlled company track layouts? 2. get trains from starting point to destination without any possibility of them getting lost en route? TIA Mike -- Mike Humberston WARNING: Spam trap in operation. Send any e-mail reply to mike, not oblivion. NOTE: E-mail currently inoperative. All replies to the news group, please.
Technical Details
Message-ID:
<ql1gn0pnsfapavbq9au6vitldm8m6eutod@4ax.com>Path:
mbox-mo1.pugleaf.net!number1.nntp.ams.giganews.com!number1.nntp.dca.giganews.com!internal1.nntp.dca.giganews.com!border2.nntp.dca.giganews.com!nntp.giganews.com!cyclone1.gnilink.net!gnilink.net!news.glorb.com!fu-berlin.de!uni-berlin.de!not-for-mailShow Full Headers
Complete Article Headers
Path: mbox-mo1.pugleaf.net!number1.nntp.ams.giganews.com!number1.nntp.dca.giganews.com!internal1.nntp.dca.giganews.com!border2.nntp.dca.giganews.com!nntp.giganews.com!cyclone1.gnilink.net!gnilink.net!news.glorb.com!fu-berlin.de!uni-berlin.de!not-for-mail From: Mike Humberston <oblivion@philomel.net> Newsgroups: alt.games.microprose.transport-tyc Subject: A Couple of Locomotion Questions Date: Thu, 21 Oct 2004 20:10:09 +0100 Lines: 21 Sender: oblivion@philomel.net Message-ID: <ql1gn0pnsfapavbq9au6vitldm8m6eutod@4ax.com> Reply-To: oblivion@philomel.net Mime-Version: 1.0 X-Trace: news.uni-berlin.de i6WPpg6zTD8VI7PZUy//4gDrcntxmZlcDJo7oioIcx/l1gR8pM X-Newsreader: Forte Agent 1.92/32.572 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit