Force Feedback effects not working correctly

[Ruslan]

Hi Virtual!
First, let me thank you for this awesome piece of software you created!
It's feature-rich and convenient to use, a masterpiece.
The most welcome feature for me is the FFB support. I've been waiting for
something like this for years, to be able to use the Logitech G940 HOTAS
in games that only support a single controller (G940's flight stick, throttle and pedals are seen as separate devices by Windows) . Finally, it seems
almost possible )
Unfortunately, being merged into a single controller through Shaul's VJoy
and Virtual Controller, the flight stick does not play FF effects correctly
in games. It shows up in various ways - sometimes the wrong effect is
played, sometimes the right effect is played for the first time, but only once during a mission, and then there's nothing. It may start using the right effects for
a while in the beginning, but after some certain effect is played - it
messes the rest up, and they stop playing at all or the wrong effects start
being used.
So, I wonder, is it me not being able to configure Virtual Controller the
right way, or the problem is in the software..or the VJoy, may be?

Attached are some sample configs that I've used for adding FFB.

I've also tried another FFB joystick - Thrustmaster Afterburner Force
Feedback. It behaves just the same way.

As for the games - I tested FFB in Star Wars: X-Wing Alliance, Star Wars:
Rogue Squadron and Mechwarrior 3.
By the way, can problem be related to the fact that these games use older DirectX 6-7? Is it critical?

So, could you please give me some advice how to properly configure FFB in Virtual Controller?
Also, I'm ready to test things out for you if required.

Thank you in advance and best regards!

P.S. Windows 7x64

[VIRTUAL]

In truth, I tested FFB only on test samples (I do not have FFB devices). But the main course of the tests was defined as the full transfer of vJoy FFB to physical devices using DirectInput. During the tests, I found some limitations of vJoy:
1. No support for custom effects.
2. Only one active effect can be processed correctly.

And some possible bug in SlimDX (module working with DirectInput): incorrected support of Ramp Force.

I recommend using the following samples:

1)
FFB [Auto] => FFB [Auto]

2) 
FFB [<Effect>] On => FFB [<Effect>] On 
FFB [<Effect>] Off => FFB [<Effect>] Off 

Try to use various <Effect> variants:
Only one Constant Force.
Only two simple (Spring, Damper, Inrietia, Friction - not simple effects).
Don't use Custom Force.
Don't use Ramp Force.
Don't use Spring, Damper, Inrietia, Friction.