mmerelles

you are welcome happy flying

double check were the navigraph manager is installing the update it should go to .../IXEG 737 Classic/fmc_data/ (that is were the aircraft loads from) maybe it is installing to another folder, the aircraft should be within Xplane11/Aircraft/x-aviation/737 Classic (not on the root folder (maybe you are confusing the uninstaller there?)

This aircraft uses its own nav database located under the 737 Classic root folder. When you say you did update via navigraph manager, did you have the IXEG 737 Classic listed on the console or just xplane? if you are not having the IXEG listed, go to 'addon mappings' then 'add' to include IXEG addon for navdata update. note: you are already running xplane, you need to restart or restar gizmo via the console

very cool idea Tom, there may be lot of limitations now but surely you will sort them out step by step

you are welcome yeah, i also tried the shortened version but didn't work reliable to me. Sometimes it works sometimes it still shakes. So i opted for loading the ixeg first on the slave, then load the saab and wait for it to switch back to the ixeg which works very reliable. If the shortened version works reliable for you is great, you are saving some time.

I have the same setup and problem than you (2 networked pcs running a copy of xplane each master/salve, multiple aircraft including the ixeg) master pc is ok, slave pc screen shakes goes crazy when at a speed. while the aircraft is stopped there is no sync problem. this problem started by xplane 10.46 (i do not remember the exact version) when laminar did a rendering engine improvement i have found an easy workaround to fix the problem. 1. You load the master and the slave sim with the ixeg 2. Wait for both sims be ready 3. On the slave mache select a different aircraft, it will load and revert back automatically yo the ixeg because the master machine will tell to load the ixeg again problem fixed. i do not know the technical details what the problem is, why loading a second aircraft and switching back on the slave solves the issue. What is reset that fixes the sync problem note: not any aircraft fixes the problem, you will have to try. On my case i do use the Saab340 for the trick. It solves the problem. Crazy as is but it works If someone else has a better understanding or solution of the problem i am also interested to hear.

folder name is: coroutes create it under the 737 root folder .../../ixeg 737 classic/coroutes/

The included manual with the aircraft has the answer, document file '2-interface guide.pdf' over the COROUTES section. -the flight plan should reside on a folder named 'coroutes' under the 737 root folder -ixeg supports .fpl format (filename no more than 10 characters length) -to load go to the FMC press RTE page 1, type on the scratchpad the filename (with no extension .fpl) and press CO ROUTE softkey note: make sure the airac cycle used to create the route and the airac cycle loaded on the fmc matches, otherwise you risk the fmc will not recognize waypoints, airways, whatever

If you are still going CWS mode time to time, please move the CWS nullzone slider all the way to the right (that is what i did on my saitek times and problem completely solved). I am unsure if monitoring the red bar is an accurate measure, i doubt potentiometer spikes will be reflected there for being so minimal in time. For the VNAV thing, there may be issues certainly. If you share all the details, origin/destination airport, route, sid, star, transitions, all perf init data, etc. to replicate your exact flight i can try it

The aircraft option for starting cold & dark, turnaround or ready to fly are on the IXEG menu that popup from the left of the screen. Select the option you like and clic apply.

that is the fuel estimation when the aircraft crosses MERLU, but take into account PROGress page is under development and the information shown is not correct yet

i thought the double door thing was IXEG testing hi-hacking countermeasures technologies for boeing pilots can go out without passenger notice the cabin was open.

That yellow CWS P mode on the annunciator means what i was speaking to @WR269, the aircraft entered Control Whel Steering Pitch mode becuase the pilot is manipulating pitch and overriding the systems. Off course you are probably not manipulating anything, this is your yoke/joystick potentiometer sending noise and the aircraft "thinks" you are trying to regain control. EDIT: @Morten was faster

This behavior is a pretty solid evidence that you use a yoke/joystick which is sending noise spikes from the pitch potentiometer (thus affecting all vertical modes), when you try to engage any vertical mode plane refuses because it is receiving pitch input from the controller and the aircraft "thinks" you are manipulating the yoke to override and regain control. This can be confirmed having a screen capture of the displays and annunciators, but being blind it is just an assumption. I am 99% sure this is the problem but please share a screen capture if this happens again and i can help you quite easy on this. Please don't get me wrong, I am not saying VNAV has no issues. It actually has and the devs have confirmed they will rework vnav, but sometimes having screen captures helps to understand other problems that we assume are all vnav or if it is vnan we can document them properly so when vnav testing comes we make sure they work.

if this happens to you again is quite important: a. You do some screen captures while the problem is going on to see what all the displays and annunciators says b. Also please share your flight details. origin/destination airport, sid, star, init perf page, etc. everything to reproduce the problem i do understand the frustration, in the other hand it is simply not possible to test unlimited scenarios under development & beta. User input is also necessary for the devs. The same that happens on the real thing with fmc issues reported by pilots and fixed by manufacturers over firmware updates.

you are welcome

Ninja fixes are for the ground issues. If you plan to use the aircraft on xp11 you still need to enable the apu and tune engine ratio parameters. See this guide including screen captures

Tom yes, if you plan to use it on xp11 you need to enable the apu and adjust engine ratio parameters via planemaker. Should be easy an smooth, if you have any doubt there is a nice guide here including screen captures

They should as long as they use xplane default multiplayer datarefs as other plugins does as pilotedge, ivao, vatsim, etc i would suggest you confirm with the plugin creator or support

This is a known behavior. In order to implement the ninja fixes for xp11 to stop the aircraft from sliding over the ramp and parking brake issue, the devs had to make a tradeoff and sacrifice pushback turns for now.

because they replaced the installer and other people had the same issue 1.0.7 and solved it by redownloading the installer and making the install again.

this is wrong have you re-downloaded the installer? i think this is quite important for the end result before reinstalling.

The crash seems related to scenery issues as per the log. I do not see any warning the crash may be related to the ixeg 737 Ideas for you to test: 1. remove plugin HSAIRXPL 'C:\X-Plane 11/Resources/plugins/HSAIRXPL-Win-64.xpl' just to make sure you have no other plugins as you said for testing 2. Try loading the aircraft over an airport/region of the world having stock scenery. You are trying to load the aircraft on KLAX and having custom scenery errors on the log. i.e. use SAEZ airport, Ezeiza south america hope this helps.

I can easily understand why you have a negative reputation on your profile. Seems you can not process and/or understand simple facts -XP11 was released less than 2 months ago. How in the earth the developers have taken a year for not making it compatible to XP11 considering XP11 did not even exist? absurd! Also note during the betas Laminar encouraged the developers (this is public on their xp devs site) not trying to do anything for XP11 yet until they stopped tweaking the new sim model. -IXEG / XA made pretty clear from the very first beginning XP11 will require: first, going final and being public, second they will have to wait a few iterations to Laminar fix main issues always arise with major releases and further tweaks not to waste developing time on a moving target. You may like this approach or not, there is nothing wrong out of this, but this has nothing to do with cheating the customers. If you know what cheating means, i strongly doubt it too.

it is my understanding the gen relays are battery feed, loosing the battery will lead to a complete electricity loss as it has happened on real life.