The KLN90B for FSX/Prepar3d in beta.

I tend to agree, I just don't know Github or any other Internet based shared development environments. My concern would be only that any such development should be organized, so someone should take the leading, coordinating role. Most probably I will not be able to contribute (thought I would like very much), so it is up to the team here to make any decision. The code is with you.

I try to help if you have any question however. I would like to see this nice module to be completed.
 
Hello! My problem is: some airports (for example URRR) are present in files "airports" of the PSS or vasFMS NavData DB, but after updating (or installing DB) on board these airports are missing in KLN and in file PTT_APT (there are not rows with "URRR" etc.)
Please help))
 
Last edited:
Where KNL takes navdata when NAVDATA=0 in file .cnf ? I think my KLN dont read other NavData (PSS or vasFMC) even when NAVDATA=3 or NAVDATA=4..... Exactly I changed the conf-file as advised....
I dont have URRR in default scenery folders. My URRR is sided (custom) scenery. I think my KLN always read default sceneries (default BGLs) . May it be?
Even I deleted DBs folder (both vas and(or) PSS), but KLN is still updating.... From where?!?!?
 
Last edited:
Hello, I am very new to making changes like this in flight simulators. On P3D, I'm trying to install this on a plane that has a KLN90A installed that isn't working anymore. I am trying to install it as both a popup and in the virtual cockpit, replacing the original in the same position. I am thinking that there is no virtual cockpit element to this, and that's the entire issue. But the screen information displays only on the virtual cockpit screen, which says it's a KLN90A, while only the buttons and knobs work on the popup version. The knobs and buttons on the VC panel move normally, but have no effect. It doesn't seem to interface with the airplane's autopilot system.

In the panel.cfg I replaced the old KLN90A "window" gauge line to: gauge00=kln90b!KLN90B,0,0,250,120

In the Vcockpit section I replaced the original line with: gauge00=kln90b!kln90b, 500,1,380


Many apologies if this is not the right place to ask this sort of question. I tried searching around for info on this but am not really sure of what search terms will get me to the right place. Someone else mentioned this issue previously in the thread, but I didn't see any responses. Thanks for any help!

 
This gauge is not still 100% ready (still in beta phase). Some improvements like VC and 2D panel working is not implemented (screen mirroring). If 2D screen is working, VC cannot work and viceversa. Knobs in Vc required modify the VC from the source model.

This gauge is nice to be added as a 2D panel at this moment.
 
KLN90B fans,

I have good news for you. I have found and fixed a bug* in 0.77B that was causing most of the crashes. It may have been the only crash-worthy bug, it certainly has the potential to have caused quite a bit of trouble any and everywhere.

I have a replacement KLN90B.dll for you to test if you would like. Simply drop it over the existing kln90b.dll in 'gauges' if you already have 0.77B installed. It will self-identify as 0.79B with a date of 2017-01-21. It is compatible with the database formats in 0.77B. If you are still using 0.76B, please install 0.77B then place this dll over the one in 'gauges' to test.

But wait, there's more!

This version also has implemented the OTH5 thru OTH10 pages. These are the fuel management and air data pages and they are very nice to have!

Also, a couple of minor bugs were corrected in the VNAV functionality and so far as I can tell it works correctly. It is also now implemented on the Super Nav-5 page also. And, regardless if you are using VNAV or not, if you enter a selected altitude on NAV 4 page then you will get an alert tone (C-chime) when you approach the altitude (in climb or descent) and the same tone if, once you are at altitude, you drift more than 300 feet from it.

http://fscaptain.net/downloads/kln90b_79B_test.zip

Enjoy the KLN90B, and please let me know if you experience crashes with this version, with all the details you can supply if you do.

Dutch

* Bug details: the problem was obvious right on the NAV 2 page on the opening screen, and when I realized that after all this time, it led to the solution. Did you notice that in 0.77B your present position was often shown in relation to an ILS and not only a VOR? That is not correct behavior. The problem was the ILS navaids were being loaded into the VOR database as VORs. But when any was accessed to be used, it would crash. You could verify this by scrolling through the VOR database. When you came to one starting with an I the KLN crashed. It was trying to handle an ILS as a VOR. Since there are many places where VORs are accessed internally as part of the nearest navaid list, this had the potential to cause seemingly random crashes.

I don't know if this is the only serious crash problem but it might be. Only testing will confirm.
 
Last edited:
Dang it...silly bug. Download it again that should be gone away.

It's why we have others test it...

The corrected version is still 0.79B but the date is now 2017-01-22 and it also now contains a feature that will detect a database from an earlier version and rebuild it automatically.

Dutch
 
Last edited:
Now, since my Joystick died i can't test myself, but, there was a bug with 0.76B (no idea if it persisted in 77B) that the direct-to buttons functionality would make it impossible to continue following the route, and even lead to crashes.
 
Now, since my Joystick died i can't test myself, but, there was a bug with 0.76B (no idea if it persisted in 77B) that the direct-to buttons functionality would make it impossible to continue following the route, and even lead to crashes.
I haven't addressed this bug. It could have been fixed in 0.77B, but I have never seen it. It's not unusual for me to skip waypoints by using the direct-to function, and it always resumes flying the plan when it gets to the selected waypoint for me. I'll check it again tonight to see.

EDIT: I loaded up a flight with 5 waypoints. While enroute normally to #2, I brought up the FPL, pressed CRSR, used the inner knob until waypoint #3 was highlighted, then pressed the Direct To key. I confirmed that was what I wanted by pressed ENT. The airplane immediately turned and flew direct to #3 without passing over #2, and when it got to #3, automatically sequenced properly to #4. So unless someone reproduces it, I think this bug doesn't exist in 0.79B.

Dutch
 
Last edited:
I have made about 8 flights so far and so far not a crash or problem. Previously before this fix it seemed to crash every other flight, so much so I went back to 0.76B. Big difference.

If others feel confident enough after a few more days, I will package up an official release of 0.79B.

When I do I'll try and get the Github source updated to match. To really complete this project we need to at least finish coding the CAL and TRI pages, and get the APT 8 approaches to work.

At that point, I believe we can legitimately call this a true simulation of the KLN90B.

I wish I could do that but I simply don't have the time to do more than track down a bug now and then. And this one was actually easy - it was a one-line correction, after I realized what was causing it.
 
Last edited:
With
ILSFREQ=0 ; 0=do not load ILS frequency data, 1=load ILS frequencies
Worked.

I had
ILSFREQ=1 ; 0=do not load ILS frequency data, 1=load ILS frequencies
CTD
 
With
ILSFREQ=0 ; 0=do not load ILS frequency data, 1=load ILS frequencies
Worked.

I had
ILSFREQ=1 ; 0=do not load ILS frequency data, 1=load ILS frequencies
CTD
I'm not able to reproduce this with the 1701 cycle either vasFMC or EADT KLN90B data. Mine builds without a problem.

I doubt however that the problem lies in the navdata. Try setting your NAVDATA=0 and rebuild and see if it still crashes.
 
Tried with Navdata=0 ...CTD at 50%.

Conf file used:

[INTERFACE]
KOHLSMAN=1 ; Do we read the Altimeter settings?
APHDG=1 ; Do we drive the AP heading in HDG mode with NAV/GPS on GPS?
OBSIN=0 ; Do we read the NAV1 OBS setting?
OBSOUT=0 ; Can we set the NAV1 OBS setting?
AIRDATA=1 ; Can we read air data from the interface?
FUEL=1 ; Can we read fuel data from the interface?

[KLN90B]
FONT=0 ; 0=Lucida Console (default) 1=Terminus (must be installed on box)
NAVDATA=0 ; Navigation data package number (0-4)
; 0: no external navigation database
; 1: traditional PTT database (no transitions)
; 2: "EADT KLN 90B" pack
; 3: "PSS Airbus/Boeing/Dash" pack
; 4: "vasFMC Flight Management" pack
NAVDIR=E:\Steam\steamapps\common\FSX\NavData ; Navigation data directory
RUNWAYS=1 ; 0=load only hard surface runways, 1=all runways
ILSFREQ=1 ; 0=do not load ILS frequency data, 1=load ILS frequencies
TC=170754
TB=986895
 
Top