f4l0

The F14A is currently only supported in the SimShaker beta. Interesting. I'll have a look an see if I can reproduce it on my side...

Did you turn up the "volume" of the seat while you run the massage test function

Looks strange, could you please check if a simshaker.lua file is in the install directory of SSA. For me its: C:\Program Files (x86)\SimShaker\SimShaker for Aviators Beta\Data

Any crash logs?

Great! DCS does not provide the best export interface and of course, there are some issues here and there but this is a one man show I'm performing in my free time. Thus it is what it is... From time to time there might be some improvements...

What do you mean with dead? that the engine effects cuts out on low idle? The reason for this is, that SSA reads the RPM gauges, however, the RPM gauge in the spitfire does not show low rpm values thus SSA can not detect if the engine is running or not...

The P47 is available in the latest beta, you can find it here: https://simshaker.com/software/general/

That would be great! You can use a draw arg. SSA reads external and cockpit 3d args. We can discuss the details via private messages, please contact me... Which SSA version do you use?

AFAIK the JF-17 has only a digital display for the RPM. I have no way to extract the digital value, out of the box. Thus getting the RPM is an issue here... this might change in the future but currently its a "known missing feature".

Hey, I added you request to the wishlist... Cheers

SimShaker for Aviators Beta Installer v2.1.5 is the latest version... and this is the latest changelog: Version 2.1.5.0 – beta release - F14A-135-GR added Version 2.1.4.0 – beta release - Autostart fixed – You might need to disable/remove autostart for SimShaker first - Manual updated – Thanks to Alexey Version 2.1.3.0 – beta release - Autostart fixed Version 2.1.2.0 – beta release - P47 early version fixed Version 2.1.1.0 – beta release - P47 fixed

F14A is supported in the latest SSA beta! Which SSA version do you use? The F14A is available in the latest SSA beta!

Not sure either, unfortunately it's not that easy to filter/search the windows logs. Here are some instructions: https://techcommunity.microsoft.com/t5/ask-the-directory-services-team/advanced-xml-filtering-in-the-windows-event-viewer/ba-p/399761 But I'm not sure how successful this approach might be... Does your AV software log something interesting?

I'm not sure about that, but maybe you can find some additional information in the windows logs?

They are, especially noticeable in prop planes What does the SSA log say when you plan DCS? Maybe the connection between DCS and SSA is not working properly...

Custom mods/planes are not supported.

Looks like you are using an old version of SSA. The other P47 models are supported by the latest beta of SSA.

Glad it works... SSA communicates to DCS via network-sockets. IPC might be a solution but would mean to rewrite some major parts of the data receiver...

I can not reproduce this effect on my side... Anyone else with the same issue?

https://onedrive.live.com/?authkey=%21AB3fFPneMUkxlDc&id=AAE14DA560024F57%21112&cid=AAE14DA560024F57

Ok something is blocking the multicast. I googled around and found this: https://windowsreport.com/firewall-blocking-multicast/ Maybe it helps?

Are you already on the latest beta?

Ok, I'll talk to HB maybe they can give me some export data interfaces for that...

You can copy settings (more or less). e.g. you have setting for the for the F14 you want to copy to another model. For that, make the F14 settings the global/generic settings for jet planes (there is a button below the effect properties). This generic setting can be applied to all jet planes if you select the generic jet entry. If SSA detects a new model, it initializes the effects with the generic jet profile. There is currently no way to copy settings e.g. to a single model!

New beta 2.1.5 is released with support for the F14A. I didn't have time to test it deeply, so please report any issues...