SeaHawk14

Hi, glad it’s been mentioned because actually I’ve noticed too that since installing the Mango sound pack the lights check activates the bell. It’s an error on their part, not from the IXEG team, I recall prior to the Mango sound pack it was working fine. It’s a small bug for an excellent sound pack so I just deal with it.

Thank you, yes it wasn't a change of cruise altitude, but as indicated it seems to struggle with extracting restrictions/constraints. So just to make sure I understand, 1.5 has been released and is the X-Plane 12 version yes? Can we expect most of this to be addressed on 1.6, as I haven't seen anything about further updates ? I very much enjoy this aircraft and this is generally the only known issue with it.

Good Afternoon, On a flight from Marseille to Provence St Jacques I had an issue with the VNAV path. Everything up to TOC was fine, however when I was stepping through route I noticed that the TOD wasn't programmed until far too late, with an entirely unrealistic descent rate of something like 25000ft in the space of a few miles. Consulting Navigraph it gave the waypoint of ENOKI at FL070 which I entered into FMC which caused the following crash in the gizmo plugin: IXEG Error.txt I'd pressed Clear and Reboot (then realising I'd have to re-configure the aircraft all over). The second time I experienced the exact same issue and the exact same crash. In the end with VNAV I just descended manually at an appropriate time. I think it's a very repeatable error, should you wish to try and replicate. LFRN Runway 28 ILS transition ENOKI (PDF's with waypoints there should you wish to duplicate). I know VNAV is a WIP however I've experienced this issue a few times now, where the FMC would keep me far too high, and when I've tried overriding it, GIZMO crash. Additional Query: I set the landing elevation on the Overhead as 130 feet, because the weather was OVC0300 I kept in Dual Channel autopilot for the full ISL autoland. The aircraft flared but it flared too early, about 10 feet above the runway, and then lost energy and touched down quite hard. I've used autoland very rarely, I've never had issues in the past however I'm wondering is it my fault for entering 130ft on the overhead (where as on Navigraph RW28 is at 121ft) or is this neglagible and the Autoland didn't function as well as it should have. LFMLLFRN_PDF_17301092102.pdf LFMLLFRN_PDF_1730109210.pdf

Please see for Graphics Settings

Good afternoon all, Last month I experienced my very first CTD because of an Out of Memory issue. It's really bizarre because I did not change the graphics settings nor had I installed anything as I recall. I treated it as a one-off occurance, today I had the exact same issue - this time after setting up the aircraft and taxiing to the runway, On rotation from EDDK in the IniBuilds A300 I received the following: BE ADVISED: X-Plane is totally out of memory. Next time, turn down your rendering settings or remove add-ons to avoid this problem. If you cannot restart X-Plane you may have to delete your preferences, found in the Output folder. (UTL_memory.cpp:1119) Please find attached: Log.txt I'm not particularly willing to lower settings because it's totally out of character and something is causing the crash as opposed to just running out of memory, I cannot figure out anything obvious. It's as you can imagine incredibly frustrating This error appears multiple times prior to the crash, however I'm unsure if its it's related - nor how to rectify if so 0:46:59.418 E/FMOD: C:/jenkins/design-triggered/source_code/app/X-Plane-f/../../engine/sound/soun_fmod_container.cpp(274): FMOD error 74 - The requested event, bus or vca could not be found. Your help is appreciated!

That’s a good point. I’ve seen some other developers make statements about their products being made compatible with XP12. Can we expect perhaps a future update comment with a bit of a road-map? As I understand the latest was a comment from tkyler about his ongoing work on the MU2, so once his work resumes on the IXEG It would be really appreciated if we could have a bit of a road-map on what future developments will bring (733,734, BCF, XP12 etc) Thanks!

Thanks for clarifying I look forward to V2! I haven't purchased it yet (new to X-Plane, need to make sure my VA can accept the A variant PIREP's) but every review I've read has complemented this aircraft very highly.

Ahh, okay. May I ask as to why? I’m guessing the two aircraft have similar(ish) performance characteristics but wouldn’t require any significant changes to the model. Honestly speaking I don’t know much about the difference in variants, my thoughts would be that there was only a difference in the engines (of course it would affect the way the aircraft handles and some of its parameters). I completely understand if it’s a matter of lack of time, after all new sounds and scripts would have to be written. I’m only asking because my VA uses the B variant. Also, apologies if it’s been answered previously, what’s going to happen with V2? What are the changes that are going to occur? I’m curious as to the improvements we’ll see, this aircraft already holds the reputation of one of the best turboprops available.

Hi, Is V2 likely to bring in the SAAB 340B Variant added to the pack?