Mostly unspecific motion output in Dirt3

Hi all,

I did my first test with Simtools as a control for my Seatmover at the weekend. Basically, it worked, but with a not entirely satisfactory result

For testing I used "Dirt3 Complete Edition" including the error patch for the socket error after the finish line. After installing and patching the plugin, I started a race and was able to drive it through to the finish line without a crash. However, the motion output is very diffuse and somehow delayed. For example, the movement when steering often only comes after the curve, when the seat should actually already be centred again. Acceleration and braking forces are basically not noticeable at all, whereas jumps or driving over a hilltop are conveyed quite well.

To see what data comes from the game, I opened the "virtual axes" view in the game engine and displayed it on a second monitor. However, when the race starts, the gameengine closes immediately (it can no longer be found in the system tray). What am I doing wrong here or what else do I need to consider so that I can observe the data during the game? I wanted to find out whether, for example, data is coming from the game at all for the acceleration or whether the actuators are not being moved despite the data.

Have I possibly forgotten or done something wrong during the preparation/set-up of the plug-in?

Thanks in advance for your help.

Thanks for your answer.

No, it was a silent crash without any error messages. The behaviour was that the tray icon was visible after the game/race was over, but in the moment I was on the edge of the icon with my mouse pointer the icon was gone.

Here a all-in-one picture of the settings inclusive the hardware settings and the used plugin:


The effects which provided by the plugin are all default and untouched.

Thanks in advance of your help

Thank for yor prompt reply, norbeast.

Yesterday I looked at all the settings and configurations again in detail and checked them. I gained a few basic insights and now understand the way it works much better. I had simply set or configured a few things incorrectly, but after changing that I am now very close to a very good motion output. I will experiment a bit more to understand the whole system and the interactions of the input parameters and settings, but I can already say that I made a big step yesterday to get the best result out of simtools. Thanks also for the links, which I will look at in the next few days so that I can set up a few more games over the weekend.