SimShaker for DCS World Sound Mode Expansion - Discussion

[geert]

Not actually a conflict. But it explains a lot and helps to fix the issue. Thank you.

You can stop flashing by pausing DCS.

 

Now I'd like to get more details regarding Sabre.

 

Just tested again. No effects in the Sabre, however, after I've taken off, there´s just sometimes a "bumb". Seems to be no logic or patern in that whatsoever.

I also noted now, that I got this message about a conflict in the LOG in the Huey with full RPM only when I use those custom samples (those posted by Olaf that I have been using for months now). When I don´t use those samples, there´s no mention of "already playing". I must also note that I was never satisfied with the standard enhanced motor whirl effect and always used those custom samples, so I'm not sure whether it´s really that different now, might have been something wrong with that effect for a longer time.

I copied some bits and pieces from the log of the sound module to some text files in case you might give you some more relevant info. See atachment.

Thanks.

Simshaker beta LOG Huey custom samples.txt

Simshaker beta LOG Huey.txt

Simshaker beta LOG Sabre.txt

[Chief1942]

Geert,

I too get that"bump" in the A-10C whenever I start a mission at a turning point or another in the air point. Haven't noticed it on the ground. It is something new and I chalked it up to the different DCS updates where some sound issue may have changed that causes the "bump". Not a big deal but it has got my attention.

[geert]

Geert,

I too get that"bump" in the A-10C whenever I start a mission at a turning point or another in the air point. Haven't noticed it on the ground. It is something new and I chalked it up to the different DCS updates where some sound issue may have changed that causes the "bump". Not a big deal but it has got my attention.

 

Chief,

 

I noticed that too in the A-10C, but just one "bumb" would be no problem, what happens in my case in the Sabre (maybe other planes too, haven´t tested them all) is that this "bumb" comes every few seconds, then a few seconds quiet and then...well, that´s what I meant with no pattern.

 

I was wondering, am I the only one having these issues? Is this beta version working perfectly for others? Just some confirmation would be appreciated.

[=Andre=]

I was wondering, am I the only one having these issues? Is this beta version working perfectly for others? Just some confirmation would be appreciated.

 

Most pilots use stable SimShaker version. Beta works with errors. That's quite normal.

[geert]

I have 2 installations of DCS 2.0, the one I usually use was copy-pasted to a new SSD. I tested beta simshaker on the other DCS 2.0 version (the one which was properly installed) and then it works much better: Sabre effects work and probably a lot more modules work, but tested only superficially. But the problem with the enhanced motor whirl persists. Even when I switch to those old samples, there still is this mentioning of "already playing" bug in the LOG. Like I already mentioned, somehow the normal enhanced motor whirl just works very bad for me and I only like that custom sample from Olaf. Would it be possible for me to overwrite the normal enhanced motor whirl with the custom one so that I can also use the new effects?

Cheers.

[=Andre=]

Hi geert,

good news, thank you :)

I hope in the nearest beta update "already playing" problem will be fixed.

And yes, you certainly can overwrite my or Olaf's samples with your own ones. I would recommend to make h_2_0_1.wav sample duration shorter than 100 ms. You can see detailed "how to" here

[geert]

Hi geert,

good news, thank you :)

I hope in the nearest beta update "already playing" problem will be fixed.

And yes, you certainly can overwrite my or Olaf's samples with your own ones. I would recommend to make h_2_0_1.wav sample duration shorter than 100 ms. You can see detailed "how to" here

 

I adjusted the 2 rotor samples to make them shorter (Olaf´s samples are very long) to below 100ms. The sound wave was actually not completely flat yet, but that still didn´t solve it since 100ms is way to long for this particular effect. But that experiment showed to me clearly what the problem is. Hope you can get it back to what it was, because this problem isn´t there with previous version or non-beta version.

[=Andre=]

But that experiment showed to me clearly what the problem is.

 

And what the problem is? Would you please share that?

[geert]

And what the problem is? Would you please share that?

 

Just that when an effect / sample is being played, simshaker won´t play that sample (or another one probably) until the sample that is playing is completely finished. That´s what the "already playing" error means I guess :doh: I guess you already knew that. What´s strange is that simshaker didn´t do that previously. it would just start the sample again without waiting for it to finish. Even if you manually play the sample with the soundmodule now, it only plays the sample again when the current sample is finished.

[=Andre=]

Just that when an effect / sample is being played, simshaker won´t play that sample (or another one probably) until the sample that is playing is completely finished.

Just the same sample.

That´s what the "already playing" error means I guess :doh: I guess you already knew that.

I knew that, but I'm trying to understand why when you've cut the sample you still doesn't like the resulting effect. If I took it right.

 

What´s strange is that simshaker didn´t do that previously.

SimShaker is an evolving piece of software.

 

it would just start the sample again without waiting for it to finish. Even if you manually play the sample with the soundmodule now, it only plays the sample again when the current sample is finished.

I need more control over playing sample to do better effects. And that's the same way as JetSeat acts.

[geert]

I knew that, but I'm trying to understand why when you've cut the sample you still doesn't like the resulting effect. If I took it right.

 

I took the sample and made it as short as possible by simply removing the long silence in the end. That made it 90-100ms long. When the rotor RPM is on full power now, it seems that the sample is still too long, resulting in much less "effects per second" than was the case without the error. Am I making any sense? :)

 

 

SimShaker is an evolving piece of software.

Great!

[=Andre=]

When the rotor RPM is on full power now, it seems that the sample is still too long, resulting in much less "effects per second" than was the case without the error.

Hi geert,

Try to make it 50 ms long.

[geert]

Hi geert,

Try to make it 50 ms long.

 

I tried that yesterday actually, and it didn't work. Pretty strange: when I play the sample I made (I thought it was around 40ms long) in any audio player or audacity, you hear the loud bass sound which you expect. However, when I use the soundmodule of simshaker to play the sound, you just hear a very silent "click" sound or something like that. And in game it is the same: no bass sound, just small tiny barely audible clicks. So something is happening in the soundmodule it seems.

[=Andre=]

I tried that yesterday actually, and it didn't work. Pretty strange: when I play the sample I made (I thought it was around 40ms long) in any audio player or audacity, you hear the loud bass sound which you expect. However, when I use the soundmodule of simshaker to play the sound, you just hear a very silent "click" sound or something like that. And in game it is the same: no bass sound, just small tiny barely audible clicks. So something is happening in the soundmodule it seems.

Hi geert,

hard to believe that one can hear very low frequency sound that is just 40ms long as the loud bass sound. That's rather a very silent "click" sound or something like that.

But, anyway, beta version update is published and I think you will want to try again Olaf's original sample.

[dissignator]

Nice! Where can i download the Beta-Version? :-)

[=Andre=]

Nice! Where can i download the Beta-Version? :-)

 

Do you have full set activated Sound Module or JetSeat?

[dissignator]

Sure! :-)

[=Andre=]

SimShaker update 1.1.1.6 is published :xmas:

http://dreamsimteam.blogspot.ru/2015/12/simshaker-for-dcs-world-and-falcon-bms.html

 

Attention Sound mode users: since we have new gain sliders for sound mode, please, customize their values once again. It's recommended to keep not used JetSeat Gain Level sliders values at 50%.

[wasyl00]

SimShaker update 1.1.1.6 is published :xmas:

http://dreamsimteam.blogspot.ru/2015/12/simshaker-for-dcs-world-and-falcon-bms.html

 

Attention Sound mode users: since we have new gain sliders for sound mode, please, customize their values once again. It's recommended to keep not used JetSeat Gain Level sliders values at 50%.

 

 

• Added Keep Awake Buttkicker Amp feature (siwtched off by default)
  

woohooo thanks for this!

[=Andre=]

• Added Keep Awake Buttkicker Amp feature (siwtched off by default)
  

woohooo thanks for this!

 

You are welcome :xmas:

That was a bit tricky to find the way keep BK alive, but it seems I've managed.

[Gisen]

I'm confused as usual since I'm using the other package, the racing one that includes dcs world - is there an update for that or should I have both packages?

[=Andre=]

Hi Richard,

the update will be available soon.

You can use both packages if you want to get it faster.

[tester]

Hi. Persons interested to download a manual - we go here.

[=Andre=]

Thanks for the feedback Michael.

Can you tell me was landing gear damaged or not?

[=Andre=]

Yes, it was. It was in BMS.

 

OK. I will take care of it.