=Andre=

Yes, the commands sent/received can be seen in the log boxes of both SimShaker for Aviators and Sound Module

it also sends the test command to the Sound Module as it does nothing it looks like there is no interaction between SimShaker for Aviators and Sound Module as it's conducted via network protocol I would suspect a firewall software blocking the packets sent by SimShaker for Aviators

what if you press the Test Vibe-Motors button on the 3rd SSA settings tab?

You are welcome! Glad you are happy with the Sound Module again.

OK, thank you. It looks like you don't have right files in the right place. Please disable Verbose logging. Unzip attached files exactly into the Documents\SimShaker Sound Module samples\Customized\1 subfolder When you start the Sound Module it shood look like this LGeffectFiles.zip

Hello, yes this is quite possible. Usually it works fine. May I see a screenshot of your Sound Module?

Talking about exactly the Gametrix Jetseat, there is a zip lock across its back side. If you unzip it you will find a soft foam layer underneath. If you carefully slightly cut the foam you will find a motors connection board inside the seat. The connectors are covered with a thermo-glue, which can be soften with a hair dryer for example. You can disconnect the motors of your choice there. As another option you can edit some of the samples in SimShaker for Aviators package, but I'm afraid it's much more boring.

Well, this would be really easy to set up with the new SimShaker Pad, but what is your seat type?

OK, it's sent

Yes, it works. I think you will want to use SSA version 2.9 or higher.

There is a guy in Germany who can help with this. I can provide his contacts through PM if you are interested in.

Know issue, but no fix. Sorry.

It looks like starting NLR HFS software first paves the way for another application. Finally I've got them both working with Win 11 24H2 update. Yes, there is a conflict on DCS Export level. Please also read here

Can NLR HFS software connect to the seat?

Log is the ForceFeelLog.txt file in the %userprofile%\AppData\Local\ folder