Yes the programme does not start under any condition. Either with the base connected switched on, with the base disconnected or with the base connected but switched off.
OK, we are investigating.
How about if you rename your Documents/SimucubeTuner directory to something else and then launch Tuner?
There is a case in our support where this worked, and we are interested in getting a “faulty” SimucubeTuner content to us. You can zip that maybe link it to me in PM here if this helped.
Doing as you suggested the programme now starts. By activating the setting: base support simucube 2 the base is detected. Is it possible to rename the steering wheels and change the image in the programme as with the old programme?
It is not possible to have custom wheel images, not at least for the moment. Its been quite popular feature that people have now asked, but no promises that it is coming back.
Only one app can be connected to UDP game at a time.
Simhub allows to forward telemetry from that to other apps, but the problem is that our Tuner patches the port to game configuration files.
We also have undocumented possibility to forward UDP from Tuner to other apps like Simhub. We are going to add instructions on how to use it very soon.
1 Like
So currently theres no way to use Simhub? I remember when I tested an early beta it worked fine. or does it only affect certain games?
This only affects the simulators that utilize UDP based interfaces for telemetry data.
At least EA WRC, EA F1, Dirt Rally are like this, but not many others.
1 Like
Hey All,
I ended up reverting back to True Drive with my Simucube 2 Pro. I’m not able to tune it anywhere near what it’s like in True Drive. I mainly use iRacing and drive the GT3 and Open wheelers.
I tried to everything to replicate my previous profiles and none feel the same, so I tried a few experiments.
- Replicate all profile settings exactly - FFB is nothing like True Drive.
- Create new profile with default settings from both TD and T - FFB is nothing alike.
- create profile and 0 all FFB settings in both TD and T - FFB is nothing alike.
I think the last test proved my theory correct so I went back to True drive. Going back to TD the difference is night and day, Tuner feels like a downgrade.
All feedback is muted and it feels like some forces are actually missing in Tuner.
Why is it so ? was this intentional to smooth out the feel or match competitors ? I would like to know is anyone else has noticed the difference as well.
I have created account here just to say this: i’ve been in the mid run while wanted to fiddle with True Drive, then it offered me to upgrade to SC Tuner, i did also updated firmware, and… i have no idea what you guys did or what was updated there but new version is just awesome.
I am previous GT4 now GT3 driver irl, and on sim drills it was always missing some fidelity whatever settings you put there, the best worked with almost everything to 0 and for some cars put Inertia to 40-80. Now the wheel is a lot more alive, no overlaoding, no punchy spikes, road texture feel is all in your hands, very very close now to the real car. Great job guys. Thank you.
1 Like
Hi,
These reports are very strange, since we didn’t change anything with regards to FFB implementation in firmware. There were firmware changes in how wireless wheel connections are managed - that is, when to connect, and how to transfer information about which wheels are available for connecting, to the Tuner.
Following FFB parameter related changes were made to Tuner (compared to True Drive):
- Simple mode profiles were not implemented.
- Slew rate limit can now only be adjusted with one decimals (but feedback taken)
- Steering angle limits are done with 10 degree steps, instead of 1 degree (but feedback taken on it also)
- The torque linearity (Gamma) filter has been implemented also for Sport and Pro models.
- The sliders in Notch filter do not exactly work in the same way where the Frequency acted as a master switch in UI for the other two settings, but otherwise the values transfer correctly.
We spent extensive time to get all the profile value conversions correct so that True Drive profiles would transfer 100% matching into the Tuner format, and that Tuner would put that to the device correctly as well. For this last step, we have a “dump” tool that will dump the device memory for each profile parameter into a text file. We would be interested to see whats going on for @Dan …
Hi Mikka,
Thanks. When can you release a full version manual with all vital steps ?
yes definitely interested Mika, I would like to know why there are reports both ways, as in better and worse. Generally placebo works the +ve way… 
Could it be i had old firmware? Now i use 1.2 Torque linearity, 30-50 Inertia and 5 Low latency. I don’t know if its palcebo or no but washed away 4 seconds from Nordshleife because i can feel corner entering much better on the wheel. I also did 200km run on track yesterday, then back to Simucube and now the feel is really better back and forth. Before the update the wheel was always spiking too much left,right, and instead driving sim you had to fight spikes. Real car also have these spikes and pretty intense, but they are with dynamic increase, not punchy like hammer, that’s exact change i felt with the update, spikes are there, but alot more dynamic, without loosing road texture.
1 Like
Absolutly awesome update, around 12-15 month ago something changed with the FFB for the worse and all the fine details and range which made this base so good were missing, no matter what did to the settings.
I’ve almost stopped playing in the last year because the FFB was so muted and it just wasnt fun anymore but this update changed that again, i can finally feel what my rear axle is doing again, the difference is like night and day so i have to second @Mitt opinion, this is so much better!
Appreciate the continued work.
I can only think that either new parameter like Torque Linearity has non default value different from previous FW or users updated from much older pre-recon V2 FW, which indeed brought some improvement to FFB feel.
This is FW release notes:
Simucube 2 True Drive development has ended, and Simucube Tuner 2.5 with Simucube 2 wheelbase support has been released on this day.
Simucube Tuner is a massive upgrade, providing total control over all Simucube products including wireless wheels.
Whats new for Simucube 2 users?
- One software for everything
- Much requested auto switching of profiles for Simucube 2
- Improved user interface
- Torque linearity filter for Simucube 2 Sport and Pro models
- Various small firmware changes and fixes
Unless there is something else in “various small firmware changes and fixes” Mike doesn’t want to talk about.
To fix numerous bugs that could have happened with analog axis configuration, and to reduce code complexity, Analog Axis stuff was changed:
- the Simucube 2 Accessory Port analog axis inputs were changed so that the 4 available channels always use the first four controller axises after steering axis
- … and the final 3 axises are from wireless wheels.
- remove previously unused possibility of there being a certain amount of sets of analog axis settings configurations (profiles, sort of) in the firmware code.
Other small changes:
- remove debug event log events 907 and 909 that were added into the log confusing amount of times, and replace with a single event that is also clear text translated to “device ID request/re-request for given serial number”. This makes it possible to more easily detect this event in the log; the device id is asked only on device start to configure the servo drive and to report correct USB product ID to PC. If there are these events in the log when e.g. in sim and driving, there are ongoing USB connection issues causing host (PC) to re-negotiate USB communications.
- Add firmware detection for a new hardware revision
- “Reset FFB device state” button also resets the temporary steering angle mode (set by a game) to use the profile set parameter again
- Firmware reports via a status bit if a wireless wheel is actually in the bite point setup mode so Tuner will be able to show that. Bite point wasn’t adjustable from True Drive, but it is in Tuner.
1 Like
And before any rumours start:
The wireless connectivity SOC module we use, has been EOL’d. However there is a binary compatible alternative from same manufacturer (same SOC, different package). It has different FCC certification ID number. To fulfill oblications to detect hardware revisions, and in case there is actually something different going on with the replacement, there needs to be separate detection of this PCB revision.
For usage, there is no differences in terms of e.g. wireless wheel reception in any way.
- Does it always connect to UDP even if you don’t have ActivePedals, if so can it be optional in ActivePedals config only.
- Also would be nice if tabs only for connected (registered) hardware were shown to limit unnecessary and confusing visual bloat.
- Can we get back to loading profiles by clicking on the list as before instead of opening additional dialog.
- And controls in wheel setting, can we have it compact and smaller as in True Drive, fitting single screen without drill down sections and vertical scrolling, it’s just not very user friendly when instead of seeing everything at once you need to go through extra clicks and paging.
Thanks
i had the same feeling with the latest true drive. I didn’t try tuner but i reverted to 2023.2 and it is better for me. But i have sport not the pro. I feel like the wheel is not linear