Rumbles too long, is it polling rate?

[Longfellow78]

Hi there.

I'm building a script with some rumble indicators for different modes (xbox elite controller on pc) and sometimes the rumble lasts 5-6 seconds before stopping. I have played about with the output and input polling rate, and it may be my imagination, but on a slower polling rate it seems to happen less?

It happens on protocol default, and seems to not happen at 250ms.

Any advice please? Thanks

[Scachi]

Show your code.
This rumble continues usually happens when not spending attention to the notes in the gpc language reference:
"ATTENTION: The ffb_set() should NOT be called on every interaction of main. "
calling it directly in main or inside a combo without a "wait(0); after the ffb_set command is basically the same.

I always apply a wait(time) long enough after the ffb_set() and wait(0); to allow the rumble to finish before doing a second rumble.
To call ffb_set in a combo correctly use something like this:

Code: Select all

 
 
combo cRumble {
    ffb_set(FFB_1, 100.0, 250);  // rumble for 250ms
        wait(0); // causes the ffb_set to be called once only
    wait(500); // wait long enough to have also 250ms of non rumble time
    ffb_reset(); // allow the game control over the rumbles again
}
 

https://www.consoletuner.com/wiki/index ... s_1#rumble

[Longfellow78]

Hi thanks. I'm not with pc at the moment so will look later.

Also I've got a weird lag problem. I upgraded from the other competing hardware to use my xbox wireless adapter, and using the same script with xbox one to emulate xbox 360 it doesnt feel as sharp or crisp. I'm wondering if this is polling rate related on the auto setting. This shouldn't happen as titan two is much more powerful. Any ideas? Thanks a lot

[Scachi]

Sorry, I have no experience with xbox or its wireless adapter.
Open another thread for your xbox wireless question. Some people may miss your second questions as it isn't mentioned in this threads topic.

[Longfellow78]

Ok thanks.