SimTools v3 Public Beta

I had to modify the export.lua to make DCS work for me in V3. I changed the following lines:

local slot_heave = accel.x
local slot_sway = accel.z
local slot_surge = accel.y​

to be:

local slot_heave = accel.y
local slot_sway = accel.z
local slot_surge = accel.x​

without that change the values for surge and heave were put into the wrong slots. Am I the only one that is using V3 for DCS or is no one else having this problem? If no-one else is having this problem, then where could the conflict be coming from?

Hello everyone, my game is MFS2020, currently using version 3.0 software;
After the game is started, when the 6dof device and the plane is taxiing on the ground, 6dof does not have any feedback of road bumps and engine vibration, is my setting incorrect? After takeoff, surge, heave, roll, pitch have the right feedback.
In the taxi, I think the 6dof heave should have a slight up and down vibration is correct, please tell me how to set?
I have used SRS software for the same equipment, which has such a vibration response, but I think SIMTOOL software is better, and I need your help, thank you.

In the Mix / Max tuning center you need to click the picture of the cloud next to the 1, 2, 3 settings. It will turn into a road icon. Then you can recapture your Min Max on that profile for ground cueing.

Thanks for the dcs update! I thought the problem might actually be in the dll, but I only had access to the Lua.

Fwiw, imho there is currently no reason why anyone would use v2 instead of v3 for dcs or msfs now. V3 is equivalent or superior in every way.

Thank you!

hello, I have a problem, after a long time I wanted to play f1 but I noticed that I have no movement, I tested roll, pitch, it works perfectly, I tested lfs, grid legends, assetto corsa, the same problem. The second problem, I saw that it also shows me an update, I click but nothing happens, what to do, pls help

when i press the play button twice the game does not start

hi,
is V3 supposed to work with starwars squadrons?
work fine for me with DCS and Nolimits2, tried SW squadrons and get some errors (array out of range.. etc..)
ideas? (plugin downloaded from the V3 interface)

Simtools V3 for DCS seems to conflict with VAICOM pro... Has anyone gotten these to work together?

I renamed the Simtools DCS lua to SimToolsV3.lua and left it in the Scripts directory, and then changed my exports.lua to be the following...

local vaicomlfs = require('lfs'); dofile(vaicomlfs.writedir()..[[Scripts\VAICOMPRO\VAICOMPRO.export.lua]])
local SimToolslfs=require('lfs'); dofile(SimToolslfs.writedir()..'Scripts/SimToolsV3.lua')


If I comment out the simtools line vaicom pro works. if i leave it in, simtools (which confirms my export file works) but Vaicom pro does not. There must be something conflicting, but I'm not sure how to figure out what it might be...

Would be really nice if both of these worked together. Any one have any ideas?

nvm.. got it to work. found some extraneous stuff that was put into the simtools lua. removed that and its working fine using the above method.

hello to all the community I have a question does simtools v3 work on 2 pc like v2 does?

Should I do that in this thread, or over in the DCS sub forum?

Hello,

I need a little help, maybe someone has an idea what is the problem here.

So far I have been able to play AMS2 with no problems with good motion. Even after AMS2 v1.5 update I was able to play with new cars.

But for some reason Simtools v3 seems to have lost it's connection to AMS2. AMS2 v1.5 had three batches published, but I can't remember if I have driven successfully with motion after those. Did any one else had similar issue? So far I have tried: re-dragged AMS2 exes and AMS2 steam desktop quick launch icon (that was the first icon I dragged when started to play with v3 few months ago). Double-click starts the AMS2 ok, but there's no movement. No motion inputs showing. I have default mix/max values setup and I have car specific setups, too.

PS: I have a working setup with AC and RBR, too. Just a moment a go was driving both. Only AMS2 has a problem. And what a fantastic setup I have with RBR, really fine movement...I really like v3.

That did it, motion is back! I very much appreciate your help. Now I'm back in business... it's so cool to drive Indycar with my rig...

Thank you!

PS: After I changed shared memory and UDP settings, my mouse seems to be stuck inside AMS2. Maybe that has something to do with it. Anyway, alt-tab gets me out to tune my min/mix setting.