v21.07.04 Discussion Thread
-
Unfortunately, no externally reportable progress.
We have ascertained the wheelbase is reproducing what is sent by the sim and not adding artefacts by itself.
For reasons we are yet to identify, GTL sends the "force on" command on collision events over a certain threshold but does not send the corresponding "force off" command to end that specific instance.
This leaves the wheelbase playing the force until the next instance on that specific force channel (there are multiple different channels) triggers. This instance & subsequent instances below the threshold are started & stopped as expected.
All other channels also start & stop as expectedTo further understand why this is occurring within GTL, communication traces between sim & wheelbase are being captured, filtered and manually examined.
With 120,000 entries per 60 second sample to process, we unfortunately do not have an estimate for when this will yield actionable results. -
As the firmware update occurs over the shared USB bus, we err on the side of caution and keep the wheelbase in "Firmware Loader" mode if every checkpoint in the update process is not successfully reached.
As you've already discovered, re-running the installer will complete the firmware update.
-
@sim-plicity-dev Perfectly understood what you say, when I receibe similar impact it gets the info of the new one.
The point is: why this issue doesnt happens with the other wheelbases that I have test on GTL? ...
ty -
Updated and had trouble connecting wheel needing to restart software and losing connection with rF2 mod game.
Re-ran the installer and all seems good now. Odd as installer didn’t show any errors etc only that connection was an issue.Just for feedback in case it happens elsewhere
-
@sim-plicity-dev The point is: why this issue doesnt happens with the other wheelbases that I have test on GTL? ...
That wasnt a rethoric question.
I really would like to know if possible. I have try Lgtech Fntec Thrstmaster, all of them work, and they receibe the same "force on" info but they dont get stuck waiting for a "force off".
Its been a lot of time since that tests...Thank you
-
Historically (pre 2013), sim titles have varied in the their level of support for DirectInput (DI) FFB as the major manufacturers did not utilise this in their devices. Logitech, Thrustmaster & Fanatec each implement FFB though a custom protocol which each title separately integrated.
With the rise of Direct Drive wheels using DirectInput based FFB (SimSteering, Accuforce, MMOS IONI, SC1 etc) support has improved within the titles that are continuously developed.
RaceRoom Racing Experience is an example, its FFB was unusable on a DI DD wheel circa 2016 but updates to the title changed the behaviour.F1 2016 would crash after 2 corners with a DI DD wheel but by F1 2018 these issues were ironed out within the title
Our initial FFB implementation (Sim Mode) was aimed at squeezing out maximum FFB resolution from the most popular sim titles.
"Game Mode" was introduced as a stripped down implementation that would run on titles outside our original core focus. It provides a 14-bit data interface rather than the 16-bit interface provided by "Sim Mode".
It is entirely possible that a lower resolution interface would widen the compatibility pool further but that is very much a background task at the moment -
@sim-plicity-dev So thats why my previous MMOS didnt have any problems with it. So 12-bit (or less) resolution shouldnt have problems. Thats why Fnatec DD doesnt have that problem? its works in less bits than Sim-plicity?
As you say, a implementation of a less-bit data system could be nice. At the moment I have a button in my wheel as alt+F to restart the ffb in the middle of the race after an impact (tracks like Macau are horrible to drive with this error...)
-
@sim-plicity-dev Hello, i bought SW30 and i'm new on this forum.
Please guide me, what "Base Driver Package" and what "SW30 Firmware version" I must install for SW30?
What I must install first, Base Driver Package or Firmware version?
When must make an update to firmware or base driver package I must uninstall previous version installed, and then install updated version of firmware and base driver package?
Thank you! -
The Base Driver Package is the same for all wheelbases & firmware versions. It needs to be installed before the firmware package as it prepares your PC for the firmware installer.
It only needs to be installed once and should not be uninstalled.
Once the Base Package is installed, the SW30 firmware package can be installed.
For your first installation (when your wheelbase is delivered), you will run the installer with the wheelbase disconnected as the wheelbase ships with firmware pre-installed. The installer thus only needs to install the corresponding desktop software on your PC.Subsequent upgrades will be done with the wheelbase connected so the firmware and desktop software components can be upgraded.
Previous versions do not need to be uninstalled.
Your SW30 will ship with the latest Stable firmware version v21.02.07 and the required software is
Base Driver Package
Wheel Firmware & Configuration Tool v21.02.07 -
@sim-plicity-dev Thank you so much for your kindness and promt answer.
