Jump to content

Litjan

IXEG
 View Profile  See their activity

  • Posts

    5,673

  • Joined

  • Last visited

  • Days Won

    412

 Content Type 

Everything posted by Litjan

  1. Litjan
    To my knowledge there is nothing that would stop us from also updating our XP10 version of the 737 in future updates. We already have a "dual installer" which will work on both versions, and most updates (FMS; etc.) are non-version specific, anyway. Jan
  2. Litjan
    Ben Supnik offered me an "experimental build" to test against this bug, but I declined since I could not reliably reproduce it. So there is a good chance that he had a good idea what caused it and may have just slipped this fix into b6. Keep us informed about your further results, please! Jan
  3. Litjan
    Ah - ok. I have noticed this, too. Sometimes it takes a few minutes for the light-level to register... The whole thing is somewhat of a mystery to us (and the staff at Laminar Research, too). First, the "LIT" texture in the cabin should not cast light on the cockpit in the first place - even if there was no backwall or door to the cockpit at all. It is not a dynamic 3D light...so we have no idea why it does that. Second, no one has any idea why it takes a few minutes for X-Plane to register the new light-level. The good news is that we are planning to add a better 3D cabin with 3D lights in a future update - at that point I hope that these problems will go away. For now my workaround (if you suffer from the time-delay) is to simply leave the Fasten belt switch to ON. Cheers, Jan
  4. Litjan
    can you try without your other plugins, please (fly-with-lua, python,...)? Thanks, Jan
  5. Litjan
    because you dont put it to on - only to AUTO. Try again, please. Jan
  6. Litjan
    The placard speed is the maximum speed for the flap setting - there is a placard near the landing gear handle for that. Obviously you must not fly faster than that, so the Vtgt will be limited to that placard speed - 5. Flap placard for landing flap 30 is 185kts, so the Vtgt for that may never be more than 180kts. Flap placard for landing flap 40 is 158, so the Vtgt for that may never be more than 153kts. Cheers, Jan
  7. Litjan
    Thanks for the heads-up, stolowski! I am in contact with Ben Supnik about this one. But if I could get the video of it happening with the IXEG so I can reliably reproduce it, that would be awesome! Jan
  8. Litjan
    I have tried entering the routing in several different ways - and nothing happened. The only odd thing is that SETAL is a waypoint that is some 3000NM away from Europe, but I didn´t get teleported. I would still place my money on a conflicting add-on, especically Fly-with-lua and Python. If you could remove them (move them to a different folder), launch X-Plane and then try again, that would be helpful! If it still happens, it would be great if you could record a short video of how to recreate the problem, sometimes it is important to get every single keystroke exactly right... Thanks! Jan
  9. Litjan
    Thanks for the replies - we will try to reproduce this and fix it! Jan
  10. Litjan
    Yes, it will be fixed with the next update. As for getting older and forgetting things - welcome to the club! Jan
  11. Litjan
    Hi, Vref never changes with wind. It is 1.3 x stalling speed 1G at the current weight. There is a placard for Vref above the pilot´s windows. You have to add speed increments to Vref to get the Vtgt (Vtarget), wich is the speed you want to fly during your approach. The formula is: Vtgt = Vref + 1/2 steady headwind component + total gust factor. (The minimum increment is 5kts, the maximum 20kts). Example: Landing runway 18, wind is 270/20G30, Vref is 130 kts Vtgt = 130 + 1/2x0 + 10 = 140 You should fly Vtgt until passing the threshhold, then reduce to Vref+total gust factor. Jan
  12. Litjan
    Hi fabiosko, thank you for continuing to troubleshoot this problem! I really have no idea which plugin may cause this - I am still suspecting that you have some key or button set to the function of repositioning your aircraft that may get triggered by a plugin or somehow differently. Go to the control settings for keyboard and find the command "Reset flight to most recent start" - try to clear that command (it is set to ctrl-; by default). To clear it, just click to the right of it. Then try the flight again. Hope this helps! Jan
  13. Litjan
    I think your explanation makes perfect sense - in beta 4 (and before), Austin´s flightmodel changes always happened. In beta 5, they only happen if you re-save the aircraft in planemaker. In your initial post you made no mention of which beta you used when reporting (and you reported at a time when beta 5 was current) - so I assumed you were on beta 5. So - if you are on beta 5 or later, you should be fine. Don´t resave your aircraft in planemaker, though. Jan
  14. Litjan
    This means that you have re-saved your .acf in X-Plane 11.10 beta - which is something we don´t recommend for this same reason. You want to re-install the 1.2 version from scratch, otherwise your plane will stay broken until we get out the next patch. Jan
  15. Litjan
    We are still checking out the new changes that you get by saving the .acf in X-Plane 11.10b5 (and later). It seems that the new downwash model is making the stabilizer more effective - this isn´t wrong, but our model is not tuned for that (yet). So you will get a lot more tail-downforce in regular flight, and will therefore need more "nose-down" trim to compensate. You will find that you run out of "nose down" trim in a lot of situations (during approach, flying faster than ca. 260kts, etc). I recommend NOT saving the .acf in the latest betas. We are flight-testing the changes, and will incorporate appropriate modifications to retain the flight-model that we are so proud of in 11.10, while taking advantage of Austin´s improvements. Cheers, Jan
  16. Litjan
    Hmm, interesting...especially the line in your log.txt where it says: 1:00:25.724 I/FLT: Init dat_p0 type:loc_tak apt:E46 rwy:15 We are taking a look at it, and I may report the bug to Laminar, if we can´t find out why it happens... Thanks for reporting it, Jan
  17. Litjan
    Hi fabiosko, I have never heard of this - it would surprise me if this was brought about by flying our aircraft (not going to rule anything out, though!) I would ask you to try the flight again after deleting your preference file and without any absolutely necessary plugins and custom scenery, then see if it happens again. You may have a key or button assigned to resetting the aircraft by accident, or there is some incompatibility with another plugin or custom scenery. Good luck, Jan
  18. Litjan
    Hi stolowski, I can´t really put out a solid forcast on the timing of the next update. At the least we will have to wait until 11.10 is declared final - there are some flight-model changes that we will need to adjust to, in particular the behaviour near the ground (wing downwash affecting the stabilizer). We will put in as many fixes as we can for this next incremental update, Tom has already fixed some lingering gizmo soft-crashes - and the reflections will be part of it, too. The stuff that everyone is waiting for - better VNAV, a 3D cabin, opening doors, etc. will not be part of this next incremental update, unfortunately. Cheers, Jan
  19. Litjan
    The reflection effect was left out of the last update by accident, sorry! It will be part of the next update. Jan
  20. Litjan
    No.
  21. Litjan
    Hi Denco, I just tried the "737 walz" in 11.10b4 that my real instructor demonstrated during my initial landing training in 96: Approach normally, but don´t arm the spoilers! Add, 1-2% N1 just before touchdown. Now float down the runway, touching down with the left wheel, then the right wheel, then the left... The ground effect will keep you floating without speed loss. You will have to pull quite a bit in X-Plane, but it shows that it there is enough elevator authority. The CG can be adjusted in the "ground services" menu before takeoff, and it will calculate the resultant takeoff trim setting for you. Note that this trim setting will be too much "nose up" after you climb out of ground effect, another sideeffect of Austin´s new downwash model. We will adjust that after 11.10 goes final. Be prepared to trim nose-down after climbing through 20 feet or so... Jan
  22. Litjan
    No, real time. Yes, you have to "pull" more than in XP11.05 during the break, but there is enough authority to do the maneuver unless trim and speed control are bad during the approach. I can´t say that I think the new model that Austin did is an improvement - but I can live with it and we may be able to do some adjustment to it later. If you are not happy with it, by all means let Austin know! File bug reports here: http://dev.x-plane.com/support/bugreport.html Cheers, Jan
  23. Litjan
    Hi Scott, the generic TOGA button works for the IXEG. You have to assign the command "Engage TOGA power." to a button/key of your liking. If nothing happens when you push it, it´s likely that you have not setup the system correct, i.e. the A/T is not armed, TOGA command is not available, etc. There are also many aircraft-specific commands you can bind your buttons to: Go to the button assignment screen, click "EDIT" for the button you want to assign, then type "ixeg" into the search field. Now you will see all specifig "ixeg" commands. Cheers, Jan
  24. Litjan
  25. Litjan
    Yes, I can properly flare this plane (you saw my video) and Austin is considering the ground effect on the stabilizer fixed at this point, and so do I. There is probably something wrong with your joystick settings or the way you set the CG, the airspeed you land at or the something else. I can fly and land the plane just fine and it does not handle much differently in the landing than the real aircraft did for me. Cheers, Jan
×
×
  • Create New...