Biggles2010

I should have asked before, but how much video ram is your system showing as in use with the E-jet on the ground. I think your card has 6Gb fitted and it's quite easy to exceed that in P3D5.

I assume you formatted the drive and did a full Win10 install rather than a repair. Also the P3D download could be checked with the checksum that LM provide to confirm it's correct. So there is absolutely nothing else installed anywhere on your pc, even if not in use, apart from Win 10, P3D5 and E-Jets v3, plus I assume Nvidia drivers. I mean no programs on other drives and zero P3D addons. Any software installed on a pc can be the cause of problems, even when it is not running, just through the installation process causing a file corruption somewhere.

You have a good system so are your problems occurring at add on airports, or also at default airports? What are your texture settings and general graphics settings? What screen resolution? Also have you tried it without installing Chaseplane, and is your chaseplane fully up to date. There were a few reports on Avsim about Chaseplane issues for some users, but they seemed rather random. Out of curiousity I flew about a dozen ILS approaches yesterday with the E195 at UK2000 Gatwick and Fly Tampa Copenhagen, both with and without full Autoland, using A/P and A/T down to the runway. All went as expected apart from one approach which failed to pick up the glideslope for no obvious reason. I was looking for anomalies and what I saw on quite a few approaches were small but noticeable divergences from the glideslope between 1000ft and 500 ft agl. These were always corrected before reaching minimums and probably caused by the way Active Sky interacts with P3D for wind variations and the way the autopilot then handles this. If I had seen this on any individual approach I would not have been too concerned.

I have no connection with FeelThere, but I have been using successive releases of the E-Jets for years, without seeing the problems you describe. You will not solve your problems by continually posting that it's caused by the E-Jets software, without considering other causes. Several of us have tried to help you, but you seem unwilling to accept other possibilities. The load on your system, both processor and graphics, is often greatest on the approach, especially to detailed airports. So some questions - What are your computer specs. cpu, graphics card etc? Which precise version of P3D are you using? Which precise download of E-Jets v3 are you using? What other add-ons do you have installed for P3D? Like any Orbx scenery, add on airfields, camera software like chaseplane, weather software, anything else.

What do your engines look like?

I've been curious about those two flap settings being the same, but never seen a proper explanation. This seems very plausible, with Flaps Full then being available purely for situations requiring maximum drag. Thanks to both of you for the explanations. Long after retirement, I continue to learn.

Thanks for the info on not using flaps 4 on approach. I've edited my previous post accordingly. I had noticed the flaps 3 to flaps 5 procedure on various real life E-Jet videos, but I had assumed it was down to choice in particular conditions. Is this procedure just for practicality, to reduce the number of flap selections, or are there other reasons like aircraft behaviour or drag/cost considerations?

A picture will not help you because the issue seems to be about technique. Instrument approaches require anticipation and preparation. You will not get a good approach by reacting late and then making drastic changes. If the software is simulating a real aircraft then it needs to be operated accordingly. Modern aircraft are slippery and take time to slow down. Try setting up a practice scenario in the E175 in clear weather conditions without wind. Takeoff with about 3000Kg fuel, turn downwind and fly a pattern on A/P at about 2000 ft agl. diverging about 10 degrees from the runway reciprocal, until about 10 miles downwind. Keep speed at about 170 knots with flaps2. Check the ILS frequency, and turn to intercept the localizer at a 30 degree angle, selecting APP. You should by now have looked up your Vref speed ( flaps 5 in the E175 let's assume 119 knots). Your Vapp speed will be Vref + 5 + half the headwind component so with calm winds the Vapp will be 124 knots. We want to be stable at this speed by 1000 ft agl. When you pick up the localizer reduce speed to 155. Reset the heading bug to runway heading and watch the glideslope indicator. When it starts moving down, go to flaps 3 and reduce to 145 kts. When you intercept the glideslope, lower the gear and reduce speed to Vapp +10 (in this case 134 knots). Monitor the instruments and let things settle. A good indication of stability is when the trim setting stops changing. Then at around 1500 ft agl, or soon after, select flaps 5 and set your your final approach speed (in this case 124 knots), to allow time for everything to stabilise. Finally at 50 ft you need to move throttle levers to the idle position. With experience these procedures can be varied, but this is a good safe way to set up an ILS approach, avoiding panic and over reaction. Remember all speeds will vary with weight. Please try this several times at different airfields and let us know if it helps.

I use ILS, with E195 v3, on almost every flight without seeing what you describe. Two observations though. First, I see you were intercepting the localizer with a 41 degree offset in light wind conditions. This would increase the chances of overshooting the centreline. Normal practice is to aim for 30 degrees or less as an intercept angle, with some adjustment made in strong crosswind conditions. Second, if you suddenly decrease speed setting from 170 to 130 when you have 3 or 4 miles to go, the throttles obviously have to retard drastically. Good instrument approaches require good speed control at all stages. Difficult to comment more without more info like flap settings and weight.

In your opening post you said you had a RTX2060 Super but later you posted that you have a RTX2080 Super. Is there a typo or have you changed your graphics card? It's significant because there is a big difference in performance and you are running a lot of addons. You say things are perfect when you don't move the controls, but the delay in rendering the external view during the takeoff run in your video was for the entire 8 seconds that view was selected. This is not normal. Your fps were around 21, but something in your system is restricting graphics performance. As a comparison, my own setup has 2 outside view screens running from a GTX 1080ti and to render an external view takes about 1 second. I use the E195 v3 exclusively. In my post on November 20 I suggested monitoring your CPU and GPU workloads and temperatures when the fps drops are occurring. This could help to show what is happening.

I think you may have misunderstood the use of the term 'upgrade' in this context. If you do not own any previous version of the E-jets you only have one purchase option. That is to buy version 3 at the full price. The 'upgrade' version is the same product, but offered at a slightly reduced price for those who have previously purchased another qualifying version of the E-Jets. It's like a loyalty bonus. The 'upgrade' version is not a further upgrade to the full price version 3. So, a question. Do you own any previous version of FeelThere E-Jets? If so, which product?

Kylian, Looking through your second video, you seem to have graphics issues with your system. The external view is not rendering anywhere near completely, which suggests your GPU or CPU cannot cope with the graphics settings you are using. Have you tried lowering all graphics sliders in P3D to check the result? What are your graphics settings? I also do not understand the two instances where the same window is open multiple times, on top of the main view. What other software addons do you have installed with P3D? I suspect there is a connection between your fps drops and the strange graphics.

Kylian, Further things to consider: Does your Thrustmaster TCA use any additional software that could be causing a conflict with P3D? Do you have any other third party aircraft installed that you could use to compare joystick and fps behaviour? What is happening with your GPU and CPU when the fps drops dramatically? You could try using 'CoreTemp' to monitor CPU temperatures and loading and 'GPUz' to monitor GPU loads and temps. Both are freeware downloads and quite reliable. Cpu temperatures can change very quickly under load and cause throttling. All these things may seem unrelated, but clearly something is causing the problem you are having. I have not seen other reports of this with the Ejets, although that does not necessarily mean it is not happening to others.

Most issues like you are reporting are down to individual systems and control setups. You have not provided much information for anyone to consider. Your video link shows some excessive control movements causing large attitude changes, but I can't see any reference to fps. Did you install as administrator? Do you use any anti virus? What controller are you using? There are various discussions on Avsim about certain controllers causing issues with other aircraft. How is your controller calibrated? Have you checked for any conflicting control inputs? These could cause undue loading on your system. Do you run the sim with full admin rights? Have you tried a fresh download and a new clean install, with anti virus off. Do you have any other third party aircraft installed? If so, how do they react?

Unfortunately when viewed from the normal eyepoint they are almost illegible. It's not just your setup. When the eyepoint is moved to the right, to look from directly in front of the FGP, the buttons become very clear. But obviously this is not a workable solution in flight. In time you will memorise the most common selections, but it would be better if the button labels were readable. It's one of several frustrations with this software. Some issues are being worked on but I'm not sure about this one.

I've installed your modified config in the E195 with SP2 and made a number of test flights at different weights. To be honest I haven't noticed much difference in behaviour or response so far, but it will need more testing to confirm. Did you have any expectations for what might change?

For me SP2 has been a big and unexpected improvement in takeoff dynamics, though still not totally smooth. For those still having takeoff issues it would be interesting to have more information on the circumstances at the time. The following things all have an affect on aircraft behaviour. Takeoff weight Flap setting Trim setting Rrotate speed used Initial climb speed set on AT Are you relying on the Flight Director for pitch attitude What controller is being used I base my own procedure on some advice an Ejet pilot gave on this forum in the past, plus what I had been taught many years ago. 'At Vr rotate smoothly, over 2 or 3 seconds, to get the aircraft into a climbout attitude. This will usually be about 16 to 17 degrees up, on the Attitude Indicator. Just before reaching this attitude, expect to push forward slightly to avoid over pitching. Don't chase the Flight Director. Select Gear Up and reduce nose up trim by about 0.5 to keep controls in trim. This should allow the AT to maintain climbout speed, typically V2 plus 10, until AP is selected.

I spent a day or two trying SP2 and it seems to be a big improvement. It looks like FeelThere have changed rather more than the few things mentioned by Vic in the release posting. The initial jump on rotation has pretty much gone, and the rotation seems more controllable. Not perfect, but much better. With SP2 I tested at 2 takeoff weights, 43000Kg and 52000Kg. I found I could get an acceptable rotation with trim at +3.5 at both weights. It did not need the +5.0 that I used with SP1. There is still a marked tendency for the nose to continue rising. This is partly controlled by a small amount of down trim as the gear is raised. Also don't be in too much hurry to raise the gear, it's not a fighter, and raising it too early will increase the nose up pitching effect. To me it still feels a bit overpowered, accelerating and climbing, at max takeoff weight, a bit faster than I would expect, but it is definitely more manageable than before SP2.

I tried v5 HF1 with a one month developer licence when that hotfix was first released. The E175/195 worked fine but the weather radar did not seem to work back then. I think it was sorted, as it was with P3D 4.5, with later AS releases. But bear in mind when P3D 5.1 is released it will almost certainly need a new release of Active Sky.

The problem with weather radar occurred mainly with one of the earlier AS beta versions, rushed out when LM launched HF3 without any warning. Fixed in AS7410 and later releases.

I think you've confirmed my suspicion that something in one of the the AS beta releases was preventing Wx radar working correctly. I found AS 7410 version worked for me with Ejets SP1, and it's also working correctly with SP2. If anyone wants to test their Wx radar, and their flying skills, select historic weather, mid day on 16 September at default KVPS, Eglin AF base. Heavy rain and 70 kts plus, so plenty of red on the MCP.

As a follow up to my earlier post, I did eventually get Wx radar working with the v3 E195 SP1. Previously I had been experimenting with P3D5 as well as my regular P3D 4.5 and was trying different versions of AS. It's possible this was causing the problem. I've since removed P3D5 and the AS beta. I am currently using P3D 4.5 HF3 and AS 7410. With this the Wx radar is working correctly. I only use the E195 and it's still SP1. I will be trying it with SP2 when it's available on SimMarket.

Ariel, thanks for that. The v3 Ejets are a good product, but they could be very good. The reports by users here are mainly intended to be constructive, but I'm sure that many of us wish that FeelThere would be a bit more communicative about reported issues. It often looks like fault reports are being ignored, even if you may be working on them. An occasional acknowledgement makes such a difference.

I only use the E195. I had found with my setup that trim at +5.0 is about optimum for a flaps 2 takeoff at all weights at normal temperatures and altitudes. As others have said, this is outside the correct trim range. I also found that using a slightly higher Vr helps with the takeoff transition in v3 Ejets, but it's still not anything like smooth, and certainly not realistic.

Thanks for responding, but are you referring to the non availability of SP2 or the dynamics on rotation?