HondaJet

A VA buddy and I found the problem. Here is the fix for anyone that may run into this issue. I had A2A Accu-feel running and had never had problems with it until now. There is something about the Lear that Accu-feel has a conflict with. When I turned it off for the Lear it no longer causes the problem. I have done a test flight up to FL430 and one VA flight at FL330 and it has been rock solid at all altitudes.

It is a little more severe with ASN on but I still get the Yaw movement and all I described above with ASN OFF and Clear Skies weather through P3D. It will take some more testing to figure out if I can make settings changes in ASN to stop this. The odd thing is with ASN running with the settings I have been using for at least a year I have no problems like this with any other addon aircraft.

I use ASN with current version and live weather. I will check the temps on the next flight. I am running P3D v3.2 in case it helps to know. No hurricane and it was normal turbulence at the time going from North Caroline to Florida. Jerry

I just did my first flight in the Lear on a 1.5 hour flight and it rocks. However, once I got above 30,000' it started with a huge yaw back and forth even though the yaw damper was on. It would do that to the full ball deflection right and left. Then once it got violent enough the bank would also start going up to about 30 degrees each direction. With both going it would almost stall. I had cruise set at FL370 and once I got back down to about FL300 it stopped and was rock solid again. It did this over and over until I descended to FL300. I tried it without the autopilot and it was even worse. I also tried the secondary yaw damper system but it didn't help either. Does anybody know how to fix this? Any idea what I might be doing wrong? I searched the forums here but found nothing on it. Nice flying airplane so far other than this awful yaw problem. My pax wanted their money back, hehe. :smile: Thanks for your input, Jerry

Guys, I post this to hopefully help someone else that might have the same problem I did. I run P3D v2.5 with all current hotfixes. When I got the PC12 I went to Cold & Dark and then proceeded through the checklist. When I got to the Engine Start every time I would start the engine (with ignition AUTO) it was at full torque and would runaway right through parking brake and across the airfield. The only thing that slowed it down was moving power lever in Beta range but by then I was off my stand and out of position. The other issue I had was with this process when I hit the starter the prop would spool up but never actually get engine start until I pushed the ignition button to ON. Then it would start but with the runway condition. I searched the forum here for an answer with marginal results and some that said "There is nothing wrong I was just doing it wrong". After a lot of playing I found that if I change the checklist slightly it solved my problem. So if you have a similar issue try this and see if it helps in your system. Set the Ignition to ON instead of AUTO; then proceed will the standard checklist from there. It started normally after I push the starter button and the torque stayed at Idle and has done so for the next 5 test starts. Therefore I think this issue is behind me now and I can go enjoy flying the aircraft. Jerry

Bryan, I thought it might help someone else if I let you know the "Clean Start" fixed the problem (whatever it was). I followed your steps above to the letter and once NGX & Reboot was re-installed it all worked great. I had FS2Crew for the Majestic Q400 already loaded in P3D and it still was working perfectly. Now both of them are operational. Thanks for the help. Jerry

Thank you Kyle, I appreciate your prompt helpful answer. Looking forward to some more Kyle videos. Jerry

Guys, I have the FS2Crew Reboot and am having problems where they recommend I uninstall it and PMDG NGX and then start over "clean". I am running Win7 and P3D 2.5+ hotfixes. Before I do the NGX uninstall I wanted to make sure I have the proper steps to do it. I seem to remember from old forum posts about doing something in the FMC before doing the Win Control Panel Uninstall of NGX. But after 1.5 hours of searching these forums and PMDG manuals I just can't find any reference to it. Can anyone provide all the proper steps to complete this process. It would be greatly appreciated since I want to do this right the first time. Thanks, Jerry

Update to my last post: I am getting no "Green Bar" even though the headset mic tests good everywhere else and it not muted (Teamspeak, Win7 setup, etc). And it all worked fine in the legacy version. I am flying P3D v2.5. I think I will try it in the legacy version in FSX and report back unless you have another idea Bryan. Edit: I went back to FSX which is still running the legacy version of FS2Crew to test. The mic would not work there either and I could not see any selections for "Headset Audio Device" in the CFG window; same for "PWR/AIR SRC". There was also no selections in the "crew region" options. I am suspecting something got messed up when I installed the reboot version for P3D. Here are the steps I did when I installed the Reboot in P3D: 1- I replaced the panel cfg in 738 main panel folder with old panel cfg file from before OLD FS2Crew install 2- Then uninstalled legacy version 3- Then reinstalled NGX v1.10.6461 4- Then installed FS2Crew Reboot Could there be files left over from the legacy version I need to get rid of? Should I start all over with uninstall and reinstall? If so could you supply proper steps so I don't miss something? Thanks, Jerry

I am getting no "Green Bar" even though the headset mic tests good everywhere else and it not muted (Teamspeak, Win7 setup, etc). And it all worked fine in the previous version. I am flying P3D v2.5. I think I will try it in FSX and report back unless you have another idea Bryan. Thanks, Jerry

I am running P3D v2/5+ all hotfixes. I had the vintage NGX working with no problems but now that i have installed reboot version my headset mic won't work. I have checked to be sure the mic is not muted, checked every step of the install for speech recognition, configured the mic again and it is working in Win7 at 100% output. Once I get in the VC I get the FO voice but when I try to respond nothing happens. I also checked to make sure I am in Voice mode in FS2Crew and HM is not on. I believe I have everything in setup set properly to work through the headset. I am anxious to get my first flight working with the reboot version. Anyone got some ideas? Thanks, Jerry

This is likely to be the last Carenado I ever buy as it was an extreme disappointment after owning PMDG NGX, 777 and Majestic Q400. I also feel the price is way beyond the quality of what they gave us with the Citation and the awful FMS. You would think they could at least get the VC quality / readability right and switches that are operated in a consistent manner. I won't be wasting my money on the Hawker as I am sure it will be just like this one and will be priced at a level of much higher quality products.

Does this also go for the Majestic Dash8? I just installed P3D v2.5. Thanks, Jerry

Thanks for the info Kyle; I already have FSUIPC registered version and have been using it for more than a year. I checked Pete's download site and found I was behind one upgrade to just installed FSUIPC v4.934 and WideClient 6.99m. Do you think I need to reinstall totally? Rob, I have had an occasional ASN crash but no simconnect errors with EFB thank goodness. Charlie, I also run EZdok along with TrackIR on the FSX machine but have not seen these crashes to be related to ASN (no direct connection I can see). I also never had any FSX crashes before SP1 but I did have OOM errors if I wasn't careful with going outside the cockpit too much. Jerry

I have tried KJFK to KLAX three times since I got SP1 and everyone has had an FSX crash with "Fatal Error - Restart Program". Every one has crashed before I completed the SID or on the takeoff roll. The last one I pulled the Event Viewer details which are: Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14 Faulting module name: ntdll.dll, version: 6.1.7601.18247, time stamp: 0x521ea8e7 Exception code: 0xc0000005 Fault offset: 0x00032eb8 Faulting process id: 0x12f4 Faulting application start time: 0x01cfb7071d839034 Faulting application path: C:\1 FSX\fsx.exe Faulting module path: C:\Windows\SysWOW64\ntdll.dll Report Id: faadfaef-2303-11e4-a229-60a44c370026 I was running ASN, Aivlasoft EFB, VAFS, PFPX, Wide Client from networked laptop with FSX on Primary machine. I didn't have this with 777 before SP1. Is it just me or are others having new FSX fatal errors (not OOM)? SP1b didn't seem to change it any for me. Jerry