Any of you experience the “flying screw” bug? I got it on my flight and then there is a screw just appears on the left window. see pic
1 Like
Yes, I thought i was going crazy lol
1 Like
HAHA me too! I think this is a bug that needs to be fixed. I thought something was wrong with my eye
@SiRRiPPERORiG just flagging this bug here for you Alex. Seems like some texture issue that cause the flying screw in the cockpit
We screwed up when re-exporting the models, but the screw has been screwed for the next update.
7 Likes
@SiRRiPPERORiG talking about pun hahaha. Loving this plane, you guys did a wonderful job
1 Like
We will rebrand to FS2Screw.
8 Likes
Thanks again that’s really interesting and useful info.
I just remembered one other thing from my setup and bindings session. Can we have the Altitude select and VS select values that are displayed on the KAS297 exposed to a couple of LVARS. The usual sim autopilot variables only get populated when the relevant modes are active/armed.
1 Like
Thats something we are working on but it is very invasive, so we won’t risk it before the break.
Hi,
Bought the PC-12 today and noted the following on my first flights:
When tracking a VOR radial, the number 2 CDI is way off.
I made the screenshot below to illustrate what I mean. In this case I tracked the 060 radial from SBG VOR outbound with both Nav radios tuned to SBG (113.80).
The RMI worked as it should, as did the EHSI.
But the no. 2 VOR indicator did not. The CDI needle should be in the center and not to the left.
The second issue is that when selecting NAV, the autopilot will not intercept or track a given VOR radial.
Instead it follows the HDG bug, although HDG is deselected and not used.
Thirdly during takeoff, when rotating, the airplane skids to the right as if it were on ice. It required a bootful of left rudder to avoid running over the runway edge.
It would be great if you could have a look at the issues I had encountered.
Many thanks in advance!
This guy done a great vid for the carenado, but has just done one for this beauty. Hes a real world pc12 pilot and finds a few oddities, but was overall impressed. Well worth the view (and subscription)
6 Likes
Let’s address each one.
I can see how you have come to this conclusion. There should really be a special note in the manual about this configuration but there is no mention. Here’s how it works. The CDI shows the needle deviation for NAV2 but does not control the OBS input for NAV 2. The OBS Knob only rotates the physical CDI compass rose but does not have an electrical OBS connection to the NAV 2 radio. Setting the compass rose here then is just a reference. To confirm that you’ll notice that if you turn the CDI knob so the compass rose rotates through a full 360 the needle deviation will not move at all. When in fact there are 2 VOR radials that should centre the needle. To set the actual NAV 2 OBS ( I.e the electrical interface) use the HSI control panel CRS knob while the HSI is selected to show NAV 2. The 1_2 button toggles between Nav1 and Nav2 when the NAV source is set to a VOR or LOC.
I have no issue following a NAV source with the autopilot so perhaps something was not set correctly. If it does it again some screenshots specific to that might help someone spot what’s wrong.
I can only assume you don’t have the latest version of the aircraft. The skidding thing was fixed in a very recent update.
Hope that helps.
Sorry but which checklist you are referring to? Is there an in-game checklist in addition to the one in the toolbar? There’s nothing in the manual.
Thanks
The document checklists are not in the manual but a separate checklists pdf.
Hi @Sling380 ,
Thank you for your thoughts!
To be honest I have NEVER come across such a behavior on any aircraft that I have flown IRL. Usually the HSI is tied to no.1 Nav receiver and the second VOR/ILS indicator is tied to the no.2 receiver. In case of a malfunction, the instrument switching system will allow to cross tie those instruments in some aircraft. The behavior of the OBS in the PC-12 seems to be bugged to me.
I have noticed today that sometimes both the green HDG and the green NAV indicator lights are illuminated. This is when the aircraft tracks the HGD bug, although NAV was selected. But this happened only sometimes and at random.
As for the slippery behaviour on takeoff, I tried it with the rudder trim centered, outside of the green band. This seemed to help a lot, though more right rudder was needed during takeoff roll.
Lastly, since I only purchased and downloaded the PC-12 yesterday, I surely hope to have the latest version.
1 Like
Me too,
Unfortunately, every discussion that criticizes the take-off and landing behavior comes to nothing.
I have several hundred hours on the Meridian/M500, it also has a PT6A, but I have only ever experienced such yaw in cold, slippery conditions.
But if the wind and weather conditions are good, you can land the Piper with two fingers.
yes the Piper is much smaller and lighter than the PC12, but is the take-off and landing behavior so different?
I don’t know, but I find it hard to believe
1 Like
Let me provide some insight based off of my experience, before pointing to our PC-12.
When in the PC-12 sim we did numerous take-off and landing tests in varying wind conditions. Every behaviour observed in the sim was questioned on the spot and verified against pilots & instructors that were with us in the sim and in the cafe.
In a no-wind takeoff with trims in the green, the plane would require right rudder in the start of the roll. Not as much as the Kodiak, I’d classify it as a small push on the right pedal. This would quickly fade out, entering a no-pedal zone towards the middle of the roll.
After that area we would enter a “left pedal” area where mild left pedal input was needed up until rotation (70-85kts depending on flaps). The more the speed went up, the more we needed to push the pedal as the rudder trim became more effective with higher dynamic pressure (airspeed).
In our plane the transition is not as smooth because the air/ground switch happens instantly. As soon as the plane crosses stalling speed it is considered airborne. That is the half we can’t control.
The other aspect of it is rudder & trim effectiveness. It seems like we need to dial down the trim effectiveness a bit, while increasing the rudder one in order to maintain the current authority but make the transition to your left foot less abrupt.
There are also other areas of the flight model we are looking to improve, but such changes require a lot of flight testing to not break what is good and improve what is off, so it will take some time. In any case our goal is not to make the plane easier, but closer to the real thing. If something is dififcult/easy IRL it will stay this way in MSFS and vice versa.
7 Likes
Please, I’ve mentioned it before, I think the flight model is absolutely great!!!
I just have a hard time believing the takeoff and landing characteristics are like, I’ll try to put it better “sensitive” like in the Simworks PC12,
but I’ve never flown a PC12 in real life,
If so, I couldn’t fly a PC12 without a sufficient type rating.
OK but maybe that should always be the case 
[SimWorks Studios PC-12 (47 and NG) - #714 by CplHak]
I am aware about the pdf but what about the checklist mentioned in the above post?