On Wed, May 21, 2014 at 3:35 PM, Elias Vanderstuyft <elias.vds@xxxxxxxxx> wrote: > On Wed, May 21, 2014 at 4:13 AM, Michal Malý > <madcatxster@xxxxxxxxxxxxxxxxxx> wrote: >> Proper decoupling of the userspace and driver is the only important thing that >> is missing from the current code. > > Also dynamic updating of periodic effects is not yet supported in > "ff-memless-next". > This can also be important in simulation games (=second type), e.g. > the "rFactor" game. Oh, and I forgot some other things that need to be mentioned: - Trigger-button is not yet implemented, as far as I know - Custom force effects, in Linux it is called FF_CUSTOM. (however I think we can neglect this effect for now) - Infinite iterations in the Linux FF API is not supported. @Roland: Now I understand why Logitech Windows drivers have bugs in the periodic implementation of the DInput specs: Logitech seems to have based their drivers on the Immersion Studio visualisation of the to-be-generated periodic effects, and these visualisations are not conform with the DInput specs of MSDN. Take a quick look at the MSDN specs for e.g. SawtoothUp: http://msdn.microsoft.com/en-us/library/windows/desktop/ee418719%28v=vs.85%29.aspx Now open the Immersion Studio (demo) and create a standard SawtoothUp effect, and look at the visualisation... It's wrong, right? Same applies for SawtoothDown and Triangle. Elias -- To unsubscribe from this list: send the line "unsubscribe linux-input" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
