Jump to content
The simFlight Network Forums

KSAN_Chuck

Members
  • Posts

    12
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by KSAN_Chuck

  1. 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
  2. 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
  3. After looking at this a bit closer, it seems I kept the download link for E-Jets V2 but lost the link for V3 (a different order). The file I was trying to install was ejetsv2-p3dv4-3 sp2. This looks like a V2 installer to me. So I need the link that will allow me to download V3 SP2. My V3 order ID is *. If I need to submit a trouble ticket on this, please let me know. Thanks Chuck Adams -- * Edit: order # removed. Posting order details on a pink forum means you have shared your purchase with every thief on the Internet. - Mods.
  4. Is there some trick I am missing when I try to install the E175 V3 SP2? I was using the E175 V2 with absolutely no issues, and months ago I had completely (I thought) removed the E175 V3 SP1 package (you can see my earlier post as to why). First I installed the V3 SP2 package, thinking that if the V3 SP1 package was required, the install would be halted. The install went as expected, but when I tried to select an E175 as my vehicle, it was clearly a V2 aircraft. In my startup menu under Feel There the only listing was E-Jets V2. So then I un-installed the V2 package (no V3 listings in the menu as noted above, and none in the control panel either). I then went in and deleted every Feel There directory in P3D and in my user data. I then installed the V3 SP2 package (I had NOT reinstalled the V3 SP1 package), and got the same result, including the E-Jets v2 listing in my startup menu. So to repeat the question--if you are currently using the E-Jets V2 package and you want to migrate to E-Jets V3 SP2, what steps should I take in order to un-install the V2 package and successfully install the E-Jets V3 SP2 package? FYI, I am not trying to run with V2 and V3 installed at the same time--I want to evaluate V3 SP2, and if that package runs as it should all will be just fine. Sincerely, Chuck Adams
  5. 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
  6. I un-installed the ERJ using IObit Uninstaller. I then deleted the ERJ directory out of Sim Objects/Airplanes, and I deleted the Feel There directory out of the Prepared3D v4 directory. I then loaded a scenario containing a default aircraft (Mooney M20), then selected the ERJ. Unfortunately, I got the same results--no request to approve the ERJ's gauge files, and I am not able to do anything except select items off the ERJ's menu bar (Thrust, Overhead, etc. ). So I am stumped. I slick my SSD every 6-12 months, and when I reinstall I will look for the latest P3D V4 update (which I am NOT running right now), and then perhaps I'll give the ERJ another try. Thanks to scoobflight and FeelThere Ariel for your prompt replies.
  7. Ariel: I do believe I am using the ERJ for P3Dv4--as noted in my initial post I am using FeelThere ERJ-145LR for Prepared 3D v4.1.... (Product Version 2.0.0.31). However, I am not using the latest version of P3D v4--I am currently running on P3D version 4.1.7.22841. scoobflight: No, the sim did not ask me to approve the ERJ's guage files. Not after the first install, or after I de-installed and re-installed. Hmmm.....not sure how to fix that, but yes, I usually get some sort of approval question after installing a new aircraft. FYI, the only other non-default software running in the sim is PMDG 777-200, iFly 737 and Flight1 Cessna Citation Mustang--and a bunch of Orbx scenery.
  8. I just purchased the ERJ for P3Dv4. I loaded and activated it, but on first glance the HUD was not visible (I tried the "H" option and pushing the W-key to cycle through the views in the 2-D cockpit). Then I uninstalled and reinstalled, but got the same results. I started P3D with a default aircraft (Mooney) scenario, then loaded the ERJ. It was cold and dark, as expected. Then I thought I'd just start it up and perhaps, with power, the HUD would appear. To my surprise I am unable to make anything except the menu bar (thrust, throttle quadrant, overhead, FMS, etc.) respond to my mouse clicks. I cannot start fuel pumps, turn on the APU, or turn on exterior or interior lights. Any suggestions will be followed to the letter. I am using P3D version 4.1.7.22841 and the FeelThere ERJ-145LR for Prepared 3D v4.1.... (Product Version 2.0.0.31). I have 875 hours on this aircraft using FSX, and I would love to get it running in P3D. Thanks, Chuck Adams
  9. Thanks for the prompt reply.
  10. I have a question about the FeelThere TBM850--does it have a 2-D cockpit? If not, does it have some sort of HUD like the very excellent ERJ V2 or E-jets V2 that I enjoy so much? What I am looking for is a high-performance GA aircraft with (1) a 2-D cockpit (because I hate scrolling all over the place just to flip a switch), and (2) good forward visibility, even when the nosed is pitched up during takeoff. Thanks P.S. I did read the forum rules, but I can't figure out if this is an approved topic, or if it should have been posted in the "Other" forum.
×
×
  • 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.