[Help FSUIPC 7 PMDG MSFS]

12 hours ago, John Dowson said:

Can you check that you have the following in your FSUIPC7.ini file and if not add it:

[WAPI]
EnableWAPI=Yes

The WAPI is now enabled by default, but if that section isn't there then the presets will not be loaded. I will fix this in the next release.

That worked; thanks!

[Help FSUIPC 7 PMDG MSFS]

I am seeing this issue with the missing Presets as well - just a blank drop-down for both the button press and button release fields.  LOG files attached.

Thanks!

 

FSUIPC7.logInstallFSUIPC7.log

[E190 v3 SP2 APU Fuel Flow]

Figured I would update to show after starting up from cold and dark without starting the APU - the FUEL MGT page still shows the same 181 kg/hr flow, but no total accrues under "Used".  I left it running for about an hour.

[E190 v3 SP2 APU Fuel Flow]

I've long noticed that the fuel burn of the v3 E190 (in P3D5, hf2) seems to be a bit high, typically running a fuel factor of about 1.1 as compared to SimBrief.  In an effort to help correct this, I had adjusted the fuel flow scalar in aircraft.cfg down from the default 1.1 to 1.0.  This only seems to help a bit, and possibly as a result now the CDU fuel predictions are effectively useless.  However..

On a flight tonight (FHSH-FAOR), I noticed that although the APU is off (it was turned off after engine start), it has still been sucking fuel at a rate of 181 kg/hr as shown in the attached pictures.  This alone is accounting for 8% of the fuel consumption throughout the flight; fuel that is essentially disappearing as the APU is off.  I'm assuming that this is a bug that occurs once the APU is started?  I haven't noticed fuel consumption prior to initial APU start, although I haven't had occasion to specifically check for it.

 

[Massive FPS Drop]

FWIW, I purchased through Steam (with which the sim root folder is not locked down) and copied the included SimConnect.dll file to the FSUIPC7 folder and experienced the same performance loss identified previously.  I can't currently check the timestamp of the file but I have no reason to believe it wouldn't be the same 8/8/2020.

[E190/170 aerodynamic tweak(for V2 only)]

I applied these "fixes" to the V2 E190 and it definitely brings the fuel consumption much more in line with SimBrief predictions and it's nice to now be able to land flaps 5 and still be able to see the runway!

One additional change I applied was the following:

[brakes]
toe_brakes_scale=0.80

Default brakes are 0.50 and they feel, at least to me, to be very weak especially when compared to the braking action of other higher quality add-on aircraft.  For instance, if you even slightly float a landing at KDCA and/or don't punch full reverse immediately, you're most likely going to buy the Potomac.  A number somewhere between 0.75 and 0.85 seems to bring it a little closer in line with the others.  Of course, as a disclaimer, I don't have experience with the real thing, so your mileage may vary.

[E-jets]

Has anybody had any experience running the E-jets V1 (170/190) in Prepar3d V4.4?

[P3Dv4.3 E195 Crash To Desktop]

Just to follow up, I did some more testing (and config changes on my end such as removing an overclock, etc.) I haven't been able to reduce this behavior down to a conflict with a hardware setting or another add-on - it has been occurring throughout the range of "vanilla" to fully loaded.  The behavior has changed somewhat, whereas before it would always simply freeze and disappear, I've also encountered instances where only certain parts of virtual cockpit freeze - such as the overhead/lighting panel, MDCU and Call!; while not causing a CTD but leaving the aircraft effectively unusable.

This all leads me to believe that it is basically incompatible with P3D v4.3?

[P3Dv4.3 E195 Crash To Desktop]

I am having similar problems with the E190 in P3D 4.3.  While I have been able to successfully finish some flights, I usually encounter a short freeze followed by a CTD showing no log in Event Viewer during the preflight after pressing one of the LSK keys (not always the LSK6R).  It's not reproducible by exact procedure (i.e. at the same time, every time) but it invariably does seem to happen at some point, usually in preflight, although I had one occur just past TOD when I was configuring the approach in the MCDU.

[VC Instrument Flicker & Text Color]

I have an FSX message window showing offsets 024C and 0290 for in-flight VAS monitoring and experimentation.  At the moment I'm flying the Aerosoft A321 and noticed a flicker in all of the "glass" Virtual Cockpit panels - PFD, ND, ECAMS and MDCUs.  However, if I either disable the message window logging or undock the window, the flickering stops.  It's not an obnoxious flicker, but it's noticeable just the same.  It's sort of reminiscent of the refresh rate induced flicker you get when you record a computer monitor with a video camera.

Granted that's a fairly easy workaround for a minor nuisance, but it does raise another issue regarding readability.  Is there any way to change the text color in the message window?  All of the other messages (GSX, SimStarter, etc.) show white, as I have that option checked in the dialog; however, the FSUIPC text remains red and while I can read it, it's not exactly the most comfortable thing to look at!

Anyway, thanks for the great utility!

-Chris

Edit:  This is with the 08 Feb 17 release 4.962.

[Updated E-Jets V3 In The Future?]

I'd pay $40+ just for a reboot to the E-190.  What we have now is still quite good despite its age, but a re-built VC and updated interior lighting would be well worth the purchase price.