to clarify, i meant the edit history for the google docs manual itself.
i like to review the docs on each release and it can be challenging to find the sections that have been added or changed without the edit history.
to clarify, i meant the edit history for the google docs manual itself.
i like to review the docs on each release and it can be challenging to find the sections that have been added or changed without the edit history.
OK, I think it will become naturally when we decide where we are going to host the manual. The current version is very much work in progress, and for this firmware version new features were not added so documentation updates are not important.
midweek update: Reading and debouncing button inputs works now, but it has to be moved into other part of the code that it wonāt interfere with communication with the drive. I got quite bad simplemotion communication problems on the first try of the thingā¦
button inputs moved. Works fine. Also, today I migrated my rig at home from Bodnar G25/G27 USB pedal adapter to self-made SimuCUBE adapter.
Hello guys.
I was pointed to this thread by a member of this board, and Iām quite excited about it.
For those of you who donāt know who I am (most of you, Iām sure!) I made the FFBClip app for Assetto Corsa. Since the lead programmer over there (Stefano) isnāt really concerned with FFB as such, I had to make a tool that at least prevented clipping and allowed users to see what was going on with their wheel. In the process I have revealed some bugs in their FFB code and most of that is corrected along the way.
I hope to be able to contribute here as well!
Welcome Atle
Open beta is coming sometime around the end of the month, would be good to also get your input and feedback.
Mika Takala from GD is lead programmer for this effort, so I am sure you two will have lots to discuss!
Cheers,
Beano
He knows already ā¦
Iām sure you will be a huge help when mika comes to analysing (hope I spelt that right) the AC ffb
Yep, it will help. From what Iāve understood of it working already quite well, AC must be using either sine effect with magnitude=0 and offset telling the torque, or just constantforce effect. In addition, it seems to be using damping effect which the new firmware does not implement yet, based on missing forces when stationary. @AtleDreier, please PM me the specs
A far as I know the damping is implemented in the a.c. Code, not externally. They do send constantorque commands, according to a post by Stefano a while back. Iāll try to get it verified, Stefano can be anything from incredibly helpful to downright hostile depending on unknown factorsā¦
You donāt need to bother asking Stefano, as I can get debug data very quickly when I get round to itā¦
Currently designing profile management.
The damping in Assetto are the value in tyres.ini
[FRONT]
ā¦
RATE=320000 ; Spring rate of front tyres in Nm
If you change that, you will see, what i meaning.
That wonāt tell me anything about what type of data goes to the wheel. Thats only some internal value that AC uses for some effect calculation. It doesnāt tell anything about how that effect is transferred to the wheel, which is the only thing that matters.
I will get debug data when I need it, its not very helpful to try to help this way.
If, however, you or someone else is interested in giving me debug data from various sims, then technical details to achieve that can be arranged. Please contact by private message.
How do you get debug data?
Deep into implementation phase for the basic profile management. Maximum number of profiles is 1000.
Nice!!! Looking forward getting the final closed beta, but for the buttons.
I run just one profile. Max torque
Buttons already seem to kind of work. Need to actually try to use them to be sure.
We discussed with @Aki about how to do and test whether current button reading speed is sufficient to see which of the signal changes is detected first, which is needed to know which direction user turns the incremental knob.
Anyone know about that for the typical simracing switches? makes, models, oscilloscope images?
Knitter and NKK switches are quality ones, most commonly use. I use OTTO P3 and P5 series also, but they are expensive.
Rotary encoders - ones from ELMA are very good, like single encoder CTS288 and CTS288V, and dual concentric ELMA E37.
I would say option to select 1:1 or 1:2 should be good enough for most cases, although sometimes 1:4 is also used in encoders.
Mechanical encoders are quite simple, CW direction, switch A makes before Switch B, and CCW direction, Switch B makes before Switch A.
So should be easy to determine by simple coding, at least the basic operation of itā¦
Hi Mika what is the plan if any of having something simular or using Accuforce 's ffb overlays from the telemetry?