TSRE Crash using Error Display > [Select Object]

[Vince]

Goku,

Using v698 Tools > Errors and Messages > I select firts object listed then Jump Button to the location. \

In this case it is an animated switch stand (very common in NEC & PRR) When I press [Select object] button TSRE crashes.
I have attached a zipped copy of the TSRE log.txt file.

ATTACH]78862[/ATTACH]

Nice work on the error thing. I was able to use it to fix several objects 'Too Far From Tile' warnings but the PRR is the first I've tried with true database errors.
I'm presently working through the list of 'Signal not referenced to Signal Shape errors. First one blew up . . . we'll try a few more.

regards,

[Pecho Lata]

I've also noticed the problem Vince mentions. But if you deactivate "Tools / Properties" you can select the object and jump to it. When activating "Tools / Properties", TSRE crashes

[Vince]

Verified.

[Vince]

Adding more info. For the moment I'm working on the easy part . . . Removing objects too far from tile. Floating trees/veg/cars/fences @ 10 Km altitude or buried a Km or more underground.

I've been able to 1. jump to these objects, 2. select them with the Error Panel, but cannot delete them until I access the pop up menu and do a 'Reset Rotation on the selected (blue outline) object.
Then I can translate (move) the object and now the delete key works.
This is a valuable tool but it needs a bit of works yet.

regards,

[GokuMK]

In this case it is an animated switch stand (very common in NEC & PRR) When I press [Select object] button TSRE crashes.
I have attached a zipped copy of the TSRE log.txt file.

Selecting broken items may cause TSRE Properties window to crash . I just fixed it for platform object:

http://www.onrails.eu/viewtopic.php?f=7&t=107&start=10

It will be fixed in the future for other items.

I've been able to 1. jump to these objects, 2. select them with the Error Panel, but cannot delete them until I access the pop up menu and do a 'Reset Rotation on the selected (blue outline) object.

You should be able to delete it just by giving focus to 3D view. Use one right button click.
In the future there will be a "delete" button in Properties window.

[Vince]

Good morning Goku,

Thank you for your attention. I'll try the single right click to set focus / / / did have focus but no delete until I used the Reset Rot Button on properties panel.
Pointer in Stick everything mode pointer does collide (show) correctly on the object.

Any advice on these in pic?
TsreErrorPanel.jpg
These are the ones that crash if properties are open.These signals, at least the four or five I've run trains through operate normally. The first (hylited) is a switchstand and animates normally. As soon a I select either bt the Select Key on Panel or use pointer to select . . . a 3-4 second pause then the Crash message displays.

regards,

[joe_star]

Good morning Goku,

Thank you for your attention. I'll try the single right click to set focus / / / did have focus but no delete until I used the Reset Rot Button on properties panel.
Pointer in Stick everything mode pointer does collide (show) correctly on the object.

Any advice on these in pic?
[ATTACH=CONFIG]78863[/ATTACH]
These are the ones that crash if properties are open.These signals, at least the four or five I've run trains through operate normally. The first (hylited) is a switchstand and animates normally. As soon a I select either bt the Select Key on Panel or use pointer to select . . . a 3-4 second pause then the Crash message displays.

regards,

Does it do the same in route riter ICHK?

I have noted these issues when placing signals close to tile boundaries. TSRE writes the TDB entries to the adjacent tile (with coordinates larger than 1024/-1024) for the signal while the world file entries are written in the correct tile, hence resulting in an error when ICHK is run.

Placing the same signal in MSTS does not result in this behavior.

The signal works fine in game though, so I've left it as that. Reported it once back somewhere here.

[GokuMK]

Thank you for your attention. I'll try the single right click to set focus / / / did have focus but no delete until I used the Reset Rot Button on properties panel.

Works for me. Don't know what you are doing wrong here.

Pointer in Stick everything mode pointer does collide (show) correctly on the object.

Why you write about it here? ....

Any advice on these in pic?
[ATTACH=CONFIG]78863[/ATTACH]
These are the ones that crash if properties are open.These signals, at least the four or five I've run trains through operate normally. The first (hylited) is a switchstand and animates normally. As soon a I select either bt the Select Key on Panel or use pointer to select . . . a 3-4 second pause then the Crash message displays.

It means that signal filename found in W file can't be found in sigcfg file.

[Vince]

TDBItems Display Needs Properties.

Works for me. Don't know what you are doing wrong here.


Why you write about it here? ....


It means that signal filename found in W file can't be found in sigcfg file.

That's not what I see. All these signals do exist in the Sigcfg file, They've been in there for ages!
When I use the Jump button after high lighting the error on the top line the location is a ABS B&O color position light that I originally installed when I built the NECv4 route.

These are signals that have worked properly for over 10 years. They are now incorporated into the PRR-East v2 route without any changes.

Something else is wrong here.

First off, there were two TBDItems displayed as the Black Cube, superimposed over each other.

I can select one, delete it after the warning message and there is ANOTHER black cube that was superimposed over the black cube at the same location where I deleted the first TDB Item.
This is EXACTLY why I asked you many months ago to provide a Properties Display for ant TDBItem displayed.

So now it looks like each of these 'errors' are two TDBItems superimposed over each other and selecting them provides no information as to what they may be.

The TDBItem display is useful but without an ID of the Items properties deleting such items is a crap shoot, not something one should do in the Track Database.
When selecting a TDBItem I'd very much like to see a way to display all relevant properties of the Item.

Next: Pointer Stick . . .

Why you write about it here? ....

These are objects listed in the Error Panel as "Too Far From Tile Border", not the Signal 'Errors'. Mostly deeply buried treelines and other scenery objects, not TDB Items.
I only mentioned the pointer stick-to the object selected in the Error panel to illustrate to you that I CAN put the pointer on the object yet am unable to deselect it or delete . . . unless . . . I first bring up the context menu where I can use a Reset Rotation button. Then I am able to successfully delete all objects listed in the Error Panel as "Too far from tile border".
Thanks for your attention Goku. Stay well.
regards,

[GokuMK]

That's not what I see. All these signals do exist in the Sigcfg file, They've been in there for ages!
When I use the Jump button after high lighting the error on the top line the location is a ABS B&O color position light that I originally installed when I built the NECv4 route.

These are signals that have worked properly for over 10 years. They are now incorporated into the PRR-East v2 route without any changes.

Something else is wrong here.

No, the error means precisely what I told you above. If the signals are 100% good in MSTS/OR then it may be a TSRE sigscr bug.
Maybe letter case in the names between .W file and sigscr file doesn't match?

[Vince]

No, the error means precisely what I told you above. If the signals are 100% good in MSTS/OR then it may be a TSRE sigscr bug.
Maybe letter case in the names between .W file and sigscr file doesn't match?

A case mismatch . . . well there's a new one!
Your previous versions didn't seem to have a problem with up/low case mismatch. Why now?

I will check but the problem is as I stated; There are two TDBItems superimposed together and when selecting these items there is no way to tell what TDBItems they are because there is no properties display.

regards,

[GokuMK]

A case mismatch . . . well there's a new one!
Your previous versions didn't seem to have a problem with up/low case mismatch. Why now?

No, it always worked this way here.

I will check but the problem is as I stated; There are two TDBItems superimposed together and when selecting these items there is no way to tell what TDBItems they are because there is no properties display.

No, there is properties window for tdbitem.

[Vince]

Object Panel Signal List Missing

[1]No, it always worked this way here.
[2]No, there is properties window for tdbitem.

1. Okay but never had problems/errors previously. Assume new error routine does look for case mismatch?
2. You got me there. Never noticed.

But a more pressing problem has surfaced: No more signals in Object Menu.

I decided to take on fixing some signal errors. These are/were the signals that I spoke of with the superimposed TDBItem black cubes (two were THREE superimposed black cubes each!

I Jumped to the location and by keeping the Properties display off was able to delete the four signals listed in the new Error Report panel. There were, after deleting the signals (red pyramid & signal shape) approx 8! black cubes waiting for deletion. I deleted them all.(thank you for that)
Now had a clean gantry to replace the four signals I deleted.
I went to the Object menu, selected [Signals] and . . . no signals listed at all! Speedpost and Milepost looked okay but no signals.

I reloaded TSRE5_v0.697.exe, selected Signals and all were there. I replaced the ones I had deleted and all looked good.
Sorry to be bringer of bad news.
Take your time, there's no hurry as I can use the new 698 ver. to flesh out the errors and the 697 ver. to replace any signals I remove.

regards,

[GokuMK]

I went to the Object menu, selected [Signals] and . . . no signals listed at all! Speedpost and Milepost looked okay but no signals.

So, now you know why TSRE can't find SignalShape and reports signal errors. There is a problem with loading sigscr file.
In .698 there was a change in loading sigscr file to fix this bug:

http://www.onrails.eu/viewtopic.php?f=7&t=156

But maybe it caused another. You have to send me your sigscr file.

[Vince]

The signals work fine in version .697 . . . In .698 no signals show in the objects Menu.

Here's a link my DropBox with the signal files.

https://www.dropbox.com/sh/92m2qi803ky5k58/AADWGX6WFlarPu7NNhE4UPRWa?dl=0

Thanks for your attention.
regards,