Elvas Tower: Unusual issue using Raidlriver with Open Rails (stable 1.2 and testing X4081) - Elvas Tower

Jump to content

Page 1 of 1
  • You cannot start a new topic
  • You cannot reply to this topic

Unusual issue using Raidlriver with Open Rails (stable 1.2 and testing X4081)

#1 User is offline   yitianetie56 

  • Apprentice
  • Group: Switchman
  • Posts: 3
  • Joined: 12-March 18
  • Gender:Male
  • Simulator:Open Rails
  • Country:

Posted 12 March 2018 - 09:13 AM

Hi,

I have recently tested Raildriver controller cab with Open Rails stable (last 1.2) and testing (X4081). After reading with attention the review of RailDriver on Open Rails website, and after calibrating several times the cab controller (an put the ModernCalibration file in MSTS main folder), I get some issues when I try to hard break (or emergency brake), or even quickly trottle, like for subways. The Framerate quickly drops from 60 fps (with adaptative vsync or 180 fps without vsync) to 12 fps, even after disabling adhesion factor (which causes wheelslipping). I have fully patched MSTS with update 1.4 and tried several routes and locos included with the vanilla version. I have attached a log with my config and the tested route (North-East corridor, USA1 with Amtrak Express). The problem similarly occurs on StAnton-Insbruck route with Gölsdorf...
However, the raildriver cab controller seems to be well calibrated because all levers run properly (I can trottle from 0 to 100% easily). But when I try to break or trottle quickly, the fps drops suddenly and I get stutterings. It is like the raildriver cannot synchronize with the speedometer of Open Rails. I have also disabled very graphic settings (antialiasing, anisotropic filtering, vsync...)
Lastly if I unplug the controller cab, the framerate does not drop anymore. I don't know where is the cause. I suspect either windows 10, Open Rails bug, or bad driver... I have sent an email to PI Engineering to explain the problem but not answer for the moment. I don't want to call them because it could be expensive as I live in France. But I will do that if necessary.

So, has somebody encountered this issue when using the RailDriver cab controller ? Would you have any solution to fix this issue ?

Best regards,
Etienne.

Attached File(s)


This post has been edited by yitianetie56: 12 March 2018 - 09:16 AM


#2 User is offline   yitianetie56 

  • Apprentice
  • Group: Switchman
  • Posts: 3
  • Joined: 12-March 18
  • Gender:Male
  • Simulator:Open Rails
  • Country:

Posted 13 March 2018 - 12:24 AM

Hi,

Maybe would you want more informations. I will just add that I have tested on differents computers, on my laptop with nvidia optimus (Open Rails works fine) and on the PC (see log file attached, which works fine too). But the stuttering still occurs in both case when hard breaking with RailDriver. It could be an electronical problem which would prevent the driver to read correctly the informations in the simulator but it would be amazing, as levers work well and are fully recognized by the calibration software.

Does anybody has an idea, or even a solution (if he/she has) ?

Best regards,
Etienne.

This post has been edited by yitianetie56: 13 March 2018 - 12:26 AM


#3 User is offline   dajones 

  • Open Rails Developer
  • Group: Active Member
  • Posts: 274
  • Joined: 27-February 08
  • Gender:Male
  • Location:Durango, CO
  • Country:

Posted 13 March 2018 - 10:06 AM

I can only guess as to what might be happening. The RailDriver is supposed to only send data to OR when something changes and it looks like the only thing that could slow down the frame rate is if the RailDriver sends data continuously. Maybe there is a hardware issue that is causing the data to bounce back and forth between two values. I don't know if there is anything that can be done about it.

Doug

#4 User is offline   Woodfyr 

  • Apprentice
  • Group: First Class
  • Posts: 38
  • Joined: 30-December 14
  • Gender:Male
  • Location:Maine
  • Simulator:Open Rails / MSTS
  • Country:

Posted 13 March 2018 - 10:43 AM

Check out the following site: http://railworksamer...php?f=29&t=3172

#5 User is offline   yitianetie56 

  • Apprentice
  • Group: Switchman
  • Posts: 3
  • Joined: 12-March 18
  • Gender:Male
  • Simulator:Open Rails
  • Country:

Posted 13 March 2018 - 03:15 PM

View PostWoodfyr, on 13 March 2018 - 10:43 AM, said:

Check out the following site: http://railworksamer...php?f=29&t=3172


Thanks for answering. Indeed, it is maybe what I thought. If it is an hardware issue, I probably should to ship back the raildriver to Aerosoft, the PI Engeneering's distributor in Europe. It is unfortunate (and not very soothing) and I don't have any certitude that the new raildriver cab control will run properly this time. It is amazing that nobody seems to not have encountered this issue. I have looked for on many forums. In the other hand, I would think about sensivity. But I don't know how to solve this. I will let a post on the raildriver official forum but specialists from PI Engeneering seem to don't know more than you...

Maybe a RDM file from somebody would not have this issue could confirm that but I really have doubt... Now, I am also waiting for an answer from Aerosoft technical support.

#6 User is offline   EricF 

  • Fireman
  • Group: Active Member
  • Posts: 159
  • Joined: 07-December 11
  • Gender:Male
  • Location:New England
  • Simulator:Open Rails / Sometimes MSTS
  • Country:

Posted 18 March 2018 - 04:36 AM

I generally use the RailDriver, and I've experienced the same drop in frame rate if the emergency brake is active -- I also get the wheel slip warning, and the frame rate drop only happens if wheel slip is being indicated while emergency braking is active.

Wasn't there an issue with the advanced adhesion model that may be connected to frame rates? I seem to remember something about that, but I'm blanking on what ever became of the issue... But there might be a connection

At any rate, I don't think it's a hardware problem -- more likely an issue linked to the very old hard-coded RailDriver programming in OR. It's kind of a leftover from earlier days.

Page 1 of 1
  • You cannot start a new topic
  • You cannot reply to this topic

1 User(s) are reading this topic
0 members, 1 guests, 0 anonymous users