It will be sooner than #soon memes. I just tested the bumpstop fixes last night.
Messages de mtakala
-
-
There was a major issue with bumpstops, which required some reworking, which was unexpected.
Its coming soon.
-
It might help to run the calibration in the Windows Control Panel.
-
The underlying technology we are using allows for packet sends every 7.5 ms, so that is a main limitation. I would suspect the real latency in Simucube Wireless Wheel System is typically around 5 ms and maximally at 10 ms level.
Two years ago I made a DIY bluetooth system for myself at home, and have had two drivers with real racing experience to test that system. I measured that system to have 15ms latency - it was made with two Teensy microcontrollers and noname chinese bluetooth units. The drivers (and myself) didn't notice any latency at the 16 ms level, it would still be fast enough for racing use.
-
FloSimRace maybe you actually got some "old stock" from a reseller - we used to sell the parts separately and not many were sold like that, and now we only supply the whole kit.
-
FloSimRace we changed the wheel-side SQR kit to include the Wedge SQR part, the new v2 30mm spacer, and the 70mm adapter. They all will come with a new SQR wheel side kit.
-
ilfreddo76 see this post on our forums:
https://community.granitedevices.com/t/which-is-the…/2219/76?u=mika
SC2 Sport throttles only after 4.5 minutes
SC2 Pro throttles only after 6 minutes
Completely different design approach to DD1/DD2 actively cooled motors.
-
Regarding SC1, we are still at "Now" location on the roadmap that we posted.
-
This is a True Drive software problem ? So anothers Simucube 2 owners could have same issue with overheat ? A specific setup in True Drive ?
We are investigating just that. But it is not a common occurrence so far, we are not yet worried.
-
We have, so far, knowledge of exactly 2 units that seem to have somehow overheated (this one and the previous one on our forums). However, current thinking is that it is a software issue of some sort.
-
For the table brackets or mounts, the Simucube 2 devices have full dimensions up to the end of the motor casing, where as the Mige motors had a smaller diameter encoder casing. For this reason, maximum tilt adjustment angles might cause the back end of Simucube 2 Sport/Pro to hit the desk, if the mount is bolted to a desktop surface. Of course it does not matter if there are just aluminium profiles that the bracket is bolted to.
-
We do not know of any games that just would not work with Simucube 2. However, some the older games that are not maintained anymore, have difficulties in assigning controls or enabling force feedback, but those are issues within those games.
-
My apologies of having had reduced effort on the forums. I was on summer holidays for the most of July.
Franconen's issue seemed to be some sort of USB bandwidth issue, and our first thought was that he should try on different computer or with other game controllers disconnected.
-
The D15 connector on the back of SC2 devices has 4 analog inputs for pedals (0-5V signaling), GND and 5V supply. There are also other types of inputs and outputs but no firmware support yet. We will give the pinout at least for those that are developing commercial products, but we do not give support for DIY purposes.
-
These strange things with belts or chain drives kind of mitigate the whole point of direct drive...
IONI will work as long as the encoder is on the same axis as the motor. If the AXI scale can be set up to handle different scales, but the result will not be optimal if there is any slack in the system. The Simucube user interface will just show wrong values for the steering degrees. We will not implement a parameter that would scale the UI values just for one user.
-
Regarding ease of use:
We are considering a simple UI with following sliders:
overall strength
steering angle (with only a few common selections)
smoothness with maybe a scale of 1…5
hardness with maybe a scale of 1…5
and the new sliders will set the (hidden as default) current settings sliders accordingly.
Then user can click “go advanced” button to see the resulting sliders. (hides the “simple” sliders).
User can set whatever, like it is now, in advanced mode.
User can go back to simple mode, but the simple mode will overwrite user’s advanced profile with those simple settings that were being used last time.
The simple/advanced will be a per-profile setting.
-
Regarding the wireless button plate modules:
We designed this simple module now to reduce the time to market. At the moment, we are envisioning a next version of the module that will have more things - but as to what they are, it is undecided. Basically, a LCD display would reduce the working time to a few hours when using a 1S LiPo battery. That is the main limitation. Those who want to have SLI will have to live with wires. Other features, well, they can be implemented for the next version of the module.Regarding support issues: First-hand support is via the resellers. Of course we are interested on the issues that a very small minority of the Simucube 2 owners have, and we think at least some of them are software related.
I'm not sure what unanswered question Stef Bord is waiting for on our forum - the forum is not the official support channel, the reseller is.
-
You are basically correct.
The filter value differences between Simucube 1 and 2 are as follows: For Simucube 2, scale goes from 0-100% where 100% is the same as 10% was for Simucube 1.
All other changes might be due to the different motors used. The Simucube 2 motors are very efficient compared to Mige motors.
-
Hi all,
That delay is something that we are investigating. However, when looking at game controllers in control panel and DiView software, there is no lag. The lag is entirely in the Simucube program and does not affect games. -
We can't really pull the 0.50.3 offline now, as it is required for Simucube wireless wheels.
Did you guys do an update of 0.10.x to 0.11.x, and not save any settings even once, and then go to 0.50.3? I did a few test and could not repeat the issue.
Safe way to continue / recover is to get the simucube_bootloader_and_reset_all_settings.dfu file from 0.50.3, use dip switch method to put the bootloader in the Simucube, and then use 0.11.2 to set up the system.