[Weter]

Quote

Did TSRE ever work for you?

It crashes after pressing the green button "LOAD"
or what do You mean exactly?

Quote

Do you have OpenGL installed on your system?

I think, yes.

[vince]

Goku, on 06 December 2020 - 01:06 AM, said:

Yes, it is fixed. Now TSRE checks if referenced track items belong to removed object before removing them. Also you have advanced track database error detection, so even if you encounter this kind of a problem, it is easy to find and fix. I think that TSRE5_v0.699.1 detects all TrItem related problems in Track Database.

Thanks very much Goku.

Best regards,
vince

[Szilard]

Hi!

I discovered an annoying bug in TSRE5 when laying certain kind of shapes with inclination, best example is A1tDblSlip6_3d. Sectionidx with vector offset (x, y, z) different than null counted incorrectly in tdb as shape inclination would be zero:

 TSRE5 2020-12-25 093533.jpg (82.99K)
Number of downloads: 8

Merry Christmas for everyone and thank you Goku for your help in advance, Szilard

[Genma Saotome]

I had a similar problem with a tsection entry that placed the object above it's origin point. Trying to add additional instances of the shape saw each one placed higher than the one before it. I reported it on Goku's board and to date have not seen a reply.

What happens when you place successive copies of this shape?

[eric from trainsim]

Interesting. I've been seeing similar "off by a smidgen" placements as I'm moving track on an existing route. Despite taking both sections out of the TDB and adding the first manually, the second will still stay off by about 0.2m (and no, there aren't any other active TDB lines nearby).

Next time I'll screenshot it.

Closing the editor and returning to that spot makes the issue go away.

[Szilard]

Genma Saotome, on 25 December 2020 - 05:03 PM, said:

I had a similar problem with a tsection entry that placed the object above it's origin point. Trying to add additional instances of the shape saw each one placed higher than the one before it. I reported it on Goku's board and to date have not seen a reply.

What happens when you place successive copies of this shape?

Additional instance is adhered to one of section on the ground, TSRE doesn't put them above each other. The placement is fine, only section computing from Tsection to tdb is incorrect in the formerly detailed case.

[Genma Saotome]

Szilard, on 28 December 2020 - 01:49 AM, said:

Additional instance is adhered to one of section on the ground, TSRE doesn't put them above each other. The placement is fine, only section computing from Tsection to tdb is incorrect in the formerly detailed case.

No, the placement is not fine.
 TSRE Bug.jpg (126.69K)
Number of downloads: 3

The full report at Goku's site is here:
http://www.onrails.e...c.php?f=7&t=190


I think this might be the same problem as reported a few posts ago.

[Szilard]

Genma Saotome, on 28 December 2020 - 11:35 AM, said:

No, the placement is not fine.
TSRE Bug.jpg

The full report at Goku's site is here:
http://www.onrails.e...c.php?f=7&t=190


I think this might be the same problem as reported a few posts ago.

I'm not sure it is the same problem. My issue occurs only at inclined shapes contained sections with non zero vector offset:

TrackShape ( 22021
FileName ( A1tDblSlip6_3d.s )
NumPaths ( 6 )
ClearanceDist ( 35 )
SectionIdx ( 1 0 0 0 0 28868 )
SectionIdx ( 1 0 0 12.471 0 28869 )
SectionIdx ( 1 0 0 25.529 0 28868 )
SectionIdx ( 1 1.6512 0 0.0912 -6.32 28868 )
SectionIdx ( 1 0.2784 0 12.4864 -6.32 28869 )
SectionIdx ( 1 -1.159 0 25.4649 -6.32 28868 )
CrossoverShape ( )
XoverPts ( 1
XoverPt ( 0 0 15 )
)
)

Red lines are counted wrong in tdb, since TSRE does not care inclination. Placing the same object with zero gradient looks fine.

[PTrains87]

Hello everyone!
I have a request/issue with TSRE5 and the gantry. First of all a question about the visibility of the wire inside the editor, is just me or is not possible to see it through TSRE5?
I think if this is a feature missing it would be a great addition to this editor since the placement of the gantry is a major part of the route building, which means that having the wire visible would be handy to place the gantry correctly.

Secondly, and this is I think an issue, is also in relation to the wire but the height of it. In TSRE5 > Route > Edit Route Settings, I can choose the wire height with a step of 0.50 (meter I guess), so I put in there 5.50 and I make myself sure to have saved all the work done. However, when I reload the tool and consequently the Route modified, I can see in TSRE5 the wire height has been changed to 5.00. I've tried again to put the correct value but nothing, TSRE5 revert it back to 5.00. Is this a bug or it works as intendend? And if so, how I should put the correct wire height for countries (like Italy for example) that has an average wire height of 5.50?

Thanks for any answer here!

[eric from trainsim]

There's a manual workaround you can try here.

If you open up the route.trk file, you should see two lines which are specific to electric routes:

	Electrified ( 00000001 )
	OverheadWireHeight ( 3000 )

Try setting the OverheadWireHeight to 5.5 in your TRK file and saving (not by using TSRE Settings).

That value gets converted to both a double and a float by ORTS, so it should be possible to save a decimal value here without causing problems.

I did that manually in one of my routes and it seems to be displaying correctly in ORTS.

As for TSRE.... My guess is that Goku is treating this as an integer value, and dropping the decimal places. That should be a simple fix I'd think.

In the editor, it looks like the wire is rendering, but at 4m vs. 5 or 5.5 -- it's a thin grey line about 2m above the yellow TDB/TSection line.

[Weter]

Hello.
What was it be?
(the ending of log-file of the first run)

[E] libpng warning: iCCP: known incorrect sRGB profile
[E] setGeometry: Unable to set geometry 18x16+640+275 on QWidgetWindow/'QLabelClassWindow'. Resulting geometry:  148x16+640+275 (frame: 9, 38, 9, 9, custom margin: 0, 0, 0, 0, minimum size: 0x0, maximum size: 16777215x16777215).
[I] #Templates - undefined token:  "version"
[E] setGeometry: Unable to set geometry 18x16+640+275 on QWidgetWindow/'QLabelClassWindow'. Resulting geometry:  148x16+640+275 (frame: 9, 38, 9, 9, custom margin: 0, 0, 0, 0, minimum size: 0x0, maximum size: 16777215x16777215).
[E] setGeometry: Unable to set geometry 18x16+640+275 on QWidgetWindow/'QLabelClassWindow'. Resulting geometry:  148x16+640+275 (frame: 9, 38, 9, 9, custom margin: 0, 0, 0, 0, minimum size: 0x0, maximum size: 16777215x16777215).
[E] libpng warning: iCCP: known incorrect sRGB profile