The ButtKicker device responds to both frequency and volume of our synthesised audio control which now includes frequency mixing and we are currently testing the synchronised Bump Aircraft turbulent bumps and frequency/volume modulated turbulent vibrations, again all synchronised with DHM and coordinated with the LWE.

 

Please read our latest OpusFSX_ButtKicker.pdf document and follow the ButtKicker audio control development on our SimForums. I also post news here when I have a chance.

 

The testing of the Bump Aircraft turbulent bumps or jolts and general turbulent vibrations is going very well. We will aim to have a new beta available soon but with the latest improved turbulent and Bump Aircraft handling we may also be posting a new release update.

 

Stephen

 

P.S.

 

No need for the client audio output, the low cost Sound Blaster X-Fi Go PRO USB sound stick is ideal for ButtKicker control wired direct from the audio/headset output of the USB sound card into the ButtKicker Power Amp.

 

Stephen

do i need to install the latest update if i only have 1 buttkicker?

 

Yes, you will see the benefit of frequency mixing with only one BK.

 

Cheryl

Hi Stephen,

 

The latest beta FSXserver.exe crashed with the following. It happens when FSX is launching when the BK vibrates a few times like a testing phases from Opus BK module.

 

Faulting application name: FSXSERVER.EXE, version: 3.3.4.9, time stamp: 0x527b6d7b
Faulting module name: wdmaud.drv, version: 6.1.7601.17514, time stamp: 0x4ce7ba26
Exception code: 0xc0000005
Fault offset: 0x00010e8e
Faulting process id: 0x%9
Faulting application start time: 0x%10
Faulting application path: %11
Faulting module path: %12
Report Id: %13

OK, that's an error in the Windows audio out driver or library which is rather fragile.

 

Can you delete your OpusFSX\ButtKicker.dat file and then after running FSXSERVER reconfigure the ButtKicker settings enabling only one BK device. That should do it.  The vibrations on launch is the audio out and BK initialisation and test outputs.

 

Stephen

OK, that's an error in the Windows audio out driver or library which is rather fragile.

 

Can you delete your OpusFSX\ButtKicker.dat file and then after running FSXSERVER reconfigure the ButtKicker settings enabling only one BK device. That should do it.  The vibrations on launch is the audio out and BK initialisation and test outputs.

 

Stephen

Yup that solved it. Thanks.

OpusFSX Beta Version 3.36.0 is now available for download on our website.

 

Remember when installing the OpusFSX_v336_Beta.msi file you must uninstall your current version before installing the new version (do not delete your previous \OpusFSX installation folder).

 

After installing please check all the settings in your Configure and Weather dialogues. You can download from http://www.opussoftware.co.uk/opusfsi/downloads.htm

 

An 'Enable ButtKicker Audio Control' option has been added to the FSXSERVER configuration which defaults to OFF.

 

The general turbulence effects have been added to the ButtKicker audio control. The general turbulence threshold or cutoff point can be set by adjusting the 'Cutoff' parameter in the Options dialog. A setting of 0% will result in a threshold equal to the average turbulence deflection for the specified DHM axis. A setting of 50% will set the threshold to the mid point between the average and maximum DHM deflection. A setting of 100% will disable the general turbulence effects altogether.

 

Modified the audio device control and audio data usage to help improve the stability of the Microsoft 'wdmaud' audio output driver mapper.

 

The FSXSERVER High Priority option has now been removed from the Configure dialog.

 

Regards

Stephen

 

ButtKicker Beta Testers ...

 

You will need to enable the ButtKicker audio control in the Configure dialog then configure your ButtKicker audio device settings from the start again. Please set the Opus Master Volume to between 70% and 100% and set all Defaults for the initial tests.

 

Cheers

Stephen

Hi Stephen,

 

I have one observation with the previous build. That is the roll out after touch down for heavy aircraft...after touch down the bk shakes at constant amplitude untill speed of aircraft drops to near 15 knots. Means the shaking amplitude do not match the speed decrease.

 

Roll for take off do not have the same issue.

Thanks, this will be sorted when we implement the landing effects. At present after landing the software is in landing mode until slowed down where it switches over to normal taxiing mode. Since the landing effects have not been implemented yet the audio control doesn't change much until the mode changes. When we implement the landing effects it will most likely be a combination of roll out and bump effects, so there will be a noticeable change in BK control as you slow down during the roll out.

 

The next phase will also make the BK control more seamless by not relying on the DHM modes and determining its own mode of operation. That way there won't be a pause when switching views and the BK effects will continue even after displaying a non-DHM view such as a panel view.

 

Stephen

 

I should have also mentioned take off is different in that the taxiing mode stays active until the aircraft becomes airborne.

 

Stephen

Thanks, this will be sorted when we implement the landing effects. At present after landing the software is in landing mode until slowed down where it switches over to normal taxiing mode. Since the landing effects have not been implemented yet the audio control doesn't change much until the mode changes. When we implement the landing effects it will most likely be a combination of roll out and bump effects, so there will be a noticeable change in BK control as you slow down during the roll out.

 

The next phase will also make the BK control more seamless by not relying on the DHM modes and determining its own mode of operation. That way there won't be a pause when switching views and the BK effects will continue even after displaying a non-DHM view such as a panel view.

 

Stephen

 

I should have also mentioned take off is different in that the taxiing mode stays active until the aircraft becomes airborne.

 

Stephen

Sounds great! Thanks Stephen.

Hey guys, what exact Buttkicker device do recommend for our simming purpose? For some reason Butkicker Gamer is out of stock everywhere.

We recommend ButtKicker Gamer 2 along with a Sound Blaster X-Fi Go PRO USB sound stick for the audio output.

 

Stephen

We recommend ButtKicker Gamer 2 along with a Sound Blaster X-Fi Go PRO USB sound stick for the audio output.

 

Thank you. Will order it.

 

Any updates on the topic since November?

Any new features implemented? 

Best to check for the latest updates on our SimForums. Reverse thrust effects have been added and we are working on the landing effects, also have plans to include additional spoiler/speed brake deployed effects.

 

Stephen

Beta Version 3.44.0 has been posted on our website. This beta includes the following ButtKicker additions,

 

ButtKicker initialisation reduced from four to three passes.
ButtKicker test messages are no longer displayed the Spy window.

 

Spoiler (speed brake) deployment effects have been added to the ButtKicker audio control, these airborne effects are dependent on the current position of the spoilers. The parameters effecting the DHM and ButtKicker landing effects now change dynamically depending on the maximum experienced body acceleration, used as a measure of the heaviness of the landing and initial roll out.

 

Landing and initial roll out effects have been added to the ButtKicker audio control, these effects need the OpusFSX DHM to be active and are dependent on the heaviness of the landing.

 

Stephen :smile:

My buttkicker died for the 5th time. I've had enough of this contraption. 

 

If yours has lasted, good on you...I must be really bad in looking after my electronics!