Visit Captain Sim web site  
  Welcome, Guest. Please Login or Register

 

Page Index Toggle Pages: 1 Send TopicPrint
V1, Vr, V2 Callout (Read 78 times)
musiol1
Full Member
*
Offline



Posts: 27
Joined: Jan 1st, 2018
V1, Vr, V2 Callout
Jun 13th, 2018 at 11:50am
Print Post  
One thing that i want to mention is that the callout are pronounced too long. Example V1 = 129, VR = 132, V2 = 137. In this case, when I reach 129, I hear the V1 command, but the VR I hear at 140 instead of at 132.. Perhaps they should be pronounced much faster to match the actual speeds calculated by the MCDU.
  
Back to top
 
IP Logged
 
Shom
Full Member
*
Offline



Posts: 28
Joined: Jun 2nd, 2018
Re: V1, Vr, V2 Callout
Reply #1 - Jun 13th, 2018 at 12:33pm
Print Post  
musiol1 wrote on Jun 13th, 2018 at 11:50am:
One thing that i want to mention is that the callout are pronounced too long. Example V1 = 129, VR = 132, V2 = 137. In this case, when I reach 129, I hear the V1 command, but the VR I hear at 140 instead of at 132.. Perhaps they should be pronounced much faster to match the actual speeds calculated by the MCDU.


+ 1 the call outs are way off
  
Back to top
 
IP Logged
 
Thantheleon
CS Team
*
Offline



Posts: 1919
Location: Toronto, Canada
Joined: Nov 7th, 2005
Gender: Male
Re: V1, Vr, V2 Callout
Reply #2 - Jun 13th, 2018 at 2:18pm
Print Post  
musiol1 wrote on Jun 13th, 2018 at 11:50am:
One thing that i want to mention is that the callout are pronounced too long. Example V1 = 129, VR = 132, V2 = 137. In this case, when I reach 129, I hear the V1 command, but the VR I hear at 140 instead of at 132.

Done on purpose to prevent the sounds overlapping. The next sound will not start until the previous one is done.
  
Back to top
IP Logged
 
Alex T
Full Member
*
Offline



Posts: 3
Joined: Jun 21st, 2015
Re: V1, Vr, V2 Callout
Reply #3 - Jun 14th, 2018 at 8:59pm
Print Post  
Thantheleon wrote on Jun 13th, 2018 at 2:18pm:
musiol1 wrote on Jun 13th, 2018 at 11:50am:
One thing that i want to mention is that the callout are pronounced too long. Example V1 = 129, VR = 132, V2 = 137. In this case, when I reach 129, I hear the V1 command, but the VR I hear at 140 instead of at 132.

Done on purpose to prevent the sounds overlapping. The next sound will not start until the previous one is done.


So that's it just deal with it being almost 10 knots late? Or how about the .wav be shortened and it won't overlap?
  
Back to top
 
IP Logged
 
Thantheleon
CS Team
*
Offline



Posts: 1919
Location: Toronto, Canada
Joined: Nov 7th, 2005
Gender: Male
Re: V1, Vr, V2 Callout
Reply #4 - Jun 16th, 2018 at 2:36pm
Print Post  
Alex T wrote on Jun 14th, 2018 at 8:59pm:
Thantheleon wrote on Jun 13th, 2018 at 2:18pm:
musiol1 wrote on Jun 13th, 2018 at 11:50am:
One thing that i want to mention is that the callout are pronounced too long. Example V1 = 129, VR = 132, V2 = 137. In this case, when I reach 129, I hear the V1 command, but the VR I hear at 140 instead of at 132.

Done on purpose to prevent the sounds overlapping. The next sound will not start until the previous one is done.


So that's it just deal with it being almost 10 knots late? Or how about the .wav be shortened and it won't overlap?


The V speeds are often just 1-2knots apart, so there's a fraction of a second for two wavs to be played.
Anyways, the callouts are nothing but a nice touch. You are a captain, you got your instruments. Do your job   Wink

  
Back to top
IP Logged
 
Page Index Toggle Pages: 1
Send TopicPrint
 
  « Board Index ‹ Board  ^Top