niokilt

ok my feedback. In think that you were right about the hardware. I use a joystick for the tiller. there were indeed some other assignements to the trim like you said and removed everithing so that the only connection is on the yoke. So of course I noticed the change, but strangely, it stills behaves sometimes like it is working on its own, especially when reaching altitudes or capturing the glide... honestly i guess it is a lack of knowledge on the FBW system. I need to read deeply the manual and watch some you tube videos. because obviously, it is a different aircraft to fly.. and I don't find it confortable as when I fly the NGX. I found that on the fms options you can set on the speed tab the FBW bug and I noticed that when putting this bug over the speed you re flying it sounds easier.. but i don't know why.. so I need to know ore about this.

ok I understand, I am going to check that and I will comme back to you! thanks

Hi thanks for the comment, No I didn't try to remove the hardware during the flight, the thing is: it doesn't do that with every of my add-ons... otherwise, it is true that normal buttons of my yoke are assigned to the trim and it does control the trim of the aircraft,( which i can see moving on the 777 yoke) but that sounds normal doesnt it?

hi, i have read some topics about trims problems but i didn't find one relating mine. i have just started a flight with the 777, everithing is fine and configured as it should, espacially the trim. couple of seconds after rotation, the aircraft pithes down, alone. I mean without any controls input...., ok, i look down the trim is moving down itself without command.auto trim, yes ok but not possible that way.... Ok i stabilize the aircraft, perfect stabilzed cruise flight at low altitude, suddenly its starts again, pitches down or up (it goes on a way or the other) without any input from me. It sounds like a bug, the aircraft is impssible to fly... please help!

Hi, I guess this subject has been already discussed before, but I don't find any of it. I don't understand why the values of MTOW that are listed on the payload page of the fmc of each versions of the bird (600,700,800,900) are so far from real values that we can get in the FCOM. for example, the MTOW of the 800 shows 79.2 t but the FCOM indicates 70.5 t. with the 700 it is worst almost 10 t differences. Thus, How can the flight model be accurate from a performance point of view, if the fmc is filled in with wrong values? thanks nic

I know that you fly the FD which brings you to v2+20, and as you said not the magenta bug,so it is not not normal to have this magenta bug on the mcp passing from the value of v2 set on the mcp speed window to v2 +20!!!!this is what I read in the ngx: if my take off profile is v2=150 kts, you put 150 in the mcp speed windows and your magenta bug shows 150kts. during lift off the FD tells you to fly v2+20 170kts then the magenta bug goes to v2+20 as well as the FD commands you, but the speed on the mcp speed windows stays a v2 150. When I pass the acceleration alt, flying manually, I will call for bug up and the pilot monitoring will set manually the magenta bug to the green bug up speed by turning the mcp speed knob. And when the bug is set at bug up you realize that the speed entered in the mcp speed windows indicates 20 kts less than the magenta bug!!!! and bizaarely when you engage the AP the mcp windows displays suddently the bug up speed!! Im going to check this next month in the sim anyway..

ok I did several other engine failures after take off and the command speed bug goes to v2+20 and after few secondes it goes to v2 or actual speed or v2+20. so ok, I am sorry for"inserting facts" . but I don't understand why during normal take off it goes to v2+20. cf flight crew training manual "command speed"-"take off": "command speed remains set at v2 until changed by the pilot for acceleration and flap retraction or until a subsequent pitch mode is engaged". So after lift off in the mcp speed windows you have v2 and on the PFD you have v2+20. when you pass acceleration altitude(still flying manually) you set bug up on the mcp and then you realize that the mcp speed windows indicates 20 kts less that the magenta bug on the pfd! tell me if this is normal

explain.

I really think the command speed should stay at v2, independently of the FD. As I mentioned before if an engine fails after v1 but before v2 the command speed bug should stay at v2 but it goes to v2+20 what ever, but in the sim, the problem is the FD which follows the command speed bug!! so in this case of the engine failure before v2(and the same at v2) the FD tells you to maintain v2+20 while you it should tell you to maintain v2 or the actual speed. so it is definitly a problem..

you will find that the command speed bug goes to v2+20 just after lift off where it should stay at v2. I have posted a new thread about this! I think that this is definitely not normal!

hey pmdg, you made a wonderfull add on , it is really fantastic!! however, I have a little problem. I am not an NG pilot, I just hold the type rating and it is start to be old now, so I m not sure if I m right or not,but! during take off, as soon as I rotate the aircraft, the command speed bug goes to v2+20 instead of staying at v2. the mcp's windows speed stil indicates v2 but the bug goes to v2+20. So I tried to simulate an engine failure after v1 but before v2 and I expected to see the command speed bug to stay at v2, but it goes to v2+20. I asked one of my friend who flys for transavia, he told me the last aircraft he flew had the latest fmc's software, 10.8 alpha, and the command speed bug stays at v2 what ever. So I was just wandering if this issue is definitely a bug or not. Thanks for having reading me nicolas jambert