Jump to content

Sign in to follow this  
softreset

PC-12 Version 2 Update

Recommended Posts

I thought that I fixed this..

Are you using FSX or P3D?

Send me a screenshot to my email address, please.

Share this post


Link to post
Share on other sites
7 hours ago, polizei said:

As the PC-12 doesn't have a pilot controlled prop control you shouldn't move your hardware prop lever either. Just leave it at the full forward position.

That's what I thought. It was just that when I did move it accidentally - strange engine/rpm things happened. (The Carenado Do228 is the same). That got me wondering where the control needed to be as it clearly wasn't totally 'disconnected'.

Full forward it is!

Share this post


Link to post
Share on other sites
9 hours ago, JRMurray said:

Had that very problem myself. I found that answer here on Avsim in an old thread, but briefly, keep the condition lever at 0, and start the ignition, then s-l-o-w-l-y increase the lever to about 20% or until the engine starts. This should eliminate the surge forward.

1.- condition lever at 0

2.- Start the engine

3.- condition lever at 5 % 

4.- after it stabilizes I raise it up to 50%

Share this post


Link to post
Share on other sites

I've seen that quite often at video reviews that the 'reviewer' has the condition lever at low or full forward even before hitting the starter button with the expected overspeed and overtorque

By (fsx) design no turboprop starter can crank the engine higher than 12%, so if you open the fuel flow at 11%-12%. That's why ctrl-e isn't a bad choice is this is closest to RW. 

Using ctrl-e also places the condition lever (in all planes) at 40% for ground idle which results in lower/more realistic RPM/torque than 50%.

As Bert mentioned it's essential that the throttle is at 0%.  Even 1 or 2% open again increases the fuel flow during start up with the associated problems.

  

  • Upvote 1

Share this post


Link to post
Share on other sites
12 hours ago, Bert Pieke said:

I thought that I fixed this..

Are you using FSX or P3D?

Send me a screenshot to my email address, please.

Email sent Bert.  Using P3D 3.4.18.  All else is working well, as far as I've flight tested it.

Share this post


Link to post
Share on other sites
4 hours ago, Ariel said:

Email sent Bert.  Using P3D 3.4.18.  All else is working well, as far as I've flight tested it.

Pretty sure that this is a P3D vs FSX issue... working on a possible solution for P3D users.

If anyone else, using P3D, finds that my mods are not working for them, please speak up!

Share this post


Link to post
Share on other sites

Ok Bert, I'll listen out.  As the Nav 2 DME range is visible on the HSI, if selected, it isn't a show-stopper for IFR navigation.

Graham

Share this post


Link to post
Share on other sites
12 minutes ago, Ariel said:

Ok Bert, I'll listen out.  As the Nav 2 DME range is visible on the HSI, if selected, it isn't a show-stopper for IFR navigation.

Graham

Graham, I sent you a PM with something to test.. please try it, and report back!

Share this post


Link to post
Share on other sites

Ok, flight tested your P3D mod and it has done the trick Bert - GNS 530 now working correctly.  Genius!  Pass it on it to your grateful fans...

Graham

(You are what's called "added value")

Share this post


Link to post
Share on other sites

Bert, I'm using your mod in P3D 2.4 and it seems to work fine. Have MZB set Nav1 on the GTN750 and PGY set to Nav2 on the 530 with the HSI showing Nav2 pointing correctly to PGY. The 530 shows the correct heading and distance from PGY when heading to MZB. Perhaps I'm misunderstanding something but it seems to be working the way is should here with P3D 2.4, although P3D 3x might be another story.

Cheers

Martin

 

Share this post


Link to post
Share on other sites

I've been noticing some tweaking it looks like LM is doing to P3D flight models and, perhaps, this is one of them?  E.g. A sim friend (FSX) and I (P3D) have noticed that P-Factor is significantly lighter in P3D, though, we haven't verified that it isn't something to do with our respective sims.  I think we'd need a simmer running both on the same machine to be sure.  Not sure what other changes (if any) might be out there.

Share this post


Link to post
Share on other sites
49 minutes ago, MartinRex007 said:

Bert, I'm using your mod in P3D 2.4 and it seems to work fine. Have MZB set Nav1 on the GTN750 and PGY set to Nav2 on the 530 with the HSI showing Nav2 pointing correctly to PGY. The 530 shows the correct heading and distance from PGY when heading to MZB. Perhaps I'm misunderstanding something but it seems to be working the way is should here with P3D 2.4, although P3D 3x might be another story.

Cheers

Martin

 

Martin,  I'm happy to hear it is working with P3D V2!

P3D V3 seems to look for gauges in different places.. as I figure it out, I'll start a new topic with some suggestions for P3D V3 users who have trouble with my mods.

 

Share this post


Link to post
Share on other sites
1 hour ago, Ariel said:

Ok, flight tested your P3D mod and it has done the trick Bert - GNS 530 now working correctly.  Genius!  Pass it on it to your grateful fans...

Graham

(You are what's called "added value")

Graham, that is good to hear!

Maybe this is a way for P3D V3 users to get my mods to "stick"  :cool:

Share this post


Link to post
Share on other sites

Yeah, I think P3D 2.4 is the most like FSX, after 2.5 things changed a lot with their file structure. Only reason I haven't updated is some of my old favorites like Aerosoft PB-Y, Digital Aviation Cheyenne, Vans RV7 and a few others will probably never see P3D 3 or 4 for that matter. 

 

Martin

Share this post


Link to post
Share on other sites
11 hours ago, Ariel said:

Ok, flight tested your P3D mod and it has done the trick Bert - GNS 530 now working correctly.  Genius!  Pass it on it to your grateful fans...

Graham

(You are what's called "added value")

Happy you like it!

Someone just told me that the  left outer GNS knob does not dial the COM2 frequency..

Quick fix:

Add this to the ASandYD.xml file (in the CustomPC12 folder),

place it just below the Anti-skid lines..

<!-- Fix GNS530 COM dial -->

  (L:L_Var5,bool) (L:SWAPNAVCOM2,bool) == if{ (L:L_Var5,bool) ! (>L:L_Var5,bool) }

 

 

 

Share this post


Link to post
Share on other sites

Has anyone noticed odd ILS LNAV issues?

I typically use the PC-12 on FSEconomy and fly in and out of KBNA as my round-trip hub. Last night there was pretty poor visibility preventing what is almost always a visual approach. I did 6 roundtrip legs into KBNA via ILS 31.

  • I'm using v2 with GTN 750
  • Default KBNA scenery
  • 111.95 in NAV1
  • Autopilot set to NAV
  • 316* on the course
  • Switch from GPS NAV to HDG
  • Set VLOC on the GTN 750

I'll set capture angle within 15 degrees and the HSI will reflect the course and GS. However instead of capturing the expected course the plane will make a near 90 degree left turn. It's always a left turn. After the first time it happened I then set 111.95 in the NAV2 just in case there was some funkiness there. I have a single GTN 750 set to COM1/NAV1.

It did this 3 out of 6 approaches last night. So I know it works but I can't explain why it only works 50% of the time. I did not have these issues with V1.

Anyone else notice odd ILS capture performance?

Note: I do not have Bert's v2 mods currently configured on this aircraft.

Share this post


Link to post
Share on other sites
14 hours ago, Bert Pieke said:

Happy you like it!

Someone just told me that the  left outer GNS knob does not dial the COM2 frequency..

Quick fix:

Add this to the ASandYD.xml file (in the CustomPC12 folder),

place it just below the Anti-skid lines..

<!-- Fix GNS530 COM dial -->

  (L:L_Var5,bool) (L:SWAPNAVCOM2,bool) == if{ (L:L_Var5,bool) ! (>L:L_Var5,bool) }

 

14 hours ago, Bert Pieke said:

Don't know about editing XML files Bert.  I tried a simple notepad edit but I'm not sure that it took.  No change seen in the sim, anyway.

The fault I see with Carenado's God-awful GNS 530 is with the radio frequency tuning knob (LH):-

1. The centre press function cycles the COM/NAV standby frequency correctly on the display.

2. The small inner knob correctly changes the decimal khz of the selected standby - both COM and NAV.

3 The large outer knob changes the whole khz numbers only on the NAV standby - even if COM standby is selected.  (I have found a click-spot outside the knob which will change the COM standby numbers).  Good old Carenado! There's always something...

If you think that your xml edit will cure that one I would like to have a copy, or the whole CustonmPC12  folder with it in, and I'll give it another try.

Graham

 

 

 

Share this post


Link to post
Share on other sites
1 hour ago, Bert Pieke said:

Sent you a new complete copy to try.

Brilliant.  Works for me in P3D 3.4.  NAV/COM 2 now tuning correctly as well.  Thanks again Bert.  My Pilatus is now flying like it always should have done!  (Not so sure about the great pitch down with 15 flap which makes flying an ILS glide-path a bit strange - but hey, I've never flown one for real, and never will now, so I'll have to buy that one.

Graham

Share this post


Link to post
Share on other sites
26 minutes ago, Ariel said:

Brilliant.  Works for me in P3D 3.4.  NAV/COM 2 now tuning correctly as well.  Thanks again Bert.  My Pilatus is now flying like it always should have done!  (Not so sure about the great pitch down with 15 flap which makes flying an ILS glide-path a bit strange - but hey, I've never flown one for real, and never will now, so I'll have to buy that one.

Graham

Graham,  Happy to hear it!  :biggrin:

Share this post


Link to post
Share on other sites
6 hours ago, Ariel said:

 (Not so sure about the great pitch down with 15 flap which makes flying an ILS glide-path a bit strange - but hey, I've never flown one for real, and never will now, so I'll have to buy that one.

The question is what's your speed with flaps 15°?  Even at MLW the correct VAPP 15° is only 98kts. 

With 50% fuel and only the pilot on board this results in a conventional -1° to 0° pitch attitude.

With flaps up VAPP is 118kts     

Share this post


Link to post
Share on other sites
9 hours ago, polizei said:

Even at MLW the correct VAPP 15° is only 98kts. 

Geez, is that it on this thing? I'm most certainly going in waaaaaay too fast. I normally approach at about 100kts with flaps 30°

Explains a lot!

Share this post


Link to post
Share on other sites

Here are the approach speeds   VAPP 0°/118     15°/98      30°/89      40°/84     

Unfortunately the fast/slow indicator on the PFD doesn't show any useable values. 

Share this post


Link to post
Share on other sites
20 minutes ago, polizei said:

Here are the approach speeds   VAPP 0°/118     15°/98      30°/89      40°/84     

Unfortunately the fast/slow indicator on the PFD doesn't show any useable values. 

Awesome, thanks.

Clearly this plane is not a good candidate for a busy Vatsim fly-in. But that absolutely would explain why I've seen some pretty crazy approach angles in my travels and the various YouTube videos I've watched of simmers. We're all going waaaay too fast.

Share this post


Link to post
Share on other sites
On 2017-03-08 at 4:19 PM, Lmaire said:

Thanks for the update Bert. GNS530 still turns off when i switch panel lights on. I've received an email from Carenado, They can't reproduce this issue. They ask me to uninstall and reinstall but it changes nothing....

Carenado just told me that they fixed this.

Download a new copy..

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Sign in to follow this  

×
×
  • Create New...