brucemarten

I got it working. I think it was because I had a corrupted windows file somewhere and the cmd to check them fixed it. All good.

I'm using Pilot2ATC v. 2.6.4.2_x64 with Navigraph. I'm using my Razer headset for sound.

Doesn't show up in the sound mixer settings and there is no sound for the ATC voices. Ideas?

I submitted a ticket. Thanks very much for taking the time and giving this your attention. Good work. Bruce

I didn't have UGCX installed, and once I uninstalled GSX I figured the tug would show up. My sliders: Scenery Objects (all normal); Special Effects Detail (high); Airport Vehicle Density (minimum) I see no tug with these settings. Thanks for the feedback. Bruce

Good discussion. I'm running P3D v5, and even when I deleted GSX the tug didn't reappear. Also, when I selected pushback and anticipated the tug coming into view (it didn't), the order to release the parking brake was immediate; which seemed strange to me. No movement in any event took place except just one time when it backed up (without a tug) and responded to my rudder pedals. This is just informational, if it's helpful. I'll just wait until a tug is modeled; however long that may take. Bruce Marten MTN1794

OK, just checked both VOR's using a non-PMDG aircraft and again in the NGX. Both VOR's were operating this time. I have NO clue why they didn't yesterday. Sorry for any inconvenience in the process. Glad it works as it should. Bruce Marten

I figured it was not necessarily a NGX issue so I put it in the general topics. However, I see your point. I did have the proper frequencies manually entered (in fact I triple checked them from different resources available to me). To my knowledge I did everything correctly. I wonder if the two inoperative VOR's are no longer in service. I still flew them like waypoints though. Bruce Marten

Flying from KMSO to KSLC in the PMDG 737-600 I flew over navaids LKT, PIH and MLD. Only PIH had a nav course bearing indication (green arrow) and the other two did not. Is that a Navigraph problem, or are the VOR's no longer in service?

Hmm, with Chaseplane on or off, and using arrow keys left and right to pan in those directions, when the panning exceeds 90 degrees (or close to that) the plane rolls in that same direction just as it did using the keypad #s. That surprised me.

I have the same, but I suspect the panning is now to be done using Chaseplane's camera feature, or (in my case) using the arrow buttons instead.

Thanks for the idea, but numbers lock was off. I did notice that while typing a document using the Word program I can move the cursor left and right using 4 and 6 as well. I think rather than try and figure out the cause, the simple answer for me is to set arrow keys in Chaseplane for left and right.

Enjoying the B737 for P3D v4. With Chaseplane installed and looking left and right assigned to the #s 4 and 6 respectively on the keypad, when I look past 90 degrees left or right, the autopilot fails and the plane rolls in the direction of the keypad number. The roll will increase or decrease somewhat after that depending on how I continue to use #s 4 and 6. Short term solution - DON'T do that (ok). Long term, does anyone know if there is a keypad # command associated with 4 or 6 with this aircraft? I didn't see any mapping to the basic P3D v4 that would do this (though ctrl + 4 and ctrl +6 = aileron trim which may be the problem but I'm not pressing "control") . No big deal, but any solution would be welcome of course. Thanks! New information: Chaseplane had nothing to do with it. I disconnected Chaseplane and pressed 4 and 6 anyway - and the autopilot disconnected and the plane rolled. Sorry Chaseplane! You are not the problem - or the solution for this one.