mmerelles

The speed brakes will deploy when reverse thrust is applied upon touchdown no matter they are not ARMed for landing. This is how the real aircraft operates. Or can you elaborate a bit more what issue you are experiencing?

-to manipulate cargo doors you use the aircraft ground menu. there is a checkbox there for opening closing the door. You will see the warning light on the overhead when open. -eyebrow is a preference, by default is disabled. Go to aircraft preferences and the option on the bottom is to enable/disable eyebrow. If enabled you use the mouse to put/quite the sun protection. -cockpit door, being on the cockpit turn the camera 180 and clic on the door to open make sure you are running 1.1. you can verify this on the aircraft left side pop up screens over the frame. Or on the fmc by going to menu, fmc, ident page. hope this helps

i do use navigraph manager, zero issues to update

maybe you should try to download the installer again and reinstall it? the link was available for a few minutes, then taken down and republished. I presume the devs made a cosmetic mistake and pushed the new link fixing the 1.0.7 thing. just retry to download and install and i presume everything is going to be just fine.

you are welcome enjoy flying

I do have a goflight tq6 and both levers work just fine but XP10 here. Have you tried to deassign and reassign throttles just in case? it could be useful once someone else having xp11 test your behavior to confirm

it has been said from the very first beginning and during the updates VNAV was not part of 1.1 It will be improved but will take longer due to its complexity.

Congratulations!!!

will try this one...

ok i did the flight #1 EGCC to EHAM, everything went just fine. no issues at T/D. note: something to point out, when selecting SID SONE1R departure there is a waypoint D304H which is being parsed as mandatory altitude 0 constrain. This may interfere VNAV refusing to engage etc. I have seen this before, not sure this is an issue on the navigraph database or the ixeg bird while parsing the procedure. When this happens you enter manually an altitude that makes sense. In this flight i just entered 2500A to match previous waypoint altitude (D296 - 2500A) and not to interfere next waypoint constrain WAL33 - FL050 mandatory. All the rest went smooth. See pictures attached of the entire fmc programming before takeoff (LEGS, PERF, TAKEOFF). A few pictures inflight near T/C, then a few pictures reaching T/D and the aircraft descending via the STAR past T/D with no complain. note: picture 1 has a red circle around the waypoint i had to edit for 2500A because it was set as 0ft MANDATORY.

thanks for sharing the details. i will try one of those myself and see if i can reproduce

did you reset the MCP before reaching T/D? Can you share a video of your issues? or a detailed flight plan including airports, runways, sid, star, route, weight, fuel, ci, cruize, etc to reproduce?

Takeoff thrust. -Map any button of your liking to TOGA, these are the small buttons on the throttle levers that when hit set TOGA thrust (TakeOff or GoAround) depending the phase of flight. This is how pilots do on real life. sim/engines/TOGA_power A/P disconnect. Never use the disengage bar, this will kill FDs among other things. This is a hard shutoff in case of an issue with ap Map any button of your liking to ixeg/733/autopilot/AP_disengage. (first clic it will disconnect a/p and you will hear the classic warning aural sound, the second clic will confirm and clear the alarm) This will emulate the button on the yoke the real aircraft has and pilots use for disconnecting A/P on final approach without removing the flying hand from the yoke. A/T disconnect. While on final and ready to take control of the throttles. Map any button of your liking to ixeg/733/autopilot/at_disengage This emulates the black buttons on the throttle levers sides labeled A/T disconnect -> note: once you disconnect A/T you need to move your hardware levers until they sync the aircraft levers current position, then you regain control automatically. This is to prevent a thrust spike. You will see the throttle ghosts in screen for rapid and easy sync while you move your hardware levers hope this helps

ohh my friend, my eyes hurts reading you re-configure all of your joystick profiles and assignments every time you select a different aircraft for flying. You can create a per aircraft profile, everything gets configured/assigned automatically when you select an aircraft. You may use a plugin like xJoyMap or use a lua script. OptionA. Xjoymap plugin. http://forums.x-plane.org/index.php?/files/file/11720-xjoymap-joystic-to-dataref-mapping/ OptionB. See a lua sctipt example attached i do use. Depending the aircraft you select it will assign everything you like. joystick.lua

I think there is some sort of missinformation you are receiving about the bird status. The aircraft FMC works LNAV and VNAV, you can complete an entire flight based on the FMC VNAV/LNAV capabilities with no issues, have speed and alt restrictions, etc. etc. This how i do operate the aircraft being offline all the time until i am 1000 to 2000ft for the runway and i put A/P, A/T off for landing. When i do fly online on PE network i climb and/or descend via SID/STAR procedure or vía VECTORS/ALTITUDES call outs coming from ATC to comply. So what is all this posts about. -LNAV, you may experience a simulation softcrash on some scenarios mainly if you perform changes to the route plan inflight. Lets say you programmed your route and once airborne you start switching procedures, editing waypoints, deleting things, changing destination airports, etc. Under those complex coding scenarios the simulation code is not solid enough and may crash. A big improvement for managing those scenarios is expected for upcoming release 1.1 -VNAV, some airport procedures (specially STAR procedures) includes very complex set of orders for speeding and altitude constraints mixed together that may be also tight to several waypoints in sequence. Under this complex scenarios VNAV simulation may fail to determine/compute a valid VNAV profile providing unexpected altitudes, etc. (i.e. when the procedures calls for Above and Bellow order for a waypoint), etc. BUT if you as a pilot review the VNAV profile once computed and edit speeding/altitudes on the legs page for those critical cases before departure VNAV will handle the approach with no trouble at all. So this is not about the aircraft not having LNAV/VNAV available, the FMC has both and they work. But if you are inflight and try change/update your flight plan this could lead to issues as of now as the simulation code still requires fine tuning. Under those circumstances i would recommend switching to HDG/FLCH/VS modes to comply do not try to do FMC porgramming micro-managment close to your destination airport. Now... hand flying this bird during takeoff and landing operation is years light ahead of anything. This thing behaves like an aircraft, you can actually feel the weight under different load configurations, how the aircraft responds under different flaps, trim, yoke input is simply amazing. Hydraulics, Electrical systems, sounds, graphical quality, factor of immersion is lights years ahead as well. just my 2 cents.

A good starting point for downloading free scenery available for the airport of you interest is the xplane org community (need to register yourself for downloading, posting, etc.) http://forums.x-plane.org/index.php?/files/ On the top right corner there is a search bar, select files and enter the ICAO XXXX code of the airport of your interest. If available or several options available all them will come to live hope this helps

the lights of the 737-300 are not specially powerful, but maybe you also need to turn up your gamma settings a bit too.

have you verified under xplane graphics settings that "visual effects sliders" is set enought to the right for HDR being enabled? Most lights will not work if the visual effect slider is way to the left to the point you are running HDR off.

IXEG recommends 0% augmentation, 25% control response. Still control response value % is a generic base, this value should be adjusted based on your particular hardware axis travel length. The real aircraft has lots of inches of travel on every axis that cheap desktop hardware lacks, thus you may need going even further than 25% for pitch and roll. Reading the included documentation, quick start guide, first flight should help you to make sure the aircraft is properly setup for takeoff, trim correctly set is specially important in ANY aircraft as actuating it on the air to relief yoke pressure as the aircraft gains speed and different flap & engine thrust configuration during the climb about.

I am not part of ixeg or x-aviation team, just a simple user that likes a lot this project and participate actively on the forums.

support@x-aviation.com response time is 3 business days. every time you send a new email you start over.

1.1 is not available yet but under beta testing. 1.0.7 is the latest version available.

cool glad to have helped.

that error on the gizmo is normal. your problem is related to reshade to me. this plugin has caused many trouble to lot of users including other aircrafts as well. I have attached an example for you below. have you tried running xplane installer again? the installer will automatically update/reinstall any file missing or modified by reshader plugin when it was running. We need to be sure the simulator ok http://forums.x-plane.org/index.php?/forums/topic/117018-answered-displays-and-reshade-plugin/