JC_YYZ

There's a large list of them in this thread: https://forum.inibuilds.com/topic/6010-vars-not-working/

That's the issue I run into more times than not - the HDG and ALT SEL will light up, but V/S and NAV and APR won't light even though they are working.

I have had issues with the A/P lights not coming on - but the A/P is still working (just no indicators on the individual buttons). This can be solved by loading a default plane before loading the Falcon (at least for me). I am often a long way into the flight setup when I realize the lights don't work, so I don't often reboot and just fly that way. Not very helpful, but just letting you know I've had the same issue with the lights.

I had the option set in my P3D settings. Oddly enough I haven't run into this problem before (that I know of). I have since switched it to US settings and I had flawless flight from KSBA to KSFO with the Falcon. Thank you so much for solving this issue for me.

Thank you so much for the resolution to this! Living in Canada, I use metric - so I am surprised that European customers haven't run into this issue. I appreciate the help of everyone in this community.

I have done the default G530 with the same result. It seems that 40 - 60 seconds off the ground, on the climb, the aircraft 'captures' the altitude and levels off. After that, if I put it back into ALT SEL, it stays in 'ARM' and will climb until tomorrow. This most recent flight, it gave the '1000 to go beep' at 800, captured at 1,800 feet (altitude selector was 6000) and leveled off. Nowhere had I selected 1,800 anything. I even started the flight with the plane running (default) on the active runway, just in case I was missing something from C/D startup.

That is my next plan. Currently I am loading into the sim and disabling the VNAV option in the GTN before I setup the flight. I will see what happens.

As a follow up I have tried EVERYTHING: 1. Reinstall (including killing all folders that were left behind by the Windows 10 add/remove program before the reinstall) 2. Downloading a new installer from my store account 3. Loading in a default flight first before flying When I take off, as soon as I go into AP mode, with ALT SEL and IAS, climbing for FL110 (selected in altitude selector), the plane will 'capture' at a random altitude at 2000 or 3000 feet. After that, if I try ALT SEL again, it just stays in ARM and the plane will climb all day. The only other thing I can think of is the F1 GTN with the new VNAV might have something to do with it. But I don't know how to turn that off (I turn it off in the menu but it has no effect).

I've tried VS with no joy. It still either captures at odd altitudes or slowly stalls as it struggles to maintain lift. I am doing a clean install and cleaning up some files right now to see if I can fix this issue.

That I will clean everything up and try again. I don't remember early beta builds of this plane behaving that way. I also have the Lear 35 and I can try with that. Other planes that use a similar system would be the AS CRJ or the Majestic Q400. I can try some other planes and see. I so appreciate the help.

I start with the default F-35 on the default mission and then switch. I have also uninstalled and done a clean install a few times. I am at a loss to figure out this issue. I am wondering if it's a sim issue - but I can't figure out what would cause that in-sim versus in the actual plane.

Thanks to everyone who helped me with the AOA question. The explanations cleared it right up. Now when I am on a flight, I set up the AP in the following way: 1. The desired altitude is selected 2. ALT SEL is selected on AP panel 3. IAS selected when at desired airspeed for climb What the plane is doing is A) either indicating the desired altitude has been reached well before the actual altitude (i.e. the altitude selected will read FL110 and the altimeter reads 4200ft) and the AP will switch from ALT SEL armed to ALT SEL cap and then ALT or B) the plane will blow right through the desired altitude with the ALT SEL constantly reading 'arm'. This video (while a little long and unedited) shows some examples of both the plane capturing the altitude well below the set altitude and the plane blowing through the desired altitude with the ALT SEL still saying 'armed'. (The capture occurs RIGHT at the beginning if you watch the ALT SEL light change from ARM to CAP). At 5:15 you will see it blow through the altitude.This video was made just to experiment with the altitude so please ignore everything else. 😛

The altitude capture was definitely a mystery. I took screen shots to make sure I had them in case everyone thought I was going crazy. While I am an amateur sim pilot at best, I know enough to know that the behaviour was odd and wasn't something I had overlooked. I will uninstall and restart when I get home tonight and then re-install the 1.7b installation. I will also select a default plane before loading into the Falcon. I am a fan of regional and biz jets, so I am excited to tour around with this bird.

This is an amazing explanation. I always thought (assumed) that it was SOP to dial in a VS and let the plane do its thing - instead of understanding correlation between the plane trying to maintain a climb performance request (from me, the pilot) and the decay of speed to maintain the desired climb. I so appreciate the time you took to type this out and explain it. Many thanks.

I will give that a try. I am using P3D 4.4, but when installing the Falcon 50, I have repeatedly used the WCP Add/Remove feature but I haven't rebooted between installs. Also, I failed to mention I am using the F1 GTN750, so I am not sure if that has any effect (although last night out of CYYZ I was just using HDG mode and didn't actually have a flight plan in the system).

I am really liking the updates that are happening with the Falcon 50. Each time I see an update in my inbox, I can't wait to download it and see what has been improved. Great work. I have a question about the climb speed and I am sure that I am doing doing something wrong. On take off, once I am gear up and stable, when I turn on AP, I typically dial in a VS of about 1500 FPM by doing the following: Dial in Altitude (let's say FL120 for the sake of this example), press ALT SEL, then VS, then dial in +1500. The plane begins the climb. I usually bring the throttles back at this point to maybe 80% N1 and let the plane climb. However, the plane slowly begins to lose speed and the AOA slowly moves from the green, to yellow (activating the auto slats) and then red. I turn off AP, push the nose down, recover from the stall, back to 250kts and rinse and repeat. With the same result. For some reason, I cannot get the plane to climb without stalling. I am wondering if I am missing something? I have checked trim, mach trim is on, flaps are clean, gear is up, but the plane just doesn't want to climb. Last night I managed to get to FL110 after almost 20 minutes at about 500 fpm with two stalls. Engines at TO/GA power. One other weird behaviour last night is that I had FL110 selected on the AP altitude, the plane climbed to about 3,600 feet, ALT SEL changed to CAP, then ALT and the plane leveled off as if it was at FL110. As well, the AOA meter stayed just inside the green the entire time. I feel like the plane is dragging through mud when trying to climb and all the videos I see on YT have people happily climbing at 2000 FPM with no issue.

It's a great jet but there are some issues with dynamic lighting (if you have dynamic lighting selected in P3D options and you turn on the landing or taxi lights, they light up the whole cockpit).

Will do when I get home from the office today. Thanks for the reply!

Hi - I seem to be experiencing a problem with the connection times when I open the program (v0.4.219 Beta Exp). Once I start the program, the circle in the top-left corner of the window spins for several minutes, during which none of my views are available (I can't switch views). I have tried using the non-experimental version, and it loads quickly every time (like it used to), however the program won't let me stay on the stable version, prompting me with a message that it will be "updated to v0.4 very soon"and should download an update, putting me back on the version where I am experiencing issues. I have checked my internet connection and I don't have any connection issues with any other programs. I also have added an exclusion to Windows Defender. By the way, once the program connects (circle changes to airplane symbol in the top left), I do not have any issues with the program as long as I don't close it.

Very helpful! Thank you so much.

Jim - thanks so much for the reply. I have also been talking to someone who feels my overclock might be unstable, which is contributing to the issues as well. I am going to 'freshen' everything up and very deliberately install add-ons, do testing, and go from there. Do you have any recommendations when installing add-ons that can help prevent this from happening again?

I am hoping to get some help from the folks here. I recently built a new system for P3D. The specs are below: - Core i7-7700K (OC'd at 4.9Ghz) - 1080ti 11GB - 32GB DDR-3000 memory - 2 x 500gb SSD I am running Windows 10 64-bit and I have P3Dv4 installed. I am using the following add-ons: - AS16 (for P3Dv4) - ASCA HD - FTX Base - FTX Vector - FTX LC North America - FTX Trees - ChasePlane - Add-on aircraft: CRJ, TFDi 717 The problem I am running into is a crash-to-desktop. This happens fairly regularly, and usually only after I take off (typically 5 to 8 minutes into a flight). I can sit at the gate all day and move around the cockpit, setup flights, etc. with no CTD. As soon as I take off, I get the typical Windows message 'P3D has stopped responding...' and when I check the event viewer I get one of the two following errors: ERROR 1 (Most common): Faulting application name: Prepar3D.exe, version: 4.0.28.21686, time stamp: 0x594a7255 Faulting module name: terrain.dll, version: 4.0.28.21686, time stamp: 0x594a71d5 Exception code: 0xc0000005 Fault offset: 0x000000000007b907 Faulting process id: 0x1360 Faulting application start time: 0x01d31bacf291af08 Faulting application path: C:\Program Files\Lockheed Martin\Prepar3D v4\Prepar3D.exe Faulting module path: C:\Program Files\Lockheed Martin\Prepar3D v4\terrain.dll Report Id: 9f145c4a-33e5-44ae-b888-059f46f4958f Faulting package full name: Faulting package-relative application ID: Application: Prepar3D.exe Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception Info: exception code c0000005, exception address 00007FFD7EA4B907 ERROR 2: Faulting application name: Prepar3D.exe, version: 4.0.28.21686, time stamp: 0x594a7255 Faulting module name: menus.dll, version: 4.0.28.21686, time stamp: 0x594a71cc Exception code: 0xc000041d Fault offset: 0x0000000000005100 Faulting process id: 0xfdc Faulting application start time: 0x01d31ba7b64f11bf Faulting application path: C:\Program Files\Lockheed Martin\Prepar3D v4\Prepar3D.exe Faulting module path: C:\Program Files\Lockheed Martin\Prepar3D v4\menus.dll Report Id: 399f3fd8-d29f-4a82-9b0d-cc19499cf531 Faulting package full name: Faulting package-relative application ID: Application: Prepar3D.exe Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception Info: exception code c0000005, exception address 00007FFD81FB5100 Stack: I have done some digging online and I have tried some solutions (Affinity Mask, re-install everything, NVIDIA Inspector tweaks) and I have even adjusted my settings (Terrain Mesh to 19m instead of 10m, moving sliders to medium) and I am still getting these crashes. ALL of my drivers and my BIOS is up-to-date (as of Monday night). I am hoping that I can get some further suggestions or areas to look at. I have yet to complete a full flight. I want to add the PMDG birds and some airport scenery, but I don't want to do this until everything is running stable. Note: I have posted this in the ORBX support forum and on the Reddit /r/flightsim as well.