Rob,
the fix that César is proposing to solve the wheel problem (PR#858) is very simple (one line added, one line modified and one line removed). You might apply such changes to your version of OR, and see if the problems are gone.
Weird Graphics Problem
#32
Posted 05 August 2023 - 06:38 PM
To add to Mick Clarke`s earlier observation. I find that new reverse points created in trackviewer do not appear in the player track monitor and neither do AI units respond.. Timetable mode. A simple plain track path with reverse point. Test activity test_brock can be found in New Forest Route Github player timetable. U2023.08.05-2137
SIMISA@@@@@@@@@@JINX0P0t______
Serial ( 1 )
TrackPDPs (
TrackPDP ( -6142 14890 642.332 28.051 678.731 1 0 )
TrackPDP ( -6142 14890 597.094 28.208 500.230 1 1 )
TrackPDP ( -6142 14890 647.383 27.920 698.663 1 0 )
)
TrackPath (
TrPathName ( "test_brock" )
TrPathFlags ( 00000000 )
Name ( "test_brock" )
TrPathStart ( "Brockenhurst Headshunt" )
TrPathEnd ( "Brockenhurst Headshunt" )
TrPathNodes ( 3
TrPathNode ( 00000000 1 4294967295 0 )
TrPathNode ( 00000001 2 4294967295 1 )
TrPathNode ( 00000000 4294967295 4294967295 2 )
)
)
SIMISA@@@@@@@@@@JINX0P0t______
Serial ( 1 )
TrackPDPs (
TrackPDP ( -6142 14890 642.332 28.051 678.731 1 0 )
TrackPDP ( -6142 14890 597.094 28.208 500.230 1 1 )
TrackPDP ( -6142 14890 647.383 27.920 698.663 1 0 )
)
TrackPath (
TrPathName ( "test_brock" )
TrPathFlags ( 00000000 )
Name ( "test_brock" )
TrPathStart ( "Brockenhurst Headshunt" )
TrPathEnd ( "Brockenhurst Headshunt" )
TrPathNodes ( 3
TrPathNode ( 00000000 1 4294967295 0 )
TrPathNode ( 00000001 2 4294967295 1 )
TrPathNode ( 00000000 4294967295 4294967295 2 )
)
)
#33
Posted 06 August 2023 - 04:17 AM
rickloader, on 05 August 2023 - 06:38 PM, said:
To add to Mick Clarke`s earlier observation. I find that new reverse points created in trackviewer do not appear in the player track monitor and neither do AI units respond.. Timetable mode. A simple plain track path with reverse point. Test activity test_brock can be found in New Forest Route Github player timetable. U2023.08.05-2137
That's not a problem with the trackviewer but with the path itself.
Starting point, reversal point and end point of path are all within the same section of track. In this situation in timetable mode, the system finds that the train is already at the final location and therefor decides that train has nothing to do and nowhere to go. There needs to be at least one junction node somewhere between start point and either reversal point or end point for the path to work.
Regards,
Rob Roeterdink
#34
Posted 06 August 2023 - 04:21 AM
Csantucci, on 04 August 2023 - 11:05 PM, said:
Rob,
the fix that César is proposing to solve the wheel problem (PR#858) is very simple (one line added, one line modified and one line removed). You might apply such changes to your version of OR, and see if the problems are gone.
the fix that César is proposing to solve the wheel problem (PR#858) is very simple (one line added, one line modified and one line removed). You might apply such changes to your version of OR, and see if the problems are gone.
Yes, thanks, this all is indeed the same problem.
I am surprised that this issue was so easily dismissed as not being relevant to diesel engines and only applied to steam engines. These code changes are in common modules, and so it stands to reason that any type of engine could be affected by this error.
Regards,
Rob Roeterdink
#35
Posted 06 August 2023 - 05:05 AM
More precisely, it affected wheels animated in the shape file. This is typically the case for steam locomotives, while for diesel and electric engines wheels are animated by OR. However, it is possible to have shape animations for any kind of locomotive.
#36
Posted 06 August 2023 - 06:53 AM
cesarbl, on 06 August 2023 - 05:05 AM, said:
More precisely, it affected wheels animated in the shape file. This is typically the case for steam locomotives, while for diesel and electric engines wheels are animated by OR. However, it is possible to have shape animations for any kind of locomotive.
Hello.
This is my old grief. There are two-axle diesel motorcars where only one axle is driven. A1 axis arrangement. Unfortunately, the non-driven shaft also rotates. I converted one as a trial before, by canceling the animation of the corresponding axis. I'm sorry, but I'm writing like an old railway axle, but of course I mean Wheel or Wheels.
I read here how there is a difference between the two names, but I did not understand exactly.
Sincerely, Laci1959
#37
Posted 06 August 2023 - 06:59 AM
Sorry I made the test path too simple. I rebuilt it with some junction nodes and the reverse point now shows . I made several saves of ok paths that became faulty in recent versions and the missing reverse points persisted. This most recent unstable does save correctly with the reverse points operating.
I regret mentioning this now, but then again I wasted several hours chasing a real problem, what ever it was!
Rick
I regret mentioning this now, but then again I wasted several hours chasing a real problem, what ever it was!
Rick
#38
Posted 08 August 2023 - 11:05 PM
Quote
Would you have any insights also into the 3rd issue regarding the net positive wheel and crankshaft inertial forces at high speeds?
Peter uploaded a fix for this some days ago. Is the problem solved with it?