@@ -120,16 +120,23 @@ Please report bug at <seb.marque@free.fr>.

   * many more...

 # Installation

-Just `git clone https://sebmarque.hd.free.fr/git/seb/zkv1000` in your favorite Instrumentation-3d dir.  

+Just `git clone https://sebmarque.hd.free.fr/git/seb/zkv1000.git` in your favorite `Instrumentation-3d` dir or directly in your aircraft files structure.  

+Please note that the `Instruments-3d` dir is recommended as the zkv1000 wants to integrate the official `$FGDATA/Aircraft/Instruments-3d` some days  

 Then somewhere in the XML configuration of your aircraft, put only few lines as described below

 ## Create the `zkv1000` Nasal namespace

-In the `<nasal>` place of your aircraft configuration

+In the `<nasal>` place of your aircraft configuration, tell FlightGear where to find the `zkv1000.nas` file

         <zkv1000>

             <file>Aircraft/Instruments-3d/zkv1000/zkv1000.nas</file>

         </zkv1000>

-Actually this is where everything begins, please have a look at this code, it would help you to follow the script.

+or

+

+        <zkv1000>

+            <file>Aircraft/My-Nice-Aircraft/arbitrary/dirs/zkv1000-or-not/zkv1000.nas</file>

+        </zkv1000>

+

+Actually `zkv1000.nas` is where everything begins, please have a look at this code, it would help you to follow the script.

 ## Set specific values for your aircraft

 Specifics values for aircraft can be set via the aircraft configuration, in the `<instrumentation>` section, just add a section `<zkv1000>` and set here the needed values.

@@ -174,7 +181,7 @@ Defaults to `none`, available entries are the `.nas` files located in `Nasal/EIS

 or the one from another aircraft. Anyway if the EIS nasal file targeted doesn't exist, the fallback is the type `none`.

-#### or you can give the absolute path (not recommanded)

+#### or you can give the absolute path (![][warning] not supported)

         </eis>

           <file>/home/foobar/fgfs-data/Nasal/testing-jet-jsbsim-EIS.nas</file>

@@ -205,7 +212,7 @@ You can specify the stall AoA in order to display it in the dedicated display.

 ## 3D models

 In the definition of your flightdeck (here are the values for the installation in the Lancair 235 in which I develop the device)

-put it everywhere you want to

+put it everywhere you want to. Note that the path `Aircraft/Instruments-3d/zkv1000` is dependant on the path where the zkv1000 is installed, this can be somewhere like `Aircraft/My-Nice-Aircraft/arbitrary/dirs/zkv1000-or-not`as mentionned earlier in this section.

         <model>

             <path>Aircraft/Instruments-3d/zkv1000/pfd-pilot.xml</path>

@@ -166,11 +166,12 @@ var init_props = func {

     props.globals.getNode('/autopilot/locks/roll',1).setValue('');

     props.globals.getNode('/autopilot/locks/passive-mode', 1).setIntValue(1);

-    data.zkv1000_reldir = 'Aircraft/Instruments-3d/zkv1000/';

-    if (getprop('/sim/fg-aircraft') != nil)

-        data.zkv1000_dir = getprop('/sim/fg-aircraft') ~ '/Instruments-3d/zkv1000/';

-    else

-        data.zkv1000_dir = getprop('/sim/fg-root') ~ '/' ~ data.zkv1000_reldir;

+    data.zkv1000_reldir = io.dirname(getprop('/nasal/zkv1000/file'));

+    data.zkv1000_dir = string.normpath(

+            io.dirname(getprop('/sim/aircraft-dir'))

+            ~ '/'

+            ~ string.replace(data.zkv1000_reldir, split('/', data.zkv1000_reldir)[0], '')

+        ) ~ '/';

 }

 var load_nasal = func {