Ádám Balogh

This early descent is just one issue, but the topic is about control problems. What is the best joystick setup for Saitek wheel? For other (yoke-driven) planes I use the wheel with zero null zone and maximal sensitivity. I used E-Jets v2 with zero null zone and about 80% sensitivity. However, V3 behaves as it would have very large null zone on his own, and then sensitivity is too high: small yoke movement, nothing, a little bit more, and the plane starts to bank or pitch very quickly. It is like flying the plane with switches. With other planes I have no such problem, not even with V2.

I used this one, but did not upgrade yet to 1.0.2. Mine is 1.0.0. My speed was Vref+5 exactly. I did not get stall warning or stick shaker.

Absolutely. LOC was already active, GS was armed. Nav source was V/L. It also could not be FLCH, because ALT was set to 1200' and I caught the plane at around 700' when I first heared "glideslope".

SP2 is installed. In my first flight with it I was appraoching LYPG. The approach starts very low, about 1200 feet which is closer than 5 nm. That is why I set flaps to 5 and slowed to approach speed (Vref+5) before catching the GS. As soon as I reached that speed the plane started its descent and I got lots of "glideslope" aural warnings. Normally I catch glideslope around 160 knots and flaps 1 or 2. That works.

Why? Is it normal that the plane starts descent miles before reaching the glideslope? Is it normal that the plane does not decelerate on approach with idle thrust? Anyway, I am flying for 17 years by now, and there were only a few planes I had problems with. I had no problems with E-Jets v2, they where very smooth. V3 jumps around, even autopilot cannot fly it smoothly on a windless approach, it pitches up and down, banks to the right and left. If I take it over in the wrong moment, the plane is out of the correct pitch and bank.

Actually it became worse. The control issues are still there, but now the autopilot does not work. It could not follow the VNAV path, throttle increased to above 90% N1 and the plane was sinking too slowly. Even worse, it began the descent for approach much before the glideslope. I had to take over early and made my worst landing in my life: -813 fpm and more than 5 degrees bank. I am not a perfect lander, but I cannot remember landing this plane below -400 fpm and v2 below -200 fpm. The current version is unflyable.

Hello, I just noticed an issue with the control of the yoke in E-Jets v3. I start with cold & dark and get a VC view from too far. This time the yoke still works as it should. However, after I zoom in and move a bit to the left the yoke begins to flicker between the state I turn and the centered state. Zooming out and restoring the view does not help. Even without any yoke connected to the USB, just keyboard, as shown in this video: Flickering With my Saitek yoke I turn it fully to the left, right, up or down, but it still flickers between that state and the centered state. I am not sure whether it happened earlier, but maybe this was the cause of my dangerous takeoffs and landings? I also tried to update to SP2, but the issue is still there. What could be wrong? This only happens with these planes, not with others.

Hello, The v2 was very smooth, I really enjoyed hand flying it. However, v3 behaves very hectically. I have my null zone set to zero, but still I feel that I fly it with switches. For example, at takeoff, I slightly pull my yoke, and nothing happens. Then all of the sudden the nose jumps into the air. Landing is even worse: I cannot make smooth maneuvers because the plane does not nothing on my fine yoke inputs but banks suddenly after a point. Also, at landing around 10-20 feet I do not pull the yoke to let the plane land smoothly, but it simply reclimbs to 20-30 feet. I never made a nice and smooth landing using v3, only high bank, high touchdown rate landings far from the center line. Almost all my landings with v2 very smooth and very neer the center line.

It is working fine. I tried the KLM liveries from iniBuilds. Really, it seems that the common textures of the 190 are in the "sharedtexture" folder of the 170, while other models have them in their "texture" folder. It is not very logical, but working. However, even the house livery refers to "..\texture" in its "texture.cfg" so it seems that the original intention was that all models have their common liveries in their "texture" folder.

Yes, it seems so. Is in only an error in "texture.cfg". Are the generic textures of the 190 in the folder of "sharedtexture" of the 170?

Hello, I just bought all four planes (thus both packages) yesterday and installed them. However, I have a problem: the installer did not install the generit "texture" folder, just "texture.house". However liveries (such as "texture.house") are referring to this folder in their "texture.cfg". Where can I get these files?