Search the Community
Showing results for tags 'AviTAB'.
Found 1 result
Hello, I am using the latest update of the GTN750. I use it in all my planes as a floating window sitting on the copilot seat. I fly always in VR with the Rift-S and the floating panel is big enough that I can see it well and manipulate it with the Touch Controllers or the mouse. Another plugin that is active is Pilot2ATC that creates the original flight plan and then scolds me if I don't follow it correctly I enter the flight plan from Pilot2ATC manually into the GTN750 when I am in the cockpit. I also use AviTAB for nav charts and a moving map. So a few days ago, I would be in the beginning of a flight and all of a sudden the GTN750 would lock up. It wouldn't respond to any click from the controllers or the mouse. But it remained active and auto-zoomed when it approached a waypoint. But I couldn't control it at all. At first, I went to the menu and closed the GTN completely. Then I launched a whole new version of it and that would work after I re-entered the flight plan. I found a better way to work around the problem, I exited VR and with the normal screen I was able to select a Popup Window. I clicked on that a few times with the mouse to be sure that it was working - which it was. I was back to normal. So then I went back into VR and the popup window disappeared, but when I was in VR there it was floating in front of me, waiting to be placed on the copilot seat. It then worked fine and I didn't have to reload the flight plan. But I seem to have found a curious connection that seems to be related. This is a whole new bug. When I am making a flight plan, I select a STAR and it inserts correctly into the plan. But when I go to select an Approach, instead of inserting BEFORE the destination airport, it inserts AFTER - so that the plane goes to the airport and then goes to the approach. I discovered that I could just delete the airport name in the plan and then the preview would show the correct line from the end of the STAR to the beginning of the Approach and down to the runway. So it didn't bother me that the airport name was no longer in the plan as long as I got to the right runway. BUT, I noticed that, in the cases where I deleted the destination airport, I had the above problem with the GTN freezing in flight. But I just made a flight and when I selected the approach, the destination airport name disappeared and the STAR connected to the Approach just like it should. When I made that flight, the GTN didn't freeze up. So sometimes the approach connects correctly and sometimes it doesn't. This is one of those mystery bugs that involves a lot of plugins, but since I can reproduce it, I report it.