Selecting Z to a RogueBluePole Crashes TSRE

[Vince]

Hi GokuMK,

Removing a Rogue Blue Pole (a single isolated blue pole) crashes TSRE.
Test sequence:
Start TSRE ok
Attach track to Blue Pole. ok
Press Z
TSRE crashes.

Log follows

[I] = release terrain  0
[I] = release terrain  0
[I] undo begin
[I] undo begin
[I] undo begin
[I] undo begin
[I] "placeTool"
[I] "engItemSelected"
[I] "E:\\Train Simulator-PRR/global/shapes/A1t30dTramCrv.s"
[I] found :  0
[I] ""
[I] "placeTool"
[I] 1:  -11055   -14283   -630.874   30.5125   978.867
[I] 1777
[I] "A1t30dTramCrv.s"
[I] defaultEnd 0
[I] ccc
[I] 0   0
[I] 2:  -11055   -14283   -630.946   29.9927   978.363
[I] "trackobj"   "A1t30dTramCrv.s" 53370
[I] Nowy  632  shape:  "E:/Train Simulator-PRR/global/shapes/A1t30dTramCrv.s"
[I] "E:/Train Simulator-PRR/global/shapes/A1t30dTramCrv.s|E:\\Train Simulator-PRR/routes/PRR_Eastern_Region-2/textures"
[I] undo begin
[I] "A1t30dTramCrv.s"
[I] 20253
[I] 39801
[I] 9.74103
[I] polacze  20252   1777
[I] 1   0
[I] 20253   1
[I] przeniose  22  items z  1  do  20253
[I] d:  9.74103

The Blue Poles that come in pairs as when a track section is moved or deleted from a world file leaving just the TDB yellow lines connecting the two poled can be deleted.

I placed a 10 meter track section isolated from any other track. Saved . . . inspecting the TDB there were 3 new datablocks;
EndNode
VectorNode
EndNode
This test was a normal track isolated track section. Three blocks sharing related data.

So an isolated Blue Pole is missing 2 or possible more datablocks and crashes the editor when 'Z' is pressed.
The isolated Blue pole has a TrNode number making it easy in the database, a single datablock missing it's 'companions'

Not a show stopper but a minor database glitch.
Any ideas on getting rid of the single isolated poles?

regards,

[GokuMK]

Can you show me the blue pole entry in TDB? I will look at a solution.

[Vince]

Good morning Goku,
Yes certainly I can do that. . . . even before my morning coffee .
Here is a clip of the TDB with the bad entry in red.

TrackNode ( 2540
TrVectorNode (
TrVectorSections ( 7 180 219 -11027 14303 124 0 2 00 -11027 14303 -1023.05 20.641006 -924.80096 0 4.2319798 0 1 1 -11028 14303 51075 0 1 00 -11028 14303 954.008 20.641006 -961.77301 0 4.2319798 0 3 3 -11028 14303 51076 0 1 00 -11028 14303 909.66797 20.641006 -984.88 0 4.2319798 0 39756 19780 -11028 14302 2406 0 1 00 -11028 14302 687.966 20.641006 947.58502 0 4.2319798 0 0 0 -11028 14302 2407 0 1 00 -11028 14302 621.45599 20.641006 912.92523 0 4.2319798 0 183 36061 -11028 14302 2408 0 1 00 -11028 14302 612.58801 20.641006 908.30298 0 4.2319798 0 330 239 -11028 14302 2018 1 0 00 -11028 14302 611.29523 20.6411 907.62598 0 4.2319498 0 )
)
TrPins ( 1 1
TrPin ( 1073 0 )
TrPin ( 1115 0 )
)
)
TrackNode ( 2541
TrEndNode ( 0 )
UiD ( -11061 14267 2355 0 -11061 14267 -390.38278 20.843204 -495.83298 0 3.9716501 0 )
TrPins ( 1 0
TrPin ( 1 0 )
)
)
TrackNode ( 2542
TrVectorNode (
TrVectorSections ( 11 39871 29054 -11149 14348 63881 0 1 00 -11149 14348 -359.20389 365.24701 311.81409 0 0.81933177 0 28863 22004 -11149 14348 63886 0 1 00 -11149 14348 -341.72723 365.24701 331.2619 0 0.64480352 0 30510 22691 -11149 14348 64177 0 1 00 -11149 14348 -331.72879 365.24701 344.55698 0 0.64480352 0 0 10 -11149 14348 64173 4 5 00 -11149 14348 -330.95578 365.24701 345.58508 0 0.64480352 0 0 22629 -11149 14348 64180 10 11 00 -11149 14348 -324.97131 365.24701 353.56918 0 0.64479721 0 39070 19777 -11149 14348 63987 3 2 00 -11149 14348 -318.96088 365.24701 361.5614 0 0.64479721 0 339 22656 -11149 14348 63989 14 15 00 -11149 14348 -297.92438 365.24701 389.53418 0 0.64479721 0 2 22676 -11149 14348 64000 14 15 00 -11149 14348 -279.89328 365.24701 413.5108 0 0.64479721 0 1 22667 -11149 14348 64013 3 2 00 -11149 14348 -219.78983 365.24701 493.43292 0 0.64479721 0 32116 29059 -11149 14348 64027 0 1 00 -11149 14348 -189.73799 365.24701 533.39398 0 0.64479721 0 39871 29055 -11149 14348 64024 2 0 00 -11149 14348 -172.74579 365.24701 555.98901 0 0.64479721 0 )
TrItemRefs ( 2
TrItemRef ( 15949 )
TrItemRef ( 15950 )
)
)

Here is a pic at the location.ROGUE BLUE POLE 2541.jpg

I can attach a tracksection to this pole but as soon as I press Z to add to tdb, TSRE crashes.

As an expriment I placed an isolated 10m tracksection and then looked at the TDB.
The 10m section was NOT attached to any other track and showed three (3) datablocks in the TDB.

I did not send a tdb clip of this as you probably already know what a TDB entry for an isolated track section looks like.
I only place it here for the educational purpose of informing the community of the mystery in the TDB that may help someone someday.

Any more info from me you need please ask and I shall provide.


Thanks for the reply,
regards,

[GokuMK]

This an ugly TDB corruption, because it is not an isolated blue pole (look at the grey line starting from the blue pole).
It points to TrackNode nr 1:
TrPin ( 1 0 )

TSRE probably crashes because it try to join two Vectors but TrackNode nr 1 is not a Vector.

[Vince]

Ugly? Strongly Agree!!
But the Grey line has nothing to do with the Blue Pole . . . It's an optical illusion due to the camera angle I used to clearly show the numeral on the pole.

Here's another pic from a better angle ROGUE BLUE POLE 2541-Pic2 (Small).jpg

Note that there are no database lines attached or associated with this Rogue Blue Pole.
Fact is, I've never seen any sign of database lines associated with a SINGLE isolated Blue Pole!

There are (were) many Rogue Blue Poles in the route that I was able to eliminate BUT . . . All were connected by a Yellow TDB Vector line.
No problem eliminating those but a Single Isolated Blue Poles are the most troublesome to eliminate.

I can't simply delete this 'Rogue' TDB Datablock as it throws all the sequential numbering off and (i tried this) deletion really slags the TDB, requiring use of the backup. I have pondered whether I might try pasting this over this datablock (the one in red in previous post) with an 'Empty Item' datablock:
example /. . . .

EmptyItem (
TrItemId ( 2541 )
)

But I'm not sure this won't introduce more trouble into an already shaky database as an EndNode (the 2541) is not really a Track Dartabase "ITEM". Opinion on this?

For sure a tough (and ugly) bug I certainly agree but I 'know' you will come up with a solution.

Best Regards,

[Vince]

Additionally, as you can see I have a wealth of Rogue Blues loose in the route.
I've highlighted the one that's relevant to this discussion, but all of these are Single isolated Rogue Blue Poles and all crash TSRE if a track is attached and Z is engaged to activate the TDB to the node.

A clip fro the Open Rails Log:

Warning: Ignored invalid track node 1110 pin [0,0] link to track node 1
Warning: Ignored invalid track node 1777 pin [0,0] link to track node 1
Warning: Ignored invalid track node 1838 pin [0,0] link to track node 1
Warning: Ignored invalid track node 2349 pin [0,0] link to track node 1

Warning: Ignored invalid track node 2541 pin [0,0] link to track node 1

Warning: Ignored invalid track node 3448 pin [0,0] link to track node 1
Warning: Ignored invalid track node 3449 pin [0,0] link to track node 1
Warning: Ignored invalid track node 3673 pin [0,0] link to track node 1
Warning: Ignored invalid track node 4666 pin [0,0] link to track node 1
Warning: Ignored invalid track node 5918 pin [0,0] link to track node 1
Warning: Ignored invalid track node 9686 pin [0,0] link to track node 1
Warning: Ignored invalid track node 9846 pin [0,0] link to track node 1
Warning: Ignored invalid track node 12284 pin [0,0] link to track node 1
Warning: Ignored invalid track node 12653 pin [0,0] link to track node 1
Warning: Ignored invalid track node 13249 pin [0,0] link to track node 1
Warning: Ignored invalid track node 13306 pin [0,0] link to track node 1
Warning: Ignored invalid track node 13307 pin [0,0] link to track node 1
Warning: Ignored invalid track node 13308 pin [0,0] link to track node 1