Just my thoughts

[Vince]

Hi Glenn,

The log only shows when running Open Rails. It is a highly detailed error report.

Get an error running in MSTS and you're in the ditch . . . without a way out. Good luck with that.

If that's what you want, have at it.
I NEVER use is anymore as Open Rails is so much superior at running all my routes without crashing.

I'll be releasing the PRR_EAST-v2 in a couple of weeks as an OR only configured Mini Route. The beta testers have it now.
It's unfortunate you'll never be able to run it as most of the route has been made over in a two year project.
[
QUOTE]I am 80 years old and like to learn something new, but it is not the end of the world if I never get this program perfected.
Glenn [/QUOTE]

Hey. I'm two years behind you and I'm having a ball building routes with TSRE and running them with Open Rails.

There's nothing to "get this program perfected".
Yes, it's a work-in-progress but even so it's a joy to run with the community providing updates, sometimes 2 or 3 a day! Never got that with Microsoft did you?

Age ain't no excuse for me. I dumped MSTS 8 years ago as soon as I got the necessary hardware (i5 Quad core cpu and a GTX650 video) to run it smoothly. Never looked back.

regards,

[GokuMK]

Vince, why does this work in RE without pressing any keys. I have not had a problem with RE and I have changed track to find what works for the space etc. I just don't understand the need to decide when a track piece should be entered in the TDB. May be in this program it is different.

You don't need to press Z during track placement. Track is automatically added to TDB when track is unselected just like in MSRE.

There is one case where manual decision is required. If you want to move existing track, you have to press Z to remove track from TDB manually. This solution avoids unnecessary TDB editing. You can safely select track shape and edit its properties without risk of damaging TDB. It was important when TSRE TDB editing was full of bugs and many MSRE users were worried about using TSRE only for object editing. But it also solves all MSRE bugs when you select a track and save etc.

[Vince]

Vince wrote:

I was NOT successful when typing in BOTH tileX & TileZ coordinates at the same time jumping within the same tile..
I needed to perform the [Jump] one coordinate at a time and I don't know why but the two-step process works where getting an accurate coordinate position was impossible when doing a two-coordinate jump. No idea why.

Hi Vince
There seem to be a lot of odd things that work for one person and not for another in TSRE.
I can change both x and z coordinates within a tile at the same time, and then jump to the new location. I am using v6963.
Garry

Hi Garry,
Same version here but I should have been more precise.
Try entering tile coordinates with the decimal point! Then [Jump]

regards,

[Pecho Lata]

Vince wrote:

Try entering tile coordinates with the decimal point! Then [Jump]

Without decimals, you jump. With decimals in the two coordinates, do not jump.

[Vince]

Precisely!

Your ball peacockg.

regards,