Quijote

Someone pointed out to me that, if you pull the trigger of the controller half way, you get a faint green laser beam which you can use to align the beam before pulling the trigger. I tried it and it works. All this time in VR and I never knew that. I will leave this thread here in case someone else can learn this....

More and more planes are coming out with the GTN750 built into the panel. There is a problem with that for VR users. In a floating window like AVItab or the GTN750 when it ISN'T built in, there is a blue laser beam that comes from the controller any time it is pointed at the window. That makes it very easy to select things - you point at them with the blue laser and pull the trigger - boom, selected. But when the GTN is built into the panel, there is no blue laser beam. If you pull the trigger, there is a green laser beam which shoots out. If it happens to land on a button, that button will be selected. But you have no idea if it is going to land on the desired button. I often take a shot onto a blank part of the panel to get a feel for where it is going to land before actually pointing to the GTN. This results in me using the floating window even when the GTN is built in because, if I am entering a flight plan by selecting waypoints, there is no way that I am going to shoot in the dark at the panel. I don't know if this is something related to the GTN or to Xplane's panels, but I mention it here in case you can help with it..... Thanks....

I turned off the GTN 750 with XOrganizer so that it wouldn't load when I selected the TBM. I will try removing it's folder from plugins and report back...

Hi, My previous post got deleted because it was a duplicate of another post. Well it was because three developers are involved and I don't know which. Hopefully I won't get deleted again.... A few days ago I began to notice that Pilot2ATC was behaving strangely. On starting it, it wouldn't finish an ATIS report, stopping after a few words and then starting again. Finally, after getting clearance, the tower tried to hand me off to departure and after departure started to respond, tower came back and tried the handoff again. In short, the control would not pass to the next frequency. When the plane was stopped the frequency would swap back and forth between the COM1 and COM2 (which is why ATIS could never finish.) Then today, I had a flight in the Eclipse 550 where everything worked. Hmmm. Then I started a flight with the Socata and the problem was back. So I disabled all AI aircraft and turned off some other plugins that used the voice system. No cure. Then I changed to a plane that wasn't the Socata. Problem fixed. Back to the Socata, back to the problem. Pilot2ATC, Reality GTN 750 and the Socata TBM900 are fighting over the radio controls. Pilot2ATC is configured as always - I've used it for several years.... Reality GTN750 I use as a floating window in all my planes since I fly in VR and can control it easily with the controllers. When I saw this problem emerge, I updated to the latest version of the GTN. I even copied the RealityGTN.ini file to the Socata from the Epic 1000 where it works just fine. The Socata is the variable that causes the problem. Any other plane works with the other 2 program settings identical.

Hi Dave and fellow simmers, I have this problem that seems to involve just the Socata TBM, but I present it here in case anyone has an idea. Here it is: A few days ago I began to notice that Pilot2ATC was behaving strangely. On starting it, it wouldn't finish an ATIS report, stopping after a few words and then starting again. Finally, after getting clearance, the tower tried to hand me off to departure and after departure started to respond, tower came back and tried the handoff again. In short, the control would not pass to the next frequency. When the plane was stopped the frequency would swap back and forth between the COM1 and COM2 (which is why ATIS could never finish.) Then today, I had a flight in the Eclipse 550 where everything worked. Hmmm. Then I started a flight with the Socata and the problem was back. So I disabled all AI aircraft and turned off some other plugins that used the voice system. No cure. Then I changed to a plane that wasn't the Socata. Problem fixed. Back to the Socata, back to the problem. Pilot2ATC, Reality GTN 750 and the Socata TBM900 are fighting over the radio controls. Pilot2ATC is configured as always - I've used it for several years.... Reality GTN750 I use as a floating window in all my planes since I fly in VR and can control it easily with the controllers. When I saw this problem emerge, I updated to the latest version of the GTN. I even copied the RealityGTN.ini file to the Socata from the Epic 1000 where it works just fine. The Socata is the variable that causes the problem. Any other plane works with the other 2 program settings identical.

I looked in the ini file and it says that I was using the 750_1. BTW, I took your advice and activated "Update Simulator GPS Waypoints" and now the G1000 displays all the legs of the flight plan. I have gotten it to work on the Diamond DA62 and the Epic E1000 so far and it is perfect.

I'm sorry, I don't know what is A GTN 750_1. I have had a 750 for a while now so it is probably an older version. I selected GPS1 as the active GPS and that is working.

Thank you, Jean-Luc, PROBLEM SOLVED! I went into the Gauge Options and changed the GPS Source from Auto to GPS1. That means that the 750 is replacing the GPS1 which was the G1000. Now the plane follows the flight plan and makes all the turns. The magenta line no longer appears on the G1000 which is just fine with me. In one of the recent upgrades, that status must have changed and now it is solved again. Another happy client......

Hello, I have spent half-a-day testing and have to report that I cannot get any plane with a builtin G1000 to follow the flight plan I enter into a "floating" GTN750. I am in VR as well. However, planes with the older GPS models 530 will follow the flight plan just fine. The G1000 error isn't noted until there is a change of direction. The plane starts the turn but in the middle stops turning and just goes straight. If I click on NAV on the G1000, it will return to the new magenta line and finish the turn. I must select NAV after every change of course. At first I thought that this was an error only with new planes with modified G1000s like the Epic or King Air 350, but when I started testing on the C172 I found that all G1000s react the same - and all the 530s work. WHAT'S NEW: I have just begun to notice that, when the 750 is following a flight plan, the G1000 or 530 also show a magenta line and the name of the next waypoint.... but only a line to the next waypoint, not the rest of the flight plan. They didn't used to do that. When we get to a turn, the G1000/530 puts up a new magenta line and the next waypoint. But halfway through the turn the plane exits NAV mode and starts going straight. I have to tell PlaneCommand "LNAV" or push the NAV button on the G1000. Then we go back to the magenta line. So it appears that the 750 is controlling the plane fine when LNAV is initiated and when the flight plan has a change of course, the 750 gives the new waypoint and magenta line to the G1000 but forgets to say "follow the magenta line". I use the 750 in ALL my planes and I never noticed this before because I used to just set a direct destination on the 750 and then use graphical editing to add new waypoints. The plane always followed the course including the turns, but putting the waypoints into a flight plan isn't working. Is there something that I am missing in the settings???????

I have had some more strange runway assignments after making the suggested changes. But, the winds were fairly light. So the 64,000$ question - how strong do the winds have to be to force a runway selection?

Thanks again Dave, I forgot to mention that I was flying VFR, using a direct heading in the GPS. So there was never a runway in the flight plan - just airport to airport. But I think it is working pretty well now.

Thanks Dave, I had Force Pilot Runway Selection checked. Unchecked now. I am going to set NOAA weather and see if that works better with a 5 minute update. I use NOAA in the sim now as well although I find that it sometimes gives me zero wind after I load even though the xplane menu says 7 knots.. Well, not your problem. Thanks again......

Hi Dave, I have been using P2A a lot recently and have noted that, when I first load a flight plan - even before the sim is connected, that P2A puts a magenta line on the destination airport indicating the preferred approach. Fine, but after I connect the sim (and force real time weather), approach continues to recommend a runway that is not correct for the wind. Usually it is the same one as the magenta line. BTW, I have P2A set to use the sim weather. It would be nice if P2A would check the sim wind at the time when Center turns control over to Approach so that Approach recommends a runway that is appropriate. Am I missing something that I should be doing?

I'm back again. I got the mixer sorted out and thought that all was well. But today I loaded a flight and when I connected P2A, it started giving me the ATIS report as usual. The problem was that, after about 5 seconds, another voice starting giving me an ATIS report over the first one. Worse, they were different reports - one was Romeo and the other Yankee! There was a difference in wind speeds, etc. I use NOAA weather and it runs normally in Xplane. P2A was also set to use NOAA data. There may have been a difference in download time and perhaps P2A was getting data directly from NOAA instead of Xplane (which already had NOAA). Anyway, is there a way to get just one weather source in ATIS? Two voices at the same time is awful.....

Hello again, Good news - P2A has nothing to do with the above problem other than it uses speech recognition. I recently installed Voice Meeter Banana - I know, dumb name - which is a mixer that allows you to select various audio outputs while using Xplane. It is very useful if you leave VR for a while and want sound on the speakers instead of headphones. Well, generally the mixer works great with VR, but with P2A the input was set to 48000mhz which causes static in VMB. Today I changed the input to 44000mhz and the static was gone and so was the drop in fps. Now I am looking at 30 fps which I consider quite fine. Sorry to have raised the alarm....... I have two microphone buttons - one for PlaneCommand, which is a marvel, and the other for P2A.