SimTools v3 Public Beta

now i understand my double click was not fast enough
thanks for your quick reply

Ok, now I understand. I tested it and yes, profile changes when the vehicle changes. Thank you!

I added the following to the simtools v3 lua for DCS and it completely eliminates the spikes that DCS induces when starting from a stop on the ground. I need some further testing to see if it messes anything up, and I may add an if statement to avoid processing this logic if not on the ground, but early results are really good. I tried addressing this with various approaches to spike filters, but any filter that removes these spikes also dampens the motions that you actually want to come through. Eliminating them at the source like this works much better (so far).

--Eliminate ground spikes
local speed = LoGetVectorVelocity()
local speed_mag = math.sqrt(speed.x*speed.x + speed.y*speed.y + speed.z*speed.z)

if (speed_mag < 1) and (math.sqrt(slot_sway*slot_sway) > 0.01) then
slot_sway = 0.01
end

Note to @yobuddy.. this is completely different than the spikes we're working on separately.

I'm not sure whether this is a bug with Axis 1a of the 6DOF linear hexapod interface.
I'm using the flypt actuator order for my Stewart platform and everything works as expected in flypt.
I can't seem to get roll working in simtools v3beta - all other axis behave as expected however, roll appears to move in the pitch axis between actuator 1 and 5 but works correctly in the virtual output? Is there something that I've missed?

The spikes caused by moving from a stop in DCS are different than the spikes I see in MSFS.

In DCS, the spikes come from the sim and they can be seen in the Virtual Sliders in simtools. They occur whether I use the serial interface or the network interface with my python script and only occur in sway. There have been numerous reports of this behavior to Eagle Dynamics (along with spikes related to the carrier cat hookup), however they have never been resolved.

In MSFS, the spikes do not come from the sim (they do not show up in the virtual sliders) and they do not occur when using the network interface. They only occur with the serial interface.

Thank you. I thought it was strange as I am not seeing what I expect from the virtual output. The axis order you have shown is correct. The only filter I am using is smoothing at 100% for all axis during testing.

I don't know if this frustrating issue has been reported, but the Simtools do not always receive telemetry from iRacing thus motion rig cannot work. I'm also usim SimHub for haptic feedback and SimPro Manager from Simagic. I cannot tell if the issue is with iracing either.

The motion rig initializes when iRacing loads, but when starting to drive, nothing happens.

Anyone else with this problem?