TDB Corruption on Route Save?
#21
Posted 19 January 2021 - 03:03 AM
#22
Posted 19 January 2021 - 04:27 AM
So far Rob's approach is working i.e. rebuilding the vector from A to B.
Hardly conclusive, but after three hours of editing, nothing that has been flipping has re-flipped.
#23
Posted 19 January 2021 - 08:36 AM
#24
Posted 19 January 2021 - 10:14 AM
The view menu option makes them show up as yellow once they've been written to the TDB, but there's nothing whatsoever when you Z them out of the TDB.
#25
Posted 19 January 2021 - 10:57 AM
eolesen said:
eolesen, on 17 January 2021 - 11:15 AM, said:
I was able to recreate in a blank route....
1) Lay six sr_3tstr_y_100m pieces in a row
2) Save/exit TSRE
3) Re-open TSRE
4) transform piece C rotate Y by 0.4
[...]
When you use your hack it seems to work at first:
https://i.imgur.com/nT5awpO.png
But when you return to editing this vector, splitting and joining, TSRE must flip it. And when it does it, this rotation hack will cause the flip to fail, because TSRE does not allow not matching rotations in a track vector, so the new one is broken:
https://i.imgur.com/bbVsqDA.png
If you want to use this rotation hack, avoid situations where you have to split it later. And if you have to, you must remove whole vector from TDB and add each track one by one from first to last, so that TSRE does not have to flip any vector.
#26
Posted 19 January 2021 - 11:40 AM
#27
Posted 23 January 2021 - 04:28 PM
Looking in the TrItems in the TDB I see a half dozen EmptyItems that I'm assuming were speedposts or signals that got clobbered when a vector got changed.
If the applicable world file items referencing them are deleted, will TSRE clean these up and renumber things or should I do a CLRDB in TSutils?
#28
Posted 24 January 2021 - 12:15 AM
#29
Posted 25 January 2021 - 12:51 AM
1. The slip is placed, in this case a single slip. The basic shape is the cross-over only, the switches are placed within this shape.
The blue poles at the end are the connections to the tracks, the blue poles within the crossover shape are the connections for the switch shapes.
SingleSlipA.jpg (197.46K)
Number of downloads: 7
2. The switches are placed. Note that the blue poles within the crossover have gone, those near the end have been replaced with the red switch poles.
SingleSlipB.jpg (203.68K)
Number of downloads: 5
3. The track has been placed and has been connected to the slip - but at the wrong position. The track next to it has the same geometry but clearly, the track connected to the slip is 1m. short of its position.
SingleSlipC.jpg (194.43K)
Number of downloads: 4
4. This shows more clearly what happened - the track has connected to the switch, and not to the 'outer' connection of the slip. Where in fig. 2 there was a red pole for the switch, there is now a blue and red pole. The track has connected to the switch and has 'undone' the connection between the switch and the slip. The blue pole at the end of the slip remains unused.
This should not be possible. There was no 'open' connection at this point (no blue pole in fig. 2 at this location).
SingleSlipD.jpg (211.97K)
Number of downloads: 4
As for the visibility of those blue poles - yes, they are very clearly visible, if you look sideways. But if you look straight from above these are not so clear at all. Sometimes, depending on the angle, they are not visible at all. When laying track in complex areas, and that's where slips are used, I always work from straight above. It provides a better overview and it is more easy to move around and zoom in if required.
Regards,
Rob Roeterdink
#30
Posted 25 January 2021 - 05:28 AM
Laid a piece of dynamic track, 3000r -0.2 for the angle.
Selected after adding to TDB, and changed angle to -3 permile.
Poof goes the editor...
Tried again, using just the default 10m straight.
Selected after the yellow line appeared, changed angle. Poof!...
It's doing it regardless if it's attached to another TDB vector or standalone.
Pretty much makes dynamic track useless if you need to make adjustments as you go...