Jump to content

Bruce953

Members
  • Content Count

    66
  • Donations

    $0.00 
  • Joined

  • Last visited

Community Reputation

2 Neutral

Profile Information

  • Gender
    Male

Flight Sim Profile

  • Commercial Member
    No
  • Online Flight Organization Membership
    none
  • Virtual Airlines
    Yes

Recent Profile Visitors

1,169 profile views
  1. Hello Dave, Re Beta n. So I just loaded a departure from EHAM and P2ATC showed departure rwy 36L. I changed this to rwy 09 with a corresponding SID. All other preparations were made as required. *Taxi clearance remained to rwy36L and the change to 09 was ignored. At the hold, departure clearance on rwy 09 could not be obtained and an instruction loop followed - between ground and tower. In the Flt Plan tab the only check was in 'Force Pilot Runway Selection'. As previously - on my system this only started happening with Beta n. . . Cheers, BB
  2. Hello Dave, 'Force Pilot Runway Selection' is checked but I just noticed that 'ATC assigns SID' was checked' maybe that caused the problem? I've unchecked that now. The issue only started after moving from Beta m to n. Will try a short flight later and test. Cheers
  3. Hello Folks, I use Beta 2n which seems good in X-Plane 11.55, Vulkan, WMR-VR. Just one small glitch noticed and that is - if I change the departure runway owing to wind direction (e.g.at EHAM with numerous rwys) then in Beta 2n the change is not recognized and the tower will not give take off clearance from the changed runway and instead sticks to the original allocated departure rwy. Thanks for your great work and looking forward to an XP12 upgrade when that is available. With best reagrds BB
  4. Dave, I did try deactivation earlier, but this time I did it more carefully, more slowly and it solved the problem. Thanks for such a rapid response. As ever, best wishes - Bruce.
  5. Hello Dave, I have an activation problem. The message box says P2ATC is on another machine, but nothing has changed here apart from the update. The PC has not changed. I have my key codes stored along with the hardware code if they are required. Cheers, Bruce p.s. Everything was fine in this mornings flight. . .pre update.
  6. I tried and tried that Dave, but originally it was absolutely stuck (i.e. P2ATC maximized or nothing). I found my solution on a google search - for info. Best regards
  7. Yep, I have this problem too. P2ATC in minimized screen has disappeared into the task bar and I cant get it back. The maximized screen comes up but that covers everything else. Have tried many restarts but I'm stuck now. For info. . .Cheers, Bruce *Ok, Try this - Go into Settings/Privacy/Background apps. Select Off. Shut down and reboot. Open P2ATC, hover over the icon in the task bar and select Move in minimized screen. I could then resize the P2ATC screen and recover my normal minimized screen operation. Go back to Privacy menu etc and select the background apps you want running. Well - this worked for me . . .
  8. Just enjoyed an excellent early morning flight from LEPA to Biarritz-Bayonne with Pilot2ATC and the great little ERJ145LR. Mic problem solved. XP11.50b9, Win10, HP Reverb Pro-VR
  9. Go to settings, System, sound and then you can run a test on your mic. This then leads you to an automatic MS problem solving screen which in turn corrected the error which sound drivers caused after the MS version 2004 update. As you say the mic appears to work normally for Win 10 but is causing problems with some apps e.g. P2ATC. This fix worked for me after a couple of hours of head scratching. . . good luck. Cheers, Bruce
  10. KenG, pls see the above post by Davearky, cheers
  11. Can confirm Win10 version update 2004 is causing sound driver problems for some apps (Microsoft response). The driver issue fix was provided automatically on the Settings/sounds page. Cheers, Bruce Win10, HP Reverb VR, XP11.50b9
  12. Me too, suddenly P2A is not recognising speech from my headset mic. I have a feeling this is related to yesterdays Win 10 update which was huge and partially VR-WMR related I believe. Spent an hour last night trying to fix and will continue today ; )
  13. Quote "Using the STEAM app OVRDrop to bring a 2D P2A window into VR I have been able to interact with P2A in the cockpit. I use the Mouse, but the controllers also were able to click on the buttons. There are probably other ways to do the same thing. Many users also just set up the flight plan and file it before going under the hood, and then fly just using the cockpit instruments and interacting with ATC. Dave" I sense that more and more people are coming to flightsim in VR mode and I too have now made the switch. Thanks for your comment above Dave as I am finding the best P2A technique exactly as you state in the above quote, i.e. ".... just set up the flight plan and file it before going under the hood, and then fly just using the cockpit instruments and interacting with ATC" . I look fwd to all future P2A enhancements. Cheers, Bruce
  14. UPDATE - Problem resolved this morning. Cheers, Bruce
×
×
  • Create New...