Feature Requests Implemented

[eric]

This is for Jerry as much as me. A quick addition to the settings.txt with the following values:

wireLineHeight = 6.6
sectionLineHeight = 3
terrainSize = 1
terrainEmbankment = 2
terrainCut = 2
terrainRadius = 9
terrainBrushSize = 1
terrainBrushIntensity = 12​

These values will set the yellow line height (using the values above) to 6.6m, and pre-fill the the terrain tools values for cut/fill to your favorite setting so that you're not having to adjust them on every editing session:

capture_500324.jpg

[CSRX]

The ability to use TSRE while on two monitors. Would be nice to still use TSRE just fine on one screen, while having the track charts enlarged onto another monitor while building routes. Would make it a little more easier to work with, than constantly flipping back and forth from the TSRE window, to the Photo/PDF window and then losing track where you left off..

[eric]

The ability to use TSRE while on two monitors.

Yep, there's a bug in the underlying QTWindows (not the TSRE code itself) that doesn't like screen positions that exceed the primary monitor's boundaries.

I use three screens (arranged 3, 1, 2) and if I open TSRE on anything other than 1, it will launch the route selector window wherever, the Navi window on 1, and then the RE window freezes up if it's on 3 or 2...

I found a way to fake it out -- which is to force TSRE to spawn on the primary monitor (which again, is where the Navi box spawns).

Once it's open, you can drag it wherever. I've been known to slide the Navi monitor over to 3 where my track charts are, and use the editor on 1.


Available to try here ---> Github

[eric]

I found some enhancement requests on Goku's forums, and have folded in a few more:

• Increased decimals available on Dynamic track to include five decimals for angle, and three decimals for radius
• Modified color for patch and world object selection to make it easier to see (was blue, now orange) (requested by Dave Nelson)
• Modified menu keys to eliminate duplicate shortcut keys
• Changed log file to add "tsre" prefix along with datetime stamp so logs don't overwrite anymore (requested by Dave Nelson)

Dynamic Track decimal precision:

capture_500333.jpg

As written into the local TSection.dat:

capture_500331.jpg

Menu hotkeys/shortcuts no longer repeate letters T, W, and O:

capture_500337.jpg capture_500338.jpg

Object Selection now highlighted in orange:

capture_500332.jpg capture_500336.jpg

Log Files:

capture_500341.jpg

[pwillard]

Modal Indicators... there are some actions within TSRE that are toggled with a keypress but there is no indication of which state you are in at any given time... Having even an LED-LIKE indicator to show status would be helpful.

I'm referring to things like the Q key or / key toggles... as an example.

[eric]

Yes, I know what you're asking for there, Pete... its the same with the height +/- toggle and being in rotation vs position movement. That should be doable with a HUD or bar that persists between panels. I also want to show the elapsed time without a save...

[eric]

A new version v8.002 is available in the file library.... File 88621 fixes a few configurable items that weren't working as advertised (e.g. line heights and terrain settings), and also adds a feature that Dave from Elvas requested -- adjusted line weights and colors.

You can now define one color and line width for terrain tile selection (orange, weight of 4px)....

capture_500438.jpg

.... and another color and line width for objects (purple, weight of 2px)....

capture_500439.jpg

These color definitions use the same style hex values as other color settings that Goku's v7.012 and earlier offered for the consist editor and shape viewer.

Weights are in pixels, with 2 being the recommended small value.

Here's an overview of the new settings:

wireLineHeight = 6.7         // sets the yellow TDB line height to help position catenary/bridges
sectionLineHeight = 5        // sets the grey Tsection line that people probably don't notice is there
terrainSize = 1              // sets the cut/fill size value
terrainEmbankment = 2        // sets the cut/fill embankment value
terrainCut = 2               // sets the cut/fill cut value
terrainRadius = 9            // sets the cut/fill radius value
terrainBrushSize = 1         // sets the terrain brush size
terrainBrushIntensity = 12   // sets the terrain brush intensity
selectedTerrWidth=4          // sets the width of the terrain tile selection lines
selectedTerrColor = #FFB612  // sets the color for terrain tile selection lines
selectedWidth=2              // sets the width of the object selection lines
selectedColor = #B612FF      // sets the color for object selection lines​

I don't plan on issuing any more new features for a while -- this version came out quickly because of the noted defects (none of which would have affected files being worked or saved).

Enjoy!

[eric]

I've yet to run into the usequadtree issue on my routes, but can change the default. If you've got others, let me know.

Jan, I'll dig into the platform line. It seems to be partially responding to the adjusted Tsection height setting.

If you change the sectionLineHeight does it respond?

[landnrailroader]

Eric,

I would sure like to see how your cut/fill parameters work but can you provide some instruction on how to install this new version of TSRE. Us old farts need to know.

Jerrry

[eric]

It's pretty simple.... unzip the folder anywhere, and use the batch shortcuts in it...

The settings are fairly generic, so you might want to paste some of your original settings from the settings.txt file in your previous TSRE folder.

The way that cut/fill works has not changed: the only modification is allowing for your preferred values to persist between sessions. It may take me a while to figure out to see if there is a way to get some greater precision similar to what we had in the MSRE.

[docmartin]

Forgive my ignorance but can someone enlighten me as to the purpose of the option for signals for custom detail as opposed to default.

Martin

[kapitaen]

I'll either get that back to using a default height for v8003, or possibly give it its own setting.

I would stick to the standard height of 1m, as the line should generally extend to both sides and the centre.
Platform left / right or no.

[eric]

I'd think an adjustable height might help with placement of high platforms.

[eric]

can someone enlighten me as to the purpose of the option for signals for custom detail

Some of us building routes use tools to attach scenery objects to other scenery objects by using the custom detail.

With my WFH tool, I can assign a detailed level of 2 to a signal, and the tool will place an equipment cabinet, a ladder, and possibly a raised embankment around the signal on the left hand side of the signal, and a detail level of 3 for the same on the right side of the signal.

On a gantry type signal, it can be used to denote where a right handed cantilever or left hand cantilever should be.

You could also set a value greater than 100 for signals placed to trigger advance signal logic and to allow for return loops, which would prevent them from being displayed in the sim.

[docmartin]

Thank you for your explanation, Eric, though I am not much the wiser! What is this magic WFH tool?

Martin