OSW Mmos to PS5

[GeekyDeaks]

Here is the log files includes multiple logs using different FFB settings in game (naming: T1_S2= Torque setting:1, sensitivity:2)
All using the same car, BRZ at Tsukuba for a lap. Let's figure something out !

Ok, there is something really weird going on there and you have some quite large gaps between the FFB reports. T3_S8 around 65 seconds shows this very clearly. I plotted a few of them here:

https://docs.google.com/spreadsheets/d/ ... sp=sharing

If you look at T3_S8 at the 65 second mark, you see a gap of over 2.5 seconds before the next FFB report:

time constant gain output
65.030905 -19092 100 -21001.2
65.045853 -19350 100 -21285
67.596864 -19092 100 -21001.2
67.614805 -19350 100 -21285
67.76577 -18834 100 -20717.4

You should see it's occurring in the other traces too. There is a kind of 'flat-line' between data points on the chart.

I'm not sure what could be causing this. You might need to select the other debug settings and analyse the delta between the timestamps to see if it's due to GIMX pausing or simply that USB records are being delayed.

You might also want to start a new thread to discuss this further so it doesn't get mixed up with the oscillations issue and the GIMX team can better help you too.

[gamechanger]

Here is the log files includes multiple logs using different FFB settings in game (naming: T1_S2= Torque setting:1, sensitivity:2)
All using the same car, BRZ at Tsukuba for a lap. Let's figure something out !

Ok, there is something really weird going on there and you have some quite large gaps between the FFB reports. T3_S8 around 65 seconds shows this very clearly. I plotted a few of them here:

https://docs.google.com/spreadsheets/d/ ... sp=sharing

If you look at T3_S8 at the 65 second mark, you see a gap of over 2.5 seconds before the next FFB report:

time constant gain output
65.030905 -19092 100 -21001.2
65.045853 -19350 100 -21285
67.596864 -19092 100 -21001.2
67.614805 -19350 100 -21285
67.76577 -18834 100 -20717.4

You should see it's occurring in the other traces too. There is a kind of 'flat-line' between data points on the chart.

I'm not sure what could be causing this. You might need to select the other debug settings and analyse the delta between the timestamps to see if it's due to GIMX pausing or simply that USB records are being delayed.

You might also want to start a new thread to discuss this further so it doesn't get mixed up with the oscillations issue and the GIMX team can better help you too.

I have a friend who is using simucube 1 and he don't have any problem with version 4.

[gamechanger]

I have a early Simucube1 been using the c.4 build for 10ish hours now in GT7, it felt great! No more "too much minimum force" oscillations.

But I noticed that there is a lot of FFB clipping. I'm not sure is the game or the settings or the firmware? feels like the FFB signal have not enough "dynamic range" if this make sense. Strange thing is the game can out put a higher force signal, If increase torque setting in game the wheel get heavier
but it still feels like clipping but with stronger forces.

I have constant in config file set to 40 and in game torque and sensitivity both at 1.



(Sorry for my bad grammar if I made any mistakes, I rarely speaks English)

in config file please keep it all 100 and avoid to add any effect on simucube truedrive and do the fine tuning , you might want to add a little bit notch filter

[syin021]

I'm not sure what could be causing this. You might need to select the other debug settings and analyse the delta between the timestamps to see if it's due to GIMX pausing or simply that USB records are being delayed.

I did not feel anything strange when the log cuts out (it's at 2nd hairpin at Tsukuba), still felt like clipping through the hole corner. So probably just usb logging delay.

You might also want to start a new thread to discuss this further so it doesn't get mixed up with the oscillations issue and the GIMX team can better help you too.

Ok. I will open a new thread.

in config file please keep it all 100 and avoid to add any effect on simucube truedrive and do the fine tuning , you might want to add a little bit notch filter

I done more testing keep all at 100, It doesn't feel any different besides just felt heavier, still clips around the same point.

Also, why do I need to add notch filter? I know it removes oscillations but using the c.4 build fix it already.

[gamechanger]

I'm not sure what could be causing this. You might need to select the other debug settings and analyse the delta between the timestamps to see if it's due to GIMX pausing or simply that USB records are being delayed.

I did not feel anything strange when the log cuts out (it's at 2nd hairpin at Tsukuba), still felt like clipping through the hole corner. So probably just usb logging delay.

You might also want to start a new thread to discuss this further so it doesn't get mixed up with the oscillations issue and the GIMX team can better help you too.

Ok. I will open a new thread.

in config file please keep it all 100 and avoid to add any effect on simucube truedrive and do the fine tuning , you might want to add a little bit notch filter

I done more testing keep all at 100, It doesn't feel any different besides just felt heavier, still clips around the same point.

Also, why do I need to add notch filter? I know it removes oscillations but using the c.4 build fix it already.

if you think the oscillation is eliminated already then no need to apply

[gamechanger]

I'm not sure what could be causing this. You might need to select the other debug settings and analyse the delta between the timestamps to see if it's due to GIMX pausing or simply that USB records are being delayed.

I did not feel anything strange when the log cuts out (it's at 2nd hairpin at Tsukuba), still felt like clipping through the hole corner. So probably just usb logging delay.

You might also want to start a new thread to discuss this further so it doesn't get mixed up with the oscillations issue and the GIMX team can better help you too.

Ok. I will open a new thread.

in config file please keep it all 100 and avoid to add any effect on simucube truedrive and do the fine tuning , you might want to add a little bit notch filter

I done more testing keep all at 100, It doesn't feel any different besides just felt heavier, still clips around the same point.

Also, why do I need to add notch filter? I know it removes oscillations but using the c.4 build fix it already.

for my simucube 2, I have to apply the the minimal notch filter otherwise the oscillation is till exist , but it is perfect after applied.

[bri77]

I'm not sure what could be causing this. You might need to select the other debug settings and analyse the delta between the timestamps to see if it's due to GIMX pausing or simply that USB records are being delayed.

I did not feel anything strange when the log cuts out (it's at 2nd hairpin at Tsukuba), still felt like clipping through the hole corner. So probably just usb logging delay.

You might also want to start a new thread to discuss this further so it doesn't get mixed up with the oscillations issue and the GIMX team can better help you too.

Ok. I will open a new thread.

in config file please keep it all 100 and avoid to add any effect on simucube truedrive and do the fine tuning , you might want to add a little bit notch filter

I done more testing keep all at 100, It doesn't feel any different besides just felt heavier, still clips around the same point.

Also, why do I need to add notch filter? I know it removes oscillations but using the c.4 build fix it already.

for my simucube 2, I have to apply the the minimal notch filter otherwise the oscillation is till exist , but it is perfect after applied.

What are your settings for your notch filter in simucube 2 true drive software?

Center freq hz
attenuation dB
Q Factor

[gamechanger]

I did not feel anything strange when the log cuts out (it's at 2nd hairpin at Tsukuba), still felt like clipping through the hole corner. So probably just usb logging delay.


Ok. I will open a new thread.


I done more testing keep all at 100, It doesn't feel any different besides just felt heavier, still clips around the same point.

Also, why do I need to add notch filter? I know it removes oscillations but using the c.4 build fix it already.

for my simucube 2, I have to apply the the minimal notch filter otherwise the oscillation is till exist , but it is perfect after applied.

What are your settings for your notch filter in simucube 2 true drive software?

Center freq hz
attenuation dB
Q Factor

Center freq hz. 2.0
attenuation dB 17.5
Q Factor 1

[gamechanger]

seems Drivehub have two new version firmware updated, 2.07 beta 8 and 9, I think we can try to update too

[isamu]

Hi guys. For those of you using DD wheels, Just out of curiosity what degree of rotation do you have your wheel set to? 900º? 540º? 360º? Is it possible to use GIMX to trick Gran Turismo 7 into thinking your "virtual" G29 is set to 540º? If so, how can I accomplish this? I don't mind using 900º but if possible I'd prefer setting it to 540º instead.