Why would I rant about the Kodiak here?
At any rate, and sarcasm aside, I was indeed pointing out that it doesn’t have CFD but, in bigger news, it doesn’t even have a prop.
The engine is set as jet instead of turboprop so we have no torque, p-factor, slipstream, or any other prop effects. Darn shame, that.
Figured it out, you need to put ILS Freq. in under HUD, works like a charm.
Good there are people looking thoroughly and not just enthusiastic streamers.
Agreed. This is a pretty weird one too.
This PC21 uses the default 747 FMS. Will it also use the Salty 747 modded FMS?
One the one hand I agree this plane seems a little bit too easy to control. But then I read this on Wikipedia:
the PC-21 is furnished with a digital power management system and the rudder control system is equipped with an automatic yawcompensator/suppression system to compensate for airspeed and engine power changes
So Iris either had to implement this automatic yaw compensation or find a workaround.
Ditto. Hud unusuable in rain, spin characteristics wrong; a lot of little issues and shortcomings that need to be properly addressed.
That HUD issue happens in all aircraft sadly.
How a plane responds (in all axes) to power/speed changes is completely customizable in the aircraft setup. And the IRL stabilization system is yaw only whereas going to jet deprives us of all the other glorious effects of a large prop out front. This includes (to a degree as it can be changed in the cfg) control response at slow speeds due to aerodynamic slipstream, down to and including the stall/spin behaviour.
On top of this, them telling people to turn on auto rudder in the sim is just adding insult to injury.
So, I jumped into VR with this bird last night and have a few things to bring attention to:
The “Start” button is inoperable in VR. I can open the cover, but subsequent presses on the button merely open or close the cover. Can’t manually start the plane as a result.
The F-18 HUD strays outside of the HUD glass. The PC-21 HUD does not.
Landing lights remain on outside of the aircraft when gear is retracted.
Pilot body is visible in VR. Not too big of a deal, but I would prefer to not have a mannequin in the cockpit where it’s legs and hands are jammed through rudder pedals and throttle. Only option is to remove the pilot from the PFD which results in removing him from external view as well.
Instability at high speed when autopilot is engaged. Anything above 350 kts results in a very jittery flight experience. Not realistic IMO.
External sound loop. It’s not too bad, but it is there.
Nosewheel steering is not implemented. The nose gear does not turn when maneuvering the aircraft on the ground. How this was missed escapes me.
Black bars in mirrors are reduced significantly in VR, but they are still there and very distracting when they do pop up.
Overall, it’s a nice plane, but I feel IRIS could have taken a few more weeks to squash these issues before release. I haven’t begun to dig into the systems just yet, these are just surface issues that one must be aware of before making a purchasing decision on this one. Since IRIS has been around for quite some time, I expect they will get most of these issues resolved in time. In its current state, I give it a 7 out of 10.
item#1 is not just vr related. it happens in pancake mode too.
item#5 you’re above the recommended operating speed there so instability doesn’t surprise me. operating speeds are located at the end of the manual that came with the plane. best speed @ FL100 is 335.
item#8 i think those black bars (unless i am thinking of something different and if i am, forgive me) but i believe they are reflections of the horizontal rib that goes across the middle part of the canopy, no?
7/10 - kind of agree but for different reasons. aerobatic flight model needs a lot of help. while this plane is cool for a → b hops, that’s not really its bread and butter. it needs to be better at awkward attitudes.
About number 5, yes. that is correct. It is the implementation of the buffeting that is in question. It’s very synthetic and not realistic at all.
The black bars I suppose are a reflection of the canopy frame, but it is a really weird effect. They grow and stretch unlike a reflection should. I realize this is a limitation of the sim, but would prefer to have static silver panels as opposed to the horrid reflection implementation by Asobo. The horizon is skewed in level flight as well. Totally wrong for a simulated reflection.
Agreed on your last comment. It flies like it is on rails IMO. Doesn’t feel floaty at all.
Woah, that’s bizarre. I couldn’t tell from the video, but I see it now. Edit: Looks like it was deemed necessary by IRIS due to inaccuracies with the turboprop model in MSFS, specifically engine response rate.
Hopefully they are able to sort it out in the future.
I’m not having a problem with this in VR or 2D, but it can be fiddly. Also, you don’t need to press that button to do a manual start… everything you need for a manual start is on the panel just to the right of the guarded switch… turn on the fuel pumps, ignition and manual start switch, then move the throttle over the gate when you have sufficient rotation.
I’m seeing the pilot body in VR if I do a cold start…but the Auto setting for pilot visibility works if you start on the runway with the engines running. I’m guessing that will be an easy fix.
I tried the manual start and the motor never turned over.
That sounds tad odd, since one of the problems with MSFS’s jet engine model is the incorrect reversed response rate (they spool up faster at low RPMs). Or did Asobo fix that?
Well that’s strange…it works just fine for me. I’m running the SU11 Beta…maybe that has something to do with it?
Did you close the canopy before pressing the auto start button? I had the same problem, and this did the trick.
Yes. The Start button lid closes instead. It’s funky.
I hope you actually reported these to Iris, rather than just posting them here.
