Tested 0.5.2 with GUI open on screen in official practice running 25 laps at Mid-Ohio DW12 and glad to report no SimpleMotion errors using AKM53K with BiSS set to 22bit (4M).
Good stuff Mika!!
tested with v0.52
perhaps this is so obvious and well known that no one has mentioned it yet, so Iâm going to ; )
in windows 10, running the GUI for the first time throws up a large dialog saying âwindows protected your PCâ - complains about âUnknown publisherâ
when running the configuration wizard and loading a drc file, in the âinitializationâ page of the wizard, the simv2 communication fault number increased from 1 to a new value of 2
in the âAudible notification beebsâ label, âbeebsâ is misspelled
I didnât change anything that could have an effect on this⌠
You will get this with Windows UAC enabled.
I have it disabled and you can do as long as you are running a good internet security program.
Some strange protection policies might do that. Hmm, might actually try to get rid of that when we go totally out of betaâŚ
This is expected, as the IONI initialization routines deliberately make the simplemotion bus to fault.
Beebs has been corrected now.
Something has changed. I literally could not have driven even three laps at 22bit prior to turning off the UI last night. I did not change anything on my end other than new SimuCube updates.
Weird? I guess we will have to see with more testing.
The PC that I am running it on is a dedicated iRacing PC.
i7-5960
32gb Ram
512 Samsung NVmE drive
Titan PASCAL (Watercooled)
ASUS X99-WS motherboard
I had the same with version .5.0
Not .4
Yea the Jog Wheel wasnât a bad way to do it as it was simple and looked good.
Yes that is what I meant as it just randomly closed the Dialog⌠In the US a crash is like a bug panic or fault that causes unintended action to occur or a complete freeze of the system. but yes it was an unintended closing of the screen which could be exactly what you described.
Understood on the stopping it at the bump stop arbitrarily, I guess what I was saying was trying to reduce the spring back in some manner (slowing it considerably) maybe a speed reduction or massive friction, It would slow the return each time it bounces eventually normalizing. iRacing actually has this problem with their virtual bump stop and I have turned up itâs rip range to allow the wheel to go past the range by 30degrees⌠It can be a pretty violent slamming of the end stop when the wheel wants to be locked at the end stop in a spot but the range allows it to go past and then it comes back and over shoots and back and forth. With the ability to lower the Bumpstop range this could make this issue more prominent in titles that donât currently have the issue⌠Something to think about (not sure if it is fixable).
On the max range I mentioned it because the issue I had was I thought there was a bug when I tried to type in 30 degrees and it only took 3 so I reduced to 25 and it only took 2⌠so that is when I used the arrows and found out the MAX of 20⌠Because I use 30 degree in iRacing i was just going to put it at 30 on here once I realized the Spring Back issue.
Im sort of not sure what the dampening adds because of it feeling the same force wise as if you are out of range you will be getting a flat signal so dampening probably wouldnât do to much and if you are in signal (short Bumpstops) you would still be using your set Dampening/Friction/Inertia settings for the main signal.
I think with the Windows Protected is that when they are done they have to register with Microsoft as a Known Publisher or link the program through that program⌠I think they have for Granity as I donât remember that label coming up. But yes it does appear with SimuCUBE.
Maybe it is just the fact that it is continually checking for bugs?? strange thing that doesnât wish to be found⌠iRacing did have an update recently do you think it could have been an issue on their end??
Hello Brion,
I was having this problem, before and after the July 27th iRacing patch.
The thing thing that fixed it was making sure the GUI window was closed. Maybe it was placebo? I would have to go back and load up 0.4.1. with UI open and closed to rule this out. Even then I doubt I would be able to pinpoint the cause.
Like I mentioned I could not have even done 3 laps at 22bit (4M CPR) without the wheel losing centre.
Obviously Beano experienced this during a run at SPA. in probably the Mercedes. The DW12 would probably accentuate this issue with the high torque of the non power steering car?
WhoaâŚwe use very similar systemsâŚperhaps I should also test with my MSI-based setupâŚI have a nice and tidy X99 dual-980GTX setup as a back-up PC from the days I had 2 sim rigsâŚmight give this a run towards the end of the week as well, if the comms issue proves elusive, as I have had some issues with earlier Asus WS (X799) boards and USB-related faults.
i7-5960X water cooled
32gb Ram
400GB Intel PCIe 750 NVmE drive
Dual MSI 1080 GTX water cooled
ASUS X99-Rampage V Extreme motherboard
edit: I actually was murdering the Ferrari GTE this timeâŚfelt like something a bit different to the MoocedesâŚ
@Brion: I think we shouldnât over-complicate the bumpstops for now, letâs allow Mika to resolve some of the critical issues and we can reconsider wider community feedback as well at some point regarding the functionality of certain items, after it has been released.
At some point, it would be great to relieve the pressure off of Mika so he can focus the engine-room matters, whilst the community coders can work on lesser functions, beautification, etcâŚ
I am personally just looking very much for a very stable and fully functional base version now, with Bootloader and buttons. The rest will be nice-to-have add-ons 
Letâs see where things are middle of the month, it is great however to be involved in this extensive beta-program, I am thoroughly enjoying it.
Cheers,
Beano
Yes, this is also important, we wonât want to drag this on forever, as there are other projects too - some other work is being done this beginning week and you must all remember that Iâm a full-time PhD student, this is only a âside jobâ for now 
Also, when we saw the obvious chinese copy being posted in the updates thread, we took the code out of Github. We will have to analyze and decide the platform and scope how to release our code for the community to develop further, while protecting our IP at the same time.
Ok, done a few laps under same conditions as V0.5.1 testing yesterday, and cannot seem to replicate the USB comms issue again.
Diag counter remains 1 in the GUI, no funny behaviour experiencedâŚactually feeling pretty good.
Did not have to recenter wheel or edit any parameters after this flash update, all settings remained as is, but probably because you are using my defaults now I guessâŚall others will have to adjust settings againâŚ
But this one feeling pretty good, Mika, to be honest, I will do more testing tonight again. Have to do some work now (on the side )
Actually, using DfuSeDemo, it wonât flash over the full flash, it only flashes the program. The settings are stored in the end of the flash memory. There is also error&version checking; some magic code is written to flash there and also the version numbers are there, so some logic is used to determine if the flash settings are already âgoodâ or that defaults should be used. Changing just the last .X in the version number does not trigger setting defaults
Great, that comes in handy! Makes life a bit easier.
Thanx for the explanation
Tonight, I will put a couple hours more practice under max torque and GUI open - will try and replicate the suspected comms issue, and if it doesnât come back, I will commission my spare PC and test there as wellâŚso 2 sim PCâs with motherboards from different manufacturers should show if there are motherboard/USB chip related issues, or if it is code-based.
1 Like
I completely understand the order of things to get them done⌠They are just things that I have noticed as Possible/Probable usability issues⌠I do understand that finding out why there is a Drop of feedback is highly important. (I havenât experienced that yet) as well as the boot loader. those are the two biggest things to be able to get it to a public beta.
Mika and I have been discussing visual and interface adjustments as well, not in the open forum⌠I decided to post those issues I see in the open forum so that others can have their input on the way that it functions and what is going on with it as unfortunately some of the new features that make the bump stops way better than before also have added a few intricacies in usability and performance. Granted they need not be fixed immediately but they should be looked at in due time to be able to create that stable finished base productâŚ
I actually cannot think of anymore features as such that are needed beyond what has already been discussed and in the interface, so it is just a matter of making everything work properly in their order of importance. Then figuring out how to let others enhance the software with their additionsâŚ
Yes it could go on forever if you let it, but at the same time what is implemented should be finalized eventually so that things donât Feel unfinished or overlooked.
@Mika - on a side note (re-open source) and it might take much longer to implement is if the Firmware is actually semi-closed with a plug-in (api) system for add-ons to be done by others⌠I think part of the whole Open Source unfortunately would mean that some IP stuff would end up having be made open unless you can somehow block it out through compartmentalizing the code. Or of course it could be open by request and only provide the source code to people who ask for it and have a plan for it.
Put in another 60 laps today of official and offline practice at two different tracks with GUI open and did not have any comm issues.