Force feedback driver - ForceFeedback scanner

Please note: If a developer game plugin is pre-given in the extractor plugin driver and you do not want some special effects you do not need to enable the graphic driver, the FF driver or the memory driver. This software is only need for a game support if there is no plugin written or the game will never get a plugin because the developer has not designed or will not design a interface for exporting the ingame datas. Using DirectX force values requires a force feedback input device.

This application implements itself between the game and a force feedback able input device like a joystick and extracts all Force Feedback effects provided by the game through the Microsoft Direct-X interface. If you are a programer, you could use this software for your own simulator control software as well. To do this some skills in visual C++ or Delphi are required. An example for exporting Force Feedback effects is located in the X-Sim 3 installation directory. The FF driver visualizes all effects that are provided by Microsoft’s Force Feedback like described in on the MSDN home page.
If you are using a Force Feedback wheel instead of a joystick which offers a X and Y axis, you also need the help of the joystick interface or the injector speed gauge detection to get a ingame Y ingame force value. These combinations help you to get every game working with X-Sim if you invest some evenings of hard work The results will be very impressive, you will get not the combined vibe effects, but separated forces. One of them is the force you feel for left and right. With single force you own the ingame lateral force of your simulator. No combined effects will be transferred to your simulator, only the selected pure lateral ingame forces!

Preperation of the extractor to use the force feedback driver:

If you own a game yoda file (.yef) you are able to enable the tool in the force-sender application in the menu.
1. Enable the use of Yoda2 by checking the “Activate Yoda FF scanner” option in the menu
2. Select your Yoda .yef file with the “Set yoda export file (.yef)” menu option
3. If not done yet, select game exe file (Same as in main dialog) and set the real yoda exe location (normally done by setup)
Now Yoda will be activated each start of a game. Insure the values are displayed in the input setup section of the Profiler2
.
 

Using Yoda with x-sim - Quickstart

Start Yoda and uncheck the mark on "delete released effect". Likewise no filter must be activated
This option will show you every short Force Feedback action without delete it out of the list if it is released.



1. If you have a dual-screen system you can display Yoda on a second monitor.

If not, you have to start Remote-Yoda on a second pc. Remote-Yoda is a just an external viewer for Yoda. If using Remote-Yoda, you have to enter there the IP-adress of the PC where the main application Yoda is running, in Remote-Yoda (enable UDP ports 4440-4450 or deactivate the firewall). After that set a check mark in the Yoda network-tab to activate the network in order to connect Yoda with Remote-Yoda. This hierarchy has to be maintained. Do not press the "start capture" button until both applications show that they are connected.

2. Start your game and look what happens. All DirectX effects that your game plays back during a race or flight will be displayed here in Yoda respective Remote-Yoda.



Yoda displays during playing a game many different Force-Feedback effects.
These can be expanded with the + symbol and exported. Therefor you have to click the right mouse button.
Important values for our purposes are mostly magnitudes.



Now the value will be displayed in the export window:



This list, together with the "ignore" settings represent a .yef file.


The ignore list list the redetection values of a force feedback effect. Yoda will look for such a effect. Unfortunately some game programmer will create the effects with different starting values. Then you are able to ignore some selected values and reduce therefore the precision of the correct redetection of a effect. You can also edit the .yef file in the windows editor and play with the values.

Example: collision

Drive your vehicle in the game towards an obstacle and watch which effects pops up, plays or changes values in the Yoda menue. These changes would be symbolized by a green 'playback' symbol or a red 'info' symbol.
Mostly these are sine-effects or effects who are combined with constant-forces.
Later you will be able to define a minimum value for each effect in the Force-Profiler, wich will initialize a simulator movement.

Example: G-effect

Drive through a curve and watch which effect, mostly constant-forces, pops up, plays or changes values in the Yoda2 menu. This value changes dependent from the driving direction (left or right curve) from a negative to a positive value.
If have done your notices, which effects you want to use, you will have to export them to the Force-Profiler2.
BTW, Yoda2 compares all DirectX effects with the ones you have selected to be exported. If similar effects are noticed by Yoda, they will be exported to Yoda likewise the selected effect.
Exported effects will be listed up in the Force-Profiler2 input setup section. The Force-Profiler2 transforms these values in simulator movement commands. There you can define, which effect will trigger which axis-movement with which speed. How to export effects is explained more precise in the export section.
Exported effects will be displayed bold in Yoda and are numbered from 01 to 40 in the Force-Profiler2 input setup list.

Important: save your export-list as .yef file, wich has to be entered one-time in the Force-Profiler!

After you have finished the search of the lateral force you can use the joystick pedal set movement to simulate the current speed or you can continue to the Injector manual and search for the speed value in a game. The Injector is then able to convert speed in acceleration and acceleration in real force values.