Thanks Guys,
Learning some new stuff during these problems!
Now if I could only remember all of it! LOL 
Hey Mika,
See below a quote from a comment I made on iRacing. Some weird Comms-behaviour issues I experienced last night.
History: I used chipset-based usb2 connection. Because I needed more ports on my pc, I added in an Orico P3usb-4V card, with VIA chipset. In game, FFB behaved very weird, something I saw with even Argon years ago, when working with VIA-based USB chipsets. FFB will behave touch and go, i.e. working/disappearing…but this is besides the point and VIA chit.
My issue came when removing the VIA drivers, and the card. I then switched back to original Config with wheel connected to the chipset usb2. Reset pc and Simucube. Tested the wheel in windows with Config Tool open. Then behaviour like below.
[quote]This is a new issue, I had some unexpected micro-FFB stutters last night after connecting to a pci-e usb3 card.
Removed the card and switched back to on-chip usb2. Rapidly turn wheel back and forth caused Comms loss between IONI and Config Tool. At first the wheel animation in the Config Tool will catch slightly, then it froze altogether. Had to reset a Simucube to get it going again. Happened another 2 times after, since then, nothing. I opened the FEV limit even more, as the first time the motor faulted just before this freeze-event.
Something Mika cab check out at his leisure.
Cheers,
Beano[/quote]
Since I flashed to the Simucube firmware, in Assetto Corsa, I sometimes get a pink screen and crash back to UI if the full ffb rate is running, or just crash back to UI if half ffb rate is ticked.
Before this I was running 1.15.1, & mmos, never had this issue
Windows 10
Gigabyte EX-58 DS4 motherboard
GTX1080
So now Assetto Corsa, and rFactor 2 will not work for me.
But I can’t revert back to the mmos. When I open the DfuSe demo, there is nothing in the available Dfu devices drop down menu. I have even tried the S1 switch, no effect, even after power cycling.
And both usb ports are connected
Take a look to see if there are devices with yellow exclamation mark in device manager. Load the correct driver for Dfu mode, if required.
Also, try to actuate the dip switch several times.
Since today I run into a critical issue: the wheel (big mige, IONI Pro HC) initializes as usual when powering on After SimuCUBE Config Tool is starting it says “Operating Mode = disabled”. In Granity all parameters are fine (or no faults). Game controller shows SimuCUBE as present, but no wheel function anymore. Any suggestions?
Addendum: also no more dfu device present…something could be broken?
After doing this and that it works again…huh.
Hi,
are you using Windows 10 and you installed an update before it happened? I manually installed an update via System Settings yesterday and after that I had the same issue, after restarting windows once more plus powering off SimuCUBE it worked again.
Hi, yep I installed a bunch of updates yesterday - could not imagine, that these updates cause the issue. lol. Anyway, problem solved. Thanks for letting me know your experiences.
Hi Mika,
looks like one certain Windows 10 update - I installed exactly one last week - caused the isdue that Pit and me were seeing (no communication possible). When I‘m back home I‘ll add the KB number.
Has anyone else seen the same problem that Pit and me had?
Regards
Guenther
I would suggest to always reboot the computer and devices after Windows updates. Don’t really know how those behave, and of course difficult to test and see those.
Never noticed because I didn’t know the orange IONI LED means there is a fault.
It is flashing LSSS - SimpleMotion communication error
And in the Configurator on the bottom left it says “Debug: SimpleMotionV2 communication fault count: 1”
So do I have to do something? The Wheel itselfs seems unaffected and Granity is working fine aswell.
https://granitedevices.com/wiki/SimuCUBE_Firmware_User_Guide#.232_Communication_Faults
Also, the reason why there is a simplemotion bus fault whenever Enable IONI USB Configuration is pressed, is already improved, and shouldn’t happen in 0.8.x series of builds that are going to be released soon.
1 Like
Hi Mika, I did several updates including the newest Geforce driver (385.69). Since then I have a lot off issues as described below:
AC starts and crashes back to the menu, sometimes it does not crash and I’m able to play.
pc2: in the settings menu choosing the wheel axis and while turning the wheel, pc2 crashes back to the desktop
iRacing is working flawlessly. Absolutley no issues here.
rf2 does not start
Dirt Rally cannot be configured. No wheel axis available to set as a standard.
All other games without a wheel starts without any problems.
Hi Pit,
I have the same setup with a GTX1070 and for me Dirt Rally is working flawless.
When you’re in the game check in Controls->Presets if your wheel is defined as wheel - if you are not sure which of the different controllers is your wheel, simple change all to wheel using the F1 key (this will toggle through gamepad, joystick wheel …).
I even decided to change one of the xml files in the inputs directory in the game folder, to assign also menu keys, but this is a tough job, esp. as some keys will lead to execute menu commands twice.
I’m not playing AC to often, but I haven’t seen it crashing to the menu sofar - today a invoked it three times w/o any issue.
And right now I even went back a decade and tried Race 07 … and it works!
Comparing Nordschleife between Race 07 and AC it isn’t to different imho even graphics wasn’t to bad in 2007.
hi chichi
by accident I could solve most of the issues, though pc2 is still very buggy I’m able to play a few games.
First of all I upgraded the firmware but using the SimuCUBE tool, tried new USB cables and tried different USB slots. On pc2 I’m able to enable my wheel, but every time I address an axis or button I have to leave the menu, if I set two axis or more without leaving the menu pc2 crashes to desktop. Dirt Rally works so far as well, I’m going now further by testing other games if still issues persist.
Hi Mika,
Firstly, this is also posted here: http://members.iracing.com/jforum/posts/list/300/3573807.page. It was suggested that here would be a better place to raise:
Hi,
I am experiencing an issue which seems to be related to SimuCUBE. When the device is connected to my PC (via USB 2.0 port) iRacing will fail to launch and crash with the following error:
iRacingSim64DX11.exe - Application Error
The instriction at [address] references memory at [address]. The memory could not be read.
Below are my system specs and SimuCUBE specs. Any ideas? I have tried with both USB cabled connected to SimuCUBE. with just the one which connects the game controller, and also with/without SimuCUBE config utility running. The only configuration that gives me consistent successful launches is to have the Simucube USB’s disconnected entirely until iRacing launches.
System:
12GB Ram checked and no errors
18GB page file
Windows 10 b15063
CPU i7 2.80GHz
SimuCUBE
Firmware: 0.7.1
Config tool: 0.7.5
IONI FW: 10601
---- Stacktrace ----
UTC: 7-Oct-2017 14:45:33
App Name/Ver: iRacing.com Simulator 64-bit DX11 2.25.3.14
App timestamp: 0x59D699F3
Offset: 0x00007FFFCC8A2456
Exception: 0xC0000005 (STATUS_ACCESS_VIOLATION)
stack @ 0x000000000D60F570
App Base=0x0000000140000000
Warning: Trace may contain false entries…
0x00000001407F404A @ +0x03A8
0x00000001407F6FFF @ +0x0488
0x000000014052C2D6 @ +0x04B8
0x000000014052C4C8 @ +0x0548
0x00000001407F7333 @ +0x0558
0x000000014059E376 @ +0x05C8
0x000000014092C6E0 @ +0x0718
0x00000001407C526A @ +0x07E8
0x00000001407C5334 @ +0x07F8
0x000000014068DEF7 @ +0x0818
0x00000001406364A9 @ +0x0868
0x0000000140959AAC @ +0x0898
0x0000000140528137 @ +0x08F8
0x0000000140957DC6 @ +0x0958
0x000000014038C75F @ +0x0988
0x000000014038C97E @ +0x09B8
Finished
Exception Module: C:\Windows\System32\pid.dll
Thanks for reporting. This is a known issue, although very rare at least on my development computer at work and also at my rig at home. The iRacing log is not very helpful. I’ve posted a guide on how to help to fix this bug here:
Thanks Mika. PM sent