lowew79

I had the aircraft configured correctly, the altitude selector was set to below runway altitude even (although I don't think this step was even necessary). The FMA screen showed aoutoland in green and all the Flair, roll out and such were armed according to the manual and the speeds were set. I was coming to KLAS and the as the flair began at the "10" callout everything seemed fine, but the plane never actually touched the runway, then it pitched up to the point of stalling (I was able to recover and land manually btw). Is there something I did wrong? Could FSX and the plane disagree on runway elevations or something?

I heard in another forum that the green speed is what you supposed to land at, but in practice that seems really really REALLY fast.

Hello! Please look at this screen shot. These are the speeds that the MFD displayed for me for approach and landing. I don't understand what they mean. I know what Vref means for example but none of these say Vref. I know what V2 means on takeoff, but what does it mean on landing? Sp please, what do these speeds mean, and perhaps more importantly, at what point in the approach and landing should an aircraft be at these speeds (I'm having a hard time with landing speeds obviously lol

This still happens occasionally, if it's pilot error I don't know what it could be.

Yeah you're right it just stinks that is that close. Changing would likely mess up the aerodynamics and the FMS calculations anyway.

Correction the message is "check alt restriction" it shows up during flight planning.

Is there somewhere to check what the FMS messages mean in the ERJ V2? In particular there is one that says "check alt restriction". Is there somewhere in the manual that lists what the FMS messages are and what they mean? I read it and couldn't find it. I dont think I should just ignore them.

I fly with FSPassengers, and my pilot is only qualified to fly aircraft under 44600 pounds empty weight. The E-175 is so SO SO close to this weight limit, but slightly (47000 pounds). So how much would I screw up if I changed the aircraft's weigh and balance in the .cfg?

it seems to be fixed after a reboot, weird lol.

*facepalm* the ERJ v2 series (the XR model in particular). Sorry about that lol.

Hi, I'm sorry if I am spamming the forums, but this plane is giving me fits, today it refuses to capture a glideslope no matter what. I tried different runways and airports, made double and triple sure that I've armed APR mode, not just NAV (it is capturing the LOC in APR mode but going right past the GS). Made sure I'm below the GS for intercept and that my speed is right. Any advice? BTW scoob are you an employee of feelthere or just the nicest guy in the world lol?

I read through the forums, and sorry if i missed it, but i didn't see anyone with QUITE this issue. My MFD (the moving map that is coupled to the FMS) seems to be skipping, or lagging may be a better way to say it. I was flying towards a waypoint, but my aircraft wasn't moving on the map, and the distance and time to waypoint wasn't changing. The only way I knew how far away i actually was, was using the FSX map. Then when I was literally on top of the waypoint, the map suddenly skipped me forward about 80 nm instantly, to my correct position. This of course threw off all the suggested descent paths, and made life moderately difficult for a while. This has happened a few times, and I am pretty sure that sometimes the FMC lags out as well as the PROG page seems to freeze and won't change the DTG numbers. (venting start) This product has been fairly exasperating on account of problems like this (venting over)

Ok I know that the ERJ does not have commanded VNAV, advisory only. I flown lots of addons that are like that. But all of them had a page that kept a real time measurement of how many Feet Per Minute are needed in order to make the next altitude restriction. Now on page 2 of the PROG section (during flight) I see where it counts down to the top of the descent, and also where it says "FPM needed at TOD". This number seem to be static however, once the TOD is reached and the descent is started it still will read the same number. I know that the magenta arrow is a real time descent measurement, but that thing is squirrely, at least on my PC. So I'd like to know if there is somewhere on the FMC that gives a real time measurement of the actual vertical speed needed to make the next altitude restriction.

Ok on a reinstall i got this, it happened on the original install too... After I selected look online for a solution the program reported that the installation was complete, I thought everything was fine, but might this explain my HUD troubles?

I am relieved to have a response, thank you! I was afraid that this product, since it was relatively old might be abandoned support wise! As far as the HUD issue, I do not have flight deck 6 installed on my machine, the forum post you linked to (not sure how i missed it) indicated that the gentleman had to re install FSX to get his HUD to work. I have a lot of addons and so forth and that would be a hassle. I will try reinstalling the product and report my results. I am disengaging the yaw damper because well, I guess I'm used to other addon aircraft where that is part of the normal operations for landing. That still wouldn't seem to explain why the yaw damper button turns off the auto pilot. The manual doesn't seem to indicate that this behavior is expected. As far as the pitch up issue, it only happens when depress (to turn off) the yaw damper, when i turn off the autopilot itself, this doesn't seem to happen. Is it possible to trim the aircraft with the autopilot on as you said in a previous post? Wouldn't the autopilot fight you and trim it back? One more thing, when i did my first install i got "this program may not have installed correctly" warning from windows. I ignored it, perhaps I should have re installed using recommended settings? I'm not sure if feelthere is paying you scoob but they should as you seem to be THE support guy for these products LOL!