![]() ![]() 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 So, now automatic installation should work on all operating systems.In the *.tdb, the locations of Trackitem (Signals, Speedpost, Milepost, Levelcrossing, etc.) are defined as follows, example entry in the TDB: TSRE uses now Tar archiwes and own tar file extractor instead of windows. fixed bug when train path stations were not in order while making services. fixed bug with loading DDS textures defined directly in data files. fixed bug when moved platform marker is not properly displayed in some tools fixed Quad Tree bug (disappearing terrain) fixed bug when editing water on tile with water disabled fixed bug when moved carspawner marker is not properly displayed in some tools many fixes and features already forgotten XD option to customize number of recent items list: "numRecentItems = X" improved kml rendering - try "markerLines = true" New window + route checks + new option: "loadAllWFiles = true" new error detected by TSRE - signal linked to wrong trackNode TSRE will remove all broken objects if autoFix is set to true in settings.txt TSRE creates an empty graphic.ace file when making a new route, so MSTS won't crash on load fixed bug when signals face wrong direction after track vector editing fixed bug when placing elevated complex tracks and shapes Make sure that TSRE has access to the internet. Try installing TSRE in new, empty directory. go here and download openAL lib for your system: TSRE will automatically download required data. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
December 2022
Categories |