Oh, those were the values for the force feedback functions, my bad. Trigger values do indeed go from 0-255.Again, thanks, that worked! Sort of. HOWEVER, I had to tweak it to make it work. You said that the gettrigger_r function returns a value from 0 to 65535. this did not work for me.The values that actually allowed the right trigger to function were 0-255. At first I was getting no response from the controller with the default value you suggested of 20000, so I set the gettrigger_r value to 100, pulled the trigger almost halfway, and it worked. Setting that number higher than 255 and the controller will not respond. Or maybe I did something wrong to make it act that way.
And now for a super silly question.... while I can now sprint with the R trigger, the L and R triggers are still giving rumble feedback depending on how much the triggers are squeezed! I can't find where these functions are being called to disable them!
As for the rumble code, if you started off using the example as a template, the piece of code that binds the triggers to the rumble function is in the step event of the obj_xinput object. Try removing the following piece of code, or at least the setrumble part:
// Set controller rumble
for (i=1;i<=4;i+=1)
{
if plugged[i]
{
left=gettrigger_l(i-1)
right=gettrigger_r(i-1)
setrumble(i-1,60000/255*left,60000/255*right)
}
}



Find content
Male


