mmerelles

@Vespa as per your video, the flap lever gauge on the front panel shows they are up/closed. BUT when you use external hardware lever the flaps may still be 0.0001% deployed (xplane does not support nullzone for this yet), thus they look up/closed while they are not.

It means the commanded speed can not be reached, you probably has some flaps still going on and the aircraft is protecting itself not to rip them. Do you use an external lever for flaps?

@albatros005 Las pantallas utilizan corriente AC (alterna) no corriente DC (directa), con solo conectar la batería no alcanza porque solo tenes corriente DC. Para que las pantallas comiencen a funcionar partiendo de cold & dark, estos son los pasos mínimos: 1. conectar la batería a ON (energía DC) 2. Encender el generador APU (para producir energía AC), o bien conectar el generador de energía externa GPU (idem para recibir AC desde un motor externo) 2.1 Opción APU: mantenes 2 segundos presionado el switch APU a la posición START y lo soltas, esperas unos 45 segundos que arranque y una vez funcionando activas los 2 switches de la APU para pasar la energía APU GEN BUS y alimentar los buses del avión con corriente AC. 2.2 Opción GPU: conectas el motor AC externo GPU vía el menu GROUND SERVICES (opción ground power unit) y despues activas la energía en el overhead panel GND PWR ON debajo de la luz GND POWER AVAILABLE 3. esperas unos 30 segundos y las pantallas se encienden solas. Nota: van a encender y mostrar información muy básica pero no van funcionar, no vas a ver mapas, ni horizonte. Para que desplieguen la información además tenes que alinear el sistema de navegación IRS en el overhead panel rotando los dos switches blancos a la posición NAV y esperar 10 minutos aprox. Para saber el tiempo restante podes rotar el switch DSPL SEL a la posición HDG/STS (status) y te va a decir el tiempo en minutos que falta (empieza a descontar a partir del minuto 7, o sea ni bien rotas va a decir 7 y cuando realmente falten 7 va a empezar a descontar 6, 5 ,4 ,3, etc. minutos)

Xplane embeded flashlight, views->toggle aviation flashlight note: HDR rendering on is required for this light to work

@jolmos those two numbers are the lowest (the # below) and highest (the # above) terrain elevations in hundred of ft amsl 006 means the lowest elevation on the covered area is 600 ft 090 means the highest altitude on the covered area is 9000 ft I can not see your present altitude on your screen capture but it seems to be high enough that the highest elevation on the area 9000 ft (090) does not represent any risk at all relative to your aircraft altitud, otherwise it will be shown colored on the display green, yellow, red, etc to warn you.

He never applies full throttle, he is applying 85% thrust for takeoff as per his fmc takeoff configuration for auto throttles. If you are planning to apply manual throttles, advance them forward not to exceed 91% N1 and you will not hear the engines screaming to hell because you are reaching speed of sound on the blade tips.

you definitively pressed TOGA or N1 or SPD mode, maybe you were rotating views on the cockpit and made an unexpected clic on any of those 3, or you have key/button mapping you are unaware off got them pressed.

if i am correct this is a known shortcoming of the actual FMC development state, on the real thing you may select the STAR and/or arrival runway inflight. It is not a requirement to be set prior to departure.

you mean, you flied them on real life or proficient over inaccurate simulations making you get bad habits?

go to the aircraft root folder / documentation / 2-interface guide.pdf Starting page 15 you have all custom commands you can map to keys/buttons of your liking. -You can move up/down the mcp switch for arming disarming A/T -you can engage TOGA button pressent on the throttle levers on the real thing -You can disengage A/T by pressing the A/T disc button on the sides of the throttles as well All you are looking for to mimic pushing the buttons like on the real thing is there.

It looks like external hardware interfering and messing with the datarefs. As per your log file you have: -"XPUIPC plugin" (which already caused issues on previous versions and the plugin developers released an updated version) -DTA rotary hardware, i am not familiar to this one. My suggestion would be, remove the plugins and the hardware, just to confirm the aircraft works just fine. Then re-install your stuff and you probably require some update, fine tuning. hope this helps

this is a known issue introduced starting 1.0.4 to fix another issue (disarming autobrakes automatically when pressing manual braking during landing). For now set the autobrakes to RTO once you are ready and aligned on the runway no longer requiring braking for takeoff. this will be fixed on the next updates.

I am experiencing the same stutters with the ixeg, it is highly noticeable and annoying during taxing not an issue inflight. Let's hope this can be fixed.

xplane has no null zone support for axis levers so far (except flying surfaces pitch, roll, yaw), it is highly recommended not to use axis for flaps, neither speedbrakes. They will keep arming, disarming, moving, fighting from nowhere due to signals coming from the hardware. It can work yes, but it is far from stable. Best advice would be use a lua script to control the axis for speedbrakes, so you can define nullzone, arm position with enough margin, also ignore noise coming from the cheap potentiometers, etc.

did you set the correct ILS COURSE for NAV1? this is mandatory for this bird.

your flaps are still at 5, the aircraft will protect itself not to rip them. You can not cruise having them deployed. unfortunately the video limits itselft pointing the throttles, it would be really nice if you can run the video again, but when you are experiencing the problem to point the camera around the entire cockpit to see what the instruments are telling you. What modes are engaged on the HSI, etc. etc.

yes please attach the video

I have read your post several times but can not understand what problem you are trying to describe. No one else gave you a response either, so i presume more people is having a hard time to understand your explanation. Can you try to explain it again please? as per your name you should speak spanish as well, you can also try to put the problem in spanish below the english explanation, several people here speaks spanish as well like myself if it is easier for you.

same here, i do use rudder pedals and RTO is disarming while taxing to the runway and applying some pedal brake during taxi.

i presume yes, at 1:43 look at the bottom right corner the speed braker lever is vibrating and seems fighting an external lever.

ok, then it "seems" your are leaving your throttle hardware leaver at a low setting and your hardware is sending noise to the aircraft retarding the aircraft throttles. It is quite important during takeoff: 1. you apply enough throttle lever for initial engine stabilization 2. then engage TO thrust for autothrottle to engage 3. Pay attention during takeoff roll when throttle ghost come on the screen and move forward your hardware lever to sync them. Otherwise your hardware is trying to tell the aircraft i am retarded, i am retarded, i am retarded and the aircraft is fighting this.

do you use any external hardware for the throttle?

i do own 2 imacs for running xplane networked for a 130 FOV One IMAC later 2013 m780 nvidia fully equipped, never had a temp issue with any addon/aircraft One IMAC later 2014 retina 5k AMD295X fully equipped, during summertime where ambient temp raises fps goes up & down (the imac throttles the gpu back) and it also goes to sleep mode for a minute or two time to time until temp lowers and comes alive again. After much researching and experiments i realized the FANs were kicking in quite late and low, presumably to make them quieter which causes the imac going sleep mode under heavy apps demands like xp. I have installed a free app FAN CONTROL, set the GPU DIODE temp as the trigger for kicking in the fans sooner and harder, haven't had any more issues on the past 6 month so far. I do not know wether the extra usage of the fans may shorten their lives, the imac 5k 2014/amd gpu has certainly a design issue for apps very demanding like xplane. The 2013 imac has no issue to me. Do not know anything about the newer 2015 imac 5k.

Shadows: To my understanding this issue happens the same to any aircraft, the specular highlight on instruments from sunshine does not get blocked like other light. This is a xplane issue they have to fix. FLCH Never seen this. Can you attach a screen capture when this happens to see mode annunciators and what is going on? did you reset mcp alt?