=Andre=

Well, I think we could walk through some examples so you could get a main idea behind it. The customization details depend on your rig configuration. Is your front-back system still going to be stereo, i.e. consisting of 2 separate channels?

Looks like rather a DCS issue than SSA.

Hi, what exactly you'd like me to do?

Does it cause any problems, if the application works?

I'd recommend you to consider at least a little padding underneath. The SimShaker Sound Module doesn't try to recognize the buttkicker. It just pushes audio into the sound card of your choice (or default one, if none was selected).

None of the noises are taking into consideration, it's a telemetry based solution.

Simconnect is for MSFS, but not DCS Either do not start the second SimShaker Sound Module instance or press the Qiut button on the error message form.

I've just checked. It's fine. Please try again.

discussed multiple times above I suppose. the cure is disabling SSA autostart with Windows option

No, it doesn't

I think the previous versions archive is handy for the case like yours. If one installed a fresh version and it didn't work and could rollback to the previous version easily. What's the problem with the "13th Nov" version?

Hi, have you tried the other troubleshooting steps from the User Guide https://simshaker.com/guides/ ?

I'm not sure that's implemented in the SimShaker for Aviators. Without it the SimShaker Sound Module can do nothing about it.

I don't think so. But you'd better backup the settings before you updated the version.

The update system had been changed. Now one is just informed that there is a new version and prompted to download it. You can get actual version at simshaker.com website if not prompted.

I don't think that's possible. But you can get back to the demo mode by temporarily renaming "\Documents\SimShaker for Aviators\Soundmodule.cfg" and re-check.

Yes, please contact me then.

talking about the SimShaker Sound Module, any version. config file is the same for both versions.

Hi, I will issue a new key for you to let you transfer it.

What if you disable Verbose Logging in the SimShaker Sound Module settings and try again? Will the issue persist?

Maybe AV software blocks access to the port?

Please email me, so I could help you. This a software support thread, not hardware.

Looks like a power switch moving contact failure. Good news that it's got fixed in the ON state

I guess, if we see too much abrupt LG status change, we should be on the alert.

It looks like there is no connection between the SSA and Seat Handler app. What if you TEMPORARILY disable firewall software and try again?