E-Jets V3 SP2???

[KSAN_Chuck]

The other day I downloaded and installed the E-Jets V3 for P3D V4.5.  Here are some of the issues I had:  

1.  I was not able to use the configuration tool to program a joystick button by double-clicking the function (engage TOGA in this case) and then pressing the desired button (NOT while running P3D).  I did do this using Options/Controls inside P3D.  Actually, this has never worked as I supposed it should in any of the FeelThere products I have owned.  

2.  The non-functional wiper control knobs are another minor annoyance, and once airborne (or sometime later in a flight) they turn to OFF.  

3.  As mentioned by others in this forum, the autobrake button does not work.  The workaround provided (using ^ + ALT + . or , ) to cycle the autobrakes is pretty lame, but with the annunciator on the EICAS at least you can control the settings.  

4.  I was unable to install repaints, although I have never had this problem with your V1 and V2 products.  I downloaded a few from AVSIM, including one thoughtfully provided by FeelThere, but was unable to get the new liveries to show up in the Vehicle Select GUI.  All of the repaints were specifically labelled as being for the E175 V3.  

5.  During long, slow VNAV descents (with the manual throttle closed) the aircraft did not want to slow below 230 KIAS.  Extending the speedbrakes just caused the engines to spool up, so I disconnected the autothrottle and took full control of the aircraft's speed and power settings--but it shouldn't work this way, and it doesn't with the V2 E-Jets.  

6.  The use of the ^ + scroll button to increase the rate of change on certain controls is certainly a nice touch.  However, the heading and speed knobs are very difficult to use--especially the 3-function speed knob.   The user interface for these controls in V2 was, in my view, much less prone to inadvertent inputs, especially when flying through turbulence.  

7.  I tried to update the default navigation data with the current AIRAC cycle, but was unable to get cycle 2007 to show up as loaded in the FMC.  This was after I made sure the scenario date was current.  I even un-installed the V2 E-Jets just to remove any conflicts--no joy.  

8.  On takeoff I spool the engines to 40%, engage TOGA, and roll the manual throttles to full forward.  Everything (PFD annunciators, N2, etc. ) looks good until rotation.  After liftoff the power surges up and down every few seconds, making a normal climb impossible.  This happens when I use the FMS or MAN setting on the speed control.  I was able to "fix" this problem by engaging VNAV immediately after liftoff (before gaining enough altitude to engage the autopilot), but I could get much better control of my speed and climb rate by leaving the autothrottle off and using either VS or FLC modes to control the climb while manually controlling the throttle if needed.  It shouldn't work this way, and it doesn't with the V2 E-Jets.  

Issues 1-6 are annoying, but 7 and 8 are deal breakers for me.  I have over 1050 VATSIM hours in FeelThere's ERJs for FSX and P3D, and a bit over 750 hours in your E-Jets V2 (FSX and P3D), so I thought the transition to a more modern virtual cockpit would be easy.  However, until some of the issues mentioned above get addressed in a hot-fix or new version, I'll be flying the very nice V2 E-jets, which I enjoy very much.  

Chuck Adams

 

[AndrejKatin]

I would add:

-  A Lite version, as the current model is very heavy. The passenger cabin is useless and lowers the frames a lot. The PMDG's 747-8, for example, uses fewer frames than the E170v3.
- Fix the knobs. In the manual, page 4 is written:

"The autopilot knobs are adjusted in the following ways:
• with the pointer over the knob the mouse wheel can be used to increase / decrease
the set value
• left of knob center left-mouse-click will increase value by one
• left of knob center right-mouse-click will increase value by ten
• right of center left click will decrease value by one
• right of center right click will decrease value by ten
• many knobs will react to a center mouse button click by synchronizing a setting to the
aircraft's current orientation, toggling displays, or engaging an function. "

Here with SP1 installed, these functions are not working.

[Fernando G]

And please please make it FPS friendly, I don’t know why PMDG products are by far more elaborated and run as smooth as butter and this plane is always suffering in the FPS

[Matty260191]

its the textures please have forum search someone has converted the textures to be better.

[sags]

Please fix the wx display problem in SP2.

Thanks

[Matty260191]

13 hours ago, sags said:

Please fix the wx display problem in SP2.

Thanks

What is wrong with it? no issues with mine.

[sags]

It is a problem for me and numerous others. Check the forum.

[Matty260191]

not for me that why I asked cheers.....

[Fernando G]

If you can add the fix page it would be very appreciated.

[Riky FSX]

Any news about the SP2 release?

Can't wait to use it in v5!

Thank you very much

[KSAN_Chuck]

I've flown the V3 SP2 E-175 for 6 flights, and I really like it.  Most of the issues that I listed in my earlier posts have been addressed, and now this aircraft is fun to fly.  I am flying on P3D V4.5, and I still have some issues, but they are minor.  Here they are:  

1.  The TOGA click spot is not there in my world.  I can use control + shift + G; not a big problem.  

2.  The autobrake control did not work, then it did work, then it didn't.  Then I installed a Feel There livery and it works again.  Go figure.  I know the work-around for this issue as well.  

3.  When I fly a new aircraft, I like to evaluate the auto-land capability (if it has one), in case I ever have to use it.  The fully automated landing capability (as described beginning p. 56 of the manual) is not too useful.  I had landing rates of -620 and -580 feet/second, and the aircraft really did not flare before touchdown (although I did get the ALIGN and FLARE indications).  No problem--this is a CAT II (i.e., disconnect at published CAT II approach minimums and either land or go around) aircraft for me.  

4.  After parking at the gate and turning off engines, at some airports I get the GPU available indication.  However, I am unable to select IN USE.  Again, not a big problem.  

And that's all that I have noticed.  So I appreciate the work that went into SP2, and I will enjoy flying this aircraft.  

Sincerely, 

Chuck Adams

 

[Matty260191]

2 hours ago, KSAN_Chuck said:

I've flown the V3 SP2 E-175 for 6 flights, and I really like it.  Most of the issues that I listed in my earlier posts have been addressed, and now this aircraft is fun to fly.  I am flying on P3D V4.5, and I still have some issues, but they are minor.  Here they are:  

1.  The TOGA click spot is not there in my world.  I can use control + shift + G; not a big problem.  

2.  The autobrake control did not work, then it did work, then it didn't.  Then I installed a Feel There livery and it works again.  Go figure.  I know the work-around for this issue as well.  

3.  When I fly a new aircraft, I like to evaluate the auto-land capability (if it has one), in case I ever have to use it.  The fully automated landing capability (as described beginning p. 56 of the manual) is not too useful.  I had landing rates of -620 and -580 feet/second, and the aircraft really did not flare before touchdown (although I did get the ALIGN and FLARE indications).  No problem--this is a CAT II (i.e., disconnect at published CAT II approach minimums and either land or go around) aircraft for me.  

4.  After parking at the gate and turning off engines, at some airports I get the GPU available indication.  However, I am unable to select IN USE.  Again, not a big problem.  

And that's all that I have noticed.  So I appreciate the work that went into SP2, and I will enjoy flying this aircraft.  

Sincerely, 

Chuck Adams

 

On No 3 I have only tried auto-land once and it went really well. It was a while ago so either release or SP1. Ill have to do my next one as an auto-land and see if its the same for me. Out of interest where did you land and was it ILS and a standard G/S?

[KSAN_Chuck]

Matty,

I flew the following approaches--

KPDX -- ILS 28L -- Not an actual CAT II or CAT III approach.  I disconnected the autopilot at about 80 feet and landed smoothly (-165 feet/min as reported on SmartCARS).  This is a typical landing rate for me when hand-flying the aircraft to touchdown.  

KGEG -- ILS 21 --  Flew the published CAT II/CAT III approach.  Visibility was very bad, and there was a lot of turbulence, which I thought may have been a factor in the poor landing.  I let the autopilot fly to touchdown and rollout (-605 feet/min).  

KSTL -- ILS 12L -- Flew the published CAT II/CAT III approach in very nice weather--no turbulence and 10+ mile visibility.  I let the autopilot fly to touchdown and rollout (-567 feet/min).  Since I could see the runway from miles out, I could see that there was little if any flare prior to touchdown.  

In all of these landings I followed the instructions on pages 56 and 57 of the user's manual, and in all cases I got all of the expected indications on the instrument panel (this is not a new aircraft for me, but in the past I was using the e-Jets V2).  

I am using P3D V4.5.  

Actually, as I hope I made clear in my earlier post, I am very pleased with the SP2 release.  It is a pleasure to fly, I think it is a better model than the old V2 E-175, and while I think I have identified a few minor bugs, there are workarounds for everything.  The autoland workaround, for me, is to either fly a proper CAT II approach (disconnect the autopilot at CAT II minimums for the approach), or fly to my alternate airport.  

Let me know what you think.  

Sincerely, 

Chuck Adams