itsjase

Did you guys read the manual?

The wind option is meant to be 0 inside the cockpit, it's meant to simulate wind in open cockpit aircraft, you aren't going to be feeling any wind inside a closed cockpit.

The first 3 are the ones that make the most difference, as they affect how the plane reacts to G-Forces from turbulence, wind, etc.

Setting the first three sliders to 3.0 gives me the effect I like, turbulence is a lot more noticeable, and it's not too sensitive to manual inputs.I found the defaults of 1.0 way too weak, but again this varies with person.

16 hours ago, Bluestar said:

There are numerous things that can determine deck angle including CG, weight, power settings, flap settings and weather just to name a few.   Also a lot of aircraft have a two stage rotation to avoid tail strikes.  

Grace and Peace, 

Sorry maybe its deck angle then? I'm assuming the PFD shows the current deck angle? So if the wings are mounted on an angle the FPV will always be further below on the PFD.

From a lot of YouTube videos I've seen, it seems the 748 has a much higher angle of attack than the 744, especially during climb and approach.

Is this by design? I've seen climbs where the nose is at 15 degrees and the fpa is only 2-3 degrees climb. Looks like its always on the edge of stalling.

Not really a bug but I've noticed whenever i have the map up pilot2atc is using around 10% cpu. If i minimise the map or minimise pilot2atc cpu usage drops to below 2-3%.

Is there a way to maybe reduce map refresh update rate? Or something else so I can keep the map open with lower cpu usage?

Even if the map only updated every 3 or 5 seconds would be more than enough.

Thanks for that Dave, will disregard the passing altitude and just follow restrictions if it won't call me.

I might've worded my question badly. I understand how descent rates work, but I'm wondering what it's best to set it at in Pilot2ATC because like you mentioned it changes considerably throughout the descent.

460Kts at 3fpa is 2300fpm like you said

but then when you get down lower and are travelling slower

250kts at 3fpa is 1250fpm.

Putting the descent rate in Pilot2ATC at 1500fpm seems to average it out and give the correct TOD but then the "pass at" altitude for the STAR entry waypoint is a bit high.

Is there a recommended way of setting descent rates? As for example on Airliners the descent rate will change quite a bit due to the big changes in speed throughout the descent.

For example on an A320 or 737 if I set the descent rate to 1500fpm the top of descent matches quite closely with the FMC's calculated TOD but the "pass WAYPOINT at " altitude for the STAR will be quite high. If I set the descent rate to 1200fpm I get called to descend much earlier, but the STAR waypoint passing altitude is much nicer.

With 1200fpm I also tend to sometimes get vectored off the STAR, is this cause 1200fpm isn't enough to follow the STAR altitude restrictions?

Thanks,

Jason

On 11/17/2018 at 8:57 PM, CKAJCA said:

If ATC want me to follow the SID routing but ignore any altitude restrictions then what phraseolgy would be used?

They would say something like: DESCEND VIA STAR TO (level), CANCEL LEVEL RESTRICTION(S) AT (point(s))

I know it's still "experimental" but is it possible to make an assignment to open the replay window. My chaseplane is minimized 99% of the time and it would be aweseome If I didn't have to alt tab and open it up to open the replay window.

Thanks

I've tried the same flight plan multiple times, works probably 50% of the time. Everything exactly the same each time.

Half way through my last three flights Vox has just stopped functioning. No more instructions and the panels don't respond to keyboard inputs.

Checked the error log and all I see is a bunch of these each time it stopped working.

Anyone else having similar issues?

$$$$ Thread time overun : 
   at System.Environment.GetStackTrace(Exception e, Boolean needFileInfo)
   at System.Environment.get_StackTrace()
   at com.intworkings.voxatc.ThreadCheck.Sleep(Int32 milliSecs)
   at com.intworkings.voxatc.FSUIPCInt.ProcessSimconMessages()
   at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server, Object[]& outArgs)
   at System.Runtime.Remoting.Messaging.StackBuilderSink.AsyncProcessMessage(IMessage msg, IMessageSink replySink)
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
   at System.Threading.ThreadPoolWorkQueue.Dispatch()

The voice cutting off issue from 7.41 which was acknowledged over a year ago is still present. Saddens me 😞

If you're flying a tubeliner or fast plane make sure you increase your vector leg length in the settings. It defaults at 1nm which requires turns and descents which aren't easy to pull off on faster aircraft.

Setting this to 5nm makes vectors much better in my opinion.

Awesome! Thanks so much!

Any ETA on the update? I've only got 4 days left on my trial 😞

I've noticed for some airports the recommended STAR is none even when its direct from my last waypoint.

An example is at Dubai INTL, my imported flight plan ends and the VUTEB waypoint, which has the VUTE3B or VUTE3E stars leading to runway 12R, but Pilot2ATC never recommends this and instead only recommends a straight in approach with no STAR.

The first screenshot shows the STAR when i manually input it, the 2nd shows the route after I click File and it loads its recommended procedures. Not sure if this is intended but if it is, is there a way to force P2ATC to always prefer a STAR over no star. I've tried choosing randomise sid's and stars but it still always chooses none.

Thanks! Definitely plan on purchasing this once my trial is up.

Just an idea, would it be possible if when a Direct To WP request gets approved, that it automatically gets set as the active waypoint in P2ATC?

Would provide an easy workaround if it ever gets stuck.

I'm on my 5th day of my trial and this has been happening to me too. The top part of the screen the waypoint either gets stuck on the first HDG-xxx fix or goes straight to the destination airport. I've noticed it usually happens when theres a SID, I even make sure to stay on the runway heading until the HDG-xxx waypoint but it doesn't make a difference. 

When it gets stuck at the first waypoint I keep getting ATC directions to climb and continue on course but never get instructions to descend. If it gets stuck on the destination airport then everything seems to work fine, I still get directed to descend via my STAR and approach.

I've included part of the log in which it occured, you can see it switches from ANKUB (departure SID waypoint) to YMML (Desination airport).

InterruptAudio in SayPhrase Jase One Two Three Contact SYDNEY Departure on One Two Three point zero ,  have a good one  10/16/2018 14:25:35
AudioInterrupts: 1 in InterruptAudio 14:25:35
ControllerChanging: True : 10/16/2018 14:25:35
ATC Speak:  Jase One Two Three Contact SYDNEY Departure on One Two Three point zero ,  have a good one 14:25:35
Sug Resp:  ~Departure on One Two Three point zero 14:25:35
NewActiveWpt: ANKUB
RespondToFlightTrigger 14:25:37 Trigger:ReachedNextFltPlanWaypoint
RespondToFlightTriggerValidated 14:25:37 Trigger:ReachedNextFltPlanWaypoint
rOnReachedNextFltPlanWaypoint: ANKUB; 14:25:37
OnTTSWavePlaybackStopped 10/16/2018 14:25:41
UnInterruptAudio in OnTTSWavePlaybackStopped SugRes:~Departure on One Two Three point zero  Jase One Two Three
 10/16/2018 14:25:41
AudioInterrupts: 0 in UnInterruptAudio 14:25:41
InterruptAudio in SayItSpeak- Phrase: Departure on One Two Three point zero  Jase One Two Three
 10/16/2018 14:25:41
AudioInterrupts: 1 in InterruptAudio 14:25:41
NewActiveWpt: YMML
RespondToFlightTrigger 14:25:42 Trigger:ReachedNextFltPlanWaypoint
RespondToFlightTriggerValidated 14:25:42 Trigger:ReachedNextFltPlanWaypoint
rOnReachedNextFltPlanWaypoint: YMML; 14:25:42
Recognized Speech: Departure on One Two Three Point Zero Jase One Two Three 14:25:45
HandleFrequencyReadback 14:25:45
CoPilot Changing Freq.  StandbyController set to: YSSY Dep              123.00  10/16/2018 14:25:47
UnInterruptAudio in OnSayItSpeakCompleted 10/16/2018 14:25:47
AudioInterrupts: 0 in UnInterruptAudio 14:25:47
AssignedController: 123.  CtlrShrtName: YSSY Dep CtlrType: Departure14:25:47
Com1StandbyFreqChanged: 119.45.  CtlrShrtName: YSSY Twr CtlrType: Tower14:25:48
InterruptAudio in SayItSpeak- Phrase: Departure Jase One Two Three climbing to Flight Level One Two Zero 10/16/2018 14:25:50
AudioInterrupts: 1 in InterruptAudio 14:25:50
ControllerFreqChanged: 123.  CtlrShrtName: YSSY Dep CtlrType: Departure14:25:50
Recognized Speech: Departure Jase One Two Three Climbing to Flight Level One Two Zero 14:25:54

Make sure your shadow settings in sim are set to theirs. I found without disabling runway/autogen shadows the runways and autoge appear really dark under clouds, even during daylight so i stopped using that preset.