Jump to content

Litjan

IXEG
  • Posts

    5,718
  • Joined

  • Last visited

  • Days Won

    424

Everything posted by Litjan

  1. You are right - this was a last-ditch effort to get this into the patch and there has been some confusion about what the right behaviour of that page should be. For now enjoy the fact that the TAKEOFF page will always show the correct trim setting - a luxury that the real pilots don´t have . Jan
  2. Thanks for reporting back and happy you got it working! Jan
  3. Roger, thanks! Jan
  4. The real elevators are not connected to the fuselage, either - except in two connections - the elevator needs to be moveable as a whole for trimming. Jan
  5. Thanks for the report!
  6. Never mind, for me it works ok on both metric and imperial... We will have to search further. Jan
  7. Well, if you look at the placard over the window, you will see that indeed quite a bit of weight-change is needed to see 1kt decrease... so I guess we can say that IF the GW changes for you on the APPROACH page, the speeds will also change - one less worry. Now we just need to find out why the GW changes for some people, but not for others... are you guys on Imperial or on Metric? Jan
  8. Now THIS I could see - I am not sure if the real page will show the speeds updating while it is open, well, it probably does. So we will have to move these to a more frequent interval, too. The original problem was that the GW didn´t update, even if you kept re-opening the APPROACH page. Just to make sure, do the V-speeds update if you keep "refreshing" the APPROACH page? Thanks, Jan
  9. Ok, thanks for the feeback... we will look into this to see if there could be any lingering issue. We (like most users, appearantly) are seeing the GW change appropriately. Maybe you can help us narrow it down - fill out the whole PERF page, fly with a route activated, use Imperial, use KGs, try different startup situations, anything to get that GW going down ;-) Thanks, Jan
  10. Did you guys reboot X-Plane after the patch? It shouldnt be necessary, but just to make sure... Jan
  11. Thanks for following up and reporting! This issue didnt make it into 1.0.3 but is already in our log... will bump it up due to the crash! Jan
  12. Hi Bernt, I will try to replicate this - stay tuned! Jan
  13. Thanks for the report - will verify! Jan
  14. Try to disable "show custom datarefs in replay" in the PREFERENCES menu. This will help with the crashing, but you cant see the spoilers and reversers in replay anymore... Jan
  15. Hi everyone, please help us scrutinize this - with every patch - despite careful testing - there is the chance that we introduce new bugs or don´t quite get the old ones (anyone said "spoilers"?? ). Would love to hear your feedback on this and keep the reports on bugs (in the support forum) coming! Highest priority of course are still the gizmo-softcrashes - though I do hope that we have reigned these in further signifcantly with this patch. Happy landings, Jan
  16. Hi guys, I think the issue you are seeing reported in this thread may actually be a bug. When turning directly to a new waypoint, the plane should just make a simple turn, not re-intercept the line between the current position and the new waypoint. We will look at that during the tuning phase... Jan
  17. Thanks gentlemen, nothing for me to add here. And thanks again for the report, Tom - especially the .84 issue should be fixed in 1.0.3 - the autopilot will now retain the current commanded speed when switching from VNAV to another pitch mode. Jan
  18. You are not alone. There are probably quite a few 737 pilots out there that don´t really understand the system and why the airplane manufacturer introduced it. Jan
  19. Could be that we mixed that up - thanks for the heads-up! Jan
  20. Excellent, Thanks! Jan
  21. Hi Bernt, be advised that "looking back" at the ground services GUI while fueling will immediately stop the fueling process - is this what is happening to you? Jan
  22. Very interesting! Can you do a DEBUG.txt output after you put in the route? That way we can analyze a lot easier! Thanks, Jan
  23. Known, not easy to fix! Thanks for the report (actually VERY surprised that we haven´t heard a lot of complaints about this one already!) Jan
×
×
  • Create New...