Other than looking messy, everything works. You can just about get to the DME on/off slide.
Thanks for this. Just looking at it now in fact. All of the buttons on the GTN bezel seem as dead as a Dodo. The GTN itself though, has just bought me back from Le Bourget to Gloucester like a charm. It is interesting…
Confirmed. Rebooted and reloaded, a.. physical buttons on the GTN750 seem inoperative. Could the other posters please confirm whether the GTN750 bezel is working on their installation, please? Many thanks.
On another subject, has anyone experienced CTD during a longer flight? I seem to CTD every time once the flight has exceeded 1.0 hour. Earliest CTD was at 1:03 of flight time, and longest before CTD was 1:56 of flight time. All CTD occurred between those two times. After each crash, I would re-do the flight in the C172 and it completed without issue. I had Task Manager open during many of these flights, did not see unusual spikes in CPU, RAM or GPU usage. First MSFS froze on screen, and a minute or so later, CTD. No issues at all with flights shorter than an hour.
I did have one yesterday at around 1.5 hours, but I don’t think it was related. Have done 2 x 2.5 hr flights in V 4.0 and all went well.
Had the same issues at least with 0.3.0, did not do a longer flight since the update.
It was also not reproducible and given the fact that there are many people experiencing CTDs, I don’t think it is specific to the PA28R.
I had a post here on my CTDs with more details, maybe you want to have a look if there are similarities/differences for you - these happened with the PA28R:
There’s also a thread on the JF forum about CTDs talking about the GNS530 that could be the issue, but I think this is just biased since of course in a PA28R forum you’ll find most people experiencing CTDs will be flying that aircraft.
But you can read a lot about CTDs with the CRJ etc. here on the forum.
The GTN 750 mod seems to screw up the UI for external view (chase camera). The RPM gauge isn’t measured, just shows zero for RPM. It also doesn’t indicate the green, yellow. or red arcs. I know it is the mod, because if I drag it out of the community folder it works as normal. It also seems to only effect the Piper, as the rest of my planes still show proper UI elements in external view.
For me it doesn’t work either. Must be a new bug. I’m on the latest update
Mine seems stable. I’m using both GPS options atm. Been flying around the new world update regions with flights up to 2.5h. Even did a couple of flights back to back. No issues so far.
I had a CTD trying to fly in NorCal but the US is super unstable for me anyways. I hav like 1 stable flight out of 5 or 6 tries in the US. No idea why.
Yes I tend to agree that is a pattern I experience too. I am beginning to think it might somehow be Just Flight Piper Arrow related as I am creating exactly the same circumstances with the default Cessna 172 and it does not CTD. I have a i9 , RTX 3080, 64Gb Ram, SSD’s and it crashes with all the graphics set to minimum, no live weather, no AI traffic but with the Cessna I can ramp all the settings up to maximum
It is usually when I interact with the Garmin 530 on the Piper Arrow or change a flight plan, it stutters, hesitates then CTD.
Had two CTDs today on long flights, about 1 hour duration. One in the UK (departure from Dundee and visiting some POIs, the CTD came when returning to Dundee) and the other one from Germany to Italy, crossing the alps, a few Nm out of SRN VOR I had the CTD.
Later I tried the UK flight using another aircraft and did not have a problem.
I’m using the Garmin 100 with state saving.
1 Like
Is the state saving working for you with GTN750 set?
When I start a fresh flight I have usually the single G100 setting and com1 and nav1 are on.
But all other stuff is saved from previous flight.
It doesn’t save the GTN750 selection. I guess it is something about the order of loading last selection and checking if the GTN750 addon is installed.
Let’s hope they fix it in the next update. Make sure you report it via ticket to their support.
Yep, just wanted to make sure it’s something not only on my side.
I totally agree with your comments. Prior to Asobo correcting this bug I purchased FCUIPC to overcome it which worked fine, but I found myself introducing an action to switch between the 10 degree bug and 1 degree switch for fine movements. 1 degree per detent for all movements are just awful. For those who have purchased FCUIPC there is a LUA script called rotaries which is supposed to add acceleration to encoders. I.E the faster you turn the greater the increments. Unfortunately despite my best efforts I have not yet been able to get it to work.
Since updating the Arrow to the latest version, I’m having a strange issue on takeoff where the plane veers HARD to the right while rolling at about 50 knots. Anyone else experiencing this? It makes it very difficult to stay on runway heading. Same on landing, have crashed a couple of times because of this. Crosswind has not been particularly strong in all observed cases.
2 Likes
Try setting the trim to be slightly nose up, I align the pip just below the neutral marker.
Seems to do the trick, though I thought they’d sorted out this behaviour in the last update or so.
Sorry forgot to mention you still need to deflect the aerilons into the wind as per normal crosswind takeoff procedure, but this stops those abrupt jerks into the wind that sometimes occur… Or at least it did for me.
For me, I found this was because I was not compensating with ailerons enough. I hardly ever get this now.
If the wind is coming from the left, you want full left aileron, and some right rudder to compensate as you being your roll
As the speed builds you gradually relax the amount of left aileron, and increase a little right rudder to compensate. The lurch I was experiencing before is now gone. It was my poor technique, not a fault with the plane. The Arrow does seem to show this more than the other planes I fly though, but all GA I fly are susceptible to it.
Wind behaviour in the sim is a little odd to say the least, so this may not be what you should do, but it appears to work for me.
The power settings looks broken… At 6000ft, the ODM tells you to go 24inHg of manifold pressure at 2500RPM, 100ºF rich of peak to achieve 75% power. However, if you do that, you will get with a fuel flow over the 75% power indicator. Mixture needs to 50ºF more or less, lean of peak, to achieve the 75% power setting in the fuel flow indicator, wich makes no sense. I’ve read a few messages back that EGT indicator must be ignored because its buged atm, and i understand it, but, looks very weird that you need to lean that hard in order to achieve the desired power setting, specially when the ODM never tells you to go lean of peak, not to talk about high power setting…
Hey everyone,
The climb performance of the Arrow doesn’t seem right to me. I’m at 9000ft AGL with 90% fuel and I’m squeezing out 200ft/min at full throttle with 2500rpm and mixture leaned for best power. IAS 75kts. That doesn’t seem right for a 200hp retractable gear single. I mean the DR400-180 I fly in real life climbs better.
Anyone have any thoughts?
try Carenado..