speedometer (pointer) NewYear_MG 64.1
#2
Posted 04 June 2020 - 12:41 PM
Can you attach the logfile? Is that cab a free download?
#3
Posted 04 June 2020 - 03:17 PM
I also have had disappearing needles , but only in 3D cabs if I back away too far from the gauges .
#4
Posted 04 June 2020 - 11:21 PM
Csantucci, on 04 June 2020 - 12:41 PM, said:
Can you attach the logfile? Is that cab a free download?
The log file is attached as an attachment.
Funnily enough, the consist have 2 equal locomotives (same cabin) at the rear, which work if you move via Ctr-E.
So am comparing even further ...... (error in log are rear locomotives ...)
Cabview can be downloaded from: https://or.trainsim.pl/sm42/
I look even further ....
#5
Posted 05 June 2020 - 01:02 AM
#6
Posted 05 June 2020 - 08:26 AM
I don't have yet downloaded the cab, but I see that in file PKP_SM42-848_OR.eng.goed the Controllers section and the VigilanceMonitor block is duplicated, which for sure should be corrected.
Cab and loco downloaded: the needle disappears because speed goes to NaN.
The behaviour is the same in the latest available unstable release, that is U2020.06.02 0706. So it's not related to OR NewYear MG.
Cab and loco downloaded: the needle disappears because speed goes to NaN.
The behaviour is the same in the latest available unstable release, that is U2020.06.02 0706. So it's not related to OR NewYear MG.
#7
Posted 05 June 2020 - 11:18 PM
Csantucci, on 05 June 2020 - 08:26 AM, said:
I don't have yet downloaded the cab, but I see that in file PKP_SM42-848_OR.eng.goed the Controllers section and the VigilanceMonitor block is duplicated, which for sure should be corrected.
Cab and loco downloaded: the needle disappears because speed goes to NaN.
The behaviour is the same in the latest available unstable release, that is U2020.06.02 0706. So it's not related to OR NewYear MG.
Cab and loco downloaded: the needle disappears because speed goes to NaN.
The behaviour is the same in the latest available unstable release, that is U2020.06.02 0706. So it's not related to OR NewYear MG.
As I mentioned in the readmy, the duplicated part was not the cause.
Once again I updated the .eng file "step by step" with the differences via file comparison, I now see that the "ORTSMaxTractiveForceCurves (" section is causing the error with the speedometer (pointer).
So I understand this is a known issue? (maybe not in MG, but generally in OR?)
Or is this "ORTSMaxTractiveForceCurves (" an incorrect setting? (Like, value "0" may already have max.traficforce?)
.
#8
Posted 06 June 2020 - 02:35 AM
My consist consisted with the (player) diesel locomotive + Steam locomotive + carriages + 2 diesel locomotives at the end.
It turns out that with "ORTSMaxTractiveForceCurves" in the .ENG file the diesels do not give any Power of Force at all ....... :ko2: (gives sound, etc. normal)
The steamer eventually pushed everything away ....... :) :cool3:
OK, even with only 1x diesel locomotive it has no power if "ORTSMaxTractiveForceCurves" is entered in the .ENG?
Meanwhile compared to other information, I think "ORTSMaxTractiveForceCurves" is correct?
(and still illogical that a Cab display item disappears through a .ENG setting? So Speed NAN is because a locomotive is pushed?)
Well, for the time being this part just left out ...
It turns out that with "ORTSMaxTractiveForceCurves" in the .ENG file the diesels do not give any Power of Force at all ....... :ko2: (gives sound, etc. normal)
The steamer eventually pushed everything away ....... :) :cool3:
OK, even with only 1x diesel locomotive it has no power if "ORTSMaxTractiveForceCurves" is entered in the .ENG?
Meanwhile compared to other information, I think "ORTSMaxTractiveForceCurves" is correct?
(and still illogical that a Cab display item disappears through a .ENG setting? So Speed NAN is because a locomotive is pushed?)
Well, for the time being this part just left out ...
#9
Posted 06 June 2020 - 04:02 AM
Hi,
neither I am able to move the loco; it moves only when autopiloted, and in such case speed is NaN and needle disappears. It might be that OR has changed something in the management of the ORTS specific parameters of the .eng file (ORTSMaxTractiveForceCurves or something else), and that this generates the problem. I don't think that the actual parameters in the .eng and .inc files are faulty, because they worked. I hope that steamer_ctn has a look in this.
neither I am able to move the loco; it moves only when autopiloted, and in such case speed is NaN and needle disappears. It might be that OR has changed something in the management of the ORTS specific parameters of the .eng file (ORTSMaxTractiveForceCurves or something else), and that this generates the problem. I don't think that the actual parameters in the .eng and .inc files are faulty, because they worked. I hope that steamer_ctn has a look in this.
#10
Posted 06 June 2020 - 05:47 AM
If the locomotive will not move and you are using the ORTS Engine definition, make sure the RPMs for idle and notch1 are not identical. This may be the problem.
Please see this thread: Idle&Notch1 RPM Identical
I just looked at the eng file...the RPMs have to be increasing..( for now ) please see above thread. Few rpm difference will suffice.
Please see this thread: Idle&Notch1 RPM Identical
I just looked at the eng file...the RPMs have to be increasing..( for now ) please see above thread. Few rpm difference will suffice.
ThrottleRPMTab ( 0 496 1 496 10 496 20 496 30 496etc