[ Closed ] X-Life ver 1.0 (rc1, r1, ++) (Page 16 of 28)

Just a suggestion here. I read about program crashes and other problems and of course, these things do happen. As an avid user of X-Life I can understand people becoming upset when there is a crash, especially those that are new to using it. Yes we are asked to post our logs here when there are problems, so then the proper information can be gathered by the JAR team. That's excellent it's great that this can be done! My suggestion is to implement a trouble shooting page here on this forum so that users can look up possible causes of problems based on information gathered by JAR so far from text logs and different problems. The team could post some quick solutions to common CTDS (crashes) and users can post how they had and fixed certain problems within X-Life. Just the other day I told someone on this forum to update to the latest 4b version. His problem was easily solved and he has traffic moving at his new airport. Result a happy X-Life user. My point is that if there is a page on the forum for trouble shooting problems and crashes within X-Life, the process of solving them might be smoother and happier.

Test flight with the newest version v.1.15b

X-Plane/X-life stocked and I had to "Force Quite"

This happened after I finished programming my Flight Plan and ATC wind opened.
I clicked on ATIS and after on DELIVERY for radio check and then it freeze...
(usually until now I got X-Plane ATC text and Voice parallel to X-Life ATC text, maybe a conflict between the two?)

stenu wrote:

Hello,

One question: Why X-Life does not utilize the 1204 parameter of apt.dat of ATC taxi routes indicating hold short points, but instead requires hold short point to be one line segment away from the runway? It makes possible to put hold short points further away from runway, which is often necessary. It can also limit the hold short for arrivals or departures only if required.

For example:
1202 41 40 twoway taxiway A
1204 departure 03,21
1204 arrival 03,21

Means that the line segment between points 41&40 denotes a "restricted" area which you can't enter before the tower gives you permission for it (runway 03/21 is free).

-J

I don't understand what is the gain of your purpose?!....

Thinking about what could be one of the next steps of development, I got an idea about making the approach much more exciting and precise.

At the moment situation, flying on approach, I open often the RADAR screen to see if there are some other AI aircrafts on same route to land on same runway. Then I enhance or reduce aircraft speed according to my estimation about distance to the aircraft ahead and time until exiting runway. This is very unprofessional.

Instead it will be efficient to get ATC warning/advice like : traffic ahead xxxx kn at distance xxxx nm, so the pilot can stay at safe distance during landing.

Only sometimes and in the last minutes before landing we can see on PFD screen the diamond of the aircraft ahead and sometimes in the horizon its  position in the sky with only its FL indication. I would like to discuss this idea to see if there are some regulation that we can implement in a simple manner into ATC, so we can handle our approach according to the incoming information. This can avoid us from GA, saving time/fuel costs and make out landing under more near real....

Good day,

Now, I have only had one maybe two GA in the whole time I have tested the X-Life plugin and I started from the beginning of the process 18 months ago when JAR ask me to start testing on the MAC Version X-Life it was also the first version that came out before, PC so, 'PIC' and I were two of the first public Beta testers I do believe.
You are the only one that keeps asking for the developer to make big changes to his plugin so my question is why,
is it so, you can talk about it on your blog and tell people you helped JAR and the X-Life well It's just wrong. If you want to talk about the XL and how all the Beta testers have done a good job making the XL good and how it's improving with the addition of the Bluebell aircraft then thats something to blog about but include everyone not just what you did! This is not about you this is a team effort and this is why I have my attitude you must include everyone that is working on the project if you are going to blog about it on your own website.
captbullett 

Nevertheless, the spacing is such now if you have the plugin set-up right your spacing will be right and you won't need to fly a GA (Go-A-Round. 

Ps, the last GA I did I had no issues with the GA I was able to go to FL50 and then use the "blue line" in the flight plan on the JAR A320Ne then contact ATC and have them tell me to contact tact Approach when I had the ILS established, and then I was able to land within I would say 15 min of the GA...

(Going now to test the latest X-Life 1.6b version)

Hi All,
Been doing a little testing of the beta.
Flying from EGCC to EGLL at FL190.
I do not know if it is just this flight but the change over on ATC from APP to CTR was at TOC, FL190.
Would it not be better to change from APP to CTR passing FL100 and set QNH to standard 1013.
Also is their any way to set which airlines are used or is it just random.
Tom.

It is wired to see such a lot KLM aircraft in ZBAA , but this is a great plugin. BTW, is the engine reverse animation have not been done now? I find not reverse on A320 landing.

Hello, so I am encountering quite an issue of which I am not sure if it is related to EADT's x737 or X-Life. Anyway I am using X-Life Deluxe and the x737 v5 as my aircraft. While contacting Delivery through the ATC menu of X-Life and requesting clearance I have encountered a problem with setting my altimeter. ATC tells me that I need to set my QNH to 1017.00 while ATIS says I can use inches as well at 30.06(Tried both, closest I can get with HP in the x737 is 1017.02) yet despite that when I request clearance my pilot says the QNH is "1013"(Which is incorrect from what I set it in the plane). Is there a workaround to bypass such as I am unable to use the ATC feature at the current moment?

Thanks.