Maury Pratt

<Solved> This is embarrassing . . . AICarriers was working all along! It never occurred to me to drag the bottom edge of the AI Ships screen down (below item 7). Guess what, more ships and "Next page" is there. I think there's an issue with P3D v3 in managing pop-up screens?

Might someone let me know if they've successfully installed AICarriers.NET in P3D v3.3.5? AICarriers appears in the P3D add-on menu when I start P3D but lists only the default ships (see screenshot ). If I select 'single carrier' the default carrier shows up on the water and travels just fine. But I can't get a list of installed AI ships for selection, such as one of the Nimitz variants. I've installed AICarriers.net and the Nimitz & Eisenhower V2 AI ships, and modified the exe.xml (using the sample file) in P3D v3.3.5's AppData.Roaming>Lockheed Martin>Prepar3D v3 folder to point to the AICarriers.exe file in the P3D main folder. I've placed both the cvn_68_69.cfg and CVN65_Enterprise.cfg files in the conf.d folder. Checking aicarriers.cfg only the default ships appear there--How can I cause that to include the Nimitz/Eisenhower (and after that the Enterprise)? Or is this problem caused by something else? (I've checked the gauge, effects, and simobject/boats folders; all the expected files are there. And I've confirmed that the contents of both aicarriers.cfg and cvn_68_69.cfg are correct.

Lost Center contact while climbing and awaiting clearance to flight plan altitude. I was switched to NorCal Approach 120.35 but got no response to reporting current altitude. Instead P2A’s state changed to “Initialized”. (Not good) Further attempts to make contact were unsuccessful. Also, using SayIt for most communications I once got an unhandled exception when selecting one of the reporting grammar help choices (voice rather than SayIt "to altitude") that required spoken transmission; I clicked on "continue" and did so, but didn't get a response. Other than that my spoken responses have worked fine. Route: KLAX CASTA GMN COREZ AVE BSR KSFO CASTA5 RWY 25R HADLY2 RWY 10L LOG: Simulator Connected Recognition Engine Installed Grammars Loaded ~Southwest Four Two Echo ready to copy IFR Clearance Southwest Four Two Echo Ready to Copy IFR Clearance; State Change to: FlightPlanDelivered Southwest Four Two Echo is cleared to Kilo Siera Foxtrot Oscar, fly the CASTA5 departure , with the GMN transition , then as filed. Maintain , Niner Thousand feet . Expect higher clearances five minutes after departure Departure on One Two Five Point Two Squawk Four Six Three Two ~Southwest Four Two Echo is cleared to Kilo Siera Foxtrot Oscar, fly the CASTA5 departure , with the GMN transition , then as filed. Maintain , Niner Thousand feet . Expect higher clearances five minutes after departure Departure on One Two Five Point Two Squawk Four Six Three Two Southwest Four Two Echo is Cleared to Kilo Siera Foxtrot Oscar fly the CASTA5 departure with the GMN transition then as filed Maintain Niner Thousand Feet Expect higher clearances five minutes after departure Departure on One Two Five Point Two Squawk Four Six Three Two; Southwest Four Two Echo Readback Correct. Altimeter is Three Zero One Zero Contact Ground on One Two One Point Seven Five when ready to taxi. enjoy ~ Altimeter is Three Zero One Zero Ground on One Two One Point Seven Five Southwest Four Two Echo ~Southwest Four Two Echo ready for pushback Southwest Four Two Echo Ready for Pushback; Southwest Four Two Echo Pushback approved ~ Pushback approved Southwest Four Two Echo ~Southwest Four Two Echo ready to taxi Southwest Four Two Echo Ready to Taxi; Southwest Four Two Echo Standby State Change to: TaxiOut Southwest Four Two Echo Taxi to Runway Two Four Right Via Taxiways Delta, Echo, Hold Short Runway Two Four Right ~ Taxi to Runway Two Four Right Via Taxiways Delta, Echo, Hold Short Runway Two Four Right Southwest Four Two Echo Taxi to Runway Two Four Right via Taxiways Delta Echo Hold Short Runway Two Four Right Southwest Four Two Echo; Taxi to Runway Two Four Right via Taxiways Delta Echo Hold Short Runway Two Four Right Southwest Four Two Echo; Taxi to Runway Two Four Right via Taxiways Delta Echo Hold Short Runway Two Four Right Southwest Four Two Echo; ~Southwest Four Two Echo waiting to cross Runway Zero Six Left ~Southwest Four Two Echo waiting to cross Runway Zero Six Right ~Southwest Four Two Echo waiting to cross Runway Zero Seven Left Southwest Four Two Echo waiting to cross Runway Zero Seven Left; Southwest Four Two Echo Advise when you reach the hold point for runway Zero Seven Left ~Southwest Four Two Echo ready for departure runway Two Four Right ~Southwest Four Two Echo ready for departure runway Two Four Right Southwest Four Two Echo Ready for Departure Runway Two Four Right; State Change to: ClearedToLineUpAndWait Southwest Four Two Echo Line up and wait, Runway Two Four Right Whinds are light and variable ~Line up and wait Runway Two Four Right Southwest Four Two Echo ~Southwest Four Two Echo ready for departure runway Two Four Right Southwest Four Two Echo Ready for Departure Runway Two Four Right; State Change to: TakeoffIFR Southwest Four Two Echo Whinds are light and variable Cleared for takeoff, Runway Two Four Right Squawk Four Six Three Two ~Cleared for takeoff, Runway Two Four Right Squawking Four Six Three Two Southwest Four Two Echo Cleared for Takeoff Runway Two Four Right Squawking Four Six Three Two Southwest Four Two Echo; NextWpt: FABRA NextWpt: ENNEY NextWpt: NAANC Southwest Four Two Echo Contact Departure on One Two Five Point Two, have a good morning ~Departure on One Two Five Point Two, goodday Southwest Four Two Echo Departure on One Two Five Point Two goodday Southwest Four Two Echo; ~Southwest Four Two Echo climbing to Niner Thousand feet Southwest Four Two Echo Climbing to Niner Thousand Feet; State Change to: DepartureIFR Southwest Four Two Echo good morning . Radar Contact. Southwest Four Two Echo Climb and Maintain , One Six Thousand feet ~ Climb and Maintain One Six Thousand feet Southwest Four Two Echo NextWpt: GHART Climb and Maintain One Six Thousand Feet Southwest Four Two Echo; State Change to: EnRouteIFR Southwest Four Two Echo Contact LOS ANGELES CENTER on One Three Five Point Five, enjoy your morning ~Center on One Three Five Point Five take care Southwest Four Two Echo Center on One Three Five Point Five take care Southwest Four Two Echo; NextWpt: AJAYE You can say: Southwest Four Two Echo climbing to <Altitude> ~Southwest Four Two Echo climbing to One Six Thousand feet ~Southwest Four Two Echo climbing to One Six Thousand feet Southwest Four Two Echo Climbing to One Six Thousand Feet; Southwest Four Two Echo good morning . Radar Contact. NextWpt: SILEX NextWpt: TWINE Southwest Four Two Echo Climb and Maintain Flight Level Two Four Zero ~ Climb and Maintain Flight Level Two Four Zero Southwest Four Two Echo Climb and Maintain Flight Level Two Four Zero Southwest Four Two Echo; NextWpt: OROSZ NextWpt: CASTA NextWpt: GMN Southwest Four Two Echo Contact NORCAL APP APPROACH on One Two Zero Point Three Five, enjoy ~Approach on One Two Zero Point Three Five Southwest Four Two Echo Approach on One Two Zero Point Three Five Southwest Four Two Echo; ~Southwest Four Two Echo climbing to Flight Level Two Four Zero You can say: Southwest Four Two Echo climbing to <Altitude> ~Southwest Four Two Echo descending to Flight Level Two Four Zero State Change to: Initialized NextWpt: TOD You can say: Southwest Four Two Echo climbing to <Altitude> ~Southwest Four Two Echo climbing to Flight Level Two Four Zero

On my 3rd try today with P2A v2002 I had a (mostly) successful flight San Diego to Phoenix: KSAN POGGI5 IPL BZA HOGGZ JUDTH HYDRR HYDRR1 KPHX Rwy 26L Cruise Alt FL330 While in contact with PHX Approach flying eastbound past the CHAVO waypoint I expected to receive vectors for the 180 degree turn westbound to join the 26L ILS, but hearing none I continued past the final STAR waypoint LEMOE, at which point the FMS' "next line" went to "vector". Still hearing nothing I dialed-in the 26L freq/course and initiated the turn myself, followed with LOC and APPR on the MCP, landing normally -- including switching to Tower when instructed and subsequently hearing a call from Tower "cleared to land ILS 26L, etc. My question is, what became of a call by P2A giving me vectors to align with 26L's glide path? If pilot error, what should I have done instead, and when, to enable vectors to be given? (I was at the FMC assigned altitude and speed throughout.)

'MyTraffic 6' is working as expected at KSFO in conjunction with AirTrafficManager on my system (Windows 10, P3Dv3). Either create a KSFO-departure flight plan (*.pln) in your Documents>Prepar3D v3 Files folder (ATM picks this up automatically) or type KSFO in AirTrafficManager's 'Departure Airport' field. FlightBeam's KSFO HD not only looks terrific, but frame rates remain normal there {not much affected by AI traffic) used in combination with AirTrafficManager.

Yes, I installed LatinVFR's KSAN in P3Dv3 manually and it works fine. As I still have v2.5 installed as well as v3, I copied the KSAN scenery and texture files from v2.5 (where I'd previously installed them in an 'Addon Scenery' folder), and listed KSAN in P3D's scenery library ('World' drop-down list).

Thanks Jorge and gb -- FSUIPC controller assignments are working fine now. I did find it necessary to leave P3D's controller assignment box checked in order to use OPUS FSi Direct View (to recognize button presses); this seems not to adversely affect FSUIPC-assigned axis and button functions. mp

I'm having the same issue -- my Saitek X52 joystick is working correctly in P3D v2.5 BUT the X52 isn't recognized in P3D's Options/Settings/Controls/enable controllers -- which shows only 'mouse control' in the drop-down box. I need to resolve this in order to 'uncheck' P3D's assignment, setting them up in FSUIPC instead (by 'unchecking' P3D's 'enable controllers' box), transferring that to FSUIPC. Has anyone encountered this issue when setting up FSUIPC exclusive controller control for flight stick and throttle devices in P3D? Or does P3D's enable controllers setting even matter if axis calibration is done in FSUIPC?

Just re-download and install current Addon Manager from the FSDT site. Mine works fine. Rob's patch directions worked without problems as well.

That was it! The problem was that when installed it selected the correct SOUND/DEVICE -- but it changed itself to another audio device somehow. Thanks for all the helpful responses. I'm host and demonstrating PMDG's 777 sp1 to members of our San Diego SimFlite club meeting tomorrow, so all's well just in time!

No, unfortunately neither restarting FSX nor the computer brings back the cockpit sounds.

When first installing 777-200 SP1 the cockpit sounds (altitude callouts, etc.) played normally, but have disappeared (mostly) since then -- the engine sounds continue, but nothing else. By that I mean cockpit sounds occasionally play normally, but only through earphones when set to default (rather than the system speakers), so I know they're still enabled. Also cockpit sounds work fine with the 737 NGX and through the system speakers. So evidently there's something going on with my 777 configuration (I've checked all the configuration settings) that I haven't been able to find in the documentation. Any suggestions? - Maury Pratt ________________________ High end 8Gb system, Win 8.1 64bit, DX10 (w/Steve's mods), nvidia and realtek drivers.

Jim, I guess I got that information here <g>. I've now flown the tutorial flight (EDDH-EBBR) with the default MS 737 to see how ProATC normally handles Approach Control and its automatic STAR flight plan amendment under GPS control. Again, no joy. It flew the MFD's ND path just fine (up to the destination transition waypoint), but controller calls stopped about 2 waypoints before I reached the SID's transition waypoint. "Check In" does nothing, there's no response though ProATC is still running and updating the moving map. Note that the aircraft icon followed the moving map's red line path exactly, even though controller calls had stopped. Any clues? (I've installed the 1.0.3.7 update)

Jim, how and when do I reload the ProATC-generated flight plan to add the arrival STAR into PMDG 737NGX's CDU? As I understand it, once COROUTE is loaded using the CDU's Route page (including the departure SID and jet route waypoints up to STATS, but only the destination airport's ICAO), there's no way I can find to load a 2nd "COROUTE" ProATC has generated (after passing the flight plan's half-way point). And so how does ProATC know where to place the TOD if you wait until you can raise Approach Control to learn which runway and STAR to set in the CDU's ARR page? I didn't find ProATC's help (manual) to be helpful at all with regard to this 737NGX-based question. EDIT: On reflection it seems more logical to simply append the existing "coplan" while enroute by using the CDU's ARR page to enter the designated STAR/Rwy (as is normal RW procedure), once that information is available. Shouldn't that be available once you enter the transition waypoint's ARTCC? Thanks, Maury.

Mark, my thanks to you also. Graham Politt (grahm3278) offered this solution on another thread as well. And I'd posted a PMDG ticket to which Ryan came back right away with the solution, even though it proved not to be an SP1 issue at all.Thanks to all!Maury Pratt