Blast3d

also since the last ovr update using the controllers to interact with foreflight and p2atc or any window works just fine, you cant see the controllers in wmr and msfs but personally i like that. if you need help setting it up id be happy to.

On 7/10/2021 at 11:45 AM, Fleahead said:

I've got my MSFS2020 CRJ working very nicely with P2A, MCE, and the new Navigraph Navdata Center (Beta). I am using the HP Reverb G2 VR headset, which is a big step forward for VR. 

Here's my setup:

*  FSUIPC7 (currently free) Required for P2A

*  Multi Crew Experience (MCE) I'm using this for the 1st Officer functions, other than the radios.

*  P2A mainly for all radio functions

*  Navigraph Navdata Center (BETA) This requires a Navigraph Pro License subscription... pricey but worth it.

*  Amazon Polly AWS Service for additional Voices for P2A and MCE. I never heard of this before, but check out Clumsy's excellent video Here. He also has a link on installing the service. It's not exactly easy to get setup, but if I can do it, anyone can. It's a subscription service, but it's ridiculously cheap. Something like $4 for a couple million words and the first year is free.

*  Microsoft Mixed Reality Portal - Required for the HP Reverb G2 headset.

 

The order of launching the add-ons is very important to be successful. Here's how I setup my flights:

1)  I load up MSFS and position the CRJ (this should work with any A/C), at the airport and gate I want. Be sure to turn off all the ATC options in MSFS.

2)  Load up FSUIPC7 - nothing else needs to be done in FSUIPC7. This is just used as P2A's communication link to the CRJ. 

3)  Load the Navigraph Navdata Center - (Optional)

4)  Load MCE - If you don't use MCE, I guess it's not really necessary, but it is very difficult to operate this A/C alone. MCE does a great job as a co-pilot, but has numerous other functions that adds a lot of realism to a flight. There are a few specific options in MCE that must be set in order for MCE to play nice with P2A, namely leaving the ATC option ON, but changing the ATC source to "OTHER".

5)  Load P2A - Push the CONNECT button and if it turns green, then you are connected thru FSUIPC7 to the A/C OK.

6)  Create and load the Flight Plan as you normally would.

7)  Note: Up to this point, my default sound devices (playback/microphone) has been my TrackIR headset. That's how I'm able to test my communications before going into VR mode. 

8)  Launch Windows Mixed Reality. Your Sound defaults will automatically switch to the VR headset devices in both MCE and P2A , so put on the VR headset and push whatever key/button you have to enable VR in MSFS. 

OK, so now we have our first dilemma. The P2A panel is not visible in the VR cockpit without peeking under the headset mask to see the desktop. (MCE is not visible, either, but it is not necessary to see it to use it.) This is a big problem for me, mainly because I need to see the instructions from ATC. I can hear them OK, but in the real world, pilots have to ability to jot down ATC instructions on a clipboard like heading, altitude, transponder code... everything that my memory is too short to handle. It would sure be nice if the folks at P2A would devise some way to add the P2A panel into the VR window like other devs have done. At the very least, there is a need to have the ATC messages someplace to view and refer to.

I'm hoping that some P2A people might see this and have a solution, or if anyone out there might have an idea, please share.

 

Jim in Ohio

i9 - RTX-3080 - 32G - HP Reverb G2

 

download OVR toolkit from steam, it allows you to set up "tablets" or screens in the sim in vr for instance if you use foreflight you can use a mirroring program to mirror the app on your tablet to your pc then use ovr to project the virtual tablet in the sim. you can tyhen attach that virtual tablet to your controller in sim and look at it whenever you need it

Thanks Dave, Email sent. from jacobiswinning

I'm having an issue when I export a pln from p2atc and try loading it in msfs. I can get some plans to load and a lot of other plans not loading and crashing MSFS. So the latest crash is with KPIH to KHOB with the ILS RW03 approach. here is a pln and vbf of the plan p2atc made https://drive.google.com/drive/folders/19N7RWmB12k1F4cfafUJE6KlMIxlNZg6Y?usp=sharing I've just been creating a plan by hand in MSFS to match the p2atc one as a workaround for now. I comapared the files in VScode and deleted the Null Intersection that p2atc creates and loaded and the crash was fixed however it breaks the plan and sends me halfway across the globe, but wanted to see if maybe MSFS doesnt like empty ICAO fields. I tried finding my bug on this forum and although some people had crashing issues I didnt see mine.