There should be a FFB2014nnnn.hex file too…
MMosForceFeedback.ini
MMosForceFeedback2014.exe
MMosForceFeedback2014LOC.dll,no more files phillip
You have only the application there. There is another zip you need to download 
Many thanks phillip, I was looking for where to download it, I could not find it!
You’re welcome, hopefully you get it sorted! 
Today I installed the new firmware on my SimuCUBE. Also did a short test drive and everything worked fine there, so there is no problem in general.
This afternoon, I tried American Truck Simulator and Euro Truck Simulator 2 and both do not really like the SimuCUBE FW in its current state.
The problem seems to be with the FFB.
You might already get into trouble when you try to assign the controls, because choosing a controller can lead to a crash.
Second, there is no FFB or only an insignificant amount when driving, it just doesn’t seem to work at all.
The problem with the crashes seems to be solved by deactivating the FFB in the game.
It might also be a good idea to use the wizard to assign the controls, I didn’t have issues with that one crashing.
When set up like this, the wheel can be used, but of course without FFB there is something missing.
I know that ATS and ETS2 are currently not on the list of supported games, but I hope that at some point they will work.
And maybe someone here has an idea how to get this worked out.
Edit: there is a free demo of ETS2 available, which might be helpful to fix the problems at some point.
Go to the steam store page:
There is a button “Download Demo” on there.
Don’t know about ATS, but if one of them works, the other will as well.
Yes, sure, simucube was detected correctly, that’s why I was surprised, it was all correct and when I left the box, started to spin like crazy, the worst was that I hooked my new sennheiser hd600 headphones and broke, xD, the truth is which was very good beta, but I have been afraid and I have returned to Mmos, soon I will try again with simucube, I will buy the sincos and it is not compatible with Mmos.
From what I’ve understood, crashes in some games other than iRacing happens when going into car rather than on start?
If you want to give more debug data, here are the steps.
- Install Microsoft Message Analyzer: https://www.microsoft.com/en-us/download/details.aspx?id=44226
- Start the Message Analyzer. Start a New Session -> Live Trace -> Select Scenario -> USB 3. Do Not click start.
- Click start, then immediately do the thing that crashes the game.
- Press stop (the square on the top of the window).
- File -> Save As -> All Messages -> save to file.
- Repeat the thing so that the game does not crash in similar situation. Save to different file.
Then share your files with me; you can msg me in private to the links, as the files from Message Analyzer could involve data that might be something, such as list of all connected devices,usernames, etc. that you should or would want to keep in private.
Everyone knowledgeable would quite easily able to try to find a the difference when iRacing starts! 
Easy way to get a sense of the message log output:
- Open field chooser
- type usbdevice into find field
- on usbdevice, right click and add as grouping
- Find a device in the listing that looks like SimuCUBE. Most probably its the one with the most number of messages (in parenthesis). You can double click on a message to see transferred data. You can invent some filters to see only some type of messages, etc…
Yes I get similar in P Cars 2 generally when going from lobby or pits to track.
i try not to move wheel till cars is on track as that is when the wheel becomes active there is a small amount of time when you hit race and see the track till you can drive this is were it has crashed
I use Martin Ascher’s shifters directly connected to the simucube.
no double shift whatsoever with the new fw.
double shifts do occur for me once in a while with some osw converted Fanatec rims. those are connected via usb, of course. But that is a known ghosting issue, and has nothing to do with the simucube fw
Next version, the 0.8.0 which has some obvious bug fixes and improvements, in addition to scaling forces using MMC on drive rather than scaling the commanded value, has been compiled. However, I was not sure sure if it worked totally OK in all situations, so I did not want to release it openly just yet. I can share that file on special request to a few testers that “want to be on cutting edge and live dangerous life.” 
Please PM me.
Edit: this limited-time offer has now expired.
I own the same gear directly connected but I have registered many double shift after installed the new firmware. Please Mika change the debounce time
Ok, I did this and captured traces of both a good start in AC and a crash.
I also had a look at the data, but tbh, to me it looks like useless chatter.
I will upload the trace files to dropbox and send you the link.
The only thing I noticed is that in the crash case, in addition to all the “Interrupt In Transfer” messages, it shows a lot of messages like this:
Complete URB_FUNCTION_BULK_OR_INTERRUPT_TRANSFER with Data
But I think it’s just the same and only the summary is different and doesn’t look like some error message anyway.
(except that I have no idea what I’m talking about here and this is possibly all wrong. 
)
Ah, two hints for those having a look at capturing traces with the message analyzer:
- You have to run it as admin or with security group rights, otherwise it won’t be able to capture
- If you’re on Win7, you need to select the USB2 provider instead of the USB3 one as Mika wrote above. That is, because the USB3 provider does not exist on Win7 (only Win8 and later).
As you can see in the 0.8.0 release notes, i’ve already changed that to 20 ms (from 10 ms).
0.8.0 will be hopefully released soon.
2 Likes
Hello,
everything works fine for me except that when i restart the computer, the Software doesn’t find my steering wheel again.
This was not a big problem for me, but yesterday i drove my online rally and after 10 stages in the sim the Software “crashed” and it was the same issue as when i restart the computer. I switched off the SimuCube and then switched on again and everything worked again.
Do you have a idea what i can do to solve this problem?
I never had this problem before with MMos and nothing changed in the meanwhile between the switch to the new firmware/software, so it’s no problem with cable or usb controller.
Please let me know. Thank you very much.
Best regards,
Andreas
All types of USB issues are being worked on next. I don’t know about this type of issue yet, so good that you reported it.
Ok thank you very much for the information. I’m looking forward for a solution.
hi ,
the simucube run well on iracing , also I can’ t connect to granity since I make the update from mmos to simucube .
I have this windows when I connect to drive on granity 1.13.01:
unknown device type : 9376 at bus 8
unknown device type : 9376 at bus 25
unknow device type : 9376 at bus adress 253 in firmware upgrade mode
and this message If I want to connect :
" Unsupported device model connected. Try upgrading Granity to latest version. Connected device ID 9376 "
in the wiki video for instal simucube this first step is not describe :
Bootloader Installation
" This step must be done only if you have NOT previously installed a SimuCUBE bootloader. Generally this is the case if your current SimuCUBE firmware is of version 0.5.x or earlier or when migrating from the 3rd party MMOS firmware.
Please connect to drive with Granity and make sure that SMO value (SM Bus Address Offset), found on the Goals tab, is 0. If not, change it to 0, save to drive, and restart drive. "
perhaps is this point wich made the defaut ?
how can I correct that ?
thx
EDIT:
sorry I forget to click on enable ioni configuration !!!
MY PROBLEME IS SOLVED .