Just a few things I'd like to request to be considered for addition to the final patch if possible. Nothing too major, but all little things that would improve the experience for me at least. Wilco 737PIC version.*Add request to start boarding(like maddog version)...play boarding sounds(would be great for airports not covered by AES).*FO turns on his clock after engine start. Usually one clock is set on startup and the other on the takeoff roll.*Ability to read out dep/app briefings. Could simply be "Are you ready for the breifing?" then an FO response. Trigger phrase after briefing complete could be "Is that understood/Any questions".*Ability to connect/disconnect external power via voice. It's just a clickspot on the overhead to do this so should be possible.*Ground crew always disconnects on their own when parking brakes are set after pushback. I'd like them to remain connected and wait for me to give them the all clear to disconnect.*"Three green" should be mentioned after gear down. Either the FO calls it after the lights come on, or the Captains response during the landing checklist should contain it rather than just "Down".Also one quick question that I can see mentioned in the manual. On the APP checklist the FO makes reference to something like approach or Vspeed being 117 knots. Were should I set the approach speed so that he reads this out correctly? Thanks

Some of those requests are airline specific. I'll see if I can add the other requests. No promises though as my sched is pretty busy.Best,

Good stuff and no rush. The connect/disc external power would be my choice if I could only pick one (shameless hint). Regarding my last question, do you remember if there is somewhere to set he approach vref so the FO reads it correctly during his descent checklist?Also had a problem today flying online. Voice wasn't being disabled when I was transmitting on Squawkbox as the patch notes describe. This led to some uncommanded manoeuvres happening which I had to react to very quickly so as to not get scolded by the controllers. Should voice be automatically disabled when the PTT button in SB is pressed or do I need to set it up somehow? The patch notes didn't elaborate on this feature really.

Good stuff and no rush. The connect/disc external power would be my choice if I could only pick one (shameless hint). Regarding my last question, do you remember if there is somewhere to set he approach vref so the FO reads it correctly during his descent checklist?Also had a problem today flying online. Voice wasn't being disabled when I was transmitting on Squawkbox as the patch notes describe. This led to some uncommanded manoeuvres happening which I had to react to very quickly so as to not get scolded by the controllers. Should voice be automatically disabled when the PTT button in SB is pressed or do I need to set it up somehow? The patch notes didn't elaborate on this feature really.

Voice should auto mute when using Squawkbox for FS9. It's not possible in the FSX version of Squawkbox to do an auto-mute. FS9 only.Best thing is to assign the mute key to the same key used for voice x-mit (push to talk).Cheers,

Voice should auto mute when using Squawkbox for FS9. It's not possible in the FSX version of Squawkbox to do an auto-mute. FS9 only.Best thing is to assign the mute key to the same key used for voice x-mit (push to talk).Cheers,

OK thanks, I'll try assigning the mute button to the same as the SB PTT one and see how that goes. It is fs9 I'm using though so not sure why it wasn't working. Perhaps an x64 issue.Just waiting for an answer about that approach VREF now?

Just waiting for an answer about that approach VREF now?

I believe the VREF he presents is calculated automatically based on your current gross weight. Are you saying the VREF is not correct?

That can't be the case because it's been read out as 117kts on every flight I've done with varying loads. The actual Vref for the flights has been near 125+ so 117 is way off.

That can't be the case because it's been read out as 117kts on every flight I've done with varying loads. The actual Vref for the flights has been near 125+ so 117 is way off.

That's one for Bryan then! Maybe the weight is not being read correctly for some reason. Could you list your operating system and other specs?

Sure, specs in sig. Registered FSUIPC and only other programs running that may interfere are ASA. It's not really a big deal...I just wanted to know whether I was supposed to set it somewhere or not, just so I could stop looking for the click spot!

[email protected], 8Gb 1066DDR2, GTX280@702/1402/1202, ASUS Rampage Extreme X48, Windows 7 Ultimate x64

Cheers

Update with regard to the mute button problem. I assigned it to the same joystick button as my squawkbox PTT button and the problem persists. I'm somewhat off the original topic now so not sure if this would all be better in another thread. Please move it into one if you think so.When the button is pressed, the "M" symbol does appear on the panel to indicate that the mute function is active, however it's not actually working at all. I've done three flights today, all of which suffered major problems because of this. What tends to happen is that when speaking to ATC, with the mute light illuminated on the main panel, I get a FO response of "OK" and then one of the MCP values starts just spinning round and round. Voice control actually crashes at this point and I am unable to take control of the MCP or regain voice control until I quickly switch voice off and on again on the main FS2Crew panel. You can imagine the workload when trying to do all this as well as follow an ATC heading and decent instruction, find time to set the QNH, and reset the MCP to the values that were present before the FO had a tantrum!Given that this has happened on every flight today, I'm going to have to stop flying online for the time being until a solution can be found. Guess I can use the time to go back to voice training to try and teach the computer what the word "on" sounds like in a non American accent!

HiDid you install SP1 (public beta)? http://forums1.avsim.net/index.php?showtopic=277333Also, check this. After you have initialized the voice engine by left clicking the PFD, go back to your audio properties and check that you microphone value has not been reset to full. In XP it has a tendency to do this when speech recognition is initialized, not sure about W7. Readjusting it back to a sensible level may help with the spurious "on" words..

SP1 is installed (don't think there was a mute function in the initial release version).No need to worry about the "on" thing. I just need to run the training again as it works perfectly well if I say "on" in an American accent.

Hi I have also noticed some of the speeds being a bit off .. its not a problem with the VSPEEDs as you can change them , but the VREF is mostly wrong . Rich

Hi I have also noticed some of the speeds being a bit off .. its not a problem with the VSPEEDs as you can change them , but the VREF is mostly wrong . Rich

Problem with VREF is that I can't read it out of the FMC, so it has to work on a table I created based on Gross Weight.It won't necessarily match up with what is displayed in the FMC.Best,