mmerelles

No, there is no chance you have a broken install if the aircraft is working just fine by itself. "By itself" i mean the aircraft works properly when you use/manipulate all the systems via the virtual cockpit not via external hardware. This is what comes to my mind assuming the ixeg works great on their end as said: -they did a mistake and re-send you the same software not the newest version. -or, for some reason you did not upgrade properly to the newest version and you are still running the old one. -or, did you double check you have selected the right profile under the VA app? I have seen on their forums you need to select the IXEG profile. The VA interface does not auto detect what aircraft you are running.

Virtual Avionics interface is not user customizable, you will be required to get in touch with them to fine tune the datarefs, custom commands they use for the ixeg to get the mcp working at 100%. Also to fine tune the gizmo issue.

attach your log.txt file found on your xplane root folder after the crash. Do not copy/paste, attach the file

Please send an email to 'support@x-aviation.com' for asking them to reset your 737 slots. -You should receive a ticket confirmation number. This confirms you are on the queue. -Response time is 3 business days They will double check (they have all the tools) you are not running out of activations due to redistributing your keys, then reset it for you. note: do not re-send the email during those 3 days or you will be re-queued back automatically.

v4 seems another big step forward, awaiting for the release. please someone test all these new features over a dual computer setup for extended fov if possible

See attached a picture where the power button is. Rotate it to ON position (clockwise) and wait a few seconds for the GPS to initialize.

ahh ok i see...

It does work just fine to me. Rotating the know increases/decreases copilot instruments background lighting. Do you guys have HDR rendering on?

what you are looking for is here

Gizmo is not compatible to Sierra OS yet, but the good news is there is a gizmo beta version already that works. You can try it.

i don't think this is related to 10.50. But OS sierra isn't compatible yet. Did you update your mac to sierra? There is a gizmo beta version available already for testing

When you have no speed / altitudes on the fmc legs page, this typically means you have not programmed the PERFormance data onto the FMC, you need to set aircraft weight, cruise altitude, cost index, etc. If you do not enter all that information vnav has no way to calculate/populate speed/altitudes for the flight plan. note: check all fmc legs pages you have no route discontinuities and be sure you activated and executed the route when you modify something on your flight plan, the fmc has to recalculate it real time until you EXECute the changes on the fmc. During this period fps typically drops to 1-2 if you have windows defender enabled and you did not set an exception for the entire x-plane folder. Windows defender consumes the machine resources and xplane dies. If you still have issues please attach your xplane log.txt file found on your xplane root folder to see if anything comes up. Also some screen captures of your aircraft and fmc configuration will help to understand what is going on.

A gizmo beta version was released for users to test, most users seems to be working ok now on sierra while a few still have issues. If you want to test:

This aircraft runs based on GIZMO, and gizmo is not compatible with SIERRA OS. It has been told and users encouraged not upgrading to SIERRA since betas Every time a new OS comes alive, things get broken, being an early adopter has its risks. The developers are already working on a new GIZMO version that works to OS SIERRA, it is under beta testing. You have to wait for the update. Aircraft/addon that relies on gizmo will not work. Or you can roll back to el capitan if you have a backup

The 737-300 (classic) from IXEG has no VNAV speed intervention. This comes with modern avionics (i.e the 737 Next Generation). You can switch to VS or FLCH mode for dialing desired speed while climbing/descending. You can also edit speeds on the FMC which is not exactly VNAV speed intervention.

there is no dataref. is a custom command ixeg/733/misc/egpws_test_act

@gpb500 i have seen other people simulator going to single digit performance when the following conditions occur: -you make a change on the fmc flight plan, as you did -you did not pressed EXEC still -windows defender is enabled. it seems when you make a change on the fmc it starts recalculating until you press exec and if windows defender is enabled you cpu will die. is it possible you are running windows and defender is enabled?

in the case of x-aviation, seems that sierra broke gizmo, thus all products that relies on it. they are working hard to get this fixed asap.

It is my understanding OS SIERRA is not supported yet, there are plenty of posts about the IXEG733, SKYMAXPRO, etc. Just do a 'os sierra' search on the bar top right. To reset your activation slots you should contact support here 'support@x-aviation.com', you should receive a ticket back and await for a response. They will not address licence issues over the public forums.

nobody on the community here can help on that. the procedure for support requires you contact support via mail (you should have received a support ticket # back), responses may take up to 3 business days. If you have sent your mail 4 days ago (friday) it has been passed only 2 days (there was a weekend in the middle). note: do not resend the email or it will make your request to start over.

i think there is no solution for the intel hd 4000 series the graphic card you have is not capable of rendering what is required. what hardware exactly do you have? check this post:

please attach your "log.txt" file found on your xplane root folder. I have seen this behaviour your describee from people that use low end underpowered Intel hd integrated 4000 graphics cards that are not supported. But not to speculate, please attach your log file, maybe something else is going on here. edit: you can check an example here, do you see the same?

Maybe a plugin conflict? do you use saitek? do you have installed any of those plugins that save aircraft status? I haven't seen this issue myself. Can you attach your log.txt file (do not copy/paste) found on your xplane root folder after you load the aircraft, see the problem and close xplane?

sounds like plugin conflict. Do you use saitek panels? Can you attach your xplane "log.txt" file (do not copy/paste, attach!) found on your xplane root folder? load xplane, load the ixeg with the problem, close xplane, attach the log

This is a limitarion on the current fmc development status. This is not related to 10.50 or mac/windows you can not select a runway only or gizmo will soft crash, you need to select an approach procedure. for queenstown you may select rnav to 05 for example. I go there quite often likes there. You can edit what required once selected. i do not know if this is already improved for next update or a later one. hope this helps.