Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 06/08/2020 in all areas

  1. Great job IXEG-TAEM ,flap setting is now so much easier to perform and all the other good new improvements, many thanks for the hard work!
    2 points
  2. Also....those who have the Gizmo Error when entering a PBD waypoint....FWIW, that message results when entering a PBD and the reference waypoint isn't in the Database for whatever reason. I have since fixed that for the next patch. Being as we're now dedicating development time to the FMS again, we will be endeavoring to organize our error handling much more gracefully. -tkyler
    2 points
  3. Works perfectly! Thank you all, guys!
    2 points
  4. Definitely on the short list. I'm working on the remaining user waypoint code even now, to include the fix page. -TomK
    2 points
  5. I presume there is a confusion here? IXEG_user_prefs.txt is the file updated/modified by IXEG to incorporate new features added B733_prefs.txt is the xplane quick_look feature (numpadkeys). Make a copy of this and place it back after an update hope this helps
    2 points
  6. Fantastic update guys. This plane has become EXTREMELY good, thanks so much for your support. And it's so framefriendly, it's incredible! It's so great to have guys like you with deep knowledge and high goals, after having so much other addons of low quality. So THANKS again to the whole team for bringing this high quality addon to the XP-world
    1 point
  7. So I have recreated it....and will take a stab at it. This one rears its ugly head from time to time and I'd love to get it fixed (as would everyone else I'm sure!) -tkyler
    1 point
  8. Thats strange Jan, but my work around this problem was to enter rwy and SID first then i was able to enter the route. But that was intresting, i will have a look at that and also look at what those other two problems are on my end. Thanks for your reply!
    1 point
  9. Yes, VNAV descent is definitely still wonky....have had to use VS to get to/stay on glide. I do hope this will be fixed when the FMC is updated. Great plane overall though! Thanks for your hard work on it, Dev Team! Jim
    1 point
  10. I haven't been able to reproduce it yet myself, but I'll keep trying. P/GVA is, I believe, the Delta Virtual Airlines ACARS program. It's the only thing I have running that would be pulling position reports as far as I know.
    1 point
  11. I don't know what P/GVA is, but that could have something to do with it...log file definitely shows it doing a lot regularly and it does precede our issue. All our GUI interface code is event driven and uses the same function to process clicks, only receiving differing "constants" depending on what is clicked. I have never seen our "widget code" attempt to index a nil value. I too, would be very interested to see if you could reproduce it. I haven't the slightest idea...I tried recreating your pref settings, then went to town clicking everything I could to no avail. -TomK
    1 point
  12. xplane default & active sky may be using different weather sources. please note WIND DIRECTION AND SPEED on the EHSI will come available when winds are GREATER THAN 6 KNOTS! ACTIVE SKY had 5 knots thus not activating the EHSI report XPLANE DEFAULT had 8 knots by the time you did the test thus SHOWN. I do use ACTIVE SKY nothing wrong, you are on the very limit of SHOWN vs NOT SHOWN on the EHSI. In aviation winds 5 knots and below are considered calm and will be reported as calm when landing by ATC.
    1 point
  13. Thanks for the quick responses guys, will investigate.
    1 point
  14. Only hardware I have is: Honecomb yoke Saitek Rudders Saitek Yoke where roll and pitch are set to None I have the Saitek yoke connected just to make the throttle quadrant to work Waiting for the Honeycomb throttles to be released, little expensive but looks great. Maybe I should set everything in Saitek Yoke to None/do Nothing or try start without it. That is all I have connected
    1 point
  15. 1 point
  16. I actually said that I was not sure if it was working or not in previous version
    1 point
  17. The PMC is the "power management computer "of the engines. It is normally always on. It does stuff like keeping the engines at climb power while it climbs automatically and provides overspeed protection and such. If it is faulty the plane CAN be flown with it off (I did that once), but the switch is in the lower nose compartment. We do not model operation without it. Cheers, Jan
    1 point
  18. It will be next week most likely. We are still working on some final FMOD tweaks to get the sounds just perfect. We will be sending it to the store as soon as we are completely happy with it.
    1 point
  19. That sounds like the aircraft is failing to activate. Can you provide the log.txt file? Also please make sure the Gizmo plugin is installed and running (the X-Aviation installer should install it with the Islander) as that is what activates the aircraft.
    1 point
  20. Hi Enrique, please don´t take this as an excuse that our VNAV is not working very well - it should be and we have full intent on fixing it. But I flew the 737 for 10 years, another 6 years of 747-400 and too many years A320... it is a very rare circumstance that I have descended (or seen my FO/CPT use it) using VNAV. Most of the time your routing is not predetermined (vectors, shortcuts) or you are subject to ATC limitations (early/late descent, advised rates of descent). So for me (and many of my fellow pilots) VNAV is a gadget that serves very little practical purpose. I think VNAV is so important to many flight-simulator pilots because they lack the ability to make accurate descent calculations in their head and they also think that it is "cool" to watch the plane glide down all by itself (and then autoland!). I think that is about as cool as using a Tesla´s autopilot when playing a car racing game . Oh and yes - we do eventually plan on making a cargo variant for the 737 (I see the pattern!) Cheers, Jan
    1 point
×
×
  • Create New...