Hi,
I've a question about the throttle curve in the game.
In the setting the throttle range is proportionnal to my stick movement , but in game I have to move the stick over 30%(minimum) to make the rpm increasing.
Is there parameters to make the throttle with the same reaction in setting and in game.
The moto I use is the murasame RC9990 2003.
Thanks,
Quote from: sdecorme on June 17, 2016, 03:05:54 PM
Hi,
I've a question about the throttle curve in the game.
In the setting the throttle range is proportionnal to my stick movement , but in game I have to move the stick over 30%(minimum) to make the rpm increasing.
Is there parameters to make the throttle with the same reaction in setting and in game.
The moto I use is the murasame RC9990 2003.
Thanks,
What your describing sounds exactly like a dead-zone to me.... So are you sure you have not set a dead zone on your throttle controller axis? ;)
Hawk.
Hi,
nodead zone and linearity at 100%.
Is there is a deadzone I can see it in the settings when the cursor move .
In my case all the axis move as quick as the command move.
Quote from: sdecorme on June 17, 2016, 05:53:12 PM
Hi,
nodead zone and linearity at 100%.
Is there is a deadzone I can see it in the settings when the cursor move .
In my case all the axis move as quick as the command move.
What % is your "
direct lean" setting?
Hawk.
where I can find this information ?
Quote from: sdecorme on June 17, 2016, 08:26:10 PM
where I can find this information ?
Go to "
Settings" from main menu, then click the "
Input" tab. You will see the "
Direct Lean" slider on that page and it's usually set at 15% on default settings, try increasing it. ;)
Hawk
Quote from: sdecorme on June 17, 2016, 05:53:12 PM
Hi,
nodead zone and linearity at 100%.
Is there is a deadzone I can see it in the settings when the cursor move .
In my case all the axis move as quick as the command move.
Disable "smooth", and set "press" and "release" to zero.
Why are we talking about direct lean when his question was about the throttle curve ?! :o :o :o
The thing he's seeing is simply due to the electronic idle of the bike I think.
Yes Hornet , it is not a lean problem.
In the advanced menu all my command are optimal
no dead zone
Linearity 100 %
smooth disable
I think this is a soft filtering problem I've the same problem with other axis , it looks like there is a low pass filteron each command input.
When you put the gaz at middle range quiclky it take time to have the moto rpm , so it is hard to adjust gaz in long curve due this delay.
Is it possible to disable this functions
Quote from: sdecorme on June 20, 2016, 06:17:36 AM
I think this is a soft filtering problem I've the same problem with other axis , it looks like there is a low pass filteron each command input.
Is it possible to disable this functions
Can you post a video illustrating the problem ? Also, which input device are you using ?
On the throttle it can come from the bike's idle and/or the throttle map. But I've never seen it on other inputs.
Sorry I've made a modification
QuoteWhen you put the gaz at middle range quiclky it take time to have the moto rpm , so it is hard to adjust gaz in long curve due this delay.
I use a potentiometer with a self made USB card , I use this card for long and on windows or setting panel the throttle react quickly , even with your HUD I can see the slider move as quick as the mechanical.
Is it possible to change the throttle map ?
The throttle map is part of the bike's physics, normally you do not need/want to change that.
But I'm still not sure I really understand your problem.
Here is a video of a test , we can see the delay of the motor response I use the 500cc from the game
https://hubic.com/home/pub/?ruid=aHR0cHM6Ly9sYjEwNDAuaHViaWMub3ZoLm5ldC92MS9BVVRIX2U3MmQ3NDJjZDdkNDY4MmVhYjA3MGVmYzU5NTc0MzQ3L2RlZmF1bHQvLm92aFB1Yi8xNDY2NDA2MTQwXzE0NjcyNzAxNDA/dGVtcF91cmxfc2lnPWZhYWRjYjBmYTAzZDdhZWE1ZDk5ODVkNTc0ZTJkNGEwOWQ0MDc3ZWQmdGVtcF91cmxfZXhwaXJlcz0xNDY3MjcwMTQw#
Strange.
Did you use the in-game controller calibration tool yet? Maybe run it again?
Yes , and the full range of the setting scrollbar is the full range of my potentiometer .
very odd mate.
sorry if this is egg sucking - do you have smoothing off/linearity set for the throttle setting?
It is almost like you are only applying a tiny bit of throttle even though it appears you are at half throttle!
Never seen that. Logically thinking, it must be something it doesn't like about your USB card but I don't know why that would be. If you have another controller (eg: default xbox) pop it in and see if the game reacts normally. Then we know if it is game or controller at least. Maybe the game is not supporting your setup and once known maybe PiB can do something.
The USB works fine because the info of the HUD works perfectly and the HUD take the same info as the game.
That is theoretical and therefore is not a totally sound conclusion. You must test it to be sure ;)
I don't understand the directinput informations are the same for all ...
The actual game may interpret your signal input differently. Remember what you see as stick input (especially MaxHUD which is not part of the delivered game but a 3rd party Plugin) may not represent the games interpretation of the signal.:
The facts are:
We have never seen this.
You are using something different.
Splitting the problem (after investigating the game a bit) means the next thing to test is your 'different' thing.
If all is the same then we can investigate the game more.
Edit: Spello
If you are using a home made rig what is the taper of your potentiometer? The symptoms you describe would arise from using a logarithmic (audio) taper rather than linear.
One thing you could try is by using x360ce software which will allow you to make an ANTI-DEADZONE, this would remove any dead area of movement.
This is what I use for Pilestone games but never needed it in GPB.
My setup video for it may help you.
x360ce can be used to fix problems with old worn out gamepads too!!!
https://www.youtube.com/v/Ts973LaWCFE
I have not tried it in GPB so not too sure about it. I will run some tests and get back to you.
One thing to note is that most potentiometers used in gaming are 10K linear pots. Just having a 5K or 20K pot would make quite a difference. Also some pots wear or are defective at the start and stop section meaning you have movement with no electrical output from the pot.
DD
Quote from: Napalm Nick on June 20, 2016, 08:00:36 AM
The actual game may interpret your signal input differently. Remember what you see as stick input (especially MaxHUD which is not part of the delivered game but a 3rd party Plugin) may not represent the games interpretation of the signal.:
Not really true: in MaxHUD, the Inputs widget shows the throttle as seen by GPB, i.e. after all filtering/deadzone/linearity.
The Joypad widget however shows the raw output of your input device (so without filtering/deadzone/linearity).
So on one point sdecorme is right: in his video the throttle is at 50%.
Quote from: h106frp on June 20, 2016, 08:10:09 AM
If you are using a home made rig what is the taper of your potentiometer? The symptoms you describe would arise from using a logarithmic (audio) taper rather than linear.
That should not make a difference because in the video above, with the throttle at 50% the bike revs up slowly: no matter the taper (log or lin), the output was at 50%.
One thing: did you calibrate your device in windows first ?
Here is the acquisition I've done
I've made a dll at 100Hz , I log RPM and throttle in same time
With my stick
(https://s32.postimg.org/ni26qvkup/Throttle_Selfmade.jpg) (https://postimg.org/image/ni26qvkup/)
here is a log with a logitech joystick
(https://s32.postimg.org/454f9pr2f/Throttle_Logitech.jpg) (https://postimg.org/image/454f9pr2f/)
The problem is the same, the stick take about 200ms to go at 46% or 56% and the RPM take about 3sec to go at the final RPM
in attachement the complete log I've done + the scilab script to view the curve
The graph for your stick looks to me like it's noisy and possibly not holding 100% all the time?
If you see correclty it is only +-1 around 55% of the throttle, it is not the problem the stick of the logitech is hard to block.
Finally, just reinstall the game and it works . ;D
I don't know which parameters I've modified but the mystery is finished.
Thanks for all