Jump to content

Litjan

IXEG
  • Posts

    5,604
  • Joined

  • Last visited

  • Days Won

    404

Everything posted by Litjan

  1. Holdings dont work. If they are important to you, I would stay away. Cheers, Jan
  2. This may be a bug with 11.20vr3: https://forums.x-plane.org/index.php?/forums/topic/141415-strange-mouse-glitch/ Cheers, Jan
  3. Here is the problem: Tom created the datarefs, but they need to be hooked up the autopilot logic. Nils is in charge of the autopilot, but he is out of the picture (due to private reasons) until about Summer 2018... Sorry for the tease - lets take the chance to review whats there, and collect what else you may need. I will compile those into a big list and then hit Nils with it when he returns ;-) Sorry, Jan
  4. Most reports of "ILS not working" are due to the user selecting the wrong ILS frequency. Often the navigational database has changed, but the ILS´s in X-Plane don´t change, even if you install Navigraph or Aerosoft data. Another batch of reports are due to "shut down tailwind ILS" option selected. The rest is due to being out of range. The ILS receivers in the IXEG work exactly as the ILS receivers in the default planes - check on the map (M) to see the correct frequency. Cheers, Jan
  5. hi Tim, havent heard of that one before - but we had some reports of users that can´t click buttons on the MCDUs after using the IXEG built-in view settings... could that be related to your issue? Cheers, Jan Edit: Also try upgrading to 11.20vr3, they fixed some problems with the mouse becoming unresponsive if the VR mouspointer is activated.
  6. Good morning, 1.) Yes, we have some code interference - this will be fixed with next update. 2.) I see this as well and we will try to fix it. Two ways to avoid it: A.) Don´t click "resume last flight", instead choose "new flight" (should be same parameters). B.) IF you get the APU not running, flip the switch to START, wait until APU started and then connect both APU generator switches. Cheers, Jan
  7. Yes, they are. But I would hold on upgrading until 11.20vr3 is rolled out (any second, now), as that one fixes a few showstoppers (for some people) of vr2... Cheers, Jan
  8. Hi Jo va Bra, to tell you the truth, I don´t remember how this worked on the 737 classic . It may have been different to more modern Boeing aircraft, or it may have been the same and we portray if wrong. I will try to find out and maybe we can adjust it accordingly if warranted. Thanks for the report, Jan
  9. Lots of info about your issue in this thread: Cheers, Jan
  10. Thats awesome! Cheers, Jan
  11. Same as before - 25% linearity, 0% artificial stability. Jan
  12. Working on a fix for that as we speak (type) - just hold on for a little bit longer. Jan
  13. I would say hold off until I tell you which sounds we specifically need. No point in doing all this work and then us not really needing it. Cheers, Jan
  14. No, I can not confirm this. The 1.21 update is suitable for both XP10 and XP11.1x+ . The installer contains different versions of the aircraft and will install the correct set for your simulator version. Most improvements are for both XP10 and XP11 users, but some (like the adjustment for flight dynamics or the added cockpit reflections) are only valid for XP11. So both groups of users benefit from 1.21. Cheers, Jan
  15. Yes, I can confirm your observation. Weird. I will investigate and see if we can fix this. I remember we had some problems with that before, its an initialization problem, which is never quite easy in X-Plane... Cheers, Jan Edit: Workaround for now is to start the APU really quick (or enable the ground-power)...
  16. I just tried and it works fine, there. Watch for the mouse to become a little hand when over the switch, then grab and pull to left or right. Nothing has changed wrt the auto-brake... Cheers, Jan
  17. Ben will provide a new version of gizmo soon that is curing a bug and also provides a checkbox so you can select if you want the old style (higher fps but some spikes) or the new style (lower fps but more smooth). You may want to experiment with that when its out. Cheers, Jan
  18. Hi Tchou, 46.022 kts, eh? That must be some derelict testing mode that Tom was using, he gets tired of waiting for the plane to arrive... I will try to recreate your scenario and bug, thanks for the report! Cheers, Jan
  19. We will take a look, thanks for the headsup! Cheers, Jan
  20. Hi Max, yeah, thanks for the kind offer - we are looking at converting the sounds to FMOD in the future and will probably have the need to get some sounds again or some new ones I missed back then! Cheers, Jan
  21. You can check the remaining alignment time if you set the switch to STS (time in minutes) Jan
  22. That is certainly an option. Jan
  23. Thanks a lot and those may come in handy. For what it is worth, I recorded the sounds we use in a real 737 with a high-level stereo sound recorder Cheers, Jan
  24. I am sure you have waited long enough for the IRS to align? It takes about 13 minutes (like in the real plane)... Nothing was changed with regard to the IRS code between 1.2 and 1.21 Jan
  25. No, I can not confirm that behaviour - on my side the APU is running fine. Please check if something is interfering, like maybe you have no fuel? Cheers, Jan
×
×
  • Create New...