Paul Jeffrey
Premium
Hot on the heels of last weeks release, Image Space Incorporated have made available version 1084 of their racing simulator rFactor 2.
Build 1084 brings some essential fixes to the previous build 1080 release, the most notable of which is a proposed driver fix for Thrustmaster driver and a fix for the Logitech G920 pedal issue.
Additional work has been undertaken by the studio to remove a issue causing users whom attempt to download missing components from a password-less dedicated server receiving the "invalid password" message on the server.
With recent criticism from some of the more vocal elements of the community regarding the relatively slow pace of development for rFactor 2, it is very encouraging to see ISI's quick reaction to the recent issues with the release of this latest patch.
Build notes:
FEATURES:
- Stopped overwriting your own Unsportsmanslike Driving multiplayer setting when you joined a server (should only affect the current setting). This would only matter if you used the same Player.JSON for both servers and clients.
- Fixed sun occlusion bug in showroom.
- Adjusted particle params for rain spray.
- Removed error msg from Mas2.
- Fix for steam launcher getting "Password invalid" when attempting to download missing components from a password-less dedicated server.
- Workaround for lag in options when using Thrustmaster drivers 2016_TTRS_1.
- Rearranged throttle/brake/clutch pedal mappings for Logitech G920 because they will be rearranged with the next Logitech driver/firmware release (which are in Beta as of this writing). If any users continue to use the previous Logitech drivers, they will need to re-map the pedals after loading the Logitech G920 profile.
- Attempt to prevent Knockout Qualifying plugin from overwriting manual grid edits.
- Lost wheel intermittent repair after driver change, possibly more likely with higher damage percent set. 'Normal' damage repairs function as intended.
- There are still some issues with various security suites that ISI are not in control of. Depending on what software you use, you will need to find a workaround based on how it reacts or what it blocks. ISI would be grateful to see these false reports passed onto the developers of those suites so that they can whitelist the software.
Much like buses, one comes along then straight after another arrives... are you using 1084 yet? What do you think? How have you found the workaround for the new 2016_TTRS_1 driver from Thrustmaster and a fix for the Logitech G920 pedals? Let us know in the comments section below!
Image credit: Remik - F1RFT 2013 mod
Last edited: