[ Closed ] X-Life ver 2.1 beta 3,4,5,6,7 (add real schedule) (Page 3 of 7)

Hmm.. Aircraft/Liveries is a main trouble it this project for now. Sure, if we will have 100% aircraft/liveries library, we can see 99% of real traffics at airports. But X-Life traffic is free and may use free libraries like OSX or BlueBell. So, we have it AS IS right now. Making new library is VERY expensive task and money what project get from Deluxe users not enough for this. So.. I dont know how we can solve this. May be in future.. Also, for now, JARDesign should pay for real schedule data requests to data-provider where we get real data online. Next, we pay for server, what accumulate/sort/delivery this data and send it to users to users. Anyway, we have test period what will explain us final project budget using a real time schedule. I hope we will stay in business. Sure, I dont want make basic Traffic plugin payware. I prefer have it freeware.

Hi JAR,

CTD while approaching LOWS, flying from LOWI to LOWS.

LOWI SID RTT DCT UNKEN STAR LOWS

Earlier, another user had reported that flight plans with a direct-to segment ("DCT") were reported to be working with X-Life. I encountered an issue last night which indicates DCT is not always working.

I was trying to fly a route between CYQB to CYOW using the following flight plan:
CYQB SID UDBAM DCT DICEN DCT NOSUT DCT ALIDO STAR CYOW
This is a real-world flight plan pulled from flightaware and was valid for the AIRAC data I have installed (verified by entering the fplan first into the 737-800X FMS as well as validating the route with QSimPlanner). ALIDO is a valid transition waypoint for the LEAMY3 STAR (ALIDO.LEAMY3).

X-Life would not accept any flight plan that contained a DCT segment between these two airports. I tried reducing the flightplan to simply CYQB SID UDBAM DCT ALIDO STAR CYOW but that was also rejected. The only flight plan it would accept is one generated by X-Life which exclusively used airways (and made for a very circuitous routing). I eventually flew the route using the X-Life generated plan successfully.

Thoughts on trouble-shooting:
While both airports have official taxiway data (as shown on the JAR map and on SimLiviries), I had made some small edits to the XLF files using the in-game Airport Editor. My personal edits showed no errors in the Airport Editor. On starting X-Life at CYQB I received the blue text warning that CYQB was not an official airport (or something similar).
Therefore, could it be that direct-to "DCT" flight plan segments are not working if either of the origin or destination airport throws the blue text caution message?

Update:

Did a bit of testing this evening, looks like it may be some issue with CYQB.
I re-downloaded the latest beta (2.1b4) and encountered the same issue with the initially posted route.
However, I was successful in loading a route with a DCT segment by reversing the route from CYOW->CYQB
CYOW SID VERTI DCT YMX STAR CYQB was accepted but a direct reversal of the initial route was not successful.
Log is attached and shows the issue with initiating the route from CYQB and the success from starting at CYOW as well as attempts with completely reversing the route.

В первом посте описано - нужно скачать и заменить .xpl файлы в папке с плагином.

@JARD I just tested out the new beta 4 from KRIC to KPHL everything run smooth but when I landed in KPHL exited the highway and reported to the  x-life  ATC  and then requested a follow me car it crashed the whole sim. Thank you

Sorry

I forgot adding log file

Ok, Thanks for info. I just find what problem was and just fix it in my code. Will work well with next beta.

if this possible - please attach log.txt and xlife.dmp file just after crash - this files will help a lot to find a reason for crash and improve code in this place.

Photos didn't post. Trying again.

Update .xpl files to beta 5. Some bugs and crash fixed.

Please install mac.xpl and win.xpl files from first post instead of old.

Regards, Eugeny!

I was using X-Life 2.1_b4 couple of days and here my thoughts.

1. General Menu seems too overloaded. I mean such items like map, guide and news aren't very important and maybe  better to put them into submenu.
2. It's wierd that ATC knob doesn't present on Deluxe panel and you, as a "deluxe-user", need to load it over general X-Plane menu.
3. Don't feel comfortable with transparent Flight plan and Settings panels. And is there a way to add an opportunity to move over the cells using TAB button?
4. I use X-Enviro and noticed that information represented on ATIS tab doesn't align (not always, but often) with x-plane metar. I know X-Enviro suggest ala-SDK and maybe it's possible to teach x-life grabbing x-enviro' data. But that's only my wishes...
5. ATC panel is popping-up once you sent FL plan to ATC. And stay such way (occupying a half of monitor screen) untill you execute departure initial radio check. Thats a little annoying.
6. One more thing about ATC panel. Horizontal-oriented panel seems too big for me. Opportunity to change size and proportions will be great.
7. Readback after Delivery was advising you to contact Ground when ready to push and start seems incorrect. It refers to Ground.
8. I faced with permanent traffic jam at Holding short RW26L in EGKK (I believe it's a bug, but suppose the reason is because Pilot Plus' EGKK  isn't  x-life-ready airport). So I was enforced to switch off and restart x-life traffic. Then x-life expect that you send flight plan once again and follow delivery, ground... procedures from the beginning. Is it possible just to reload traffic not affecting to ATC?
9. I see you uploaded beta_5, so maybe it's too late to post my damp files from beta_4, but...

Hey JAR, just wanted to report that the bug I was experiencing on that CYQB-CYOW route with DCT segments is now fixed with 2.1r5. Thanks for the hard work keeping this constantly updated!