RailDriver/Route Riter and Donner Pass Cab Forwards

[niknak]

Hi guys, I'm getting jerkiness when running cabfwds in Donner Pass thru Open Rails with Rail Driver. So I've tried modifying the eng files to mesh with Rail Driver by using Route Riter's Rail Driver option. The trouble is Open Rails then can't find the loco when I try to resume the activity. So how do I make Open Rails see the new eng file that Route Riter has produced? I can't see any obvious changes to the new file so I would appreciate any help.

[R. Steele]

OR supports Rail Driver, so I doubt that using RouteRiters Rail Driver option would help at all. I just tried the first cab forward activity that popped up on the Donner Pass -- 1952 Storm activity -- everything works fine. Suggest posting log, perhaps the "jerkiness" is an indication of some other problem. Maybe a video problem...FPS?

[niknak]

Frame rates seem unaffected at around 50fps or so. Log attached but I can't see anything obvious on it. Also if I disconnect Rail Driver then all runs smoothly.

[R. Steele]

I'm not a Rail Driver expert, nor a steam guy...nothing in the log specifically points to Rail Driver, try posting in the Rail Driver forum, or be patient and maybe someone with more knowledge than myself will respond...sorry could not be of more assistance

[niknak]

That's fine Gerry, thanks for your response.

[Vince]

A few things I noticed in the log:
1. Dynamic shadows off but Shadow all shapes on. I'm not sure this is a conflict.

2. Performance tuner on. I've seen this cause problems. Try running with it off.

3. Vertical Sync. My thinking on this is my monitor can only display at 60Hz so I let the monitor control the video output putting a stop to the video logic attempting to stuff 200+ fps into a monitor that only can accept 60Hz video!
All the other 140 attempts have to be rejected. That takes processing time. May impact the vid processor.

regards,

[niknak]

Thanks for your input Vince. Tried your recommendations above but no change. My own thoughts are that I need to calibrate the cabfwd with Rail Driver somehow but if I use Route Riter to do this then Open Rails won't recognise the amended eng file. I've posted also in the Rail Driver forum and will await developments.

[slipperman]

Hi niknak,
I don't have RailDriver, so these are only my thoughts and suggestions

If you have v2 of the NVIDIA GT 710 with GDDR5 memory, that should be fine, but if you're using one of the old ones with GDDR3 memory, it might be the reason for the 'jerkiness' you're seeing.

You posted "Open Rails then can't find the loco when I try to resume the activity.". This would imply that you started the activity with an unmodified .eng file, then suspended the activity, used Route_Riter to modify the file, then attempted to resume the activity. If that's so, I don't think it's in the rules!! It would mean that data saved from the 'old' .eng file is no longer valid.

If the above doesn't reflect what actually happened, maybe you could zip up the modified .eng file and attach it.

Cheers,
Ged

[niknak]

Hi Ged. not sure what version of the graphics card I have. Tried various searches but none mention the GDDR rate and the fact that all is ok if I switch off Rail Driver makes me think it's not a graphics issue. Once I've amended the eng files, if I then go into Open Rails and choose "explore" activity the amended loco doesn't show up at all in the list of available locos, so it's not that I'm attempting to restart an activity with an altered eng file. I've posted in the Rail Driver forum and hope for help with calibrating the Cab Forwards if that's what the problem is.

[slipperman]

Hi niknak,
Thanks, mate
That's put me right on at least one thing, anyway!

As you're posting in an Open Rails Forum, I'll assume that you can't check the .eng file by running MSTS. That being so, and as OR can't 'see' the loco, it would imply there's an error in the .eng file. That being so, I suggest you zip it and post it here so that many pairs of eyes can peruse it!! Alternatively, tell us from where the loco can be obtained, together with its folder name and .eng file name.

I've just done a simple test with the default Class50 and applied the R_R RailDriver modifications (Modify Diesel .eng for RailDriver) and it shows OK in both MSTS and OR. Which version of Route_Riter are you using, and which RailDriver option did you select? Does the existing .eng file have any Open Rails-specific commands? If so, it might be confusing R_R.

Cheers,
Ged

[niknak]

Attached are the 2 eng files that Route Riter modified after I clicked on "Modify steam engine for Rail Driver." These are the files that Open Rails doesn't now recognise. I'm using RR version 7.8 and afaik there are no Open Rails specific commands in the files, just changes to sound and smoke. I should add that the jerkiness occurs only after I've been running the activity for 15-20 mins or so and using Rail Driver only.

[slipperman]

Hi niknak,
Thank you
Each of the .eng files you sent is missing a close bracket at the end. That will prevent the loco from showing up in MSTS and Open Rails, but it's not the only problem!

I'm using Mike Simpson's last version of Route_Riter (7.6.26), and that creates the same 'no-show' loco. The reason is that the Cabview and HeadOut lines have been removed while a great many additional brake parameters have been added - which I'm not in a position to validate!!

I suggest you add the missing final close bracket to each .eng file and add the following lines to the 'front' file :

CabView ( CabF.cvf )
HeadOut ( 1.85 3.7 4.40 )

You will probably find these lines at about line 467 in the backed up original file (*.enx): I placed them at about line 390 in the modified file, but anywhere in the Engine section should do.


As the 'jerkiness' doesn't start until 15-20 minutes into a run, it sounds as if it may be a memory, or heat-related, problem.

Cheers,
Ged

[R. Steele]

NikNak -- Open Rails has a specific calibration procedure for Rail Driver --- It can be found in the "Installation_Guide" - which is located in the "documentation" folder in the latest stable version of Open Rails ( version 1.3 ) -- if you cannot find it...PM me.

You can also download the Rail Driver versions of OR ( they can be found in a thread at Elvas Tower ) the program has an actual Rail Driver Tab that also contains a calibration routine that is quite effective.

At the moment I cannot find the link, I don't know if the raildriver tab is included in the Monogame or Unstable versions...I assume that it will be folded in once the changeover to Monogame has been complete.

...and Ged jogged my memory about the CabForwards...there was a thread here ( or at ET ) concerning all the corrections to the engine files...I had installed those.

[niknak]

Hi niknak,
Thank you
Each of the .eng files you sent is missing a close bracket at the end. That will prevent the loco from showing up in MSTS and Open Rails, but it's not the only problem!

I'm using Mike Simpson's last version of Route_Riter (7.6.26), and that creates the same 'no-show' loco. The reason is that the Cabview and HeadOut lines have been removed while a great many additional brake parameters have been added - which I'm not in a position to validate!!

I suggest you add the missing final close bracket to each .eng file and add the following lines to the 'front' file :

CabView ( CabF.cvf )
HeadOut ( 1.85 3.7 4.40 )

You will probably find these lines at about line 467 in the backed up original file (*.enx): I placed them at about line 390 in the modified file, but anywhere in the Engine section should do.


As the 'jerkiness' doesn't start until 15-20 minutes into a run, it sounds as if it may be a memory, or heat-related, problem.

Cheers,
Ged

Hi Ged and thanks for the tips. I added the missing cabview (why did I not notice that!) which has restored the loco to the Open Rails roster but you were right to mention the changes to the brake files as I now have no brakes when I run the loco! (the end bracket you mentioned was there, but right at the bottom of the file.)As all runs smoothly if I turn off Rail Driver I don't think it's memory or heat related somehow. Maybe Rail Driver just has a problem with Cab Forward locos - The logfile shows " Warning: Steam engine type parameter not formally defined. Simple locomotive has been assumed" Which the Cab Forward definitely isn't!

[slipperman]

Hi niknak,
I think the "Steam engine type" is an OR-specific parameter - running the Scotsman gives the same message.

Also, the Route_Riter option seems to have really messed up the .eng file!

As well as having no brakes, mine has no throttle/regulator!! I'm having a close look at the original and modified files, and will come back.

Cheers,
Ged