Jump to content
The simFlight Network Forums

turbojetfan

Members
  • Posts

    18
  • Joined

  • Last visited

Posts posted by turbojetfan

  1. This was taken directly from an E170 AOM:

    "Under no ice detected with “ALL” selected on the REF A/I line and the ice protection selector knob set to the AUTO position, the wing anti-ice system is activated when wheel speed is greater than 40 knots and remains activated until 1700 ft above ground level or 5 minutes after liftoff, whichever happens first."

  2. Was doing a flight the other day a taking off during a snow storm and had selected 'REF A/I' to ON in the TRS page of the FMS  before departure since I was getting an "Icing Condition" on the center display however some time after taking off and climbing and leaving the cloud layer containing the "ice," the white messages displaying that the system was still active did not go away. I confirmed that the anti-ice system was using bleed air via the status anti-ice page on the MFD. Even after reaching cruise of FL310 in clear, sunny conditions, the white system message remained.

    So, a few minutes ago I decided to see if I could replicate the issue with NO 3rd party weather add-ons and encountered the same issue. Here are the steps I used to replicate. This on the latest version of Prepar3d (v4.5) and I was able to do it consistently with the 175:

    1. Load up the simulator.

    2. selected the "clear skies" weather scenario.

    3. loaded the E-175 into the P3d default airport (KVPS)

    4. on the FMS TRS page, selected REF A/I to ALL, ATTCS to ON, FLEX to ON and ECS to ON and used 15C as the remperature.

    5. started, the engines, turned off the APU, set flaps for departure and climbed in clear conditions  (15 degrees C on the ground to start) all the way to FL320 while having the anti-icing system active. The white text reads "A-I ENG 1-2 VLV OPEN," "A-I WING VLV OPEN," and "ENG TDS REF A-I ALL."

    The only way to turn the system off was to depress the engine 1, wing, and engine 2 toggles from the overhead panel. That turned the system off but the white system message also stayed. Didn't matter if I switched to CLB-1, CLB-2 or CRZ (I usually leave it on AUTO).\

    (These screenshots are from my test flight)

     

    2020-2-10_19-20-2-326.tiff 2020-2-10_19-20-24-685.tiff

  3. Also, this can easily be remedied in-sim by using these keys:

    Elevation Up : Hold SHIFT, press ENTER
    Elevation Down : Hold SHIFT, press BACKSPACE

    Left : hold CTRL+SHIFT, press BACKSPACE
    Right : hold CTRL+SHIFT, press ENTER

    Forward : hold CTRL, press BACKSPACE
    Back : hold CTRL, press ENTER

    It does not save these values and you must press this combination each time you load an aircraft.

  4. I'm having the same issue. If I use the keyboard flight controls, no issues. Here's what I've tried so far without any luck:

     

    -Mouse yoke causes this FPS hit as well.

    -I tried with a fresh install of Prepar3d (both v2.5 and 3.2) without FSUIPC or anything else being installed.

    -Tried with FSUIPC installed but controllers disabled.

    -Reinstalled E-jets several times (as administrator) both with and without the 175/195 addon.

    -I read somewhere that it might be an issue with the SSD so I tried moving the E-Jet installation off the SSD and on to a mechanical drive with a junction link back to P3D.

    -Tried updating USB drivers

    -reinstalling joystick drivers

    -tried with both a logitech joystick and CH yoke

    -Interestingly enough, I noticed that my CH throttle quadrant didn't appear to affect frames when moved but it has more to do with control surfaces (yoke or rudder).

     

    Running Windows 7 Pro with all the latest updates. No antivirus aside from Microsoft Security Essentials.

     

    Looking for suggestions as well.

     

    Thanks!

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.