[Official] SimShaker for Aviators

[Steel Jaw]

28 minutes ago, =Andre= said:

Pardon me?

Please see attached picture, the numbers in SSA are changing so I do not believe it to be an issue with your software

[Boomer74]

I just received the NLR HF8 seat. Install went fine, however when I start DCS, I get the following error message. Has anyone seen this or knows how to fix it?

[=Andre=]

5 hours ago, Steel Jaw said:

Please see attached picture, the numbers in SSA are changing so I do not believe it to be an issue with your software

I meant another window to check, but OK. It' looks like some activity is presented.

Maybe you've got the game audio getting into the BK as well?

4 hours ago, Boomer74 said:

I just received the NLR HF8 seat. Install went fine, however when I start DCS, I get the following error message. Has anyone seen this or knows how to fix it?

Please remove NLR software and Repair DCS Export script. There is a button for repair in SimShaker for Aviators settings.

[rapid]

So looks like the two softwares cannot co exists, I started getting the same error.

So you can only have one installed at a time?

[Boomer74]

rapid,

That is correct. I went back and uninstalled the HF8 software and SSA software for a clean install. Plugged everything in, installed ONLY the SSA software and everything worked fine. 

[=Andre=]

On 1/28/2024 at 12:30 AM, rapid said:

So looks like the two softwares cannot co exists, I started getting the same error.

So you can only have one installed at a time?

Hi guys,

I've performed some testing with NLR HFS and SimShaker for Aviators having them both installed.

It looks like there is a conflict between NLR and SSA scripts.

If you decided to use SimShaker for Aviators with DCS and not to use NLR HFS you can resolve this conflict by slightly editing Export.lua script in C:\Users\%username%\Saved Games\DCS\Scripts subfolder *.

NLR HFS inserts its line in this file to engage the script:

local HFSlfs=require('lfs');dofile(HFSlfs.writedir()..'Scripts/HFSExport.lua')

If you comment this line out by adding -- in front of it as below:

--local HFSlfs=require('lfs');dofile(HFSlfs.writedir()..'Scripts/HFSExport.lua')

the conflict will be resolved without NLR HFS deletion.

I recommend to edit lua scripts with Notepad++ app since Windows Notepad can damage the file structure.

If you are not fond of editing scripts you can simply replace the file with my one, which is attached.

Hopefully this helps.

 

* - C:\Users\%username%\Saved Games\DCS.openbeta\Scripts subfolder for DCS Open Beta branch correspondently.

Export.lua

[Ala12Rv-Tundra]

19 hours ago, =Andre= said:

Hi guys,

I've performed some testing with NLR HFS and SimShaker for Aviators having them both installed.

It looks like there is a conflict between NLR and SSA scripts.

If you decided to use SimShaker for Aviators with DCS and not to use NLR HFS you can resolve this conflict by slightly editing Export.lua script in C:\Users\%username%\Saved Games\DCS\Scripts subfolder *.

NLR HFS inserts its line in this file to engage the script:

local HFSlfs=require('lfs');dofile(HFSlfs.writedir()..'Scripts/HFSExport.lua')

If you comment this line out by adding -- in front of it as below:

--local HFSlfs=require('lfs');dofile(HFSlfs.writedir()..'Scripts/HFSExport.lua')

the conflict will be resolved without NLR HFS deletion.

I recommend to edit lua scripts with Notepad++ app since Windows Notepad can damage the file structure.

If you are not fond of editing scripts you can simply replace the file with my one, which is attached.

Hopefully this helps.

 

* - C:\Users\%username%\Saved Games\DCS.openbeta\Scripts subfolder for DCS Open Beta branch correspondently.

Export.lua 254 B · 0 downloads

Thanks for your work

[YSIAD_RIP]

Excellent Support - Thanks @=Andre=

[evensen007]

My SimShaker software just went into demo more for no reason. No windows reinstall, hardware refresh, anything. I would really hope Andre moves to a managed key solution instead of having to email him to activate or re-activate. What if something happens to him and our software goes into demo mode for no reason? We just don't get to use the software ever again? keygen or netlicensing would be options. 

Edited February 5, 2024 by evensen007

[=Andre=]

5 hours ago, evensen007 said:

My SimShaker software just went into demo more for no reason. No windows reinstall, hardware refresh, anything. I would really hope Andre moves to a managed key solution instead of having to email him to activate or re-activate. What if something happens to him and our software goes into demo mode for no reason? We just don't get to use the software ever again? keygen or netlicensing would be options. 

 

Reason always exists. It can be not visible, not obvious, etc. but existing.
In your particular case re-enetering the key would be enough I suppose.

In general, if I suddenly become unreachable, incapable, etc. there is a guy, @Sergio on this forum, known as one of my partners, who will be able to help with this. Probably it will take some time for him to get situated.

[rapid]

On 1/28/2024 at 8:00 PM, Boomer74 said:

rapid,

That is correct. I went back and uninstalled the HF8 software and SSA software for a clean install. Plugged everything in, installed ONLY the SSA software and everything worked fine. 

Manny thanks sir.

On 1/30/2024 at 7:32 PM, =Andre= said:

Hi guys,

I've performed some testing with NLR HFS and SimShaker for Aviators having them both installed.

It looks like there is a conflict between NLR and SSA scripts.

If you decided to use SimShaker for Aviators with DCS and not to use NLR HFS you can resolve this conflict by slightly editing Export.lua script in C:\Users\%username%\Saved Games\DCS\Scripts subfolder *.

NLR HFS inserts its line in this file to engage the script:

local HFSlfs=require('lfs');dofile(HFSlfs.writedir()..'Scripts/HFSExport.lua')

If you comment this line out by adding -- in front of it as below:

--local HFSlfs=require('lfs');dofile(HFSlfs.writedir()..'Scripts/HFSExport.lua')

the conflict will be resolved without NLR HFS deletion.

I recommend to edit lua scripts with Notepad++ app since Windows Notepad can damage the file structure.

If you are not fond of editing scripts you can simply replace the file with my one, which is attached.

Hopefully this helps.

 

* - C:\Users\%username%\Saved Games\DCS.openbeta\Scripts subfolder for DCS Open Beta branch correspondently.

Export.lua 254 B · 2 downloads

I appreciate ALL your hard work and support =Andre=

[=Andre=]

11 hours ago, bflo said:

I'm getting the error also.  Tried your export.lua from Andre, but didn't help.  So I uninstalled NLR HFS, & still got the error.  I had no problem with this in FS 2020 though.

 

Sounds strange.

May I see a screenshot what is in the SimShaker for Aviators -> View -> DCS Debug window during the mission when you get this error.

[=Andre=]

11 hours ago, bflo said:

Debug window stays blank.   This is a new DCS install, I ran it with SSA (beta & stable) several times.  I did a DCS long repair.  Got the error as soon play starts, & nothing in debug window.

I guess if you press OK in the error message something will appear there.

[Dedbeat]

Is there a way to keep my settings after an update? I updated yesterday and everything is back at 50, I have a lot of modules and had everything set perfectly. Would rather not have to set it all up again if I don’t have to!

thanks 

[=Andre=]

1 minute ago, Dedbeat said:

Is there a way to keep my settings after an update? I updated yesterday and everything is back at 50, I have a lot of modules and had everything set perfectly. Would rather not have to set it all up again if I don’t have to!

thanks 

I think it was discussed above multiple times.
Recommended way is to create backups from time to time (especially before updates) with the SimShaker for Aviators File menu, restore settings when needed.

Sorry for you loss. Please check \Documents\SimShaker for Aviators  folder. Some backups are created automatically. Maybe you will be able to use one of them to restore your settings.

[=Andre=]

16 minutes ago, bflo said:

• •  

 

Posted 10 hours ago

I guess if you press OK in the error message something will appear there.

 

Nothing happens when I click on the debug window, just a blinking cursor.   This is really strange, the pad works fine testing vibrations, & FS works perfect.

No, I don't mean you should click on the debug window. I mean you press OK in the error message and check the debug window after that.
It looks like there is some data incoming and causing this error. The easiest way is to check the  debug window.

If it doesn't work, you can use a packets sniffer software to see what's coming in, like WireShark. But it's harder.

[Dedbeat]

11 hours ago, =Andre= said:

I think it was discussed above multiple times.
Recommended way is to create backups from time to time (especially before updates) with the SimShaker for Aviators File menu, restore settings when needed.

Sorry for you loss. Please check \Documents\SimShaker for Aviators  folder. Some backups are created automatically. Maybe you will be able to use one of them to restore your settings.

Thanks Andre. Reading my post back I came across a bit rude - I do apologise, it wasn’t my intention! I absolutely love your software and couldn’t fly without it now! Thanks!

[=Andre=]

14 hours ago, Dedbeat said:

Thanks Andre. Reading my post back I came across a bit rude - I do apologise, it wasn’t my intention! I absolutely love your software and couldn’t fly without it now! Thanks!

No worries, Dedbeat. I would also get upset loosing the settings.
SimShaker for Aviators is developed by f4l0.
Happy flying!

[evensen007]

After switching from a buttkicker to a 5.1 seatpad device (SimRacingStudios Ushake6), there are a couple of "Strength SoundModule" settings for aircraft that don't seem to respond to adjusting them up towards 100. The main one I would like to solve is the "Cannon/Gunfire". In the p-51 for example, whether I leave it at 50 or change it to 100, it barely changes anything and barely rattles the seat. I am not using unlimited ammo or anything. Just wondering if I might have a setting misconfigured now that I swapped to the Ushake seat. Most other settings to work well except for catapult launch which has the same issue as above. 

[=Andre=]

7 hours ago, evensen007 said:

After switching from a buttkicker to a 5.1 seatpad device (SimRacingStudios Ushake6), there are a couple of "Strength SoundModule" settings for aircraft that don't seem to respond to adjusting them up towards 100. The main one I would like to solve is the "Cannon/Gunfire". In the p-51 for example, whether I leave it at 50 or change it to 100, it barely changes anything and barely rattles the seat. I am not using unlimited ammo or anything. Just wondering if I might have a setting misconfigured now that I swapped to the Ushake seat. Most other settings to work well except for catapult launch which has the same issue as above. 

It sounds strange that you can't adjust the effect.

Regarding low vibration intensity, the gun fire samples I've made are of frequency 20 Hz. It may be too low for a particular shakers type.

Please try to use the attached sample which I made of 50 Hz.

You will want to put it in the \Documents\SimShaker Sound Module samples\Customized\6 subfolder. Assuming that you enabled 5.1 pattern in SimShaker Sound Module settings.

[Jandar]

Am 25.8.2023 um 15:58 schrieb =Andre=:

Hello Jandar,

what if you try to turn up this effect strength in the SimShaker for Aviators settings?

Version 2.7.2 – beta release

Added

Changed

• DCS: Spitfire RPM effect reworked. Please provide feedback!
• DCS: F18 RPM effect reworked. Please provide feedback!

Dear Andre,

install the beta 2.7.3, test starting Spit engine, now the effects runs under 1000rpm perfectly!!

great job, thanks

p.s. can't test f18, no modul

[f4l0]

8 minutes ago, Jandar said:

Version 2.7.2 – beta release

Added

Changed

• DCS: Spitfire RPM effect reworked. Please provide feedback!
• DCS: F18 RPM effect reworked. Please provide feedback!

Dear Andre,

install the beta 2.7.3, test starting Spit engine, now the effects runs under 1000rpm perfectly!!

great job, thanks

p.s. can't test f18, no modul

Thanks for the feedback. Just some notes, I'm the dev of SSA

[jgreg]

I use a Jetseat force-feedback seat. All FF works well with the Gazelle (rotor vibration, guns, missiles, g-effect etc.) except one thing; when I land there is no 'judder' through the seat. All other DCS helos have this, and it's a good thing to have, as you get some feedback when your skids touch the ground. I have approched Polychop regarding the issue, but they are saying that the problem probably lies within the SSA interface. Any chance you could take a look please?

[Polychop Simulations]

17 minutes ago, jgreg said:

I use a Jetseat force-feedback seat. All FF works well with the Gazelle (rotor vibration, guns, missiles, g-effect etc.) except one thing; when I land there is no 'judder' through the seat. All other DCS helos have this, and it's a good thing to have, as you get some feedback when your skids touch the ground. I have approched Polychop regarding the issue, but they are saying that the problem probably lies within the SSA interface. Any chance you could take a look please?

@f4l0If there is anything we can do to mitigate this, please let me know. 

[Hammer1-1]

also quick question: is the Jet Seat considered a 5.1 / 7.1 surround sound system? Im trying to troubleshoot some audio and this would be helpful to know if it pulls a signal from an onboard sound card.