Jump to content

Room112

Members
  • Content Count

    142
  • Donations

    $0.00 
  • Joined

  • Last visited

Community Reputation

27 Neutral

About Room112

  • Rank
    Member

Profile Information

  • Gender
    Male

Flight Sim Profile

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

Recent Profile Visitors

1,006 profile views
  1. I think for commercial flights you're to enter your flight number, like 345 so that ATC refers to you as Ryanair 345.
  2. Great video. Really showed the product off. Quick question though. Those thunderstorms in the distance at the end of the video, if you had taken off again would you have been able to fly into them, or are they just 'painted' in the distance. (Apologies if it's a dumb question!)
  3. Same here. Sat on the loading screen for 10 minutes. Had to kill the task. Only change was new Oculus drivers. Reboot fixed it.
  4. Should already be 2 samples in the application folder.
  5. Any SAPI5 64-bit voice should work but most people stick with voices from Ivona or Cereproc. There are pay-as-you-go voices from Amazon but setup is tedious and sometimes takes a bit of work to get going.
  6. Not to hijack this thread, but has anyone tried their PA add-on? I have PacX and SLC but neither work particularly well in VR, and have more of a passenger management component then I care to have.
  7. Somebody posted an archive of the Polly Player for Windows so I thought I'd give it another shot. Like before, it's hit or miss. Sometimes it works when I start the software the first time, others times it might be the 3rd or 4th attempt. I go into Config and play each Polly voice before I set up my flight. If they play, then they will work for the entire flight. If not, I have to restart P2A. Cost wise I spend about $0.25 a month, but I don't use it for every flight. You have to give your CC details when setting up your AWS account, and it's automatically charged to the card. All in all, it was a bit of a chore to set up, but now that I have it up and running it works pretty well. One thing to note, not all Polly voices will work, but there are around 20 that do. I have a different Polly voice in each position.
  8. Run the make runways utility to read the scenery, then import it into P2A. It'll correct most, if not all, of the taxiway issues. For the rest, there's a taxiway editor in the game.
  9. I can't even get it to show up in VR so I gave up on it, which is a shame because it was such a handy utility.
  10. The link worked for me and I'm able to get Polly working for me consistently. Some tips I've seen floating around that worked for me: - Set the correct region when registering Polly in Windows. - Assign a voice to each controller, don't use the randomize feature.
  11. I use Sky4Sim because it works with both NeoFly and Pilot2ATC so if you use either program it's a no brainer.
  12. Current version doesn't work in VR. Saw the dev say that they're going to make VR compatible windows in 1.4.
  13. So have you been able to get Polly to work consistently in P2A without multiple restarts?
  14. I think your end goal should be to use it with the app window completely minimized. If you have your co-pilot respond and tunr radios then your only speaking for clearance, pushback, on final and taxiing to parking. Your co-pilot will handle every other interaction. Then you get the benefit of dynamically assigned SIDS, STARS and approaches and all the other features of P2A.
×
×
  • Create New...