When you lose a piece of track or road at negative inifnity or so

[landnrailroader]

This subject has bounced around a bit and I really don't think a few orphan items hurts the operation of the simulation but if anyone looks at it on Track Viewer (part of ORTS) or in TSRE and sees all these orphan specks of this and that it seems a bit sloppy. So after I finished the last branch off the CNO&TP 2nd District, which was the Oneida & Western that went from the CNO&TP at Oneida to Jamestown, about 45 miles through very rugged terrain I knew I would have a few. To reduce the number, whenever I was placinig a piece of track and it got "lost" I immediately looked at the object window to see what it was, lets say a 100M piece. Then I hit delete, and reselected and placed a new piece. But I still had a dozen or so scattered around so I used Track Viewer and turned on the World Files and grid. Then select a world file & jot down the values of it and note the approx. location of the orphan, like, near NW corner.
Then open the world file with a text editor, I like the Context editor. TSRE does not compress world files so when you open the file it is readable. Roll down through it looking for a track piece that has a negative "Y" value, i.e. the middle value in the location. When you find it, I suggest putting in a number of meters that is 50-100 greater than the average terrain, or just bigger than other items "Y" value. Then jot down all 3 location numbers - these tell you where the orphan is located in the world file. Now open the route in TSRE and jump to the world file just edited. Using the XYZ values, enter these into the XYZ boxes for the Camera. For "Y" you can use the same value as the orphan, or better 20-30 meters greater. Then the camera will jump to the entered location and there you should find the orphan. Just delete it, and save. Caution, when you find the orphan by the Context editor, there may be a temptation to just delete that item BUT DO NOT DO THIS AS IT WILL GET YOUR TRACK (OR ROAD) DATABASE OUT OF SYNCH. Very bad. Since we don't have a rebuild function (yet) you probably would just have to fall back to your last backup of the route.

Jerry Sullivan (retired frrom CSX, SR, and Docent Corps of C&TS)
Jacksonville, FL

[eric]

I've got an enhancement on the list to limit how far infinity is... No sense having it be over 2000m away from your cursor.

[landnrailroader]

Eric,

Yes, I have seen your comments on that, but the way I figured out to fix the errors was pretty easy and accurate and usable until such time as your fix comes in. How is that land acquisition in Tennesee coming - Nemo is on this simulation I am cleaning up. I intend to create the bridges for it, especially the big one at New River, and the other large one at S. Fork, as well as the old bridge at New River. I also want to put signs at the entrance/exit turnouts to the historic routes - all manual turnouts. Then I'll put it in "incompletes"/

Jerry

[eric]

The "don't fall in the deep, deep hole" problem is proving to be a little tricker to work out, but I'll find something that works eventually. It only seems to happen when you don't show terrain.

As for Camp Nemo... we closed on the land about 90 days ago, and started tree clearing enough to where we can get our RV parked there in about 60 days.

With luck, the power line easements get worked out before winter, and maybe we'll have power up and running next spring. Then we can start working on the barn and house...

Ironically, it's the powerlines running to the south portal of the new tunnel are part of the hold-up in my getting power... Those lines and NS's roadway access to the new south portal didn't get all of the needed easements recorded from the landowner, and it appears my powerlines have to cross his land. Until the courts work that out, our easement is on hold unless we find another way into the property. Unfortunately, powerline access isn't a guaranteed right, nor does the county have the right to grant one along the roadway that the lines will follow.

On the CNOTP3, our house will eventually be at Tile -11367 14107 Position -675.439 395.139 252.78 ---- feel free to leave an Easter egg. I have a 300 ft. radio tower on my version.

The tree in the foreround... one of a half dozen pines we dropped, averaging 75-80 feet long.

20240729_093550.jpg

After limbing it out, cutting into 3' sections and stacking the logs elsewhere....

20240802_100517.jpg

[eric]

Here's what I was able to come up with....

In "Errors and Messages" I can highlight track sections and world objects which have an altitude of less than -100m, which should cover just about every realistic route created. They'll show up on the error list, and you can jump to those as needed to remove track nodes and/or delete static objects...

Track Nodes are troublesome... they don't list the shape easily, but you can jump to them and then dive underground as needed to zap them. If it's a multi-track or curve, you might have the same piece show up with multiple nodes.

capture_500778.jpg

World Items are a little more forgiving -- you can jump to -and- try to select them.

capture_500779.jpg

There's also the option to "Autofix" these which would delete them automatically. I'm not sure I want to take that approach just in case they were legitimately buried 300+ feet below sea level....

After I test a little more, This will be is in 8.005c as a testing release for others to try out.

[eric]

Made a slight tweak to the error message that will come out in the next version (not going to do one just for this), and also added the UiD for a better form of reference than the TrackNode.



Saying something had a negative altitude was reminding me too much of a not so well known Meatloaf song and album title...

[eric]

This will also be written out to the logfile:

[I] Errors:
[I] Route Error Msg  105 :  "WARNING" : "RoadDB" : "TrackNode: 12866 UiD: 9521 is deep underground: -2225.05"
[I] Route Error Msg  104 :  "WARNING" : "RoadDB" : "TrackNode: 12845 UiD: 10357 is deep underground: -2682.75"
[I] Route Error Msg  103 :  "WARNING" : "RoadDB" : "TrackNode: 12731 UiD: 9520 is deep underground: -2541.94"
[I] Route Error Msg  75 :  "WARNING" : "RoadDB" : "TrackNode: 6288 UiD: 30043 is deep underground: -3868.8"
[I] Route Error Msg  74 :  "WARNING" : "RoadDB" : "TrackNode: 6260 UiD: 29789 is deep underground: -3135.45"
[I] Route Error Msg  73 :  "ERROR_FIX" : "RoadDB" : "Item not referenced in W files. Id: 873. Type: levelcritem"
[I] Route Error Msg  72 :  "ERROR_FIX" : "RoadDB" : "Item not referenced in W files. Id: 872. Type: levelcritem"
[I] Route Error Msg  65 :  "ERROR_FIX" : "TrackDB" : "Item not referenced in W files. Id: 12712. Type: speedpostitem"
[I] Route Error Msg  64 :  "ERROR_FIX" : "TrackDB" : "Item not referenced in W files. Id: 12710. Type: speedpostitem"
[I] Route Error Msg  63 :  "ERROR_FIX" : "TrackDB" : "Item not referenced in W files. Id: 12525. Type: speedpostitem"
[I] Route Error Msg  48 :  "WARNING" : "World" : "StaticObj sg_fietspad50x3.s is deep underground: -3738.72"
[I] Route Error Msg  47 :  "WARNING" : "World" : "StaticObj hw_fnc20.s is deep underground: -2553.52"
[I] Route Error Msg  46 :  "WARNING" : "World" : "StaticObj hw_hge20de.s is deep underground: -2259.71"
[I] Route Error Msg  45 :  "WARNING" : "World" : "StaticObj hw_hge20de.s is deep underground: -2257.43"
[I] Route Error Msg  44 :  "WARNING" : "World" : "StaticObj hwy-pipeculvert1.s is deep underground: -826.392"
[I] Route Error Msg  11 :  "ERROR_FIX" : "World" : "Object 'levelcr' - referenced trackItem has wrong type. UiD: 13838. "
[I] Route Error Msg  10 :  "ERROR_FIX" : "World" : "Object 'levelcr' - referenced trackItem has wrong type. UiD: 13837. "
[I] Route Error Msg  9 :  "WARNING" : "World" : "StaticObj srv_10x10chainlinkfence.s is deep underground: -2085.89"
[I] Route Error Msg  8 :  "WARNING" : "World" : "StaticObj hw_hge50de.s is deep underground: -3270.41"
[I] Route Error Msg  7 :  "WARNING" : "World" : "StaticObj doc_4telegraphwires.s is deep underground: -3917.56"
[I] Route Error Msg  6 :  "WARNING" : "World" : "StaticObj bdtelepole1.s is deep underground: -3712"
[I] Route Error Msg  5 :  "WARNING" : "World" : "StaticObj hw_hge20de.s is deep underground: -4001.31"
[I] Route Error Msg  4 :  "WARNING" : "World" : "StaticObj de_fence.s is deep underground: -2102.12"
[I] Route Error Msg  3 :  "WARNING" : "World" : "StaticObj de_fence.s is deep underground: -2104.75"
[I] Route Error Msg  2 :  "WARNING" : "World" : "StaticObj de_fence.s is deep underground: -2168.62"
[I] Route Error Msg  1 :  "WARNING" : "World" : "StaticObj srv_singletelegraphpole.s is deep underground: -3541.17"
[I] Route Error Msg  0 :  "WARNING" : "World" : "StaticObj srv_singletelegraphpole.s is deep underground: -3643.36"​

[Pecho Lata]

This list in logfile will be very useful, at least for me.

[HookitandBookit]

I never get the option to "jump" anywhere. I badly want to fix thses, how would i do that when i cant even find the files i need to remov?

error.jpg

[kapitaen]

If there is no position data, you cannot jump there.

However, you can use the autoFix = true function. Activate this and then start TSRE.
Screen Shot 02-06-25 at 03.21 PM.jpg

After opening the error list, the repaired errors are highlighted in blue. Now don't forget to save the route.
Screen Shot 02-06-25 at 03.28 PM.jpg
Jan

[HookitandBookit]

Yes, i tried that to no avail. Even tough i have applied the required setting TSRE does not attempt to repair even one of those. I must have missed something.

[eric]

DeepUnderground won't prevent it. It only can flag the mistake for cleanup. Best practice is to not move tracks without the terrain grid visible.

Sent from my SM-S911U using Tapatalk

[HookitandBookit]

I apologize to all parties involved, as per usual this was another user error. I had not removed the # marks and as such the TSRE settings was not having any effect. Sorry for bothering you with my sillyness.

[rdayt]

Cool, that's how we all learn.

Randy