Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 04/17/2018 in all areas

  1. Dear Jan, you're very welcome, glad I've been helpful. Keep up your excellent work! Best regards, Toto
    1 point
  2. Litjan many thanks for the explanation, I understood everything and very well, i saw that I could not believe it because obviously in the real world it is almost impossible to see (without instrumentation and outside of cockpit) and not in any other aircraft in x-plane or other simulator, sometimes the angle of this correction is very wide, so I thought about my mistake or even to a bug ... thanks again for the explanation. Base
    1 point
  3. Ok everyone, I have worked a bit more with N55E008 and he has been very helpful in identifying and isolation the problem in XP10. Indeed it turns out that in our move to support XP11 I have made a mistake in changing the script for the fuselage drag. This will indeed result in a drag in XP10 that is too high. This error is most prevalent at higher speeds (of course), so you will notice mostly during speeds in excess of 250 kts (climb and descent). Cruise and lower altitude operations should still be ok, although technically the drag is a bit too high as well, naturally. I have fixed the script, we will run it through some internal testing (I would like to avoid another embarrassment!) and then we will distribute it to those interested (= still on XP10). I expect this to happen very short-term. Thanks for everyone´s patience and especially N55E008´s help! Cheers, Jan
    1 point
  4. We're still waiting on Andrey from XEnviro to return to normal life after what he went through in Russia (The fire with multiple fatalities). He and his family, who were there, are safe, but it's shaken him up pretty badly. So, we're not rushing him, and just letting him get settled and get back to us when he's ready.
    1 point
  5. Hi, I have run this performance test on X-Plane 11 (I don´t even have XP10 installed anymore), but I don´t think anything should have changed with regard to the performance. I have used my official flight planning data for the 737-300 I used to fly. These are the test parameters: Airport at sea level Temperature ISA +10 (25C). Brake release weight 58.000kgs. No wind. Climb schedule: V2+15 to 1500 feet. Then 250kts to 10.000 feet. Then 290kts until Mach is 0.74. Then 0.74. Full climb power. Watch for the IAS/MACH changeover, if you are on FL CHG it will automatically change from 290 to 0.71 at ca. 26.000 feet. That is too early, you need to revert manually to IAS and switch over when the speed reaches M.74 (c/o button). Here are the values I get (first the flight test values with IXEG 1.21, then the values from the book): Altitude Distance(IXEG) Distance (Real aircraft) Time (IXEG) Time (Real aircraft) 6.000 11.2 10 3:25 3 10.000 18.2 17 4:54 5 14.000 29.8 29 6:59 7 20.000 48.3 47 9:59 10 24.000 64.9 65 12:29 12 28.000 86.4 89 15:33 16 31.000 102.3 104 17:46 18 33.000 117.0 125 19:50 20 Climb rate just before reaching 33.000 feet was 800 feet per minute. Cheers, Jan
    1 point
  6. The current version of the Saab (up to and including 1.5.1) uses a custom sound engine, which is not capable of playing custom sounds during replay. This will be changed in v2.0.
    1 point
  7. Already done! Will see what xEnviro team say. I'm still hoping that you guys can solve problem in cooperation... without noding to each other.
    1 point
×
×
  • Create New...