Train-Sim.Com
MSTS Route Design

Proposal RC1: Route Specification and Description Frm

Proposal RC1: Route Specification and Description Frm – image 1

Notice to all visitors and members of the Train-Sim.Com message forums:
If you plan on using a signature banner in your posts, we would like to remind you that there is a maximum size for banners. That maximum is 450 pixels wide by 120 pixels high, and not to exceed 25k. Your compliance is appreciated. FORUM RULES Problems? There are two common reasons for problems with logging in and posting messages. The first is that you are running a firewall that prevents your messages from being sent to the server. The other is that you have cookies disabled; the DCForum software requires cookies to work properly.

Previous Topic | Next Topic

Printer-friendly copy Email this topic to a friend

Reading Topic #6248

Charter Member · 1674 posts

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

Alert | IP

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

Charter Member · 534 posts

RE: Proposal RC1: Route Specification and Description

Proposal RC1: Route Specification and Description Frm – image 2

I think it is perfect just the way you have it.......Great job and I hope the rest of the community will approve as well.......I see no reason not to.......Its time has come. We need it......as you say there are so many routes out there now it is becoming impossible to decide which ones to use.........if we all had two 100gb harddrives on our computers it wouldn't matter much but there is no way to have more than 6 or 7 routes at a time and have the space for them.......Again, thanks for the work you are putting into it.......and I propose you be one of the ones with access to the forum........Most people trust your judgement......and you have been here a long time......Anyway, good luck and I hope it flies with Nels and all of the route developers.........TimProposal RC1: Route Specification and Description Frm – image 3
The Spur Line
http://tahunter.net/thespurline
Appalachia RR - Midwest & Rocky Mountain RR - ADFRR Route

Alert | IP

Printer-friendly page | Edit | Reply | Reply With Quote | Top

Charter Member · 16 posts

RE: Proposal RC1: Route Specification and Description

Very nice idea. Just three thoughts for now:1) Concerning the listing of non-default items, please include a section where the developer can supply links to WHERE any non-default items were obtained. Not all of the non-default stuff comes from the Trainsim file library.2) This might be pushing it but what about inclusion of an optional zip file with the non-default stuff available for download, only if no copyrights are violated and the original author doesn't prohibit it.3) This format could be used (with modifications where appropriate) to locomotives, activities, custom scenery, track objects, and especially utilities. I hope all of the great contributors here decide to adopt this principle when creating the documentation for their creative efforts. As a very greatful and happy user, to all you developers, keep up the good work!

Alert | IP

Printer-friendly page | Edit | Reply | Reply With Quote | Top

Charter Member · 260 posts

RE: Proposal RC1: Route Specification and Description

As before, I am all in favor of this plan: please go ahead, and thanks very much for organizing it!Three points:1) Thanks for the plug of my Cliff Hanger Route, but: I think Chris Cyko beat me to it by a day or so! He upgraded his route later, removing the first version, so that Cliff Hanger is now the "oldest" route file at Train-Sim.com. Rather than getting into arguments about "which route was first", why don't you simply skip this point!2) About the "percentage of scenery completed": how do we measure that? What does "completed" mean? I am afraid that this cannot be answered: in Albula 2 I am laying footpaths, but I am still missing all the flowers, lizards, mosquitoes and pebbles, so it is very far from "complete". The question about Level of Detail should suffice to address this issue, in my opinion.3) I am not in favor of quoting FPS: when I see such numbers quoted, I don't know what do with them, because I have no idea how to convert them to my PC, and because they depend on so many factors. But I don't mind if others supply that information: I just don't know how to use it.Michael Vone
Step by Step Guide to Route Building for MSTS - http://trainsimulatorworld.com/catalog/b470.htm
Albula Line Route
Rocky Islands Route
Cliff Hanger Route
http://avsim.com/hangar/utils/mvchallenges/

Alert | IP

Printer-friendly page | Edit | Reply | Reply With Quote | Top

Charter Member · 318 posts

RE: Proposal RC1: Route Specification and Description

Another item to consider is where the DETAIL sliders and other options are set. I can drop 4 FPS just by turning on the Dynamic Shadows. I recall there was some discussion about the detail of bridges in Bill Burnett's Sea View 2 route, which was based on the slider settings.

Alert | IP

Printer-friendly page | Edit | Reply | Reply With Quote | Top

Charter Member · 14 posts

RE: Proposal RC1: Route Specification and Description

LAST EDITED ON Aug-27-02 AT 01:58 AM (EDT)

I am in favor of a set of standards for routes and this looks like a good start. First to make everyone aware I like to speak my mind and sometimes it takes a moment for me to get my point understandable. I apologized in advance if I may at times sound rough as that is not my intentions.In the coming months of this winter I hope to be more active with MSTS. I already have a start on the Bluffs & Rivers route which is the tracks along the Mississippi River from St. Paul, MN to Savanna, IL with tracks going to Portage, WI as well (terrain teraforming is almost complete for the 400+ miles). Along with this will be some paintjobs of engines and cars for this area (BNSF, CP, UP, CNW, SOO, MILW, BN, DME, IMRL, IC…)Now for my comments and confused questions to the detail section.1. FPS - I my option this is worthless as no two computers will have the same results even if the hardware is identical. This comes from experience as a network specialist and testing that I have done with MSTS using various parts for computers I build. I really see no point in FPS numbers except for the designer to use them as a "benchmark" to suggest the need or lack thereof for fast computers.2. Percent of Scenery (or percent of anything) Complete. Nothing is ever complete. Percentages are based on a total possible done divided by actual done. I would suggest that for the scenery completed maybe have miles or tiles with mostly scenery completed followed by miles or tiles total.3. Installation Method - Is this needed and what would go here for the details?4. Freight or Passenger - Ditto on #3. What is meant by this subject?5. Length of Branches - Okay how the heck would this be calculated? What is the definition of a Branch as compared to a mainline?6. Mixture of Dual and Single Track - What is meant by this subject? Why is it needed? What would go here for the details?7. Level of Detail – Isn’t this scenery?8. What about a version and release date of the route?9. Fictional or Prototypical Operations, Freight or Passenger – Suggest replace both these with one subject Theme. Example; Theme: Prototype – based on railroad along the upper Mississippi River10. What about a grade profile subject. Example;Grade Profile: Most flat grades less than .75%. Maximum mainline grade of 1% Sparta to Tunnel City eastbound.
So far this looks to be a very good start.

Alert | IP

Printer-friendly page | Edit | Reply | Reply With Quote | Top

Charter Member · 1674 posts

RE: Proposal RC1: Route Specification and Description

Please see http://www.train-sim.com/dcforum/DCForumID6/6202.html for some background.Lawrence

Alert | IP

Printer-friendly page | Edit | Reply | Reply With Quote | Top

Charter Member · 1674 posts

RE: Proposal RC1: Route Specification and Description

Please note that these are guidelines to the route builder to answer. The need seen for these guidelines is to help the user have more information *before* spending time (and money) downloading huge files. There is no way that we can ever get everything that someone wants. However, out of all the previous discussions, these points have come up as ones that would be good to have.I will now respond, with alacrity I hope, to some questions.level10: Non-default equipment. If you have been reading the other forums, the message is coming loud and clear to document these types of things. About using this format for anything in the file library, yes, it could. However, since a route is at least 10+ times the size, several have stated it would be nice for the user to have this information before downloading. Mivone: First route. Point taken, will be removed. Percent scenery, certainly, nothing is ever "done." That's not the point. The point here is does it have scenery or not, or is it just blank terrain with track. A good example of this is David Klem's IC project. The fact that a route developer feels that more or different scenery needs to be added to a route is not the point. We all "tweak" the routes. Regarding FPS. Certainly there are lots of factors. However, if showing that on a fairly robust computer you are only getting 1-4 FPS, that would certainly show important information. Again, using David Klem's IC route as an example, in the last update he cautioned that an area of the route now brought certain computers to there knees. This is the type of information being asked.chuckzeiler: Absolutely. See above on my response to Mivone.mttcrlsn: Again, FPS, see above for Mivone. There is not ANY benchmark, in my opinion, that can be *absolutely* correct. There is always room for error. The same here. However, as I mentioned above to Mivone, it is a guideline. Percent Scenery--asked and answered. Installation Method--this is a very important point, and reading the background to this project will shed light on it. All other points are considered. Thanks, all, for the comments.Lawrenceps. Sniper once said that Nels said getting route developers to agree on anything is like herding cats! I agree. However, I think that we have made a significant step and we can lead this community in providing more information to users before spending time (and money) downloading huge files. lrk

Alert | IP

Printer-friendly page | Edit | Reply | Reply With Quote | Top

Charter Member · 260 posts

RE: Proposal RC1: Route Specification and Description

Lawrence: I agree with all your points, but still am confused how to calculate the percent scenery. What is the formula? What does 58% mean? At present I have no idea what percentage values to quote for my routes. If "The point here is does it have scenery or not, or is it just blank terrain with track", then that can better be said in words, and presumably is covered by the detail level.You quote that "getting route developers to agree on anything is like herding cats!" I have done similar things in my real life, and find that this is just human nature, not limited to route developers. You just have to stop the discussion at some point, and go forward from there, despite complaints. Thanks again for your initiative!Michael Vone
Step by Step Guide to Route Building for MSTS - http://trainsimulatorworld.com/catalog/b470.htm
Albula Line Route
Rocky Islands Route
Cliff Hanger Route
http://avsim.com/hangar/utils/mvchallenges/

Alert | IP

Printer-friendly page | Edit | Reply | Reply With Quote | Top

Charter Member · 1674 posts

RE: Proposal RC1: Route Specification and Description

>Lawrence: I agree with all your points, but still am
>confused how to calculate the percent scenery. What is the
>formula? What does 58% mean? At present I have no idea
>what percentage values to quote for my routes. I have only used Abula once or twice, as I could never stay on the tracks! If this is the route you do not know what to put for the scenery, I would say 100% from what little I have seen.>If "The point here is does it have scenery or not, or is it
>just blank terrain with track", then that can better be said
>in words, and presumably is covered by the detail level. Point well taken.>You quote that "getting route developers to agree on
>anything is like herding cats!" I have done similar things
>in my real life, and find that this is just human nature,
>not limited to route developers. You just have to stop the
>discussion at some point, and go forward from there, despite
>complaints. Thanks again for your initiative! Ya, I know, human nature. I thought that I would just throw that in for some lightheartedness if anyone was getting too serious about this.Thanks for the thanks. I took the initiative for several reasons, one of which I will mention here: I think it is a good idea, it is time for it, and it was dying for "lack of a second," as they say in Parlimentary Procedure.BTW, there *will* be an RC2, as I have thought of how to clear up some possible misconceptions.Lawrence

Alert | IP

Printer-friendly page | Edit | Reply | Reply With Quote | Top

Charter Member · 163 posts

RE: Proposal RC1: Route Specification and Description

Lawrence - good proposal. Thanks for all the work you've sunk into this. I think it's a great idea and will be very helpful. I agree with your responses to the comments. Let's not get too tied up in the numbers for things like % scenery completed. I'd suggest something more qualitative - none, scant, trees only, partial, full, etc. Either that or limit it to ranges - 0-25%, 25-50%, etc. Beyond that, I have no comments. I vote we go with it pretty much as it is. Nothing's perfect, and trying to get there will only keep us from having anything. There's an adage in engineering, "The perfect is the enemy of the good." Let's toss this puppy out there and let it swim!Andy

Alert | IP

Printer-friendly page | Edit | Reply | Reply With Quote | Top

Member since Aug-23-02 · 59 posts

RE: Proposal RC1: Route Specification and Description

Lawrence,Great job!!!There is only one area that I would like to address: Fictional or Prototypical OperationsLong time readers of the Model Railroader magazine, would categorize a railroad's theme as Fantacy, Prototypical, or Freelance.Fantacy: A route which has no resemblence to a real world railroad either in area, timeframe, and/or operational style. An example would be to set a steam only motive power into the modern era and run it like a real railroad.Prototypical: as faithful an emulation of either a historical or a modern real world railroad - as much as possible.Freelance: this blends the two above. It uses enough real world operational and location details to make its existance operationally plausible, although the railroad's name is purely fictional. This is seen a lot with model railroaders, examples of which you will find in nearly every issue of Model Railroader. This is a "what if..." kind of railroad...like in "what if ATSF did not succeed in its hostile takeover of the BN"...or UP with the SP.Other than that...everything looks great. Personally I will not be getting into the FPS spec...as it is too hardware dependent.

Charles Burgess

Alert | IP

Printer-friendly page | Edit | Reply | Reply With Quote | Top

Charter Member · 1674 posts

RE: Proposal RC1: Route Specification and Description

Good point, I like it, though, if you don't mind, I think I'll spell it "Fantasy," okay??? BTW, I have addressed this several times, and I cannot understand why it *appears* the point is not understood, and that is, that the FPS is just a *guideline*. If you have read what I have written, then I don't need to say it again.Can you shed light on why this _seems_ so hard to understand???Lawrence

Alert | IP

Printer-friendly page | Edit | Reply | Reply With Quote | Top

Member since Aug-23-02 · 59 posts

RE: Proposal RC1: Route Specification and Description

>Good point, I like it, though, if you don't mind, I think
>I'll spell it "Fantasy," okay???
>
>BTW, I have addressed this several times, and I cannot
>understand why it *appears* the point is not understood, and
>that is, that the FPS is just a *guideline*. If you have
>read what I have written, then I don't need to say it again.
>
>Can you shed light on why this _seems_ so hard to
>understand???
>
>Lawrence Fantacy...oopppss...all thumbs at times...heheFPS rating is actually a very complex issue that is totally dependent on specific hardware combos. Now, if we tied a specific FPS to a specific tile which contained a certain amount of objects...that would be more meaningful info. We also have differences in density configurations by different route designers: i.e. in the default MP, with the density settings turned down a couple notches, you still get a lot of buildings and scenery objects, but on some routes from the Train-Sim library, all you get at the same setting is just terrain and track, with a few trees once in a while. But if you turn the density settings up, then the other objects and scenery shows up all of a sudden....no incremental increase in scenery density as you increase the settings in the options menu.Other than to add another category of themes for a route, the FPS is not an issue as far as your Route Spec outline....all very good, and I support you 100%. On the other hand many of us route designers do see a need to further define, among ourselves, on how to define the FPS...we need to discuss that some more now that it is a needed spec. Overall, we route designers can forsee some problems with the FPS spec, thus some of us have injected it here (myself included) when we should start up a separate thread to discuss it. The FPS spec is needed, we just need to figure out how to use it in a meaningful way.

Charles Burgess

Alert | IP

Printer-friendly page | Edit | Reply | Reply With Quote | Top

Charter Member · 163 posts

RE: Proposal RC1: Route Specification and Description

Who's "fantacy" is it, anyway? If it's really a fantasy/phantacee/etc., maybe that's the way it's spelled in their world. Andy

Alert | IP

Printer-friendly page | Edit | Reply | Reply With Quote | Top

Charter Member · 374 posts

RE: Proposal RC1: Route Specification and Description

Click to send message via ICQ

LAST EDITED ON Aug-27-02 AT 10:55 PM (EDT)

routeartisan, I agree with most of what you and the others have said with one exception and will explain .."Other than that...everything looks great. Personally I will not be getting into the FPS spec...as it is too hardware dependent"My reason for wanting this is .. if you have a marginal system, this makes all the difference in the world as to whether you will enjoy it or try it and delete it. I have d/led a quite a few routes that were 'gorgeous' if that is the correct term, but to run them, I either had to turn the sliders down to where there was nothing but track and terrain or stumble along at 2-4fps. I would estimate at least 550mg of downloads have been deleted this way. With broadband it isn't really a problem, but what about the dial-ups.Yes it is hardware dependent, but by knowing what your hardware is and roughly what you are getting in fps, I can extrapolate fairly accurately what my fps would be so as to know whether it's in my ball park or not.Just my feelings on this one issue.{edit} Sorry Lawrence you beat me to it

RobertR .. ADF-M&RM at http://www.adfrr.com

Alert | IP

Printer-friendly page | Edit | Reply | Reply With Quote | Top

Charter Member · 1756 posts

RE: Proposal RC1: Route Specification and Description

Lawrence;Great proposal and I think it would be of great help to future route downloaders.My 2 cents on percent complete and I'll be the hardest on myself than anyone that uses the route. My guess after the last update is that most people would say the line from Clinton to Dunkle is 100% complete. To me it isn't. But so long as it has scenery on it I would call that area complete. The fact that a buidling is missing doesn't make it not done.LaterDavid

David Klemm
Illinos & St Louis Divisions
IC Version .9 uploaded

Alert | IP

Printer-friendly page | Edit | Reply | Reply With Quote | Top

Charter Member · 1674 posts

RE: Proposal RC1: Route Specification and Description

>My 2 cents on percent complete and I'll be the hardest on
>myself than anyone that uses the route. My guess after the
>last update is that most people would say the line from
>Clinton to Dunkle is 100% complete. To me it isn't. But
>so long as it has scenery on it I would call that area
>complete. The fact that a buidling is missing doesn't make
>it not done.
As a user AND as a developer, that is my take on the situation.Lawrence

Alert | IP


[ Home | MSTS Forum | MSTS FAQ | File Library ] Copyright © 2002 by Nels Anderson. All Rights Reserved.

Restored from the Train-Sim.Com archive, captured October 2, 2002. About this archive.