[Amtrak115]

 roeter, on 20 April 2021 - 07:58 AM, said:

Allthough I did not write the code for the Trackviewer myself, I was involved with its development. I might be able to answer some of your questions but am I also very interested in what your plans are.
As far as changes to the generated data are concerned : it is not possible to just change Trackviewer, any changes to the output of Trackviewer must be made simultaneous with the related changes in the operational code where the path is processed. And I'm afraid that is no easy matter.

Regards,
Rob Roeterdink

Rob, I understand that changes to the output of trackviewer would require changes to OR itself. My rational for looking at trackviewer, is that once I understand how it works and can replicate it, then being able to make changes in the OR baseline will be somewhat easier....at least that's my premise.

As for my plans for trackviewer, I think that with some minor additions, trackviewer could be a one-stop shop for activity generation. you can now set wait points for AI trains in Trackviewer, however player events are set in an activity generator. Why not generate those while in trackviewer. Also, I believe that trackviewer should be able to import legacy info from MSTS, output will initially be MSTS, MSTS + ORTS, and eventually optionally only ORTS. those are the quick thoughts on "my plans"

Barry

[Csantucci]

Expanding TrackViewer to a full MSTS-OR Activity generator would be welcome.

[eric from trainsim]

Side comment: Would it be out of scope for Trackviewer to be able to show more details on signals? Right now it shows the signal and direction, but not any other info e.g. number of heads, which nodes the heads are linked to.

[Amtrak115]

Remember I'm just getting into it, however, I'll keep that in mind...off the top of my head a right-click properties might show that information....

[scottb613]

Hi Barry,

Just THANK YOU for taking the plunge.
:)

Regards,
Scott

[Genma Saotome]

This image shows siding "points" rather than the labels. I've been using them as spotting locations (IMO we need to have those as something separate from siding names but we don't). Having a mousing movement over one of the points to display the name would be a nice feature enhancement.



Another improvement from mousing would be to capture the exact xyz location when positioned over track (add right mouse click) and simply saving it to a text file as the data you need to place a consist or loose consist. At some later time it moves directly into an Activity editor.

[Amtrak115]

Noted, Dave.

[Genma Saotome]

I'll add my thanks to you for trying to improve this software. I've long thought it was very good work with potential for far more. I've love to see it expanded into an AE, even if it is just a basic one.

[R H Steele]

Barry, my thanks also. Much appreciated, I know you are in the exploratory-learning phase, take your time, and I wish you success.

Attached thumbnail(s)

• 

[cjakeman]

Hi Barry,

 Amtrak115, on 20 April 2021 - 07:26 AM, said:

I wish there were documented "programming" standards for OR, if there are, I haven't found them yet.

Here is an extract from the Contributing.md document which is on GitHub and linked from http://openrails.org...eveloping-code/



It might be useful to read the whole document. Is that what you wanted?