LAST EDITED ON Aug-26-02 AT 01:20 PM (EDT)
Please review and provide any last suggestions before this is "officially" sent to Nels. Thanks. LawrenceProposal RC1*: Route Specification and Description ForumIntroductionNeed for ProposalMicrosoft Train Simulator (MSTS) was released a little over a year ago, and several route-building pioneers emerged to create routes. The early pioneers, as the pioneers of any country/land, found this new "land" to be fraught with challenges--the Route Editor (RE) being the greatest. How could routes be built with such a tool?Notwithstanding such a tool, routes were released--with Michael Vone's Cliff Hanger Route being the first, original, released route. Now there are 133 items listed under the Routes section of the www.train-sim.com file library, and many more routes are available in locations around the world. Even a cursory perusal of the Route forum will show that more are in the works.At the time of the early, route-building pioneers, the routes were few, and releases were infrequent.Today, however, that is not the case. Because the route downloads are significantly larger than non-route downloads, it has become apparent that more factual information is required than either the short description in the file library or the "promotions" by the route builder. Therefore, over the course of several weeks, discussions have occurred in the Route Design forum about how that information can be presented.This proposal is a result of those discussions.Goal of ProposalThe goal of this proposal is to provide information--factual, objective information--about a route to any and all visitors to http:\\www.train-sim.com, so that the visitor can make a better determination about the route he/she would like to download. Further, it is the goal of this proposal to NOT be a rating tool, and all attempts at making it a rating tool will be thwarted.Who Proposal Aimed atThis proposal is aimed at route developers, users, and the person(s) posting the information. For the route developers, they will provide the information about their respecive routes. Route developers' participation is strictly and totally voluntary, and no judgment will be made on those route developers who choose not to participate. Route developers can also request that the information about their route be modified or removed from the listing, again, without fear of reprisal. Route developers do NOT have to have their route in the http:\\www.train-sim.com file library in order to use this service.For the user, this proposal makes available factual information which can assist in determining whether or not the user would like to download the route.For the person posting the information, this proposal aims to make his/her job as low-maintenance, low time-consuming as possible; basically, cut and paste the information. The person posting has the right and task to edit the material for readibility and length.ProposalWhere Store the Route InformationWe propose that a new, locked, information-only-type forum, titled "Route Specification and Description Forum" be opened at the http:\\www.train-sim.com forums. This forum will be moderated by Macster and Nels, with one or two other people having access to posting information. Therefore, only three or four people will be able to "post" in this forum. It is desired to have persons other than Macster and Nels to post, as Macster and Nels are quite busy enough without having to take on the responsibilities of this proposal.How Route Developers Submit InformationProminently displayed in the Route Specification and Description Forum will be the e-mail address to submit entries. At least the one or two posting individuals will have access to that mailbox, with Macster and Nels optionally having access.Nature of Information Stored at New ForumThe information stored at the new forum will be factual information that is provided by the route developer of a route. No other person will be able to provide information about that route, however, the posting individuals will have the right and task to edit the material for readability and length. It is requested that the information provided be information answering the following "questions":Name of RouteDescription (~100 words or less)Installation MethodSize of DownloadSize of Installed RouteFictional or Prototypical OperationsFreight or PassengerEra or GenreLocationLenght of MainlineLength of BranchesNumber of BranchesNumber of SidingsNumber of YardsMixture of Dual and Single TrackLevel of DetailPercent of Scenery CompletedFPS Specs, with qualifiersActivities ProvidedNon-Default Consists or Rolling Stock Required in Activities(Edited) Add-In Track Sets: Xtracks required, compatible with v3.2 or later(Edited) Tsection.dat file used: Standardized Tsection.dat, release 00008 or laterURL for More Information and ScreenshotsKnown ProblemsWhere it can be downloadedRoute developers are not REQUIRED to provide any information; however, all information provided will be put into the above format.ConclusionIt is the hope and desire of all the participants, be they route developers or route downloaders, that this proposed forum and program will provide the needed information that is currently lacking.End of Proposal*Release Candidate 1
Printer-friendly page | Edit | Reply | Reply With Quote | Top
RE: Proposal RC1: Route Specification and Description , zhivago47, Aug-26-02, 03:10 PM, (1) RE: Proposal RC1: Route Specification and Description , robertreedy, Aug-26-02, 05:40 PM, (2) RE: Proposal RC1: Route Specification and Description , level10, Aug-26-02, 07:13 PM, (3) RE: Proposal RC1: Route Specification and Description, mivone, Aug-27-02, 00:45 AM, (4) RE: Proposal RC1: Route Specification and Description, chuckzeiler, Aug-27-02, 01:01 AM, (5) RE: Proposal RC1: Route Specification and Description, mttcrlsn, Aug-27-02, 01:57 AM, (6) RE: Proposal RC1: Route Specification and Description, LawrenceKellie, Aug-27-02, 08:04 AM, (7) RE: Proposal RC1: Route Specification and Description , LawrenceKellie, Aug-27-02, 08:19 AM, (8) RE: Proposal RC1: Route Specification and Description, mivone, Aug-27-02, 09:18 AM, (10) RE: Proposal RC1: Route Specification and Description, LawrenceKellie, Aug-27-02, 10:41 AM, (11) RE: Proposal RC1: Route Specification and Description , DRGWK36, Aug-27-02, 09:12 AM, (9) RE: Proposal RC1: Route Specification and Description, LawrenceKellie, Aug-27-02, 10:41 AM, (12) RE: Proposal RC1: Route Specification and Description , routeartisan, Aug-27-02, 10:26 PM, (13) RE: Proposal RC1: Route Specification and Description, LawrenceKellie, Aug-27-02, 10:50 PM, (14) RE: Proposal RC1: Route Specification and Description, routeartisan, Aug-28-02, 06:26 PM, (18) RE: Proposal RC1: Route Specification and Description, DRGWK36, Aug-29-02, 07:36 AM, (19) RE: Proposal RC1: Route Specification and Description, robertreedy, Aug-27-02, 10:54 PM, (15) RE: Proposal RC1: Route Specification and Description , DKlemm, Aug-28-02, 12:39 PM, (16) RE: Proposal RC1: Route Specification and Description, LawrenceKellie, Aug-28-02, 12:54 PM, (17)
Conferences | Topics | Previous Topic | Next Topic

