[ Closed ] X-Life ver.2 Early BETA 1,2,3, RC1 (Page 1 of 2)

Topic "Plan for Future" is very useful. Sure, I am understand well what airports coverage depend of users what send us taxiroutes for checking and publishing. We should care about users who create it. Yes, WED is some special software and not easy to use. Yes, be better to create own instant taxiroutes editor. And yes, it is Done now.

What new in ver.2.X:

beta 1:
+ add instant taxiroutes Editor
+ add new .xlf (one file format) for taxiroutes
+ old .dat + .txt support is continue
beta 2:
+ Insert point action fixed
+ Unluck verification as ARR/Alt airport fixed
+ Export/Import flightplan procedure fixed
beta 3
+ Runway Dep/Arr settings not saved fixed
+ Sea-level airport crash fixed
rc1:
+ add airport drawing check
     - if two points very close but not connect
     - if not connected end of the line not have gate/stand
     - if gate too far from nearest taxiline point
     - if there is no holdshort marked lines exist between runway and taxiways
+ fix some bugs and CTDs

Permanent link to actual beta 2
http://www.jardesign.org/x-life/download/xlifeb.zip

Installation:

If you use ver.2.X, you need update .xpl files only (attached)

If you use ver.1.X, you need delete old and install new FULL plugin from ZIP, please not mix any

1. Be sure what you use OSX 10.9-10.12 or Windows 7-8-10 and X-Plane 64 bit 10.42+ or X-Plane 11 64 bit.

2. Be sure what you have at least one of static library installed -
OpenSceneryX. If not, you can install it for free opensceneryx.com

3. Copy “X-Life” folder to your ../X-PLANE 10/Resources/plugins/ folder

4. If you prefer use HD “Bluebell XL” traffic AI library, please download 3 files from
http://jardesign.org/downloads/BBXL/BBXL-1.zip
http://jardesign.org/downloads/BBXL/BBXL-2.zip
http://jardesign.org/downloads/BBXL/BBXL-3.zip

Next unZIP and put “Bluebell XL” folder to ../X-PLANE 10/Custom Data/ folder
and install folders “PackA”, “PackB”, “PackG”, “PackJ”, “PackP” to
../X-PLANE 10/Custom Data/Bluebell XL/ folder

UPDATE YOU NAV DATA WITH FRESH CYCLE (if needed)
X-Life use NavData (old) cycle by Aerosoft from own /navdata/ subfolder
or from ../X-PLANE/Custom Data/GNS430/navdata/ folder if exist

If you need update your cycle, please use Aerosoft/Navigraph
- “JARDesign a320/330 Native format” or (the same in fact)
and put new cycle to ../X-PLANE/Custom Data/GNS430/navdata/ folder

How Airport Editor work

For initial understanding we prepare airports data in new .xlf files format
(you may open it with next editor also):
EFHK http://simliveries.com/index.php/2017/0 … life-beta/
UAAA http://simliveries.com/index.php/2017/0 … life-beta/
Sure, you can find this EFHK.xlf and UAAA.xlf in your /X-life/Airports/ folder

Load your aircraft in some airport, as example EFHK
Not need start traffic before!
Tap: Plugins -> X-Life -> Tools -> Airport Editor to start editor
Tap: on tab (LINES / GATES / RUNWAYS / RADIO) to switch different elements of airport what you want to create/edit
Use LINES tab if you want operate with points/lines as example
Use GATES tab if you want operate with gates/stands
Use RUNWAYS tab if you want to see Runways end points. You can move this points if need.
Select (clicking on Name lable) points, lines, gates (select needed tab
Click action buttons what available after selection
Drag points and gates (UNSELECT them before) by 'tap and hold' left mouse button on it
Rotate gates (SELECT this gate before) by 'tap and hold' left mouse button
Use SAVE button to save your data to, as example EFHK.xlf file
.xlf format include all datas for traffic in this airport

If you want draw some new airport from scratch, for example LDDU:
- please be sure what LDDU scenery folder is exist in your Custom Scenery folder
- please be sure what this scenery folder name include ICAO-code (LDDU in this case)
- please be sure what apt.dat file is exist in /Custom Scenery/LDDU Dubrovnic/Earth nav data/ folder
- please be sure what no files with LDDU name (like LDDU.dat, LDDU.txt, LDDU.xlf) not exist in /X-Life/Airports/ folder
(this file will be use by editor to import initial runways data)
- load your aircraft at LDDu and open Airport Editor Plugins -> X-Life -> Tools -> Airport Editor
- Switch RUNWAYS tab to see runways lines what was imported from that apt.dat
- Draw lines and gates
- Save result to LDDU.xlf file
- Close Editor and start traffic
- Next time when you will run editor, just saved file LDDU.xlf will be loaded from /X-Life/Airports/ folder

*** important note about taxiways MARKing:
Taxilines may be selected (need tap on it name lable) and marked (have visual different colors) as:
- runway (if taxiline is a on runway)
- hold area (if taxiline stay between runway and hold short)
- taxiway (for all other taxilines)
You can check how this done and look at EFHK and UAAA airports as example.

We will prepare details manual for Airport Editor some later.

FMCar update
Please use this files to update FMCar and make it compatible with new .xlf files format
http://jardesign.org/forum/viewtopic.ph … 877#p17877

All remain the same
- please post you opinion about this version, post what you like/unlike
- post your log.txt + x-life.dmp if Crash happen and you are on Windows.