Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

different way to handle soft mute

Featured Replies

Bryan.I am one of the many persons out there that cannot get the soft mute to work, have a request. I dont know if its just me, but i think i may remember the way the soft mute works in the maddog version is when you are using VATSIM, when you press the transmit key the product detects this and activates the soft mute? If that is so, then could you also add that feature to the 767 version?

Bryan Richards

 

"People depend so much on automation that they forget how to get the automation to work." B.W.

  • Commercial Member
Bryan.I am one of the many persons out there that cannot get the soft mute to work, have a request. I dont know if its just me, but i think i may remember the way the soft mute works in the maddog version is when you are using VATSIM, when you press the transmit key the product detects this and activates the soft mute? If that is so, then could you also add that feature to the 767 version?
Hi Bryan,Soft mute is in the 767 Version.Make sure you have the latest SP installed.Remember to assign the Soft Mute key via the FS2Crew 767 Config Manager.Use the LEFT CONTROL keyboard button as a test.Cheers,
  • Author

Bryan trust me, i've done everything. Soft mute doesnt even work with the maddog version for me. It only works when im using Squawkbox on VATSIM and im tuned to a voice channel, when i press the transmit key i have assigned in squawkbox, thats the time the softmute works (for the maddog version), if i change to a frequency that is not voice enabled, then soft mute doesnt work. I dont mind because all of my flying is done on VATSIM, so when there is no ATC to talk to i just use the hard mute option. Im just asking in the next patch please add that feature, as it would help us vatsim pilots a lot.

Bryan Richards

 

"People depend so much on automation that they forget how to get the automation to work." B.W.

  • Commercial Member
Bryan trust me, i've done everything. Soft mute doesnt even work with the maddog version for me. It only works when im using Squawkbox on VATSIM and im tuned to a voice channel, when i press the transmit key i have assigned in squawkbox, thats the time the softmute works (for the maddog version), if i change to a frequency that is not voice enabled, then soft mute doesnt work. I dont mind because all of my flying is done on VATSIM, so when there is no ATC to talk to i just use the hard mute option. Im just asking in the next patch please add that feature, as it would help us vatsim pilots a lot.
Hi Bryan,I just tested soft mute in the LDS 767 and it worked for me.I said "Set speed 210" with Soft Mute enabled (red M visible) and speed 210 was not set.I then said "Set speed 210" with Soft Mute not pressed, and the FO set speed 210.Please confirm this:1. Open the CFG file that contains the Soft Mute assignment.It's located here:Microsoft Flight Simulator X\FS2Crew2010\Versions\LDS767\FS2CrewInputMapper.CFGOpen it with Notepad.Mine is set to Left Control so it looks like this:FS2_Main=LCONTROLIt definitely works for me.If you don't see an assignment in the CFG file, please ensure UAC is fully disabled on your system then try-reassigning the Soft Mute key via the FS2Crew 767 Config Manager.Cheers,
  • 1 month later...

Hello allI'm expieriencing a similar problem altough I'm using a Saitek Pro flight yoke and there is no LCTR on this Yoke. I can assign it to Home and it works when pressing it on the keyboard. But I am using the Red Button as PTT for Vox atc and then it should mute fs2crew... any advice?Regards simon

EDITIgnore me...had the same problem but found for some reason, mute works only with "NUM-". Doesn't work with anything at all other than that. bit weird but at least its working now!

i7 2600k @ 5.1Ghz, ASUS Sabertooth P67, 8GB Corsair Vengeance DDR3 1600Mhz, EVGA GTX 580 @ 950MHz, OCZ Vertex II 240GB, ASUS Xonar DG, Thermaltake Toughpower XT 875W PSU, Antec KÜHLER 620 W/C, Corsair 600T SE White

 

My FS9 Screens - http://fs9screens.blogspot.com/

 

Callum Richardson

  • Commercial Member
EDITIgnore me...had the same problem but found for some reason, mute works only with "NUM-". Doesn't work with anything at all other than that. bit weird but at least its working now!
That's rather odd. I always use LEFT CTRL.But if it works for you that's all that counts.Cheers,

Yep defiantly a bit odd. Could never use LControl as it's un-assignable through fsuipc. Looks like I'm going to get the same problem with this one as I did with the 737PIC version through Bryan. FO is still adjusting values on the MCP while I'm reading back ATC instructions and the M symbol is illuminated. Haven't had any runaways though yet so should be more manageable than it is for me with the 737.

i7 2600k @ 5.1Ghz, ASUS Sabertooth P67, 8GB Corsair Vengeance DDR3 1600Mhz, EVGA GTX 580 @ 950MHz, OCZ Vertex II 240GB, ASUS Xonar DG, Thermaltake Toughpower XT 875W PSU, Antec KÜHLER 620 W/C, Corsair 600T SE White

 

My FS9 Screens - http://fs9screens.blogspot.com/

 

Callum Richardson

  • Commercial Member
Yep defiantly a bit odd. Could never use LControl as it's un-assignable through fsuipc. Looks like I'm going to get the same problem with this one as I did with the 737PIC version through Bryan. FO is still adjusting values on the MCP while I'm reading back ATC instructions and the M symbol is illuminated. Haven't had any runaways though yet so should be more manageable than it is for me with the 737.
Hi,You shouldn't ever get runaways because I figured out a way to ensure they can't happen in the 767 version.As for mute not appearing to work... Very hard to say... Is your FS window "in focus"... if you see the "M" icon Mute is running.Follow-up... I'm wondering if this is FSUIPC related... Maybe when you hold the button down, FSUIPC doesn't hold the button down "steadily"... maybe it "momentarily" releases the button but it happens so fast that it's imperceptible, but that fraction of a second is just enough time for the voice command to slip through.Can you try again, but don't use FSUIPC... so use a key command, not a joystick one.Cheers,

I think you're probably spot on with that theory to be honest. I remember testing the 737 version and the problem never occurred when using the keyboard button. Not sure if there's any way to edit the repeat rate for a keypress in FSUIPC however. I'll probably leave a message over at the forums there and see if Mr Dowson can help out. Will let you know the outcome.Great that you've sorted the runaway problem! Any plans to add this to a patch for the 737?

i7 2600k @ 5.1Ghz, ASUS Sabertooth P67, 8GB Corsair Vengeance DDR3 1600Mhz, EVGA GTX 580 @ 950MHz, OCZ Vertex II 240GB, ASUS Xonar DG, Thermaltake Toughpower XT 875W PSU, Antec KÜHLER 620 W/C, Corsair 600T SE White

 

My FS9 Screens - http://fs9screens.blogspot.com/

 

Callum Richardson

Create an account or sign in to comment

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.