[ Closed ] X-Life ver 4 for X-Plane 11 (Page 3 of 24)

Want to fly from Tampere (EFTP) to Helsinki-Vantaa airport (EFHK). Enter the alternate airport, and wwseti EFHK does not. Enter English letters, "Shift" do not use.

Hmm.. I dont know exactly is this possible without turn Off traffic or not. But I will look at this, thanks!

Need enter small english letters, like abcdefg. Is this is possible for your keyboard?

Yes, i know, but _this_ much? The latest version without VR is not like this. At _all_.
Even if i start xlife on a incompatible airport, where it add no airplanes, the framerate plummits. This can not be correct?

Btw: Did you even watch my video? I mean, i just open the xlife window, without even starting it, and the frames die.
If I press start it goes down to 2 FPS.

My specs are: Intel Core i7 @ 3.70GHz, 16 GB RAM, NVIDIA GeForce GTX 1080 Ti, Oculus Rift.
This should run just the Window of xlife4 well in VR. But it does not :-(

This drop is not normal. But nobody can help you here. Skype is exist for direct help j.a.romanov

Okey :-) But just before I nag you on skype. Here is my summary:
At airport, big or small, compatible or not, I open the Xlife4 window and frames goes from 45FPS (45 due to Asynchronous Spacewarp) to 23FPS.
I close the Xlife window, FPS goes up to 45, but VR is stuttering like Xlife window is not closed properly.
I then switch from VR to 2D, framerate goes to 60 FPS and Xlife works perfect (but 2D suxs a** after playing in VR, so will never ever fly in 2D).

Any suggestions to anything I can try before contacting you on Skype?

Can anyone else here confirm that Xlife4 work fine for them in VR?

Dear JAR,

I have following issue/ effect with latest X-Life version 4 in XPlane 4k resolution and XPLane user interface sice is set to 150% in graphic settings menu (running Windows 10):

Menu icons from A320 or X-Life radar are doubled

Same effect with latest version of GHD

Effects not occour with settings of 100 % user interface sice in XP

Would be nice when it works with 150 %, because 100 % XP nenu size in 4k is to small. (Ic checked my glasses and it is OK  )
I also attached log, but I do not think there are information for issue this topic.

Best wishes

Dear JAR,

after several flights with Ver. 4, I want to report that generated traffic works randomly for me. Means that sometimes the airport on gates and stands are filled with XLife aircraft, but no movement on ground or sky. Other case is that traffic flows on departure airport, but at arrival is no traffic movement, but XL aircrafts parking at gates, as well. I can figure on radar that there is not realy much movement during flight. Latest version 3 sky was busy. I feel so lonly...

Best wishes

Iam new in VR thats why thanks so much for porting this Addon to VR.

PC spec: I7 4790K
             GTX 1080
             16GB DDR 2400mhz
             X-Plane on SSD

So without X-Life my Ram is going to 9Gb (X-Plane minimized)
With Xlife (and bluebell Library) its going to 15,5 of 16 (X-Plane minimized so in real its more used)

That causes extremly stuttering and at the and a CTD without any message. Idont know what I can do. I have the 3JFPS script for more fps and no HD Mesh or Photos. So are 16GB Ram not enough actually for Xlife and VR? Using a Samsung Odyseey.

I'm having many issues with V4, previous version worked well.

1) The new menu is very large and gets in the way of your instruments.  After takeoff, regardless of if you have filed a flight plan or not, this menu always pops up, covering the complete cockpit, or outside view.  This menu should stay hidden unless the user commands it open!   The menu in the previous version was much small and more transparent.

2) Once the menu is open, i can find no way to close it!  Pressing the red dot in the corner does nothing??

3) I have the deluxe version, but see no options for the deluxe menu which was very convenient

4) To solve most of the issue above, keep the menu closed unless the user asks for it to open, either view a small menu like before, or, a very good solution would be a key press which toggles the menu open and closed, this would be perfect, and could be mapped to a joystick button.  Currently I use the keyboard to do the commands, but there seems to be no keyboard command for menu open close.

5) The problem of departing aircraft taking off to fast is still there, they seem to go 400kts immediately after takeoff so you always have TA/RA warnings after takeoff as all following aircraft fly past you!  It would be good if they had a 200kt limit to 2000ft agl then 250kt to 10'000ft, that would solve the issue completely.

6) A suggestion, I fly 50% with flight plan, 50% withouth.  It would be really good if you could have aircraft at the arrival airport, even without a flight plan.  One way I do it, is turn of X-life in cruise, then about 10nm from the arrival airport, turn it back on, and traffic is generated at the airport (usually).  Would it be possible for traffic to be auto generated at airports within say 20nm and when your aircraft is under 5000ft?

7)I seem to often have a bug where the runway is use is opposite to the wind direction, not always, but quite often.  Is this a known bug?  For instance, ENBR, Bergen, wind 300 at 10 kts, RW in use 17?

8) Lastly, it would be nice if you chose not to file a flight plan, that the ATC just ignored you, traffic generation at destination airport would be great in this instance (see point 6).

For now I am back to the previous version, I can post pics or videos of the problems mentioned above.

Hi Jar,

thanks for updateing x-life. I have also some Issues with the new window.

1) If you file a flightplan you can't enter a long callsign like "AIRFRANCE 2 6 PAPA FOXTROT" which is correctly said by the TTS engine. If you enter "AIRFRANCE 2 6 P F" TTS says "two six p f" and not "two six papa foxtrott"

2) If you hit "command say" button while window is hidden it fires up the selected command AND shows the window. It would be nice if the "command say" would only show the window if it was hidden on the first press and than fire the command on a second press. With the old version i was able to handle 95% of the atc action with one button while flying, now you need three "command up" which makes the window visible then "command down" to reselect the last "SAY"-box and then "command say" to actually say it. so 3 clicks on 3 different buttons instead of two clicks with one button.

Thanks in advace

The new v4 cause huge frame rate drop in VR