XPlanePort

"isn't Mac OS Sierra still in beta?" It is, and this is why I'm not complainig : "IXEG Team, this is for your information only (I purposely use Betas to discover problems)" and this "If you have any suggestions (other than do not install Betas ) please let me know."

IXEG Team, this is for your information only (I purposely use Betas to discover problems): After upgrading to the latest public Beta macOS Sierra (refer to the attached screenshot for OS details): , looks like Gizno is not working. Please see attached X-Plane screenshot: Menu is not showing on the right. I tried removing all X-Aviation files (folders) from X-Plane folder, Gizmo from plugins folder. Reinstalled IXEG 737 and reapplied the latest HotFix 1.0.7. I did not get activation window for IXEG after selecting the plane in X-Plane. The problem did not go away. If you have any suggestions (other than do not install Betas ) please let me know. Thank you!

Submitted the bug to Laminar http://dev.x-plane.com/support/bugreport.html Will see... "Your bug has been filed successfully."

Thank you. Will do.

KTUL ILS or LOC RWY 36R APP CRS 360 I was expecting course selector to go from 359 to 000 On the left COURSE selector, I was able to dial 360 (359 to 360) On the right COURSE selector, it goes from 359 to 000 At least, I am expecting consistency from the both. What should it be?

I would say this is known. The team is working on improving the VNAV. On some routes it works (depends on altitude constraints), on other not so well. As the team works to improve the VNAV, what you can do to help, is to post your IXEG debug file for the route you have problems with the VNAV (or even LVAN): After setting up the FMS, press the period key four times “….” on the CDU. This should generate the IXEG debug file in your X-Plane main folder. Upload the file here, so the IXEG team has the information to use during the VNAV tuning. "Does the FMS/autopilot have a managed mode descent function or does the descent have to be pilot monitored?" It does and it will work properly in the future. But for now, switch to manual autopilot management as soon as you see something is not right

I have not seen anything like this since I started flight simming in 1995. Nothing comes close (I know what I am taking about )! The combination X-Plane with IXEG 737-300… Makes me smile every time I use the combo. And THE SUPPORT! Thank you so much!!!

Do you have NVIDIA card? If so, try installing NVIDIA Web driver from here: http://www.insanelymac.com/forum/topic/306535-nvidia-web-driver-updates-for-el-capitan-update-05252016/ Choose the one for your OS version. P.S. just noticed that you are running Yosemite. the drivers from the above link are for the 10.11.* El Capitan. You may want to consider upgrading your OS and then use the NVIDIA Web drivers.

On my Mac laptop with Intel High Definition Audio (just like one above in the screenshot), when I first load the 737 and start to prepare for my flight, I can hear all the switch sounds (window heat, pitot static heat, autobrake, external lights (the landing lights are ok all the time!), marker, WX radar, maybe some more). After takeoff, more sounds are being introduced into the mix (wind, engines, trim…). At first, I was thinking that I just can’t hear switch sounds with all the additional noise, but I can clearly hear all the sounds on my home desktop. Alter landing, I can hear all the switch sounds again. So, I am trying to find out if there is Intel High Definition Audio driver (not from apple updates), that can be installed (I found some drivers, but they are for older Mac books). I am hoping, if there are stand-alone drivers and the Intel High Definition Audio on Macs can handle all the IXEG sounds at once, the problem can be fixed. Or, if there are no stand-alone drivers (that potentially can fix this), and the Intel High Definition Audio can handle all the IXEG sounds at once, but there are something on Mac that uses some of the sound card resources, does anyone know what background processes (I have all the apps off when using X-Plane) can be using the audio resources, so I can try to shut them down and try? P.S. Not related to the sound problems: I was able to fix my hard crashes by installing NVidia Web Drivers. The sim was crashing almost every flight for me with all the latest apple updates. Installed NVidia Web Drivers and have been crash free for over a week now (flying multiple times per day).

Thank you Jan, Works fine now. About to take off I will definitely report. Just want the report to be reliable and reproducible to help you fix whatever is causing this.

Going through the above steps, I can no longer reproduce what I was observing just minutes ago. There may have been specific sound settings combination that was triggering the behavior. If I will be able reliably reproduce, I will report back. Sorry.

I just also tried to flip A/T switch, after “Marker” switch reduces the “Cockpit Sound Volume”. Flipping the A/T switch resets the “Cockpit Sound Volume”.

Airplane is in Turn-around mode. This may be reproducible using different configurations. This is what I did: Open Preferences window from the left menu. Check “Master Sound Volume” at full right. If not, set it all the way to the right. Check “Cockpit Sound Volume” at full right. If not, set it all the way to the right. Keep the “Preferences windows” and monitor the above sliders. Flip left “Windows Heat” switch (as an example. I don’t think this specific switch is related to the problem. I use it just to test.) to hear the switch sound. Flipping “Marker” switch reduces “Cockpit Sound Volume”. If the above can’t be reproduced, try to adjust the “Cockpit Sound Volume”, flip a “Windows Heat” switch and then “Marker” switch. You should eventually see the “Cockpit Sound Volume” move and hear the sound decrease. Sometimes (don’t know exact sequence of the steps) the “Cockpit Sound Volume” would go all the way to the left, mute). If you need me to do more tests, please let me know. I know you have fixed sounds for the upcoming full patch. Reporting just in case you missed this one.

Check this:

Benjamin, Thank you so much for pointing me into the right direction! I am fairly new to MACs… At some point, I was briefly looking for latest Nvidia drives for MAC on the Nvidia website, but did not find what I was looking for. After you mentioned "WEB" drivers, I did Google search this morning and was able to locate the latest drivers: Nvidia Web Driver - 346.03.15b01 --> build 15G7a: ://www.insanelymac.com/forum/topic/306535-nvidia-web-driver-updates-for-el-capitan-update-05252016/ I am now on the latest driver and will be flying (testing) with it. Before (GPU Driver Version: 10.10.13 (310.42.25f01): After (GPU Driver Version: 10.11.12 (346.03.15b01): THANK YOU!

By the way, are you the same Dave23456 from x-plane.org who commented on my KGAI scenery regarding trees? If yes, I replied

Thank you. I see the crash in the log. Developers should be able to help. What IXEG 737 are you running? Is it 1.0.5?

For now, just attach the whole GizmoLog.txt file. Don't copy and paste the file content.

Hi Dave, What you are describing (window with the red line) is Gizmo Soft Crash. If it happens, look (in your X-Plane main folder) for GizmoLog.txt file and upload it here. Developers should be able to see what possibly went wrong and fix it. Also, if you get the Soft Gizmo Crash, you need to reboot your Gizmo plugin. The reboot button is on top of the Gizmo Crash window (Or if you close the window, you can locate Reboot button on the right menu (move your cursor all the way to the right and the toolbar should appear)). After rebooting the Gizmo, you will be able to use FMC. Unfortunately, everything will be reset, and you will need to reenter all the information. But, the good news is that developers fixed most of the Soft Gizmo Crashes, so they are very rare now. If you get one, please report and upload you Gizmo log.

I have the plane installed on my Windows PC at home and I don’t have any problems with hard crashes. I also have the plane installed on my MAC laptop (running latest beta OS). I use this laptop to document and report all the bugs. Since I am running Beta OS, I did not want to report hard crashes, assuming this to be related to some problems with the bate OS (can as well be the Beta OS related). But, since other having hard crashes, I will report. This is the latest crash while in cruse. This specific flight, I was at CRZ altitude and interacting with CDU (specifically changing the arrival, but then erasing the changes without Executing). The crash did not happen during the time I was navigating the CDU, but maybe 15 seconds after I interacted with it (may not even be related to me interacting with the CDU. On the previous hard crashes, I don’t remember using CDU before the crash. I don’t have logs from the previous crashes, so I don’t know if they are the same.) Attached is my X-Plane (--=={This application has crashed because of the plugin: Gizmo64}==--) and Gizmo logs. I hope this will help you solve this (if the crash is related to the Plane / Gizmo plugin). Log.txt GizmoLog.txt

Thank you!

You can attach your Gizmo log file for developers to take a look and see what is causing the Gizmo crash. Or, at this point just wait for 1.0.5 (Should be released tonight/tomorrow) and try selecting the transition...

Hi, There are some problems with VNAV (including this one). They are currently fixing crashes and will work to tune VNAV after addressing most of the crashes (soft / hard).

The MCI is to close, so I think this is why. Selecting direct to BLUZY redraws it correctly with left turn. How should your code handle the MCI in this case?

KMCI to KDCA LAKES8 SPI J80 VHP ROD APE J30 BUCKO FRDMM3 Dep. Runway: 19R Please let me know if this is a problem and you need any logs. Thank you.