[nicober]

Hi Jeroen!

I think the better way would be to start on a blank screen when you launch Trackviewer and not to start allways on the last route you opened at your last session. You can keep the last route coordonates and click on OK to start it or you have allways access to your menu bar at the top to change the route or the options.

The functionality to search tracknodes would be a real must in your utility.
If you add a Path editor it will be fantastic to work with this option,

Keep up your great job gentlemen!

Thanks very much for this utility.

Cheers!

Nicober

[JeroenP]

Dear all,

I give you an update to TrackViewer. Unfortunately at the moment still only source code.

I did a number of changes, as requested by some of you.

• Now starts with empty screen, so possible errors are easier to recover from
  
• Better printing of non-ascii characters in platform and siding names
  
• Option to search for tracknodes and trackitems
  
• Added endnodes/terminals (just weren't available in first release).
  
• Option to set background color
  
• Zooming is now only using discrete steps (but still with same small zoom step). Meters/pixel is now shown on ruler. Using shift together with mouse-wheel gives finer zoom.

I am still considering adding the possibility to edit/create MSTS paths. This will be something completely different from an ORTS-specific path editor. That one will be really different.

Quote

Does it show grade-crossings

I am not sure I fully understand the question. It shows tracks and also roads. It shows 'levelCrItems' on both tracks as well as roads. If I am not mistaken, the grade-crossings should be placed at these points on the road, not?

Best regards, have fun (I know I have).
Jeroen.
Note that the attachment no longer works with recent ORTS updates. The code of trackviewer is now available as part of ORTS source (under source/Contrib), although you still have to compile it yourself.

Attached File(s)

•  TrackViewer_20140211.zip (485.44K)
  Number of downloads: 333

[markus_GE]

JeroenP, on 11 February 2014 - 12:41 PM, said:

I am not sure I fully understand the question. It shows tracks and also roads. It shows 'levelCrItems' on both tracks as well as roads. If I am not mistaken, the grade-crossings should be placed at these points on the road, not?

You correctly understood my question and replied saying exactly what I wanted to know :blush2: :negative:

Cheers, markus

[Csantucci]

I see that somehow TrackViewer has been introduced in release 2067; thanks for that! However at a first glance I couldn't find how to start it. Must a specific build be created? And how?

[BillC]

Csantucci, on 02 March 2014 - 12:56 AM, said:

I see that somehow TrackViewer has been introduced in release 2067; thanks for that! However at a first glance I couldn't find how to start it. Must a specific build be created? And how?

James removed the solution file in 2068 , was breaking the automatic builds.

In 2070 you can build track viewer manually by adding TrackViewer.csproj in Souce\Contrib\TrackViewer to the solution file. Do a Rebuild Solution. The TrackViewer.exe will appear in V2070 - Copy\Program\Contrib. Run TrackViewer.exe

[Csantucci]

Thanks Bill, your indications were essential, because what stays in the TrackViewer manual seems to be no more valid referring to program building.

I wonder what the idea is about how to make TrackViewer easily available to all the ORTS friends, without needing to perform the above steps.

[markus_GE]

What about distributing it as a separate download on the ORTS website? It´s a splinter project of ORTS, so why not add it as an experimental download, precompiled and source, as the ORTS X releases?

Cheers, Markus

[James Ross]

Csantucci, on 02 March 2014 - 12:36 PM, said:

I wonder what the idea is about how to make TrackViewer easily available to all the ORTS friends, without needing to perform the above steps.

I'd like it to be included in all releases, either in "contrib" or ultimately as a fully-supported tool. The only reason it isn't in the builds right now is that it can't be built automatically for the same reason OR itself couldn't a year or so ago. It's a solvable problem. :D

[JeroenP]

Dear all,
For clarity, I am working on solving the issue, and progress is good.
Jeroen

[disc]

I've tried track viewer, and i noticed that, with big routes (1200km+) it have about 1 fps. While it's normal with smaller routes like the default routes.