f4l0

I'm working on a patch... should be available soon...

but SSA somehow thinks that it should use the SoundModule, thus recheck the output tab and check if it's disabled

Which plane/model? not for me... i need to check if there are other RPM indicators I can use... Did you select sound module as an output mode? Please revisit the output tab

SSA reads the RPM needle from the Spit, thus, if the needle does not move/show a value, SSA can not calculate the effect

As Andre said, SSA is free, I don't charge anyone and I develop everything in my free time... I can not look into the HF8 issue since I don't own one. And currently I don't plan to buy one by myself to add support. If HF8 would send me a seat, I could have a look. But up to know, they never contacted me...

HF8 Seats are currently not officially supported by SSA.

Its bit messy. You may try the repair function of SSA

The SimConnect box will not turn green. It's only for SimConnect (MSFS). Could I see you export.lua in the DCS profile folder?

I just created an easier to use web page, not perfect yet, but maybe easier to use: https://simshaker-for-aviators.github.io/SimShaker-for-Aviators-Releases/ I've currently some family related issues which need my attentions thus I'm a bit quite...

What are your system specs? Do you use another plugin which uses telemetry data from DCS? Did you check the frame rate limiter in SSA?

Could you please send me the SSA logs? Thx, for the feedback. I currently don't own the MB-339. I tried to implement it "blind". It's also interesting that the numbers of pylons does not match... Could you send me a screenshot if the DCS Debug Window? I'll recheck the 3d module arguments for the MB-339. Maybe the are not correct or do vary (a bit) during flight...

Could you check if SSA saved a logfile in the installation directory? SSA tries to launch the UWEditor. Looks like it can not find the file. It should be here: C:\Program Files (x86)\SimShaker\SimShaker for Aviators Beta\Data\UWVEditor

I tested the F15 in the instant action mission and gun/afterburner worked... Could you please provide some details on your issue? Ah thx for this information. I try to reproduce it on my side...

I can not reproduce your issues on my side. I just started the Shooting Range instant action mission and fired the gun. Which SSA version do you use? Could you please disable all effects except the cannon/gun effect and try again? You can also use the effect monitor to see if the effect was triggered...

Yeah there are more effects listed, but does a WW2 airplane have an afterburner? Speedbrake? Foldable Wings? So usually, add the effects for each model depending on the data available from DCS and the "capabilities" of the real plane You may test the SSA beta version. The stable way not updated for some time, I try to release a new stable "soon". I do not see that SSA detects that you've fired... Did you use unlimited ammo?

Which SSA version? All FC3 aircrafts? Which SSA version? Yeah, some WW2 planes do not have good hit effects. It's a lot of work for me to identify all 3d model arguments which may reflect damage. DCS does not provide a simple interface to get "noticed" if one is hit... Which effect do you miss in your WW2 plane? New Mirage will be added soon... Could you show me the log output of SSA when you fire? In general I'm still on the road but will start to work on the above mentions things soon...

For the latest DCS beta you need to use the latest SSA beta. I plan to release a new SSA stable next week SSA can not bind the network port it needs to talk to DCS. SSA uses port 29375. Does any other application on your system uses this port? Do you have two SSA instances running?

What exception message? SSA stores its settings database in your documents folder Did you install additional 3rd party software? Did you modify your export.lua?

Thx for the report, I'll have a look what I can do... Could you please check your SSA profile folder a shortcut called "SimShaker Sound Module" or "beta SimShaker Sound Module"

Version 2.5.8 – beta release Added - DCS: Support for KA50 III (BlackShark 3) - Feedback is welcome Changed Fixed - DCS: FC3 support fixed

FC3 support will be fixed in the next SSA beta BS3 is coming with the next beta. I've currently no joystick at my hand, thus I was not able to test everything. Flying a helo with keyboard is hard Which effect feels different for the F16?

I started my work on the BS3. Looks like it's very similar to the BS2.

It's nothing to blame ED. There was an API change, I adopted SSA to this change, and we are all happy ;-).

I'm currently working on a fix for the issues introduced with the latest DCS open beta version... I currently don't own the BS3 and the MB module thus currently no support...

As usual, i need to see you export.lua i guess there is something wrong...