paradoxbox

Am I the only one who feels the Flysimware MU-2 is the funnest turboprop twin available in prepar3d? The aircraft is remarkably dynamic. While not quite the fidelity of the Majestic Dash 8, it's a very different aircraft and mission profile, and it's quite well done. I love how the aircraft behaves on approach or when slow and low - it will bite you if you get stupid, but if you fly it properly, it's sooooo smooooth. I find myself loading this add-on more than any other, despite having a very large library of add-ons. The MU-2 is an insane performer - very high lift when you want it, tiny toothpick wings with the flaps up, excellent power with the throttles to the firewall, respectable useful load. What a wonderful aircraft. It's got its opponents out in the real world but when flown by the book like a high performance aircraft it's really hard to find fault with the MU-2, and Flysimware has done a pretty good job with it in p3d. I'd love to see this bird brought to 2020 fidelity 🙂

If it's an actual control surface deflection (Watch the yoke to see if it's pulling back) then check that you haven't assigned the axis to both FSUIPC and P3D - they'll fight eachother. Otherwise I would suggest verifying the AP mode you're in, if you have IAS and ALT hold on, chopping the throttle in cruise will cause a pitch up and perhaps porpoising while the AP tries to find the right pitch attitude to maintain your selected altitude.

That is a good idea, I never really thought about that! Will update all my FSW aircraft this weekend as they're probably all way out of date.

Got it fixed! Looks like the font was corrupted in the windows directory. A reinstall followed by reboot restored it, now it looks beautiful in both jets 🙂 thanks very much for the help.

Update: It's definitely a font problem. After finding another post about a similar problem with an aerosoft product, I tested out the Quartz font in MS Word and it wasn't displaying properly. I at least have a good starting place now, going to try to fix this, it's most likely a windows issue not an aircraft issue.

Getting a little confused by what the problem is - it is more prevalent in the Lear but it's present in both aircraft. I did a complete uninstall / folder delete of both airplanes then reinstalled, no joy, so I uninstalled both planes AND P3D V4.5. Reinstalled P3D 4.5, then the aircraft, same story. No change. As you can see the lear's altitude select gauge is blank, but it is working - I'm able to set an altitude by rotating the dial and the AP will follow it. But it and a number of other gauges are just blank and don't work properly, and still, the payload managers for both aircraft show black empty boxes.

Unfortunately it didn't work. Files were all the same size and date anyway. Confirmed the quartz font was there but still no go, payload managers are blank.

Just looking through the old threads in this forum, one user at some point had a similar issue to mine and someone mentioned it was most likely a missing or corrupted font file. Before I go uninstalling and reinstalling everything I'd like to just try replacing the fonts..!

Yep, the dll file is in the main directory, and the xml you've posted is in the dll.xml file exactly as you've posted it.

Note it's not only the gauges but the loading panel windows for both aircraft - I can't see the aircraft weights, fuel to be loaded etc.

Hi, I just bought the Falcon 50 and it's wonderful. Unfortunately the digital readouts for EGT and N1 don't display, and a number of the other gauges in the cockpit also appear blank. Any ideas? I just looked at my Lear 35a and noticed it appears to have the same issue, the digital numbers in the altimeter are all messed up. This is the first time I've used Flysimware aircraft in P3D V4 so I'm wondering if that may be part of the problem. Also, the load managers for both aircraft are completely blank wherever text would be expected. Not running any migration tool or anything similar. Falcon 50 is a fresh install. Lear 35a works fine in P3D V3 so I know what it's supposed to look like.

You should be calculating all your speeds and power settings before takeoff. You have to base these speeds and power settings depending on your weight, the winds, the runway being used, and any other special considerations. I don't own the F50 yet (Probably will buy it soon) but I'd imagine this info is in the flight manual.

I've discovered the source of the problem. It has to do with a content and client mismatch. The content that was installed during the reinstall was not matched with the client that had been installed and that was what caused the unusual behavior with the windows. I hope this helps someone out there having the same problem, I've seen it before on the GSX forums and it has frustrated the hell out of people trying to figure it out. Make sure all content, scenery, client etc. is all on matching version numbers, otherwise it will partially work but there will be mysterious behavior in certain modules.

I'm at my wit's end here. I reinstalled P3D V3 as it was a years' old installation with performance degrading and too many mods installed. I uninstalled it completely using the uninstaller, then removed all of the remaining associated folders and files and registry entries. I then reinstalled it onto a new SSD drive with a different drive letter. The problems began when I tried reinstalling add ons which require simconnect to function. While the addons appear in the addon menu, their functionality is broken. Example: FSLabs Concorde uses some gauges which interface with simconnect. After 20 or 30 minutes of flight, the INS gauges begin to freeze up and behave very strangely. They don't all go out at once but they all fail eventually. The dials can no longer be moved and the displays become frozen and garbled, it's not a simulated failure, simconnect is losing connectivity with them and they're breaking. Another thing I noticed was that when changing the fuel quantity in the FSLabs loadout menu, the "Total Fuel" quantity slider no longer adjusts the amount of fuel in all the other tanks. They can each be moved individually and the change is reflected in the aircraft, but the total fuel slider no longer does anything. This is more evidence of a simconnect issue. Another example: ActiveSky 2016 can inject weather into the sim and it works almost perfectly, except when I try to make a Weather Request from the add-on menu in the sim, nothing happens. There is supposed to be a window pop up that lets me select from a few different options i.e. local airport, local weather station, winds aloft etc. This can't be brought up anymore. Another example: GSX / SODE / COUATL are all running and test fine, but again, when I try to bring up the GSX window to do a pushback or loading or whatever, the window doesn't come up. But it is running and I am able to access the parking editor and aircraft editor. I've tried uninstalling and reinstalling the simconnect msi's in the redist folder that come with p3d but it doesn't seem to make any difference. The problem persists even on a nearly bone-stock P3D V3 installation - just the Concorde and no other mods. I've also done a full uninstall and reinstall of all add ons and p3d itself to no avail. I'm not running P3D networked to anything else, it's all supposed to be a self contained installation, not a networked one. Any solutions would be welcome.

I would appreciate some assistance with this. I have recently been having nearly the same problem. I'm able to start flights and get the test pattern and audio call but at some point during the flight the radar stops working and pressing the test button no longer works. I've experienced this in both the 777 and 747 and it's a fairly recent problem on my system. Using P3D V4. Have sent support tickets to both companies but would like to hear any suggestions. FSUIPC is not installed in either sim.

Nice catch. Send a ticket to them, they'll work on fixing it in the future.

If you use a consumer grade throttle quadrant like saitek you'll only be able to get full reverse when you put the lever into the reverse detent. but using F1/F2 you can get fine control of the reverse thrust. Reverser policy depends on the airline and the airport you're flying at. I typically use full reverse when able and reduce to idle rev at 80 knots, then stow the reversers at 60-40 knots depending on runway conditions. Full rev is not recommended below 80 due to FOD risk, but idle reverse does not carry the same risk of blowing crud back into the engines so you can keep it there longer. On the topic of reversers, a thread I made on pprune a month ago had a lot of interesting replies. It was regarding uncommanded thrust reverser deployment in flight at various stages of the flight. A lot of excellent info came out of that thread. If you fly jets it is well worth reading as it may save your life some day - it's one of the few plausible incidents that can kill you in seconds but is recoverable with quick action.

Level D is working on a 757 for 64bit. Their screenshots look promising. It is safe to assume they will release a 64bit 767 afterward. I had previously predicted that PMDG will do a 767 but with Level D back on track and making real progress, I do not think PMDG is going to dilute sales by doing a competing product with a company that has so much history and experience with that specific platform. I think we may get a classic Boeing such as a 727 or maybe something new and unexpected such as a DC-9. The other aircraft to watch are anything Mr. Randazzo flew in the earlier stages of his pilot career - I believe we have most of them in the sim so far but possibly not all.

I have reported this bug before. I was able to turn it off using my saitek switch panel's "Fuel Pump" switch. As far as I know there is no way to turn off this bug. The fuel pump seems to be either hardcoded into FSX or coded into the PMDG aircraft. I was only able to turn it off using the saitek, pressing the keyboard fuel switch might be worth trying but I couldn't turn it off using anything other than the saitek switch.

There are a lot of differences in ground handling and takeoff with the 300ER Rotation rate is very different in 300ER, you have to be careful of tailstrikes. Same for landing. Much of it is very similar, but the 200LR / LRF seems to be "stronger" - basically the same engines on a smaller airframe, electronically derated by the factory. 200LR is better if you want to make extremely long haul nonstop flights to difficult destinations on the opposite side of the world. There are not many airports outside of the range of a 200LR. 300ER will be slightly more limiting (Though it still has huge range if you want to carry a normal passenger load)

Oh wow, a Falcon 50! That is more than enough for me. I have been waiting years for a well done Falcon to show up in a sim. I have flown Wilco's Falcon but uh.. I'll refrain from saying anything else about it. (If you've got nothing nice to say..) I'll break out my wallet when FSW releases that bird. Very nice! The MU-2 has been a very fun turboprop experience.

I was really glad to find Flysimware recently. I hadn't known about the products from this company until last month. I now have the lear, 441 and MU-2. I might pick up the piston twin too. But what's next for Flysimware? Everyone knows there is a huge vacuum in the flight sim world for realistic high performance business jets. Is there any chance of a modern high performance bizjet by FSW?

Sorry but this thread is the height of ridiculousness. Reminds me of a customer from Singapore I fired a few years ago.

Had a nice flight tonight from KLAX to PHNL. It pushed the limits, there was a strong headwind the entire trip but with careful step climbs I was able to make it and still have a safe reserve. I was grossly overweight (Max passenger and cargo load) so the cruise was probably not as efficient as it should have been. The engines were at max thrust the entire cruise but at the very high cruise altitude this was not much of a problem. I'm using the experimental FDE you posted. I'm not too sure about the realism of this, but I will poke around the net and see if I can find some more info about how the engines behave in cruise and in particular during long range flights. I am not sure the Real Lear 35A could make this flight in similar conditions at these weights. I'd also like to check whether the apparent lack of power at high altitude is accurate. I have a feeling the engines should burn more fuel but also produce more power at very high cruise altitudes. I was never able to catch the barber pole at any time of the cruise. I was constantly about 15-20 knots slower than the pole. At FL50 the barber pole was around the 200 knots range.

The manual in that link is gone. Does anyone have a copy of this?