search

openrails / test-launchpad-bugs

TEST repository for Launchpad bug migration exploration
0 stars 0 forks source link

[BUG 1609442] Digital Cabsignal MSTS/ORTS problem #1761

Closed twpol closed 8 years ago

twpol commented 8 years ago

Imported from https://bugs.launchpad.net/bugs/1609442

Property Value
Reported by Stijn (stijndecaluwe)
Date reported Wed, 03 Aug 2016 14:38:50 GMT

Hello,

I'am a cabviewcreator, and some cabviews have a digitalcabviewsignal.

Bud if the train have a max. velocity of 200 km/h i give in this piece of cabview this data:

    Digital (
        Type ( SPEEDLIM_DISPLAY DIGITAL )
        Position ( 338 290 32 32 )
        ScaleRange ( 0 200 )
        Accuracy ( 0 )
        AccuracySwitch ( 0 )
        LeadingZeros ( 0 )
        Justification ( 3 )
        PositiveColour ( 1
            ControlColour ( 255 0 0 )
        )
        NegativeColour ( 0 )
        DecreaseColour ( 0 )
        Units ( KM_PER_HOUR )
    )

If the linespeedlimit is 300 km/h in MSTS, the digital speedlimit gives max. 200, that is correct.

But in Openrails he gives Always the speedlimit of the line :-(.

I hope that this bug can be fix please.

twpol commented 8 years ago

Imported from https://bugs.launchpad.net/or/+bug/1609442/comments/1

Property Value
Posted by Stijn (stijndecaluwe)
Date posted Wed, 03 Aug 2016 14:38:50 GMT
twpol commented 8 years ago

Imported from https://bugs.launchpad.net/or/+bug/1609442/comments/2

Property Value
Posted by Cédric GNIEWEK (sharpeserana)
Date posted Mon, 08 Aug 2016 01:00:16 GMT

Works correctly on my side (line limitation 300 km/h and train limitation 200 km/h) with the latest version of Open Rails.

Please attach your log file.

twpol commented 8 years ago

Imported from https://bugs.launchpad.net/or/+bug/1609442/comments/3

Property Value
Posted by Stijn (stijndecaluwe)
Date posted Mon, 15 Aug 2016 14:28:26 GMT

I have test and have send a email for give my results, bud i'am not chur of the email is be recieved.

twpol commented 8 years ago

Imported from https://bugs.launchpad.net/or/+bug/1609442/comments/4

Property Value
Posted by Stijn (stijndecaluwe)
Date posted Mon, 15 Aug 2016 14:35:57 GMT

Hello,

After my work i have tested on the last workversion (X3602)

This is result: (Digital cabsignal stay on 300km/h too), in CVF file is 200 km/h as max given.

Bud fort he digital component, you see difference at ORTS & MSTS, bud maybe for us cabvieweditors it is handy that we can give in the CVF file a lettertype hight.

MSTS: 200 km/h when linevoltage is 300 km/h exactly what i have writ in the CVF file of this cabview. This train have max. of 200 km/h, if this train drive on HSL (TBL) than can it display not higher a digital number than 200.

Printscreens in this message are gone.

Greetz,

Stijn

twpol commented 8 years ago

Imported from https://bugs.launchpad.net/or/+bug/1609442/comments/5

Property Value
Posted by Cédric GNIEWEK (sharpeserana)
Date posted Mon, 15 Aug 2016 18:40:24 GMT

Hello,

What is the speed limit defined in the consist file ?

twpol commented 8 years ago

Imported from https://bugs.launchpad.net/or/+bug/1609442/comments/6

Property Value
Posted by Stijn (stijndecaluwe)
Date posted Mon, 15 Aug 2016 19:56:16 GMT

Hello,

Consistfiledata:

    Serial ( 1 )
    MaxVelocity ( 400.0 1.00000 )    => It stay on 400 ???  
    NextWagonUID ( 13 )
    Durability ( 1.00000 )

Bud must i change the 400 to 200 now, or are this values Mph ?

Greetz,

Stijn

twpol commented 8 years ago

Imported from https://bugs.launchpad.net/or/+bug/1609442/comments/7

Property Value
Posted by Cédric GNIEWEK (sharpeserana)
Date posted Mon, 15 Aug 2016 22:19:44 GMT

Ok, the speed limit of the next signal (or speed post) is the minimum between the signal (or speed post) speed limit and the maximum speed of the train. Then, this calculated value goes through the TCS script for the Overspeed Monitoring. Then, we get the value from the TCS script to show the value on the cab.

The maximum speed of the train is given by the MaxVelocity value in the consist file. Your current value is 400 m/s... that's a bit high. ^^

That's why it doesn't show the correct speed limit. The correct value is 55.56 m/s (for 200 km/h).

twpol commented 8 years ago

Imported from https://bugs.launchpad.net/or/+bug/1609442/comments/8

Property Value
Posted by Stijn (stijndecaluwe)
Date posted Tue, 16 Aug 2016 23:16:40 GMT

Hello,

After change that 400 to 55.56 in the .con file the cabdisplay and trackmonitor give 200 km/h for maximumspeed, the signals give 300 km/h, that is correct.

Than is it good see that the .con files have the right data for communicate.

Bud in the ENG file, WAG file you have a max velocity command to, read ORTS this command to for this? or onley the .con max velocity

Problem with youre tip is solved, it is no a bug bud a wrong programmation of builder of consist. Thanks!

twpol commented 8 years ago

Imported from https://bugs.launchpad.net/or/+bug/1609442/comments/9

Property Value
Posted by Cédric GNIEWEK (sharpeserana)
Date posted Thu, 18 Aug 2016 03:26:46 GMT

Indeed, OR only takes into account the MaxVelocity value in the consist file.

twpol commented 8 years ago

Imported from https://bugs.launchpad.net/or/+bug/1609442/comments/10

Property Value
Posted by Cédric GNIEWEK (sharpeserana)
Date posted Thu, 18 Aug 2016 03:32:41 GMT

By the way, it seems coherent that the speed of the train is set in the consist file because the speed limit depends not only on the speed limit of each vehicle but also on the total mass of the train. For example, in France, in a freight train, if the mass is very high or if the braked mass is low, the category of the train will be set to MA80 (= freight 80 km/h) instead of MA100 (= freight 100 km/h).

Since this is not a bug of the simulator, the bug report status is now "Invalid".