Jump to content

Chrjs

Members
  • Content Count

    490
  • Donations

    $0.00 
  • Joined

  • Last visited

Posts posted by Chrjs


  1. Even though it is not mandatory i would recommend that you update your airac in a reasonable time frame (i do it about every 3 months). It is just not very nice for both the pilot and atc if you have to respond to many sid/star/trans/direct calls with 'unable/not in my fmc'. The navdata providers have special deals for a limited amount of cycles per year for the cost of a cheap addon - very much worth the investment!


  2. 1. Because of that: http://en.wikipedia.org/wiki/Density_of_air, and therefore the measured speed up  there (the actual air pushed through a small tube) is not the actual speed but only the IAS - Indicated Air Speed (TAS - True Airspeed and GS - Groundspeed are calculations out of numerous factors).

     

    2. Has nothing to do with resolution. when you set eg 80 thedistance from your airplane symbol to the top is 80nm, half of it (so half way down your ND or better to say the left inboard Display Unit DU) is 40nm.

     

    3. you have to sign your post with your full name in this forum.


  3. To enter 6000' or above, type /6000A and put it into the desired waypoint. 6000' or below is "6000B". The speed restriction is similar. You can enter "220" (means exactly 220 knots), 220B, or 220A.

    Are you sure we are talking about the same aircraft? This is neither an Airbus nor Boeing. There is no AT so no use in entering speeds in the FMC...


  4. @

    Chrjs

     

    I will give it a try- the turn from TEB to the ILS 22L in Newark KEWR might be a good place to try

    Thanks. I noticed this problem less with ILS-approaches, however with "pure" RNAV Approaches flown in NAV/VNAV. For example the following GPS Approach into PAJN (I know, no applicable for planes of category C/D in real life) - coming from the IAF Nimle the plane turned way too early on final approach and somewhere got lost on a parallel course south of the original path.

    http://skyvector.com/files/tpp/1313/pdf/01191RV8.PDF

    Looking forward to your obeservations!


  5. I've done a couple practice approaches to PHNL ILS 08L, with my intercept speed being at the fastest 180kt.  I do find that the aircraft "smart turns" before intercepting the "pink line" which is normal. I'm blue needles at the time (ILS displayed), and when the aircraft recognizes it turned a bit too early (usually due to wind pushing it away from the LOC), it maintains a bit of a track towards the localizer. Within a few miles it has corrected back to on course. 

     

    This is pretty much how the real aircraft behaves (yes! I know!). The autopilot is not the greatest at intercepting the final at speeds around 180kts and above. It will do it, but it will need some time to correct. 

     

    Regarding your issue- what speed are you flying to intercept final? and does it never correct back on course? I know it's a pain, but would you be able to post a few screen shots when this is happening? A few V-key presses might make me understand what is happening.

     

    -B

     

    Hi Brendan,

    try to fly a RNAV Approach with a turn to final and you will see the issue. It is less noticeable in LOC-mode.

    Regards, Chris


  6. There is at least one tutorial which covers this in great detail. (But to cut a long story short, 185kts to 10000, 210 up to cruise [you might want to reduce gradually from around 18000 upwards], in descent 270 to 10, then 240.)


  7. I think there are really two sides of the same coin.

    First, being a graphic designer myself, i know that every developer tries to improve his work, every following project has to be better than the previous one. That's just normal and also needed for progress.

    But then there is the other side: the customer. Just have a look at all those preview forums: Can we have this, this is a must, i want, we need, is has to have..... The quality of payware scenery has significantly improved over the last few years, but costumers still want more. Developers, that were state-of-the-art a few years ago but didn't keep up the pace of developers like FB, FSDT, FTX are today often criticised.

    This seems to be a natural development, however problematic, because of the hard limit of FSX. Yes DX10 and maybe DX11 (P3D) can somehow push the boundaries a bit, but until FSX gets rid of the 32bit apllication-limit this line will be reached at some point.

    So, who is to blame? the developers look at their product isolated and say it is fine - and they are rigth. if you have a vanilla FSX and just use this one addon, you are going to be fine - but what percentage of simmers does that?

    Both developers AND costumer have to accept the limits, the fact that FSX/Flight Simulation in general has always been and will always be a a compromise. Formerly, FPS was the main concern, today, it seems as the most important problem to take into consideration when developing is VAS-load.

     

    However, i see another negative effect of the improving quality - parallel to the more detailed products, the cost of theses products has risen sharply as well. Most of this price increase is certainly due to the increased  work load and effort, therefore justified. But especially young simmers that just dip into this new hobby are certainly scared off by the high costs. Flight Simulation is limiting its own basis and future.


  8. I'll check this out when i get home from my japan trip- it could be when the FMS "smart turns" it affects the VNAV path calculation. 

    This is the same issue i have. I've just the topic in the official forum:

    http://majesticsoftware.com/mjc8q400/support.html

    ("2 issues i hope to be improved in the Pro Version")

     

    Btw, Brendan, i just noticed that you live in EDTF - me too, so if you want you can just come over and i show you the "issue" live.... :lol:


  9. Hi, long time since i started this topic. I had quite a longish discussion about it with the support and, unfortunately, we couldn't solve the problem. It's no problem for me anymore since i moved on to the 777 and there is absolutelly no braking problem with it....

     

    Thanks for your answers.


  10. "Our" ( :P ) 777 uses the GE90-110B engines.

     

    OT: There is an performance tool coming from Aurasim. It was scheduled for release in october, but due to team commitments it's probably going to be november.

     

    Allright, you got me there. But still, the difference should be pretty significant - both weight and performance-wise.

×
×
  • Create New...