Ton4s

Just had to do it.

Create a new cold and dark after a successful LAND3. Works for me.

Ok. tried it quickly The CDU being a webpage has its advantages and disadvantages. A webpage is more versatile of course. The Android App has "clicks" and an option to keep the screen on. The Android app does not always connect to existing, saved situations (but saved with the CDU working, no problem), but Mark Foti's version does. Need to find a full screen browser, and set the display time-out to infinite... Foti's app/page seem a bit slower at times.... I think I'll fly with the Android app for now. When I am ready for the 777, I'll start with the Foti CDU. OMG, a 747? Didn't know that. Banking,Banking... Android app does this too. Ideal for Netflix binge watching and flying long routes :wink: Does Mr Foti have more apps??

Ok. Haven't tried it yet, but the pics look great. Wish to have known this before... Hmm, no prices, have to send a request... Strange... Update: now I know, its EUR 27.50 for 3 licences...

Samsung TAB s PC is wired and Tablet via Wifi.

Hi, not associated with the company. While looking through the Android Playstore I found a virtual CDU This is my tablet, can also connect phone, either as two of the same CDU or as F/O CDU.. If anyone knows more of handy Android thingies, plz...

I kinda guessed that , hence. Got it working? Maybe you have to load a "fresh situation" after changing the settings.... There are some unfortunate oddities with loading and reloading saved situations....

Transavia PH-HZM Land3

I get LAND3, and it does its thing. The relevant stuff from the ini file: [Displays] Glass_PFD_ND=1 PFD_low_airspeed_alert=1 PFD_groundspeed_displayed=1 PFD_Vref_plus_20_bug=1 PFD_100knot_bug=0 PFD_rising_runway=1 PFD_split_axis_flight_director=1 PFD_pitch_limit_indicator_popup=1 PFD_radio_altitude_round_dial=0 PFD_angle_of_attack_dial=0 PFD_landing_altitude_bar=1 PFD_2500_height_alert=1 PFD_show_landing_flaps=0 PFD_integral_heading_scale=1 EFISMAP_radio_altitude_round_dial=0 EFISMAP_80knot_bug=0 EFISMAP_flight_path_vector=0 ND_trackUp=0 ND_VOR_course_lines_displayed=1 ND_VerticalSituationDisplay=1 ND_RangeArcs=1 ND_TCAS_RangeRing=0 ND_ActWptData=1 PFD_ND_NPS=0 Engines_SideBySideDisplay=0 Engines_ColorChangeInhibit_5minutes=0 Engines_ColorChangeInhibit_10minutes=0 Engines_LowOilQuantityInverseVideo=1 Engines_HighVibrationAlert=1 Engines_ShowRefN1=2 Engines_ShowOilQPercentage=0 Engines_ShowMaxContLines=1 Fuel_LowAlertBelow1000lbs=0 Fuel_TOTALDisplay=1 MFD_FlightControlSurfacesIndicator=1 MFD_BrakeTemperatureIndicator=1 [Engines] Engines_DoubleDerate=1 [MCP] MCPType=1 [AFS] WingsLevelatTO=0 AllowGSCaptureBeforeLoc=0 RollOutEnabled=1 [FMS] DefaultAccelHeight=1500 DefaultReductionAlt=1500 DefaultCutBackAlt=800 DefaultRestoreAlt=3000 DefaultTransAlt=3000 [GPWS] GPWS_AltCallouts=1 GPWS_2500_RA=0 GPWS_2500=0 GPWS_1000=1 GPWS_500=1 GPWS_400=0 GPWS_300=0 GPWS_200=0 GPWS_100=1 GPWS_50=1 GPWS_40=1 GPWS_30=1 GPWS_20=1 GPWS_10=1 GPWS_MinimumsType=1 GPWS_AprMinimumsType=4 GPWS_WarnBankAngle=1 GPWS_TerrPeaksMode=1 GPWS_TerrUseCyan=0 GPWS_V1Callout=1 [TCAS] TCAS_ShowAllTraffic=1 TCAS_FilterRange=40 TCAS_FilterSeparation=2800 [Airframe] Airstair=0 ShortFieldPackage=0 FlightTestPackage=0 SteelBrakePackage=1 DualBatteryPackage=1 JumpSeat=1 Yoke CheckList L=1 Yoke CheckList R=1 ETOPS=0 DualCargoBottleSystem=1 SingleClassCabin=1 EyebrowWindows=0 SatcomAntenna=0 ISFDInstalled=1 HGSInstalled=1 HGS_AutoAIII=1 HGS_GSrefInPRI=1

I "upgraded" the Transavia Livery with autoland, just used the exact same settings from the PMDG one. Works. Exact same behavior...

ok

Hmmmm.. I saved the situation where the spd bugs did not show. I took off anyways, and during the flight I peaked at the forum. Switch was not on auto. Set it on auto, completed the flight. Loaded the "no spd bugs" situation. Behold, spd bugs showing. %&%*%???

Hi, When I enter my flight data in the FMC most of the time all goes well, v1, vr, v2 are calculated and shown on the display. But in some cases, the display still shows No Vspeed in yellow: I start looking around, clicking, but no way I can get the speed bugs to show... What did I do wrong? Thanks, Tony

Yes, I will... Hoped that PFPX made my life easy, ehhh click and fly But. Tony Thats pretty nice. But, bought enough stuff for now. Even the sim says Banking, Banking all the time :( Tony

Ah. Magvar: http://www.aero.sors.fr/navaids.html Navaids and runways: http://www.aero.sors.fr/navaids3.html And then update the NGX db with: https://www.navigraph.com/ Kept me from auto landing on aprons etc Tony.

Oh Boy, ehhh Looking at Navigraph: DEP: It says, Wavey: expect vectors to R156 (115.9 JFK) ARR: RILEY6 Anyways, did the return to KLAS, PFPX came up with something, but I used an actual route from flightaware : KLAX LOOP8 DAG KEPEC3 KLAS. No spaghetti, just an S Since i did a downwind 01L

Ah.... Just learning :smile: How it is in real life, alah. My goal, for now, is to learn how to use the FMC. I just fly around a bit, short flights, and solve spaghetties Oh. BTW. Enormous big thanks for the help !

And I think I know how I get my spaghetti. The BASET3 star is loaded, but incomplete. I then add a BASET STAR form the FMC menu, and voila, purple lines all over Ok. I just use PFPX, it gives me that.

Ah, the BASET3 STAR is not complete in the STARS database of the NGX I guess. If I load the flightplan and add the missing waypoints manually between TNP and BASET the STAR is complete....

I am a bit sure: DEP: KLAS/LAS 19R AWY WAYPOINT MT ALT WND/VEL TAS REM FUEL REM / USED LEG ACC NAME TMP FREQ GS DIST POSITION ETO / ATO -------------------------------------------------------------------------------- KLAS/19R 2181 8.6 / 0.3 MC CARRAN INTL 255 N3604.8 W11509.1 ...../..... *TOC 183FL340 302/046 450 87 5.7 / 3.3 :15 00:15 -54 461 168 N3440.8 W11535.8 ...../..... DCT TNP 182FL340 302/038 449 35 5.3 / 3.7 :04 00:19 TWENTYNINE PALMS -54 114.20 460 133 N3406.7 W11546.2 ...../..... *TOD 248FL340 302/038 449 32 4.9 / 4.0 :05 00:24 -54 421 101 N3401.3 W11623.7 ...../..... BASET3 IPHIW 248*DES 4 4.8 / 4.1 :01 00:25 97 N3400.6 W11628.4 ...../..... BASET3 ARRVD 252*DES 13 4.8 / 4.1 :01 00:26 84 N3359.1 W11644.0 ...../..... BASET3 KONZL 252*DES 19 4.8 / 4.1 :04 00:30 65 N3357.3 W11706.7 ...../..... BASET3 TRTLE 252*DES 6 4.8 / 4.2 :01 00:31 59 N3356.6 W11713.9 ...../..... BASET3 PDZ 252*DES 15 4.7 / 4.2 :02 00:33 PARADISE ONTARIO 112.20 44 N3355.1 W11731.8 ...../..... BASET3 CACTS 268*DES 6 4.7 / 4.2 :02 00:35 38 N3356.1 W11738.9 ...../..... BASET3 BASET 267*DES 17 4.6 / 4.3 :03 00:38 22 N3358.7 W11758.7 ...../..... BASET3 DOWNE 251*DES 7 4.5 / 4.4 :02 00:40 14 N3357.9 W11807.4 ...../..... BASET3 REEDR 251 128 078/000 258 8 4.5 / 4.5 :02 00:42 +18 234 7 N3356.9 W11816.6 ...../..... BASET3 KLAX/25R 254 128 7 4.3 / 4.6 :02 00:44 LOS ANGELES INTL N3356.5 W11824.5 ...../..... ARR: KLAX/LAX 25R -------------------------------------------------------------------------------- My problem is not finding the correct "real life" route. The route above is a flyable one. However, how can I let the FMC execute it? Thats where I am stuck :(

I think I understand SIDs and STARs, At least what they are for. If I plan a flight with PFPX, it actually gives the STAR, like f.i to KLAX from KLAS : 3 KLAS 1 DIRECT 1 N 36.0801 W 115.1523 2181 ----- 1 0 1 2181 - -1000000 -1000000 TNP 5 BASET3 1 N 34.1122 W 115.7699 0 0 0 0 KLAX 1 - 1 N 33.9424 W 118.4081 128 ----- 0 0 1 128 - -1000000 -1000000 ------------------------------------------------------- BASET3 is the STAR. (ILS 25R) If I load the route in the FMC (with co-route) the STAR is not in the flightplan. It has two BASET3 variants of the STAR available however. If I select either one of them, the spaghetti starts. Making me crazy :(

Hi, still learning the FMC.. I have Navigraph and PFPX. If I plan a route, I add the SID and STAR for the the runways in the FMC. However, I have no idea which one to choose for my particular route. I know that if you pick an runway, it shows the appropriate, possible SIDS and STARS, still a lot to choose from.... I try to find these somewhere in programs and documentation, but no luck until now. I pick one that seems kinda ok, stepping through the legs, sometimes end up with spaghetti Where/how can I find the options available in the FMC on charts? (Would save me some fuel too ;-) ) thanks, Tony

There is some "problem" with the cockpit design, I guess. There is an invisible bit blocking the mouse access?. If I loose the clicks, but move a bit forward with EZDOK, mouse clicks work again.

Thanks.

Hi, Started flight simming back in the days (remember Aviodome?), made sceneries etc. Stopped and flew a real airplane for a while. Recently got a laptop with a resonable processor and graphic card, FSX Steam and the PMDG 737NGX. Things have progressed over the years Updated navaids ( http://www.aero.sors.fr/navaids3.html Guy or gal deserves a medal ) after the 737NGX did a perfect auto-land on an apron somewhere Updated PMDG Nav with https://www.navigraph.com/ . Somewhere in a thread someone mentioned losing the mouse clicks, I had/have that too... I ran into the debug_log.txt in the "C:\Program Files (x86)\Steam\steamapps\common\FSX\PMDG\PMDG 737 NGX" directory and found errors of missing wav files, like: Creating systems: 01 02 Can't access WAV file: 0 (Sound\PMDG/737NGX/Various/PMDG_737_StarterTruck.wav) Can't access WAV file: 0 (Sound\PMDG/737NGX/Various/PMDG_737_AirTruck.wav) Can't access WAV file: 0 (Sound\PMDG/737NGX/Various/PMDG_737_EngineShutdown1.wav) Can't access WAV file: 0 (Sound\PMDG/737NGX/Various/PMDG_737_EngineShutdown1_Ext.wav) Can't access WAV file: 0 (Sound\PMDG/737NGX/Various/PMDG_737_EngineShutdown2.wav) Can't access WAV file: 0 (Sound\PMDG/737NGX/Various/PMDG_737_EngineShutdown2_Ext.wav) The wav files really are missing. I mentioned this to PMDG support, discussion is still ongoing, I think. I noticed that reloading saved flights in flight not always works with the PMDG 737, have to restart FSX to get it going.... Sometimes the PFD freezes, changing views gets it going again. (V1 at 50 knots) As an introduction/learning flight I flew the KLM version of the 737NGX from Amsterdam to Asia in about 12 hops. Landing, shutting it down and save the flight, continue again from saved flight. Somewhere during this flight the aircraft got stuck with a texture showing the lights on, and the fan blades remain stuck, not rotating. Doesn't affect flight Loading a new flight (not a previous saved one) get things back in order again. In the top left of the FSX screen is a tiny white rectangle, probably some PMDG stuff. Curious as I am I enlarged it, but could not re-size it to its previous size. See picture below. Ok, yaw damper needs to be on to get rid of the "FLT CONT" warning, when the center tanks is empty you get a fuel warning and need to stop the center tank fuel pumps. Still learning the FMC.... Gee, you can spend a lot of money on this hobby nowadays... But its fun. Picture with light texture on plane while light is off, the stopped fans, and the mysterious white rectangle top left: