@sim-plicity-dev Weird.. it works now. I tried game mode before, didn't work. Now it does ..

@sim-plicity-dev , thank you for this detailed and explicit information!

@Sim-plicity-Dev said in USB PCI-e controller not working with SW20v3 base: @frijsdijk The wheelbase heavily exercises the USB bus and will forcibly eject itself if the bus it is connected to is not sufficiently stable. As your description suggests all is fine using the motherboard ports, it would appear the PCI-E USB bus is currently below the stability threshold. Replacing your USB cable with a new Shielded cable would be a first step in raise the bus stability over the threshold. Thank you! I'll try some time (found other solutions)

@Sim-plicity-Dev , Thank you!

@Sim-plicity-Dev said in Firmware v21.10.01: We are currently aiming at end of March (dependent on the release of our new hardware platform) @Sim-plicity-Dev, Thank you!

Thanks, After reseating the plugs all seems fine again.

"Center Wheel" in the simplicity software has always worked for me even if its just a few degrees out.

@loermansa Sorry for the late reply. Thank you. Much appreciated

@loermansa thank you Arjan, and sorry for the late reply. I did actually get it going, but now I had to restore the pc to an earlier point and I forgot how I got it running again lol.uat be the order that I installed everything. Have to work that out again. Cheers for the reply

@byagm See response here

@rowland "Weight" is a calculated force that acts against movement of the wheel in any direction. It seeks to simulate the masses that would exist in the steering system of a real-world car. Consequently the optimal value will differ from car to car. Ideally, you want just enough "Weight" applied that you can steer with a fingertip down a long straight but not so much that you can hands-off completely. "Torque" is the value you adjust in concert with iRacing's Force settings and ideally should not be set at values that cause over-exertion. In iRacing (or any other sim), the "Telemetry" tab is your friend for identifying clipping. FFB sessions in excess of 60 seconds are displayed in real-time with the last 4 sessions stored as historical data. The basic principle is to run a representative lap with "Torque" set to a comfortable level. 8-10Nm is a good starting point. Use the auto setting in iRacing to get into the Max Force ballpark and run another representative lap. Check the "Telemetry" tab for clipping in the current session. If your clipping % is higher than 0.00%, raise the Nm value to reduce the gain from the sim and raise the "Torque" value to compensate. Ensure the FFB session is ended by disabling FFB within iRacing then re-enabling it. Iteratively run representative laps till "Telemetry" shows 0.00% clipping Adjust the "Weight" if required to reflect the current settings Finally switch to the "Settings" tab and reduce the "Controller Mode" iteratively until you feel no additional benefit (the lower your "Weight" values, the lower you can run Mode values without motor noise).

@kkullar You will still need the RBR patch referenced in the thread but first you need to get past the RBR issue with high resolution wheelbases highlighted here It suggests reducing your "Rotation" to the minimum available (180 degrees) prior to assigning the steering axis.

@noppishen I understand you've been supplied with the required information by the Sales team. The Esport wheelbases currently have a separate release in the v21.07 track. Labelled as v21.07.03, it is functionally equivalent to v21.07.02 with support for the Esport hardware configurations.

@sim-plicity-dev That's very good news. I'm all in for this. That's going to be the first wheelbase lineup (let alone first DDs) on the market to offer Linux support.

@jeanv78 Generally, you would choose Sim Mode unless the title in question requires Game Mode to function. The Presets Installer creates both entries and leaves the choice to you.

@ochso Many thanks for the confirmation. I''ll get the Sim Support matrix updated to reflect

@buscho6 From a end-use perspective, the key difference is the extra 5Nm. We design each wheelbase around the motor, selecting components & developing firmware to most efficiently deliver a given level of performance for any attainable torque level. This approach means the visual difference is limited to a larger control box for the SW25 (264mm x 246mm x 127mm) compared to the SW20 V3 (131mm vs 246mm x 127mm).

@frijsdijk Your description suggests UCR is grabbing control of the FFB channel from iRacing (probably on startup). You can get iRacing to wrest control back by disabling then re-enabling FFB within the Options>Force Feedback menu Make sure you exit the Options screen between disabling and enabling.

@xB Just had a quick play with KartKraft & would say it's not a hands-off-the-wheel type of sim. With this in mind, it should be possible to get a realistic/useable feel without overdamping the wheel. Can you post a screenshot of your Input Bindings screen within KartKraft as well as your Settings, Advanced and Telemetry tabs from within the SW25 desktop app

@aotto1977 Hi yes the same, I have a sw20 v3, I advised two friends to turn to v4 Unfortunately they got tired of waiting with a month of delay and the lack of communication of not having an answer and apparently they did well because it went from pre-order to: no longer for sale... too bad it's good to devote yourself to development but if you develop so as not to sell it's a little missed your target...