Request (Feature) Mixing vibration data into normal data

Yes buddy, this is what I am saying, it will work just like your drawing.

Yes, it will work like this.
(Say we only need heave on a acuator as to make this example easier.)
If in axis assignments we assign "heave" at 70% and we then assign "ride height" at 30%, we have exactly what your graph is showing and no clipping will occur.

I was trying to explain that we need to find the best way to create this "vibration data" as to make it available as an extra dof in the plugin.
For RPM we could maybe try a sin wave?
For Road Noise, "Ride Height", or whatever you want to call it we just need some experimentation to see what works best.
(take an average of or use the biggest input etc..)

You actually need to (take an average of or use the biggest input) the 4 suspension corners and move them all the same.
Or your sim will kick like a mule, and at times, only 2 legs may be touching the ground.​

In short, we just need to do some experiments to see what works.
Take care,
yobuddy

Yes I'm taking for granted the hardware to achieve the output desired, but from a software side of things, no clipping will occur.
Take care,
yobuddy

@hexpod,
We need to figure out a formula for turning rpm 0 thru 10000 say into a sine wave.
Something where the frequency of the way goes up with higher input, but the amplitude maybe falls a bit with input.

So maybe it outputs a sine wave with a amplitude of -100 and 100.
But at a rpm of 10000 it is at -75 and 75.
And the frequency should go up with higher input.
The output from something like this could be sent thru a plugin as a dof, and we could see what happens.

So, do you have any idea on the formula needed?
We may need to brush up on geometry a bit. lol
Chat soon,
yobuddy

Here is the formula for RPM I believe.


Where (a) is the amplitude we want
(f) is the frequency we want
And (x) is the looping input between 0 and 2π.

Next is to figure out how to get the amplitude and frequency we want when RPM is zero, and when RPM is maxed out.
Take care,
yobuddy

I think something like this would work.

‘Constants
_MAX_RPM = 10000
_Start_Frequency = 0.5
_End_Frequency = 0.01
_Amplitude_Decrease_Amount = 500

‘Mock Code
RPM = Current RPM input

If RPM > MAX_RPM then
RPM = MAX_RPM
End if

‘Decreasing amplitude
Amplitude_Out = (1000) - (_Amplitude_Decrease_Amount * (RPM / MAX_RPM))

‘Increasing frequency
Frequency_Out = (Start_Frequency * ((MAX_RPM – RPM) MAX_RPM))) + (End _Frequency * (RPM / MAX_RPM))

Then with the constant vars, we could tune in what works best for the output.
_Amplitude_Decrease_Amount can be adjusted to loose as much amplitude as we thing we need it to. (at 500, it will loose half its amplitude at rpm = 10,000)
Same with the rest, once we find formulas that work well.

Take care,
yobuddy

Close enough that you knew what i meant

@joe extraknow,
There is no need for extra hardware buddy.
We are adding an Extra dof output from a game plugin for RPM.
I believe that is all that is needed.
Take care,
yobuddy

@joe extraknow,

What up buddy,
Always nice chatting ideas, let me go over a few things and see if this makes more sense.

Keep in mind that all of the outputs already affect the main telemetry stream. (roll, pitch, heave, yaw, sway, surge).
So all of these actions would already be on the sim in some fashion already when tuned correctly.
We are simply testing out amplifying the RPM vibrations (for some geeky fun).

Rpm is event driven also as it depends on the users input?
Come to think of it, everything is event driven, as it all depends on the users actions?

I'm using 2 end frequency's, but the output would be all frequency's between these to values.

Chat soon fellas,
yobuddy

@BlazinH

Yes, that would make it harder for sure!
Thanks for the assist buddy!

I suppose I should throw something together now to see what happens.
Take care,
yobuddy

Here is a Dirt Rally Experimental plugin with RPM enabled as Extra 3.

For those of you that like to see code, here is what I used.


As you can see, I'm using the milliseconds from the PC as to achieve a constant loop timer.
Now we just need to find the best overall Start and Stop frequency to use.
And how much the amplitude should decrease when the engine is revved up.

I would suggest you add 10% or so to the axis of choice to start with.
(I think with this, less is more.)
And maybe auto capture some Min / Max values for Extra 3, as none are provided with the plugin.

All feedback is welcomed, as i have only tested that it spits out the data like it should.
When leaving feedback, please show what settings you are using for others to try.

Take care,
yobuddy