Leaderboard

Hi, I've solved the issue. I took 2 steps but I don't know which one exactly did the thing for me. Normally when experimenting I check results after every step but I was a bit tired and therefore forgot to check after my first step. So what I did was to simply install openAL on my PC directly from their website (download the installer, run the installer, don't know what it did but it was fast, I suspect it put openAL32.dll and perhaps some libs somewhere). Then I deleted openAL32.dll from the "X-Plane 11\Resources\dlls\64" directory. I run XPlane's installer again to download the latest .dll and tested. No more errors in my log.txt. I was surprised because I always thought the sounds worked well. I was a bit suprised that putting the headphones on didn't affect sound but now I know that I was really wrong. After correcting my issue, what a change to the TBM900's soundscape ! Awesome. This model keeps astonishing me by its depth. A big thanks to the developers.

My video uplaod has finished and I can now show you how the thunderstorm situation seen on my screenshots looks in motion. This possibly also helps on judging if performance is good enough for some users but I think those flying at locked 30 fps on pretty modern computers don't need to fear anything (and even if then SMP is worth the tweaking for compensation). :-) My specs: i7 2600k, 4200 MHz 32 GB DDR3 @ 1333 MHz RAM (with 16 GB @ 2133 I get about 5 more FPS) GeForce GTX 1070 (8 GB VRAM)

Hello again. I'd like to give another update. During our investigation into updating our NavData to the XP1100 format, it became apparent that this must be the way to go for long-term future compatibility and more reliable route calculations, including holds, but would require a significant rewrite of the FMS base architecture to do so. So over the last 4 weeks, we have done exactly that. We now have the beginnings of a 2nd FMS running in parallel with... but independently of.... our original FMS. We are running 'newFMS' on CDU1 and 'oldFMS' on CDU2. We will NOT be simulating dual FMCs though. This old/new arrangement only exists so we can compare the new with the old while developing the new. It is much like building a new bridge alongside an old bridge...and when the new one is ready, we will remove the old. Much of the challenges we have faced with regards to drawing routes / vnav have been related to the limited nature of the navData format we have used since we began the project. Moving to a format which have been designed expressly for "navigation processing" will go a long way towards easing our algorithm development. The image below shows the two CDUs, both on the "IDENT" page, but clearly displaying differing data as they use differing algorithms/databases....and for those curious, the pilot CDU displays 'odd' formatting simply because we were testing our new display drawing code. We are very excited moving to this new XP1100 format. We have, in 4 weeks, accomplished what took us over 24 months to accomplish originally. Of course we have the benefit of experience, but the elegance and efficiency of the new navData format and architecture allow us to focus on the FMS functionality by orders of magnitude more than before. With the new infrastructure complete, we will begin working on the route editing. The current navData set only supports about 8 different waypoint types. Arcs are not supported, as is common in today's RNAV procedures, but the new format contains all path/terminator types typical in today's procedures. As usual, we thank you for any patience you have managed to muster as we work to improve the IXEG 733. P.S. Jan and myself will be at Flight Sim Expo in Orlando, FL/USA in a few weeks if anyone wants to talk shop. -Tom Kyler