Now, I have waited up to 5 minutes and eventually closed the program because it was not responding. I have about 3300 consists so loading is not instantaneous, but always in less than 1 minute. I click on the same shortcut I have used for months, the normal screen pops up showing the available folders and the number of consists and rolling stock folders, nothing happens. But today, after multiple attempts, I have been unable to launch the CE. And until today, I have had absolutely no problems creating and/or editing consists the entire time I have been using it. It is intuitive and, therefore, quite easy to learn and to maneuver around. I have been using Goku's Consist Editor for almost a year now and have had absolutely no issues w/the editor. com/forums/ index.Not sure if this is the correct location on the forum for this question, and if not, hopefully someone will point me to the proper place to make this post. So it seems, that OR can handle also TrItemSData( ) for TrackItems, if the space-coordinates are not present. Then the problem in OR disappears and the signal A precedes signal BĪnd OR is handling the Signals correctly! This problem is probably also the cause of similar problems with other trackitems. In the OR simulator, the signal sequence then appears as reversed, signal B is in front of A, which leads to disturbances of the signals. Calculated according to TrItemRData (OR simulator), signal B precedes signal A. This is even so in the six MSTS original routes!!Ĭalculated with TrItemSData (MSTS simulator), signal A precedes signal B. The MSTS-RE has left many routes where the two coordinates do not indicate exactly the same position of a Signal. In order to ensure the compatibility of the OpenRail with MSTS, TrItemSData( ) should also be used in OpenRails and Trackviewer for the location of TrackItem OpenRails uses, in CONTRAST to MSTS, the space-parameter in its tools.īUT the TSRE5, the only route-editor for OR, uses the same parameter as MSTS The MSTS consistently uses the same parameters for location of TrackItems: OR and MSTS process these coordinates differently to determine locations and function of TrackItems: TrItemRData ( ) is a three-dimensional coordinate in space, for the same object TrItemSData ( ) is the distance in meters from the starting point of a track part There exist two Parameter to locate a TrackItem, which define the same point In the *.tdb, the locations of Trackitem (Signals, Speedpost, Milepost, Levelcrossing, etc.) are defined as follows, example entry in the TDB:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |