mmerelles

Please attach a screen capture of your problem. Just saying doesn't work doesn't tell much.

I would suggest you put the CWS nullzone slider to the right, it won't hurt at all and if you controller is sending noise/spikes it will prevent from interfering a/p operation

can you share a few screenshots of the forward cockpit to see what the systems and mcp status are? or maybe a video of the behaviour? thanks

PROGress page is WIP not ready yet.

About your first issue. This is the A/T system protecting the aircraft during a dirt configuration (takeoff and approach) -If you want to increase the speed, you need to retract the flaps as per the flap schedule, otherwise A/T will not allow speeding the aircraft beyond current flap setting capability not to rip the surfaces. -If you want to decrease speed, you need to extend the flaps as per the schedule, otherwise A/T will not allow the aircraft to reduce speed below the minimal current flap maneuverability speed no to stall and crash. note: make sure you do not use any hardware lever as an axis, unless you use a detent plugin or similar. Otherwise your potentiometers nois/spike will keep moving the flap position no matter you are not touching at them About your second issue. Calculated VREF speed for landing is based on aircraft GW (Gross Weight) for the given flap options. If you are getting such a crazy low speed values, this would indicate you did not load anything on the aircraft during pre-flight. Before departure: 1. Go to GROUD SERVICES menu 2. Select REFUEL TO xx tons of fuel as required for your trip 3. Adjust ZFW to around 50 tons or similar (this is pax + cargo) 4. press Instant to load everything. This will result on an average packed aircraft and you will see what IXEG flight model is all about, you will actually feel the weight during TO pull and landing. note: for the purpose of landing on calm days, you have to configure VREF +5 knots on the MCP SPEED DIAL during approach to cross the runway threshold at that speed and you bleed off those 5 knots during flare while you retard the throttles to a VREF touchdown. Landing on windy conditions require more complex calculations to the VREF +XX, you can experiment later on this once you materized the above. hope this heps

mmm weird. works just fine to me. what you mean it doesn't work anymore? the tug doesn't come and attach? it does not push back the aircraft? Are you sure you are running latest betterpushback version 0.46? Did you update to latest xplane beta? maybe an issue there? Did you try removing other plugins, maybe a conflict?

Open your Navigraph manager, go to the addons mapping section, and include ixeg

It really sounds like you are still running windows defender or something. be adviced when you reload the computer or update it reactivates if you turned it off. Microsoft is very strict on this. Are you windows? Can you try setting a folder exemption for entire /xplane 11/ folder? When the problem occurs, if you open task manager, is the CPU overloaded? and what process?

You have to go x-aviation web portal, login and download the instaler from your listed purchases run the installer and that is it

what is your route? departure and arrival airports, sid & star, route and perforamance data. Weight, Cruize, etc. I can give it a look for you. This is VNAV no working properly, but i am curious what is going wrong on that specific route.

you press PROG on the FMC, it will report there NM left to the arrival airport near the bottom. note: this page is still in progress, when completed you can see here fuel consumption and ETA time (zulu time) predictions to intermediate & destination, among other info pressing page next. Most information as of now is placebo data. WIP.

by 3.3 FL 370 / 3.3 = 112NM away for your ball park descend point.

Most common issue arises when the STAR arrival procedure contains orders like cross this waypoint above xxx & below zzzz. The FMC will always read them as cross them above zzzz resulting on a very late T/D. While VNAV is rebuild just to some briefing of the ruoute and altitude constrains, if wrong, simply type correct constrain on the scratchpad then override by pressing corresponding right soft key on the LEGS page. note: this also apply for SIDs. Always scan for those such kind of altitude constrains and make the corrections on the legs page. You will be fine. hope this helps

yes perfectly correct. engines need to go to idle thrust first (by pulling the thrust lever all the way back), then you are able to initiate the reverse engagement. This is how the real aircraft works. note: there is a pin safety mechanism that does not allow reversers to engage if throttles are not all the way back to idle

Toggle reverse is for most simmers having a throttle lever but no reverse lever. So you "toggle" from forward thrust to reverse mode, then you move your hardware lever fordward to apply reverse thrust. Hold max will do everything as long as you push and keep pressing the button enough time for reverses to engage, and thrust to be applied automatically. When you release the button thrust go away and the engines go back to forward thrust. note: reverse thrust will not engage in any Boeing aircraft if forward thrust is still applied. Double check there is no a calibration issue, you can monitor if engines are properly at IDLE thrust on the displays for the purpose of testing and test reverse at the ground. No need to go landing for testing this.

what do you use to engage/apply thrust reverse? -if you use toggle thrust reverse command it will just engage, you neet to apply throlttles which will apply reverse. -otherwise you need to to hold thrust reverse at max. This will engage and apply reverse thrust while you keep pressing the button

You may send them a message on their page if using facebook. They have been very responsive to me on the past while fixing a texture performance issue. The scenery is great and works great! https://www.facebook.com/avioteksoftware/

If you are windows, go to the windows defender configuration and set a folder exemption for the entire /x-plane/ main folder. Note it is a folder exemption not a file exemption. This will cure your problem entirely. Problem is when you are inflight and try to make any FMC change to the route plan, the fmc starts recalculating until you press EXEC but windows defender (or similar) will analyze the scripts and cpu goes 100% hope this helps

I am assuming you are xplane 11. anyway xplane 10 is more or less the same. 1. Go to xplane settings icon, on the top right corner 2. Select the joystick or keyboard tab menu (depending you want to map a joystick button or a keyboard key) 3. Select your desired button or key and on the right side go to the ixeg/.../... tree to map the desired command (you can use scroll and +, - keys to navigate, collapse, extend the trees).

It would be nice if you can attach some screen captures that covers all displays and the pedestal so we can see what the aircraft and systems status when the problem occurs to better understand what is going wrong.

@BlueNose I do understand now... this is weird i do not remember this issue reported before. Hopefully someone else experienced this and have any clue.

@BlueNose Maybe we are having a miss-understanding about you issue then. The windows defender issue (i say windows defender at first, because this is what 100% of the windows pcs have installed by default, despite some users using something else). The sympthom: when you make any sort of modification to the FMC inflight, the simulation gets almost completely freezed. Why only inflight? because while you are programming the fmc in the ground, the aircraft is not moving so the fmc doesn't need to recalculate values until you commit (EXEC) When you are inflight and make any change, the fmc starts recalculating the values, windows defender kicks in over the scripts and CPU goes 100% I did understand as per your post above, your issue was related to introducing changes to the fmc inflight. If that is not the case, could you please share a youtube video of your problem for trying to understand what is going on? is this repeatable? same area? any pattern? note: plugin conflict is another potential thread, i would recommed you remove any third party plugins to confirm problem is over, then reinstall them one by one hope this helps

This is windows defender running against the simulation scripts and putting the cpu to 100% usage. Go to windows defender, set a folder exemption for the entire /x-plane 11/ folder. PROBLEM SOLVED. note. please note this is a folder exemption for the entire xplane root folder, not a file exemption for the xplane executable.

what airport, runway? also make sure you did set the CRS curse selector to the ILS course

Sounds very cool! We have had a Pilotedge event just past saturday as well Departing airports: Phoenix, Seatle and San Francisco Arriving airport: Salt Lake City within arrival time frame 2100 to 2130 ZULU. Around 100 jets arriving KSLC within 30 minutes window timeframe from different sources plus some GAs trying to land as well. Was a great event, pretty crowd airspace, but traffic load was handled so good by PE controllers. I just arrived straight in as planned to ILS34L having a southwest 737 parallel to me set for 34R during final approach and traffic everywhere on the ND/TCAS. Lot of ground operations upon arrival Once at the destination gate, i just sat there for a few minutes and tuned back tower freq. for listening workload pointing the camera to approach runways. Seeing those parallel bright light spots queued for landing felt so great