Log In
Register Now!
Help
?
Page 1 of 1
public class TracksideCamera : LookAtCamera
aka Camera Trackside
Rate Topic:
#1
- Foreman Of Engines
-
- Group: Status: Contributing Member
- Posts: 982
- Joined: 31-May 10
- Gender:Male
-
Country:
Posted 18 June 2011 - 11:20 AM
#2
- Owner Emeritus and Admin
-
- Group: ET Admin
- Posts: 15,350
- Joined: 11-January 04
- Gender:Male
- Location:United States
- Simulator:Open Rails
-
Country:
Posted 18 June 2011 - 11:51 AM
Interesting analysis here. IMO it is good that people can read the OR source code and comment like this. Thanks!
#3
- Open Rails Developer
-
- Group: Status: Elite Member
- Posts: 5,491
- Joined: 30-June 10
- Gender:Not Telling
- Simulator:Open Rails
-
Country:
Posted 18 June 2011 - 03:11 PM
Eldorado.Railroad, on 18 June 2011 - 11:20 AM, said:
A rather careful search of the code leads me to beleive that the limit of 12 is based on how many car's explicit braking information can be displayed in the HUD.
This is completely incorrect; it has nothing whatsoever to do with the HUD display.
Eldorado.Railroad, on 18 June 2011 - 11:20 AM, said:
If it is not the priority of the OR team to do anything with trackside camera in any forseeable future release could the values of
MaximumDistance and the "Max consist length for the explicit braking information" (sorry, I had found what the variable name was some weeks back, but I lost it) be allowed to be startup parameters for runactivity.exe?
MaximumDistance and the "Max consist length for the explicit braking information" (sorry, I had found what the variable name was some weeks back, but I lost it) be allowed to be startup parameters for runactivity.exe?
You've really worded this post badly but if what you're asking for is the trackside camera to stay until the whole train has gone by, this is a fixed issue in current development versions (and you should really have just asked that directly).
Page 1 of 1