It’s not yet public, but some users a testing a pre-release version.
1 Like
You should put any custom files in Documents/Simucube 2/wheels
Thanks for this information
Ok OK now I try…thanks
OKk it Work…thanks again
Hello! A stupid question, most likely, but when a new version comes out, can I just run exe-file and install it over the old one in the same folder? Or i need to delete the previous one
Yes, just install it over the previous install.
only for wireless wheel?
usb wheel I not have wireless wheel
1 Like
There was no bad feedback about 2021.12 testing, so I’ve released it now.
There is also a bunch of work already for next release, but it is unlikely that there will be a new release before Christmas.
Next improvements are related to getting to the bottom of the audible noise increase since 2020.10 release, and some other things 
5 Likes
There’s an issue where editing the ffb and saving a profile activates it. Also the previous profile is still highlighted.
I see what you mean. It is in the web app side. We’ll do the fix for that separately.
now that setting changes functionality is possible with the tahko, can we have this implemented to keyboard shortcuts for evryone else? Would raise usability A LOT to be able to change profiles/various ffb settings in game. The current interface is quite nice and has cool features but edits/changes are cumbersome and slow.
Even assigning a dedicated key combo to a specific profile would be great, would allow to quickly select a car\game through something like a streamdeck or autohotkey shortcuts.
2 Likes
We’ve been thinking about these methods. However, making such keyboard shortcuts that would need to user configurable to not interfere with other games, and most likely would need admin priviledges to work over all other keyboard shortcut actions. Not a simple project to do 
Nice that’s very good to hear, really think it would be an amazing usability feature. Obviously you guys think so too to implement it on a wheel.
About user-created key conflicts, I really think its a non-issue. Most input device software already does this, even for devices with ultra-wide targeted markets like logitech\razer products (where you can map a keyboard shortcuts to a mouse button or even macros). So I think this is a case where users can be trusted with the added complexity.
1 Like
Would it be possible to expose the api a bit so that someone could possibly write a simhub plugin for that usecase?
If we exposed such API, then we would also need to keep it and its documentation up-to-date.
And we would rely on 3rd party hobby project for a feature in our product.
This sounds great to me but I’m probably a minority xD
1 Like
What kind of language are you using in the background?
There are already tools that generate documenations for the API. 
Edit:
And you are already using Auth0. So should be easy to grant access.
Fix for this is now deployed.
Did you see the About and Licenses -window already?
There are a few reports of 2021.11 not detecting the wireless wheel module.
We thought we fixed it for 2021.12, but there might be another glitch that is happening.
Therefore, once I come back from spending some family time tomorrow, a beta release will be available:
Changes and fixes
- Improve the bug fix in 2021.12 release - Fix rare fault where the wireless wheel receiver module is not detected on device start.
- Improve servo drive tuning in Safe Torque Mode. This should eliminate unwanted resonation with some wheels with low inertia or loose parts.
- Improve servo drive sinusoidal current generation smoothness.
- Eliminate some audible noise glitches that appeared in some driving situations and when device goes to safe torque mode due to e.g. hands-off detection feature.
- Change firmware code to not reset all profile settings to Safe Profile after firmware update.
- Change firmware code to not force Resonance Reduction setting on after firmware update.
- Add event log entries for illegal parameter write debugging purposes. Ilegal write can cause unxplained 485001 faults.
7 Likes