G Torq
ALTA B2O
88
   |
Posted - 2013.02.24 11:02:00 -
[4] - Quote
ongoing tests:
- The "Lag" appears to be controls resetting
- The issue appears to be RF interference or input-"noise"
- Other things can cause the same issue, plausible same Root Cause
@1: Controls Resetting
When the issue comes up, what is experienced is that all actions are cancelled
- Running is stopped
- Aiming stops
- Firing stops
- ... stops
This even when it happens for just a few miliseconds
From this, my observation is that it relates to a bad input-handler.
Normally, the input handler would look for 2 events:
- Button depressed
- Button released
In the case of Dust, it appears that it expects a continuous stream of "Button still depressed" events, to consider the action as continuing.
When the headset and other RF interference occurs, that stream of events is interupted, and Dust returns to a default position.
In other games, I've finally managed to reproduce related effects:
- Borderlands 2 will continue the action despite interference (much better!), but may on rare occassions continue the activity for a few miliseconds too long (over-steering)
- Need For Speed uses the "continued stream of events" and speed may occassionally "sputter"
Overall, the issue is a LOT less significant in other games, even with the virtual surround turned on (more data = more interference)
@2: RF interference
It would appear that part of the issue can be RF interference between the Sony Playstation SixAxis/DualShock and the Sony Playstation Stereo Headset - but in that case, also with other sources of 2.4GHz equipment.
I am seated 5-6 meters from my PS3, with line-of-sight except for a plywood panel - at this range, the two devices CERTAINLY should not experience interference, but it does appear to happen.
Will be buying a long USB cable to test this, using the SixAxis via USB and the headset wirelessly. Should be able to get some kind of results.
If anyone has equipment for testing RF Interference, or generating noise in the public 2.4GHz, feel free to test within confines of local law.
@3: Non-Headset interference
It has been reported in other threads that having equipment attached to USB may cause "lag" or control-resets (as above). A standing recommendation is to unlpug everything from USB when playing Dust.
This leads me to speculate that it may also be a different issue with the Dust input-handler: Resetting activities on unknown events.
Normally an input-handler would have a dummy default "catch-all" function, where unknown/irrellevant events are basically ignored. Given that having equipment attached to USB causes issues (e.g. controllers in a charger), this is also a likely scenario. |