If you have the GNS530 mod installed, get rid of it. I had the same issue, and getting rid of it worked for me.
You also need to have the PMS version of the GTN mod installed (obviously) but I assume you already know this.
EDIT: I see you already got it sorted, but this might help out someone else that was having a similar issue.
Well the gear at least now locks in place but there are still issues with it. The animation is still bad and what role does the main gear handle play. The release notes say to put it down but that makes the gear come down as normal even when you have all power off. I need to check this next point again but I swear activation of the emergency lever automatically moved the main gear handle down but it could of been the way I was testing.
I too want to re-test this. The first time I did it I was overspeeding, and tried to lower the gear. They ended up partially deployed, sticking out part way. I then used the emergency lever. I don’t remember raising the gear lever, but I may have raised, then re-lowered it in an attempt to “fix” it.
If you think about it, the only reason you would use the emergency lever is if you had tried to lower them normally, and it failed, so you might then decide to leave that lever in the lowered state anyway. I don’t know why you would raise that one, then use the emergency lever.
In the real plane is there a reason to do it like this though?
I use the 530 and don’t have this issue. It might just be necessary to update it.
where can you find the 414’s changelog? I got an email saying there was an update, but the email didn’t provide any details. So I clicked the link in the email, and it just takes me to Flysimware’s homepage. I then navigate to the 414’s store page, but it also doesn’t provide any details on the update?
Click on ‘Beta 1.5.0 to Current Version Change Log’ here -
https://flysimware.com/website2019/flysimwares-cessna-414a-chancellor-msfs2020/
It’s all there, starting with the most recent.
I even had this issue with the most recent version of the 530 mod installed. At a guess, I’d say there’s nothing wrong with the 530 mod itself. I’d say it may have been conflicting with another add on I have installed. When I was having issues getting the GTN750 to turn on in the 414, someone suggested that I remove the 530 mod, and sure enough that fixed it. I never did find out what it was conflicting with though.
Just had a play with the emergency gear release, and forgot not to do something on final. So I had no luck with breaking the gear by overspeeding, even in a dive at over 300kts, so perhaps I imagined that part.
With the main gear lever in the up position, I pulled the emergency lever, and the gear started to come down in steps. They came down at different times, which seemed like a nice touch.
On final it was force of habit, but I pulled the normal gear lever down, and something odd happened.
The animation reset, and it raised the gear instantly, and started lowering them again, but in the manner the emergency lever does.
But I didn’t suffer a gear failure this time, so that’s good. 
How amazing is this. I have for the first time a working nav2!
To explain, i flight outbound traking the VOR-frequenzy 114.90, witch is 32.80 away from the station with this unknonw device.
The 414 emergency gear extension system is basically a nitrogen blowdown bottle that blows nitrogen into the hydraulic system shuttle valve pushing it to the “air” position and then flows out into the gear uplocks (blows it out to free fall) and then down into the gear cylinders which forces them down and hopefully locked. It’s one way and irreversible without maintenance coming along and fixing it all up. The gear handle has to be down and the circuit breaker pulled so that you don’t inadvertently try and retract the gear after using the one-time one-way ohcrud blowdown bottle and break things even worse than they already are for you to have tried to use it in the first place……
I just bought this plane and for the life of me I can’t figure out where the clickspot is for the EFB tablet. I can see the cursor turn into a pointing finger when I hover over the A-frame of the pilot’s window but no matter how many times I click the tablet doesn’t show up.
Click spot is top corner of triangular window next to the pilot.
Thank you!
Hi all. I tried searching but wasn’t finding what I was looking for.
I can’t seem to lock on to a localize using the 530 model. It’s likely user error but I’m confused what’s going on.
For example, I loaded up a custom flight, mid air, roughly 20nm from Glasgow (EGPF). The only freq I put into the 530 was the localizer for EGPF (RW05), 110.1.
Immediately after engaging auto pilot and setting my course to runway heading, the LOC button was illuminated and the plane was steering to intercept. GS was alive as well. I hit the GS intercept altitude and the plane flew me to the runway.
I did the same steps as above, but after inputting the LOC freq of 110.1, I put my standby NAV1 freq to the GOW vor (115.4), which is right outside EGPF. Since the LOC freq was primary, my LOC light was illuminated. But I switch to the GOW freq for about 10 seconds. VOR light was illuminated. I switched back to the LOC freq. The LOC light failed to illuminated. The plane would not intercept. I was still far enough out to navigate using the LOC too.
So my issue is… I can do a bunch of VOR navigating from point to point, but whenever I activate a known, working localizer frequency, the plane fails to capture it. No LOC light illuminated. Nothing.
Yet when I start mid flight, and only have the LOC be the active frequency WITHOUT switching to anything else, the localizer navigation works. I’m so confused as to why the localizer fails to capture if switched from a standby frequency to a primary frequency.
Is this a bug or am I just doing something wrong? And yes, this issue happens on multiple flights. And when I start mid flight to do my localizer test with no other frequencies, the localizer is captured. I tried on 3 different, start-mid-flight approaches.
Hi,
Concerning the EFB tablet, I was able to bring the EFB into view by clicking the top corner of the small triangular window on the pilot side. But no matter how much I clicked there, I could not remove the EFB again.
To make it disappear you must click on the small round area on the EFB.
In effect, the camera. I believe you can turn it off, but leave it in place with the bottom power switch as well. It’s really well done, and better than having some arbitrary “fake” switches on the dashboard that some have chosen to implement to do things like open passenger, and cargo doors, and the like.
That makes sense. So what I saw was probably a failure of logic in how the animations are triggered.
I didn’t lower the gear handle, just the emergency release. Gear came down in steps as expected, and got three greens.
I then lowered the gear handle, and the gear “reset”, and lowered a second time, again in steps as before, which according to your description should be impossible if that bottle had already blown, assuming it always fully discharges.
A trivial thing to be looked at perhaps after more important things like the flight model are fleshed out.
I don’t think it’s all user error. I’m having issues with capturing an ILS too, both on the 530 and 750 versions. I tune the frequency into the standby radio and switch it it to active. I go from CDI mode to VLOC. And I arm the approach button. I also set runway heading course. Sometimes it will intercept the localiser, but more often than not it won’t. The localiser needle shows up on the display, and the glide slope bug shows up on the artificial horizon showing that I’m below it. But like I said, more often than not it won’t capture either.
I’ve not seen that particular issue, but I haven’t tried ILS approaches in the new version yet. I hope to try out 2.2 this evening.
