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)
-
OpenRailsLog.txt (14.25K)
Number of downloads: 240
This post has been edited by yitianetie56: 12 March 2018 - 09:16 AM