Sign in to follow this  
mwilk

Unhandled exception

Recommended Posts

I'm using the latest beta. I was just doing an IFR flight from EGLL-EIDW. It was going very well. I had been given my STAR and assigned runway. I was handed off to the next controller. I dialed in the wrong frequency and when I attempted to contact center I received an unhandled exception warning. I was no longer able to contact ATC beit center, approach, or tower. I was being given traffic advisories though.

Share this post


Link to post
Share on other sites
Help AVSIM continue to serve you!
Please donate today!

Dave:

 

I too had some unhandled exceptions.  Also happened while changing frequencies. I might very well have entrered the wrong frequency.  The problem occured when I tried to contact center.

Share this post


Link to post
Share on other sites

I was actually headed here to post the same thing.  This also happens if you step away from the PC a bit too long.  Typically on long flights Ill run errands, chores around the house and come back in time for descent.  P2A doesn't seem to like this however and will usually throw an exception error for me.  Is it possible to maybe get an option for the FO to take over radio's and ATC for situations like this?  That would be a killer feature for me.

Share this post


Link to post
Share on other sites

 

 


Is it possible to maybe get an option for the FO to take over radio's and ATC for situations like this?  That would be a killer feature for me.

 

It would be nice if Dave could implement this kind of feature. As you said, there are times when you have to be away from the computer for a bit and are going to miss frequency changes. 

Share this post


Link to post
Share on other sites

Have you tried using the "Pause" button on Pilot2ATC?  That will stop the event firing in P2A while you're gone.

When you get back, as long as you are still at cruise altitude en-route prior to TOD and prior to the first waypoint in a STAR, it should figure out where you are and let you continue from there.

 

I have not tried this feature on such long flights, but theoretically it should work.  Let us know what you find if you try it.

 

Dave

Share this post


Link to post
Share on other sites

Dave,

 

Is there a way to tie P2A to the pause feature in FSX/P3D?

 

I believe ProATC does this other wise you have to deal with two pause buttons?

 

Bill Clark

Share this post


Link to post
Share on other sites

Hi Bill.

I initially had it set up that way, but it caused many unintended issues.  By having the separate Pause Button, in addition to avoiding those issues, you are able to Pause P2A while FSX/P3D continue a long flight as Mike and Chris were discussing above.

 

Dave

Share this post


Link to post
Share on other sites

Hi

 

Just also experienced an unhandled exception due to dialing in a wrong frequency (.05 out). Exception occurred as I contacted center on the misdialed frequency. Pressed continue.

 

Pilot2ATC continued to run, and I was again asked to contact the new center frequency (so Pilot2ATC was still able to detect I had not changed to the correct new center frequency after some delay). Was able to acknowledge that second request using SayIt, not PTT. Dialed in the correct frequency, and tried to contact the new center again. PTT button goes green by no recognized text comes up.

 

So while Pilot2ATC carries on (plane moving on map, radio window working, etc.) the speech recognition engine crashes, so that's it for the session using voice recognition.

 

Maybe this will help track why / how a wrongly entered frequency should cause the speech recognition engine to quit or design a trap to catch the error.

 

Rob

Share this post


Link to post
Share on other sites

Rob,

Thanks for the detail. That should help track down the problem.

 

If you still have the log file from that flight, could you please email it to me.

 

Thanks,

Dave

 

Edit: Never mind the log file. I think I found the problem and the fix will be in the next update.

Thanks,

Dave

Share this post


Link to post
Share on other sites

Dave

 

Sorry I exited without copying and saving the log. Maybe when I have some time I will try to trigger the error again deliberately dialing in a wrong frequency, and be more diligent about saving the log.

 

Rob

Share this post


Link to post
Share on other sites

Have you tried using the "Pause" button on Pilot2ATC?  That will stop the event firing in P2A while you're gone.

When you get back, as long as you are still at cruise altitude en-route prior to TOD and prior to the first waypoint in a STAR, it should figure out where you are and let you continue from there.

 

I have not tried this feature on such long flights, but theoretically it should work.  Let us know what you find if you try it.

 

Dave

 

I have never noticed the the Pause button before!  Shows how observant I am.  I'll give that a go tonight and report back.

Share this post


Link to post
Share on other sites

Dave,

 

tried it and didn't works. P2A loses the synchronization. Passed in P3D some planned waypoints but after I terminated the break in P2A I've got repeated "off-course" instructions related to the last as "current" registered waypoint. Reached the arrival setup radius and P2A announced STAR/APPR and instructed the stepwise descent but as long the "EnrouteIFRState" didn't changed the "off-course" instructions didn't stopped.

 

Helge

Share this post


Link to post
Share on other sites

Helge,

Did you make changes in P3D while P2A was paused?  If so, I would expect the off course calls.

 

The only way  to change the P2A flight plan that ATC is expecting is to FILE a new flight plan, or to request and get approval from ATC for a different route, approach, etc.

 

Dave 

Share this post


Link to post
Share on other sites

No Dave, I didn't changed anything in P3D nor deviated/left the planned route nor tried to change the P2A flight plan.

 

Flew in P3D the filed flightplan while P2A was paused as you suggested in post's #5 & 7 (intention to make a "break" and let the pc alone on long flights without ongoing frequency changes from P2A). I paused P2A in "EnRouteIFR_State" on CTR-frequency and after leveled out at planned FL + 10 NM and terminated the pause 40 NM before reached the TOD or ArrivalSetupRadius - still "EnRouteIFR_State" and also still in the jurisdiction from normal CTR not APPR. But after that break P2A wasn't able to synchronize the current position in P3D according to the P2A flight plan and ignored the meanwhile passed waypoints. Only the moving map shows the current position but ATC expecting me at the old one before I pauses P2A.

 

Helge

Share this post


Link to post
Share on other sites

Helge,

Thank you for the additional details. 

While the Pause feature was not really meant to be used this way, I thought it might work.

 

I will see if I can make a tweak to get it to work.

 

Thanks again,

Dave

Share this post


Link to post
Share on other sites

I've tried the pause feature and had some mixed results myself - usually with the mixed side being error on my part.  If you unpause too late and you should be in decent - P2A doesn't like this which I'm assuming is to be expected.  My new way of doing long flights and stepping away is enable the copilot handling radios and readbacks once I'm ready to step away - and let er' do its thing.  P2A will continually communicate with itself.  If you'd like to take control again, I just disable the option.  So far its been pretty flawless for me - and actually ends up adding a tad bit of realism as the copilot is handling the radios for you.  Pretty sure real pilots can't press "pause" while they're up there ;).  

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this