mmerelles

I do own the products from Goflight https://goflightinc.com/store/gf-mcp-pro-airliner-autopilot-module/. I did consider moving to VA hardware being modern and some nice cool features like backlighting, but since they do not work to all aircraft of my liking (in fact for xplane they only work to the IXEG so far and not 100%) it was a no go for me. Every aircraft uses different datarefs and custom commands to mimic the real aircraft avionics and features, when you have an external hardware to interact with, you need a software that assign/customize those commands on a per aircraft basis profile to assign switches, buttons, display, rotaries to the aircraft counterparts. So when you flip, move, push your hardware they translate into proper orders to the sim aircraft. VA interface software is not open to the user, you need from VA they create those profiles on a per aircraft basis to support every aircraft of your liking. So you are stuck to what aircraft they consider to support as well as their time frames to release those profiles. Goflight provides a SDK interface for their hardware and a third party developer Pollypot developed an application were the user create their aircraft profiles on a graphical interface by itself. You can assign the hardware buttons, display, rotaries, switches, etc that loads automatically based on the aircraft you chosen on xplane. This is important to me because i want to use my hardware to any jet i have, currently i do own FJS727/737, FF757/767/777, IXEG 733. While the hardware MCP layout is based on a 737, every jet has IAS, ALTITUDE, F/Ds, VS, ALTITUDE, VORs, FLCH, HDG, APP mode, etc, and assigning those features and manipulating them from there is much more immersive than rotating the camera and using the mouse to me. If you are not much concerned on using your hardware other than the IXEG bird you are just fine, because this is a high demand bird, VA released support for it already and working on fine tuning the profile to make all features to work. If you are concerned on the FF777 that could be a problem because there is no profile from VA available yet for their interface software that assign the hardware buttons/switches/etc to their aircraft counterparts. Ask VA if any plans/timeframe for releasing a profile for this bird. Hope this clarifies a bit

They work just fine to me. Please confirm you have enabled this custom features on the 737 preferences menu!

The FF777 will not work with your VA MCP + EFIS at all. Ask VA if they have any plans to support this aircraft in the future. VA hardware does not include an open interface that allows you to use your hardware to any aircraft of your liking. They have to develop and release profiles support on a per aircraft basis for you to use it. This is a very bad approach to me. You can not use any aircraft of your liking, every time a developer updates their bird you also risk to have your hardware grounded until a VA update for that aircraft comes alive. Hope they change this approach. I do agree their hardware looks impressive and quite cool, but ii would put usability top on the list for the decision. edit: Just another perspective, not trying to start any war here

Attach you xplane log.txt file please found on your xplane root folder

I do not use co routes myself, BUT have you seen the requirements and usage details on the included documentation? Check on the aircraft documentation folder, the file '2-interface guide.pdf' page 11. It says there where to put them and lot of information! hope this helps.

I presume oil temp is so low because if you look at your TAT and OAT you are at high altitude and dozens degree below zero. Reality is no matter you set the engines to idle at that altitude the oil temp should not drop that fast that far. I think oil temp is not ixeg custom yet, but data is coming from xplane. if i am not wrong, refinements are coming for this on next update.

uhhh this is weird! maybe you got a virus or something that corrupted xplane.exe? when xplabe crashes on startup due to a plugin or anything, you typically see the xplane logo window at least then it crashes. Don't you see anything at all when you launch xplane? Maybe you should try to run xplane installer, select search for updates and if anything is missing the installer will fix it. You may also check you antivirus or whatever is not preventing xplane from executing.

the 'log.txt' file is under xplane root folder.

This is my understanding. Fuel to the APU comes always from the left manifold side, which doesn't mean the fuel is coming from left side tank1. It depends on electrical fuel pump position. When the center electrical pumps are ON, they provide higher pressure flow than wing pumps. This why the engines burns fuel from center tanks first when all 6 pumps are ON and fuel is available on the center tanks. Center pumps win and feed the manifold. This applies for the APU as well, having center tank pump ON they will feed left side manifold, thus engine and apu will get fuel from center tank not from the wing tank. note: if no electrical fuel pump is ON, then yes, the APU will always suction fuel from tank1 via its APU bypass valve. Summary for the classic (left side): No pumps turned on at all. Engine and APU will suction fuel from the left tank via their corresponding BYPASS valves Left pumps on. Engine and APU will receive fuel from left manifold being feed by the electrical pumps. Left and Center pumps on. Stronger center pump will feed left manifold. APU & Engine will get fuel from center tank. I am also curious to get this clarified

It seems you upgraded to SIERRA? Sierra is not compatible with Gizmo plugin which is required for the aircraft to work. You have 2 options -Rollback to el capitan -Install Gizmo beta plugin under development to make it compatible to sierra

says private

this is exactly why i (as others) suggest putting a folder exception to defender, we have seen this already plenty of times and those smart ways to disable defender fail sooner or later one way or the other. glad you are back ok

Windows defender can not be disabled to my understanding and if you kill the process it will come back again when restart. Your best action would be: go to the windows defender page, see there for exclusions and add an exclusion for the entire /xplane 10/ folder (you can add exclusions per folders or per file basis, use the 'per folder' menu and add xplane root folder). Thats it.

just curious, have you been able to get your VA MCP fully working?

simply beautiful. congrats!

Your log looks clean to me. Seems to be a known bug. I just found this 2 post below for you. Anyway lets see what the developers say when they see your post.

i have never seen this can you attach your xplane log.txt file found on your xplane root folder please just in case, you can not use default xplane a/p on this bird. You have to use pedestal or custom commands to engage

you are welcome.

are you windows? be sure you have set an entire folder exception for the entire /xplane 10/ folder under the windows defender otherwise the cpu may die while you do changes on the fmc inflight. if you have also an antivirus be sure it is not scanning xplane. hope this helps.

Yes, this is the problem with joystick sending noise and the aircraft think the pilot wants to override a/p. Note on the PFD screen it entered CWS mode illuminated yellow

There is a CWS nullzone slider on the ixeg preferences left screen menu, move it full to the right just to be sure. This will prevent the a/p from disengaging as well as several modes refusing to engage if you joystick potentiometers are sending noise. The aircraft systems "think" the pilot is moving the controls manually on purpose to override the systems. If you still have issues i would recommend you attach some screen captures or a video for us to see what is going on.

You should receive an email to your registered email address.

Skymaxpro as well as most x-aviation products relies on GIZMO plugin to work, they provide the plugin embedded on their products. Problem is, the newer operating system from apple 'SIERRA' breaks GIZMO, so most products from x-aviation stopped working for people that upgraded their mac as yourself. Major os releases always break things, that is why people is always encouraged not upgrading to newer OS right away until fully tested first. In order to get people working again, the developers have released a gizmo beta version that fixes sierra issues for testing and feedback. The beta version has a time expire because it will be replaced for a definitive gizmo plugin when ready. This is just to prevent people from going forever under a beta version. You as a legitimate customer have 3 options: -Stop using skymaxpro until gizmo sierra compatible version is ready. or -Install the gizmo beta version for sierra to get your product back working and install the definitive gizmo plugin version when ready. or -roll back to el capitan os if you did a backup to get gizmo working again. hope this clarifies

Any update you purchase, just one cycle, a 3 month deal, or the whole year package is already valid for the entire sim/hangar not just one aircraft. When you run the navigraph app it will detect you have xplane, x-fmc, ixeg, flight factor if any, etc. If you just select to update the ixeg and later on you want to use any bird that uses default xplane gps it won't have latest navdata. Is there any reason why not upgrade everything? your purchase covers the entire sim/hangar already.

I had this exact same issue you describe above and was a plugin conflict. In my case the force feedback yoke plugin, problem was solved updating the plugin. Based on my personal experience. -You should move all plugins out the /xplane 10/resources/plugins/ folder for testing (except gizmo which is required by ixeg) -Move them back one by one to see which one causes the trouble note: xplane must be restarted when you remove the plugins and/or adding them back. Disabling/Enabling them vía plugin admin on xplane menu does not work the same. Please attach your xplane 'log.txt' file found on your xplane 10 root folder. I can have a look at it for you.