Results 1 to 10 of 19

Thread: Transitioning to TSRE

Threaded View

Previous Post Previous Post   Next Post Next Post
  1. #1

    Default Transitioning to TSRE

    I know I'm not the last holdout making the jump to TSRE, but finally took the plunge about two weeks ago.

    Starting with the CNW Chicago, I replaced all the imagery that I'd loaded with SRT years ago with newer images. I've now also done the UP Gila Sub (Sunset Route), and will be re-doing Packerland eventually. Here's an example of the tearing (e.g. roads not lining up at sub-tile or tile seams) that SRT did:



    It's fixed the tearing, but exposed way too many places where the ROW was placed slightly off from the real world, and it's visually distracting. That's going to force me to move existing track, and that means ripping out existing signals...

    So... let the transitions begin. Rather than work each of the three routes I have in progress from start to finish, I'm going to work them in parallel starting with tracks, signals, and then other interactives like mileposts and crossing.

    I'd already started with textures, and sped things up a bit by creating another of my hack apps to replicate all the mouse clicks needed to create terrain textures from a map:



    (and no, that app is not ready for prime time release just yet... it's customized too much for my desktop...)

    Basically, if I center on the corner of four tiles, it can repeat the sequence four times while I go do something else on my other PC during the two minutes it takes to load four tiles and create the terrtex.

    This past week, I dived into moving track. I used to be able to do this in my sleep with the MSTS-RE, and it will definitely take a while before I'm back to that level of comfort... Starting with the UP Gila, I replaced 25 miles of track between CP Wellton and CP Mohawk. Fortunately that was mostly straight runs with only a few turnouts and slight grade changes. But that was the low hanging fruit... the next week will be a little more challenging as I'll have to deal with more curves on moderate grade changes.

    So far, I've used the following features:

    • Placing new track
    • Moving existing track
    • Milepost placement
    • Terrain maps to terrtex
    • Terrain painting
    • Terrain height adjustments
    • Auto-paint by TDB vector


    As I mentioned to a few others, muscle memory is the hard part. I'm still hitting F keys from the MSTS-RE out of habit, and I'm having to keep a cheat sheet plus Pete Willard's PDF open on my second monitor, but so far I haven't blow anything up beyond repair...

    All in all.... it hasn't slowed me down aside from learning new keystrokes or where a value is displayed on the sidebars.

    Things I miss so far:

    • Shortcut keys for all major functions....

      Example... there's a shortcut to select objects, but not a shortcut to place new objects? (OK, apparently there is and I didn't see it in the book...)
    • Tile re-loading from the W file... it looks like this is loaded once, and never refreshed. Haven't seen a function to force re-load a tile.

      This is a personal difference - I want the ability to go into a World file and make tweaks, e.g. using Tangent to calculate a new QD, or swapping out a shapefile name. With the MSTS-RE, if you moved more than 3 tiles away, it would reload the tile from the source file when it came back into view, so I could force a reload by jumping away and then returning.
    • Ability to change the World but ignore Terrain changes...

      Seems odd that there's an ability to disable changes to the TDB (which I do like), but no such option to isolate changes to the .T files or .W files... MSTS would save .W files by default, but gave you the option of ignoring terrain changes. That would be useful, particularly for people who temporarily raise up terrain to make it easier to place objects...


    Things I find hugely valuable:

    • Transform track rotation...

      I use Google imagery as my terrain textures, so there's not much tolerance to be off by >3m when it comes to track alignment. Being able to skew a straight section of track by 0.1d on the fly has been a life saver.
    • Auto-painting a texture pattern by TDB vector. Especially with Google imagery, it's nice being able to mask some of the transient things that creep into the ROW e.g. shadows or images of a train that managed to be captured in the satellite pass, or a railroad vehicle that was parked near tracks. I still have to figure out a good resolution for my rock textures to match the clarity of my ballast, but that will happen with time. Interestingly, Microtex.ace still looks good after 20 years...
    • Keying in rotation values. No more need for a mouse or keypad... Would be nice to have a shortkey to edit that value box, though. Used to be F4 in the MSTS-RE...


    I'm sure there will be other items as I go.

    If all goes as planned, the changes on the UP Gila will wrap up before the end of the month, and I'll be able to tackle the CNW Chicago, where there are at least 40-50 miles of multi-track mainline that will need to be shifted by about 5-10m to match where the ROW shows up on the Terrtex.
    Last edited by eolesen; 12-13-2020 at 04:23 PM.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
-->