Changes in LK8000 version 3.0 vs. version 2.2e

GENERAL

• Huge code cleanup, smaller executable size
  Faster startup
• shows version number at startup
  Waypoint engine retuned and optimized
  Graphics engine retuned and optimized:
  Faster zoom in/out with full topology and airspace rendering
  
• Support for 320x234 and 234x320 screen resolutions
• Support for 240x400 portrait mode, support for 854x358
• PC version using current execution directory as LK8000 folder, if _System/_SYSTEM folder and file are found.
• If no directory _System is found , or there is no _SYSTEM file inside, then we go using the old classic
• Documents LK8000 folder, as usual, which is the old default folder.

CONFIGURATION

PROFILE-SYSTEM (system profile + airplane profile + pilot profile):

. System profile (all relevant system parameter settings)
. Airplane profile, default glider Standard Cirrus
Airplane parameters (those in config page 7: Category,Polar type, Max Speed, Handicap, Ballast dump time, Aircraft type, Registration,
Competition classe, Competition ID) are saved separately from system profiles.
They can be saved in the config page 7 (either as new, or overwriting an old one).
They can be loaded on startup from the profile subpage in the first start screen.
On program termination, aircraft profile is saved to DEFAULT_AIRCRAFT.acf file, like for DEFAULT_PROFILE.prf.
If you change anything in the configuration regarding aircraft, it will be automatically be saved into the
DEFAULT_AIRCRAFT file. Remember to "save as" or "save new" if you want it to give a name to the aircraft config.
Airplane profiles can only be selected on startup, not during runtime.
. Pilot profile, default pilot Wolf Hirth, to be set/initially saved from config page 20 (logger)
. Startup screen profile page is showing pilot name, aircraft, reg-no and used polar, and pilot-, airplane- and system profile they are updated
while changing eventually changing them.
However, remember that these choices are saved to defaults ONLY if you enter the program, and NOT if you
exit without running really the LK. In that case, in fact, no profile will be saved.
. Profile full reset warning system
In profile-SYSTEM a virtual RESET LK8000 profile is selectable: if chosen, LK will reset
default aircraft, default pilot and default system profiles to factory defaults.
LK will display this pending situation on the splash screens.

. New configurable Infopages.
System config menu 10 let you configure individually each infopage, except traffic.
If all pages of a branch (for example, all 2.x pages) are OFF, then that branch will not be selected
during rotation.
Direct access to pages through custom keys is always possible, bypassing this configuration.
Traffic pages 4.x - when Flarm is detected - are always available. If you don't want traffic informations,
then please disable these traffic data being sent by flarm in its protocol, and save CPU.

. New configurable BottomBar.
System config menu 10 let you configure individually each bottombar stripe.
While rotating, only desired stripes will be shown.
Even if all bars are set off, NAV1 is shown.


. New configurable Efficiency parameter in Safety config menu 6.
This is the default value for the Basic setting's efficiency
and it is loaded on startup.

. New Total Energy usage in configuration
When TotalEnergy is in use, LK will calculate the height you would gain by pulling up the aircraft at the current speed, up
until the speed becomes the optimal for best glide.
For example if you are flying at 200kmh with a discus with no ballast, the speed energy would be calculated as if you would
pull up and slow down to 100kmh: you would certainly climb to a better altitude of course.
This speed height will be added to all arrival altitudes. By default this feature is DISABLED, for safety reasons.
The totalenergy in LK does not affect glide ratio values. Only arrival altitudes.

. Add PREROTATE and ENDROTATE external execution programs.
PREROTATE1.exe PREROTATE2.exe and PREROTATE3.exe will be executed before anything else.
On exit, ENDROTATE1.exe ENDROTATE2.exe ENDROTATE3.exe will be executed before ENDLOAD_99.EXE .
Example of how to make the screen rotate 90 degrees on startup, and make it back normal on exit:
- Copy rotate.exe from System CEUtils folder of LK in the LK8000 folder, where LK8000-PNA.exe is.
- Rename rotate.exe into  PREROTATE1.exe
- Copy rotate.exe again, and rename to ENDROTATE1.exe
- Copy rotate.exe again, and rename to ENDROTATE2.exe
- Copy rotate.exe again, and rename to ENDROTATE3.exe
This way, screen is rotate to 90 degrees on startup, and by 270 degrees on exit.



DATA

. Support for CUP files with no header line
. OziExplorer waypoint format supported

POLARS
. Polars are now files inside _Polars folder, and can be viewed and edited.
. Extended polars are possible for use of FLAPS settings indicator. See Example.plr  file in _Polars.
NEW POLARS
IS28B2 Lark
SZD-38A Jantar
LS-6-15
Lak17A-15
Lak17A-18
Nimbus 4
SZD-56-2 Diana2
Ventus 2Cx (18m)
and more ...


GRAPHICS

. FastZoom for all devices
. Show user friendly mapscale values with changing units as needed
. New autozoom threshold option for paragliders
. Show pg initial zoom values as numbers in config page 23
. Modify mapscale precision printed on map, give 2 decimals when using non-metric units
. Terrain shading disabled at low zoom levels, automatically.
. Add ACT indicator in mapscale for ActiveMap status
ActiveMap can be enabled/disabled with both a customkey and menu button.
When it is enabled, the indicator appears near the map scale.

USAGE

. LOCK mode (Config 1, Lock Mode button) is available for all aircraft modes.
Paragliding/Hanggliding mode will automatically unlock the device a few seconds after takeoff.
Other modes (car, GA, gliding) will keep device locked until manually unlocked.
This is useful on some devices that are pocket-sized such as Funtrek.

. Ungestures: in 2.x 3.x 4.x pages, an alternate mode for advancing through pages (aside gestures, still valid) is to
simply click on the left and right screen border, in the center.
+-----------------+
|                    |
|                    |
|X                X|
|                    |
|                    |
+-----------------+

Gestures are still available of course, but this facility is speeding up page flipping a lot!
. Paragliders screen unlock is valid by doubleclicking only on lower right screen corner.
Previously any position was good, leading to possible false unlocks during takeoffs.
. Advance in Analysis pages also by clicking on the right part of screen like on Nearest pages.
. IBOX mode is no more available
. New menu button: Auto MC Thermal+Final
. New Total Energy button in Config 2/3 menu
. New Button DISPLAY 1/3 and CustomKey "Change Terrain Color".
It will rotate among the available terrain colors, in real time.
So it's now possible to adapt map colors to the current terrain.
. New Info Status System indicators for :
Simulator mode
GPS device in use for fix
Software version

. Customkey selection list is now alpha-sorted.
. CustomKey TopRight is available for PGs as well    

NEW CUSTOMKEYS
. Customkey "Change screen colors backwards"
. CustomKey "OLC Analysis"
. Customkey "Nearest airspace"
. Customkey "Toggle Total Energy"
. Customkey "Notepad"
. CustomKey "Change Terrain Color"
. Customkey "Center Creen"
Center Screen is a customkey called by clicking for at least 1 second
in the map center area (with some good tolerance). By default this CK
is assigned with the "Oracle" function.
If PAN mode is enabled, this key will not work.
. Customkey "Screen Lock"
. Customkey "Airspace Analysis"
. Customkey "Toggle MapAirspaces page"
. Customkey "Zoom in"
. Customkey "Zoom in more"
. Customkey "Zoom out"
. Customkey "Zoom out more"
. Customkey "Toggle Optimize Route
Optimize route is a function for paragliders only, right now.



Flying AIDS

. FLAPS setting calculator , for extended polars
. Orbiter enabled only after 50m thermal gain achieved. Below this gain, we assume the thermal center is not valid.
Orbiter will autodisable after 700m thermal gain. Thus it is now working in the 50-700m th.gain range.
. Show overlay BEARING while circling.
We could not display bearing difference while thermalling, because it was constantly changing.
. MC buttons will hide AutoMC buttons if manual changes are selected.
This will show screen overlays in landscape mode.
Pressing on Manual, will make them appear again.
. Overlay distances for paragliders have always 3 decimal digits, when the distance is not 0 and below 99.
. E.20s added one decimal for LD value
. New +SAFETY overlay indicator on map display.
When the multitarget is a landable waypoint, and safetyaltitude is in use,
and safetyaltitude was set as at least 50m, then the safety height is printed
below the arrival altitude, e.g. +300
. New info page 3.3 "Thermal History"
This page can be also disabled as usual. It will list up to 50 thermals, out of a max 100,
related to current flight. Thermals cannot be saved!
Each thermal listed is showing usual values as in the nearest page, and the average lift.
You can sort by distance, bearing, lift and name.

The thermal name is the local time you entered the thermal , example: th1437 if you entered
this thermal at 2:37pm .

Selecting as usual a thermal will pop up a page where you can SELECT it.
Once selected, the thermal is assigned to the L> multitarget, and you are instantly brought
to L> moving map.

- In the thermal details page, a Team Code is shown in order to let you broadcast via radio
the position of this thermal to friends.

- A nearby location is shown also in thermal details title window
The nearest waypoint within 15km is used for this purpose.

After a new thermal is detected (after thermalling), this thermal is automatically assigned to
the L> multitarget.

The L> is always showing the thermal name, ex. H1237  and no more a simple "THERMAL".
In the 3.3 page, the selected thermal has its name leaded by a > .
Example:      >H1237

The 3.3 page is listing red and italic all thermals that are currently unreachable.

>> The thermal position is assigned using the aircraft position just after started thermalling,
and its altitude. Thus you will be pointed exactly to the place you were (right or wrong)
just before you started climbing. <<

When selecting multitarget L> in map mode, a circle will appear around the
center of the selected thermal, at high zoom levels.
The circle will not appear at low zoom levels, being not enough visible on
a small screen.
The circle is drawn around the thermal center, while the multipoint L> target
is slightly different because it is indicating the point you have actually
entered the thermal, and its altitude.
Thus on the moving map you will see both the entering point, and the thermal center,
giving you an exact idea of how you started thermalling there, and were you ended up to.

Some thermals are added for the simulator, appearing in 3.3 in SIM mode only.
The closest thermal is .. real for the SIM, meaning that going to that
thermal will show real sink and lift!

. New ALTITUDE ALARMS (config page 15)
There are 3 available altitude (height, really) alarms available.
An alarm will be triggered everytime the configured altitude is reached or crossed.
The alarm will not be repeated within the next 60 seconds.
After 1 minute, if altitude has been lower than Max Altitude and then becomes higher again, alarm will sound again.
To disable this alarm, set it to 0.
The altitude used for alarm is the one chosen in Config menu 5 "Use baro altitude".
Multiple alarms set at the same altitude will have no effect.
Glider pilots should be careful not to set alarms below a safety altitude, during critical phases of flight.
Each alarm can be repeated max 30 times. After 30 times, an alarm will automatically self disable for the current flight.
The visual alarm message automatically disappears after 12 seconds.
Each alarm has a custom sound that can be changed inside _System _Sounds folder.
They are named LK_ALARM_ALTx.WAV
Default is 0 (no alarm).

. New Configurable AutoMC on/off on startup, and new overlay indicators aside MC overlay.
When autoMC is enabled, an "A" is painted aside MC overlay.
AutoMC indicator is : F (Final glide) A (Average climb)  E (Equivalent)

. New AutoMC buttons and configuration. It is possible to change AutoMC type at runtime now.
The AutoMC mode is shown as overlay indicator, and through MC buttons a pilot can change
on the fly MC among manual and all auto modes. Configuration is kept for default value.

. New Color scheme for GA: relative terrain.
This scheme will show red any terrain above current altitude.
Anything below, up to 500ft below, will be graded to yellow.
This scheme is NOT good for gliders, because it does not consider the loss of altitude while gliding.
It is intended to be used by general aviation mode, optionally activated by a button.

NEW INFOBOXES
AlternateX Distance
AlternateX Bearing
BestAlternate Distance
BestAlternate Bearing
Max Altitude reached
Max altitude reached during the current flight.
It is reset at takeoff and at task restart.
Max Height Gained
This height is calculated using the min and max heights detected AFTER the start of free flight.
This value is normally used for badges.
Head Wind Speed
This is the wind component relative to your current track.
It is the difference between the TAS true airspeed and GS ground speed.
A positive value indicates a HEAD WIND, and a negative value indicates a TAIL WIND.
If true airspeed is not available, estimated TAS is used.
In this case the value is only guessed against the current wind set.
Logger
Logger INFOBOX, showing  ON if logger is active, no!  if disabled and not manually forced, Auto
if enabled but not logging because before takeoff.
Home Arrival altitude
Nearest vertical distance to an airspace (or to leave a fly zone)
Nearest horizontal distance to an airspace (or to leave a fly zone)


NAVIGATION AIDS

. Magnetic declination internal calculator for truewind and maybe in the future for true bearings

ORACLE
The "Oracle" is printing informations about your position, by examining both topology and waypoints,
and figuring out a reasonable position reporting to be used via the radio.
Oracle is creating a verbose description of your position.
You can call the oracle with a button in INFO 1/2  and also with a customkey that you can
configure. By default it is assigned to the new CENTER SCREEN customkey.


NEW AIRSPACE ENGINE

. NOFLY/FLY airspaces introduced.
. NOFLY zones - works like the old airspaces. You are in a wrong position when you are inside a nofly zone.
Warning events based on this, so if you try to enter a nofly zone you get warnings to not do that.
. FLY zones - Zones you should be in to be safe. You are in a good position when you are inside a fly zone.
Warning event based on to remain in a fly zone, so if you try to leave it you get warnings to not do that.
Flying to an adjacent fly zone is permitted, in that case no warnings issued. (For ex. corridors beetween
different fly zones)
In the openair file the AF sentence defines a zone as fly, or you can change it from the UI.

. Current / predicted position
Predicted position of the aircraft calculated by lk. This calculation based on current mode (circling/cruise),
ground and vertical speed, and the configured warning time. This is the time before an airspace warning event
is estimated at which the system will warn the pilot. Warning messages based on predicted and current position
as well.

. Warning levels, warning messages
. Yellow warning:
Your current position near a warning situation. This means that you have a possibility to be in a wrong position
in the given warning time. (30sec by default). There are two types of yellow situation:
Predicted warning situation - your predicted posititon in a wrong zone (same as old airspaces case)
Near to a warning situation - You too close horizontally or vertically to a warning position.
(Too close comes from actual speed and nearest warning point distance and from the configured warning time)
. Red warning:
Your current position is wrong, you shouldn't be there because that position violates airspace rules.
(For example you enter a nofly zone, or you leave a fly zone)
. New airspace warning dialog
. Shows the reason of the message, warning level, name of airspace, horizontal and vertical distance, airspace
base and top altitude
. Dialog auto closes after a configured time automatically, or you can close it
. There is a possibility to acknowledge the given warning level for a configured time to not show up again.
. The old one still accessible under Info1/Analysis/Airspace/Warnings button
. Acknowledging
. Each airspace has a warning level and a corresponding ack level.
. Actual warning level calculated by LK based on distances, fly/nofly zones, etc.
. Ack level set by the user, by acknowledging warning messages.
. The warning message appears only if the warning level increases above the ack level. Lets see a few examples:
1.You are circling in a position where a no warning/yellow warning situation flipping. When a yellow warning
situation occurs a warning dialog appears. If you do not press the ack button then in every circle the new
warning dlg will appear beacuse warning level > ack level. But if you ack the yellow warning then the dialog
not shows up again in the yellow warning case for a configured time. If the ack time (120s) expires, then the
ack level goes back to zero, so the warning will appear again.
2.The same case if you are circling at a nofly zone border. Half circle inside the zone. This is a yellow/red
warning flipping. If you ack the red warning for a time, then you won't get a new warning message on every circle.
. Daily acknowledging - enable/disable an airspace
There is a possibility to disable an airspace (until lk restart). You can do that from airspace
details dialog (long click on map), pressing the Disable button. Disabling an airspace means that warning
dialog will never appear for that airspace, and it is not shown on the map as well.
. Warning dialog messages can be:
. "Predicted leaving FLY zone" : Current position inside, predicted position outside a flyzone (YELLOW)
. "Near leaving FLY zone" : Current position inside a flyzone, but you are too close to the border to leave it (YELLOW)
. "Leaving FLY zone" : You have just leaved the fly zone (RED)
. "Predicted entering NOFLY zone" : Current position outside, predicted position inside a nofly zone (YELLOW)
. "Near entering NOFLY zone" : Current position outside a flyzone, but you are too close to the border to enter it (YELLOW)
. "Entering NOFLY zone" : You have just entered the nofly zone (RED)
. New airspace info messages
. When leaving a nonfly zone
. When entering a (new)fly zone

. New Airspace details page, two new buttons for SELECT and ANALYSIS.
SELECT is used to choose an airspace to be monitored for Hdist and Vdist infoboxes.
We call the Selected airspace "Preferred".

. New airspace 2.4 info page with airspace flags (the * column on the right)
E = Enabled
D = Disabled
S = Selected
F = Fly-In modality

When flying inside an airspace, the Distance instead of 0 is showing IN
When flying near an airspace in yellow condition, the Distance is showing a trailing "!".

All 2.4 rows are painted white, red or yellow (light colors)  following alerting situation.

. New airspace drawing options for drawing airspaces with borders and outlines
This will actually tell you at a glance where is the internal side of airspace.
(Warning, this can slow down devices with high screen resolution or slow processor, use with caution!)
. Airspace details now are possible by clicking on them only if ActiveMap is enabled.
. Airspace 2.4 page settings are now permanently saved to a config file on shutdown.
It is now possible to select and airspace, enable/disable a single airspace, and
make these changes permanent.
Be careful that changing airspace file will also remove old settings!
. 2.4 nearest airspace page contains airspaces in maximum 100km range
. Daily acked (now disabled) airspaces are not drawed on the map
. Infobox nearest airspace shows the horizontal distance to the nearest airspace (or to leave a fly zone)
. In airspace details dialog (long click on map) ACKDay button behaviour changed, now it shows a simple question to toggle actual ackday setting.
. Airspace ACK Day functionality changed to disabled/enabled
. Enable/Disable and Fly/Nofly buttons do not close the dialog automatically, and do not pop up a confirmation dialog
. Airspace nearest vertical distance infobox shows vertical distance to an airspace directly above or below at current position (or to leave a fly zone)
. Airspace nearest horizontal distance infobox shows horizontal distance to an airspace at the current altitude (or to leave a fly zone)
. ArSpcH Airspace Horizontal distance below 1000m (~3300ft) will display 2 decimals.
Example, instead of 0.7km it will show 743m
. Airspace warnings working only after 1 minute have passed since takeoff
This is to reduce pilot overload during critical phases of flight.
. Use manually selected airspace for distance infoboxes.
In order to see Hdist and Vdist infoboxes, an airspace must be selected from Airspace details page.
. Airspace support for airspace files containing V sentences
with no space beetween V and X characters (for example, Rieti's official airspaces)
. Add YELLOW and RED colors to airspace warnings.
. Decrease airspace warnlevel to yellow, when leaving a nonfly zone

. Airspace warning labels on map
. Can be disabled from config page2/Warnings
. Shows a red mark on the nearest posititon to a warning situation
. Shows airspace name, and the vertical distance to the border
. Vertical distance negative if airspace border above, positive if below your current altitude. (like in landables case)
. Label color means:
- Black - vertical distance ok, you are in good position vertically
- Red - vertical distance wrong against that nofly zone
- Orange - vertical distance wrong against that fly zone

. NEW nearest airspace side view analysis with obstacle calculation, realy useful!


LOCATION MARKERS

To mark the current position in a waypoint, use the button on the main menu or the customkey.
A virtual waypoint called MK123456  will be created , assuming in the example that the time
was 12:34.45 (local time).
The waypoint detail's description field will report the nearest known waypoint
(for example   Near: London).
Markers will appear as waypoint inside both 2.3 TPS and 3.1 COMMON pages.
Markers are inserted in the COMMON 3.1 pages as Last-in First-out.
They are inserted after the usual commons (home, bestalternate, alternates, task points..).
Up to 10 virtual waypoints for markers are allowed. Creating a new marker beyond this number
will overwrite the oldest existing marker.
On the moving map, markers will appear with a yellow Flag icon.

All markers are also saved to a CUP file called with the current date, like LKyyyymmdd.cup .
So each flight in a different day will have its own markers cup file, that can be reloaded as
an ordinary waypoint file anytime.

BESTALTERNATIVE

BestAlternate rotate multitarget available for PG/HG only if a valid bestalternate
was ever found so far during the flight. If no landables are configured, or if these
landables have never been elected to a bestalternate, then rotation will skip this choice.
In other words: if nothing can be found, even if an old bestalternate which is now unreachable,
then instead of showing --- we skip it.



CONTEST

AAT
. AAT min time step is now 5 minutes, and no more 10
. Enable Contest Engine also for non-glider aircrafts, IF infopage 1.5 is enabled.
This means that using glider mode will not require 1.5 to be enabled.
But using paragliding, GA or Car mode will require 1.5 to BE ENABLED otherwise the
calculation engine will NOT run.
Be careful enabling during flight calculation engine, because all previous point since the
takeoff will not be valid, and the freeflight detection will be wrong of course.
. Drawing of thermal bar disabled for Target PAN map mode
. Target PAN sectors position set to the screen center
. Target dragging switched to clicking for AAT Target PAN dialog
Dragging a small circle on the screen is not a turbulence proof interface.
It is extremely hard to do it during a turbulent flight. Now a click is
enough to move AAT target inside the AAT area.
. Target PAN zoom level increased a bit to make it easier to move the target
. Orientation of active waypoint fixed in Target PAN to not rotate the screen constantly while selecting AAT target
. Multitarget bearing line fixed for non-waypoint overlays in AAT task
. Radius size in task setting has now a 0.05 step for better precision
So it is now possible to use correct cylinder sizes expressed in imperial
units like miles.
. Task speeds <99 are now printed with one decimal value.
. Overlay distance for paragliders using 3 decimals.
Bottom bar using max 2 decimals, even for paragliders.
Lets remember that the gps fix precision is not better than 4-5 meters
in the best of cases! When logging for a competition with another logger,
the two gps may have different distances to the waypoint, and using 3
decimals will result in a false reading.
. Reset topology zoom levels in configuration to defaults.
This is needed because old values in previous profiles were saved as km, not as meters.
Changing the name of variable for profile does the job. Old variables are not read, and new variables will be saved.

. Optimized routes for paragliders.
Leaning on AAT locked target and virtual waypoints, a pretty effective result.
Optimization can be enabled in Paragliders config menu 23, and as a customkey.
When enabled, the T> overlay, the Next waypoint distance, altitude diff, bearing etc.
are all related to the optimized turn point on the cylinder.
The correct optimized point of turn is visualized also.
The optimized turnpoint is named with a "!" leading. Example: turnpoint name is "JACKHILL"
as optimized point it will appear as T>!JACKHILL   and also in turnpoint list and nearest pages.
This is a virtual waypoint, like thermal, takeoff etc.

Since Optimized Route (O.R.) rely on the internal AAT engine for gliders, it is better that
paragliders check the TARGET  cylinder radius to be at -100% , in order to let the calculator
consider the max radius as a turnpoint. By default, but only when you create a new task as
paraglider with this version, all radius are set to -100%. To check, menu NAV 2/3 and then
"Target" , then select turnpoints exluding first and last (start and finish).
Check that Range is -100%, and Radial is 0.


LOGGER

. New G record validation scheme, not using DLL anymore.
. Add modelname and hw type for logger header
. New Logger indicator near the battery indicator in the right bottom corner.
If autologger is disabled, and logging was NOT manually enabled, then
this indicator will NOT show up.
The logger indicator in fact appear only when logging is automatic or
manually enabled.
Orange dot blinking means: ready to log as soon as takeoff is detected.
Red dot steady (not blinking) means: logging in progress.



LK FLIGHT LOGBOOK

Each time that a landing status is detected, three files are created/updated automatically inside _Logger folder.

LOGBOOK.LST is a notepad formatted file, textual, where each flight is saved on a single line.
It can be read using Info 2/2 LogBook "LogBook List" menu button.
Only relevant informations such as date, flytime, takeoff, landing, pilot, location and aircraft rego are written.
The pilot has all the flights listed here, similar to other instruments logbooks.
In case of SIM mode, a "SIM" field is appended to the flight line.
The LOGBOOK.LST can be reset by user request in LK, using reset button in Logbook menu.

LOGBOOK.TXT is a notepad formatted file, textual, and it can be read from LK using
Info 2/2 LogBook "LogBook Details" menu button.
This file is reporting aircraft type, time of takeoff,
landing, flytime, pilot, towing time, toing altitude, max altitude reached, odometer, OLC distance ,max height gained.
In case of SIM mode, SIMULATION is added also.
Will not be accurate of course for Winch launches!
(It is active only for gliders, not for paragliders.)
Each flight is on a single dedicated note page, and it is possible to browse through all flights using the arrow keys.
The LOGBOOK.TXT can be reset by user request in LK, using reset button in Logbook menu.

LOGBOOK.CSV is in Comma Separated Value format, and can be open as-is by any spreadsheet.
It is never reset by the software.  It is made for external usage.
In case of SIM mode, a "SIM" field is appended to the flight line.

Notes on LogBook:
- A flight is added to the logbook when the landing status is detected.
- It is also added on lk program exit, if the aircraft is still flying.
- On PNA/PPC versions, Logbook is kept only in FLY mode.
- On PC version Logbook is made also in SIM mode.
- A Takeoff must be detected, in any case, in order to "start" a flight that can be "closed" with a landing.
- Remember that the LANDING event is detected automatically about 45 seconds after real landing.



SIMULATION

. Added FLARM traffic to simulator, if FLARM on Map is enabled in system config menu 13.
Four flarm objects are added around the plane. One of them will become a ghost and a zombie quite soon.
Objects are moving a bit, but just to let you experiment with traffic on LK.
Page 4.1 TRF is of course enabled, and FlarmNet is used as in real life.
Overlay multitarget F> is also enabled, and need an object selected in 4.1.
Selecting a target in 4.1 will show it in page 4.3 and 4.2 .
All of this is useful for making practice with FLARM traffic and explore the 4.3 sight page.
Do not expect to have a videogame, because traffic is not moving as in real life.
. Added some thermals for testing
. new more direct menu location



DEVICES
. New priority based automatic selection of baro altitudes, when more than one baro altitude is available

. support for LX 16xx device
. support for Medion S3747 aka Royaltek BV-3200 aka other brands. Baro altitude is managed.

. support for Holux FunTrek aka CompeGps rebranded device, full support for battery power,
resolution, baro altitude etc.
. support for Zander ZS1 including MC and Wind
. IMI ERIXX logger support, also for task declaration

. Reset FLARM after a task declaration.



ENERGY
. New Battery indicator is appearing in the right bottom corner
decreasing in green and becoming red when battery is nearly empty.

---------------------------------------------------------------------------------------------------------------
CHANGES
---------------------------------------------------------------------------------------------------------------

. WEATHER support for RASP is no more available.

. Old JPG2000 terrain files in old XCM maps are no more supported.
If you are still using old XCM maps and you want to convert them to LKM
please contact us. NOTE: Norway was already converted over 60 DEG !

. Changed "V rough air" into "Max speed" .

. Change bottom bar STA3 Radial into MaxAlt

-------------------------------------------------------------------------------------------------------------------------------
FIXES
-------------------------------------------------------------------------------------------------------------------------------

.  Distance & ETE to Start : use Optimized Wpt when PGOptimize=ON
Change Optimized Wp to Correct Side of SG for Exit SG

.  Fix flickering startup problem, workaround.
Since 2.2, selecting profile on startup would show for a while the first left button in a wrong position.
Use Correct Finish raduis in PGOptimize

.  Fix Max Height Gain should not be reset after task start or restart.
It is reset only on free flight detection after takeoff.

.  fix PG Optimized Wp with Exit Start
Use Optimized Wp for NextETE if PGOtimize=ON

.  Fix wrong thresholds for moving map painting when using non-metric distances (nautical or statue miles):
- max zoom level for shading terrain
- max zoom level for colored snail trail
- max zoom level for drawing thermal circles

.  Fix RealScale for Activemap nearestwaypoint: on non-metric distance units selected, it was hard to select a waypoint
on the moving map clicking on it, not enough tolerance!

.  Fix RealScale for Heading (track) line, appearing wrongly also at low zoom levels when non-metric distance units selected.
The heading track line, if activated, should only appear within a reasonable zoom level.

.  Fix RealScale for WaypointInRange: for non metric distance units, more waypoints than necessary were processed for calculations.

.  Fix RealScale for Waypoint printing on the map.
For non-metric distance units, waypoints were not correctly printed depending on map scale.

.  Fix problem with non-metric distance unit, setting configurable topology thresholds incorrectly.
This was resulting in quite wrong rendering of topology!! Selecting for example 5 for small cities,
would show small cities up to 5km in the original intentions, but really it was also showing them
up to 5nm , if nautical miles were in use.
Now the topology configuration must show corrected scaled values for topology, and convert them
between different distance units.

.  Fix problem in topology settings, also in 2.2, not saving decimal values .

. Draw thermal band under overlays
http://www.postfrontal.com/forum/topic.asp?TOPIC_ID=5850

. Fix BestCruise track indicator is only relative to T> , and should not appear in other
multitarget modes.

. Fix final glide bar mode flashing orange and red.
The final glide bar will no more indicate X or orange flashing, to simplify things:
red for negative altitude, green for positive.

. Fix snail trail flashing colors. Colors are shown only at a meaningful zoom level, better tuned.

. FIX BestAlternate search bugs, excluding nearest outlanding when low on terrain and choosing not the best.
OVERSAFETY altitude (100m) no more used, because of too conservative results. We use only 70% glide best capability
and safety altitude.

. Bugfix TaskETE was not calculated when not enough height to complete the task.
Task ETE is a simple DistanceToGo / SpeedAchievedSoFar

. Fix bug AAT next waypoint target bearing and bearing diff wrong .
They were always related to waypoint center, and not to the target

. Fix glidebar painting arrow based on a value that was ignoring safetyMC in some cases.

. Fix replay logger problem not resetting some variables in flightstats
This will not solve at 100% all replay problems when replaying several IGC files. Currently the only safe solution is
to restart LK to be sure all statistics are reset correctly.

. Fix bug not calculating TC.Avg and Th.All at flight startup.
LKCalculation freeflight detection was resetting StartClimbMode and this was bad.
Because StartClimbMode is set before we actually start climbing, and discarded if
after a few turns we are not really circling.
FF engine is also using the first thermal to detect FF, and this was causing a sort of a loop.
The problem was more likely to appear only in IGC flight replay mode in simulation.
However, even in real flight there was 1/100 of chances to get this (minor) problem.

. Fix AutoQNH problem. Takeoff wp was used in place of Home first!
Correct mode now is: look for home, if no home nearby, look for another known waypoint near 2km.
Do not consider TAKEOFF as a valid waypoint for QNH because it is itself assigned an altitude!
If no waypoints nearby, and no home, use terrain altitude if available.