Jump to content

LRW

Members
  • Posts

    150
  • Joined

  • Last visited

  • Donations

    0.00 USD 

Reputation

42 Neutral

Profile Information

  • Gender
    Male
  • Location
    Plymouth, MN

Flight Sim Profile

  • Commercial Member
    No
  • Online Flight Organization Membership
    Other
  • Virtual Airlines
    No

About Me

  • About Me
    1st real flight was in a Ford Trimotor in the early '60's. A $5 ride that my uncle paid for. I was hooked.

Recent Profile Visitors

1,670 profile views
  1. LRW

    Exit 1L Data

    [update to what I wrote below. I tested this at gate F7 at KATL. I went back in a tried gate A6 and got the "door too high" warning. I'll have to do more testing to see if that's because of different configs (or models) for different gates.] With Imagine Sim's KATL now supporting SODE, I found this thread once I realized that the 777 didn't work with SODE as-is. Using some of the examples and tips from this thread, I played around with the parameters and ended up with this for the 200LR and the 300ER %appdata%\12bPilot\SODE\AircraftParameters.ini [b77L] 1L = 2.0, 0.0, 10.0, 3.4, 3.7 2L = 2.0, 0.0, 0.0, 3.8, 3.8 [b77W] 1L = 2.0, 0.0, 10.0, 3.4, 3.7 2L = 2.0, 0.0, 0.0, 3.8, 3.8 <P3D>\SimObjects\Airplanes\PMDG777-200LR\aircraft.cfg [exits] number_of_exits = 5 exit.0 = 0.4, 35.0, -9.8, 6.1, 0 //Door 2L exit.1 = 0.4, 67.0, -8.9, 6.1, 0 //Door 1L exit.2 = 0.4, 49.639, 10.121, -3.736, 1 //Fwd Cargo exit.3 = 0.4, -46.387, 10.121, -3.736, 1 //Aft Cargo exit.4 = 0.4, -61.272, 5.341, 2.906, 1 //Bulk Cargo <P3D>\SimObjects\Airplanes\PMDG777-300ER\aircraft.cfg [exits] number_of_exits = 5 exit.0 = 0.4, 51.0, -9.8, 6.1, 0 //Door 2L exit.1 = 0.4, 84.0, -8.7, 6.1, 0 //Door 1L exit.2 = 0.4, 65.954, 10.121, -3.736, 1 //Fwd Cargo exit.3 = 0.4, -62.184, 10.121, -3.736, 1 //Aft Cargo exit.4 = 0.4, -77.069, 5.341, 2.906, 1 //Bulk Cargo SODE prompts for L1 or L2 when connecting, the jetway and hood line up nicely, and Ctrl-J still connects to L2 at non-SODE airports (as Xander showed).
  2. Yes, FSUIPC can handle that as long as you assign both the rudder axis and the steering axis to "direct to FSUIPC calibration". Check the "FSUIPC4 for Advanced Users" pdf for the details.
  3. Loops like that do occur from time to time in SIDs. The FMC doesn't know that the SID says to make a right turn to intercept R126 LON. It only knows that it needs to intercept R126 LON from the previous waypoint and it computes what it thinks is the most efficient way to do that. The pilot flying does know that a right turn is required, having briefed the SID, and as that portion is being hand-flown, will fly the correct path. I've seen the FMC recalculate the correct path once airborne.
  4. I assigned an axis to "Steering Set" in FSUIPC.
  5. I use Pete Dowson's VAS Monitor with WideFS on a separate PC. It shows free VAS and current FPS. It's in the library here.
  6. I spend 99% of my flight time in the PMDG 737 NGX and 777. I've used a Saitek yoke+TQ plus a 2nd TQ for three years. They've held up well and, obviously, can be configured for a variety of aircraft, but I wanted something more immersive (I'm always aware that I'm moving little plastic sticks on the Saiteks). I seriously considered the GoFlight TQ6 as a compromise solution. Higher quality than Saitek, not fully realistic but configurable. I ended up buying the JetMax 737TQ for the most realistic TQ that I could afford. I've been using them for a couple of weeks and I'm very satisfied. The throttles are smooth as silk and its great to have detents for the flaps and speed brake. Peter (and everyone) at FDS have quickly responded to my few questions. I'm still using one of the Saitek TQs on my left side for the tiller. Of course, now I'm on the list to get MFG Crosswind rudder pedals and I'm looking at replacing my yoke. Full cockpit, here I come.
  7. Yes, I have. Both the FSX base 800-900 and the 600-700 expansion.
  8. Just use the link on your previous order; it should download the current build. I always rename (SaveAs) the zip file when I download it so that I don't overwrite the previous file (this build is 6436).
  9. In my first flight, which was at MTOW, I definitely noticed differences between the -200LR and -300ER. It took more power to break away for taxiing. V2 was 183, which is 15-20 knots higher than any -200LR V2 I've used. It took more effort on my part to get the nose down at acceleration height and get my speed up, probably because I was used to the quick acceleration of the -200LR. The clean speed was around 265 and it climbed at 1200fpm to the initial FL280. When I landed 15 hours later, I actually found it easier to land than the -200LR. Maybe it was beginner's luck. And I haven't tried the -200LR with SP1 yet, so some of the difference might be attributable to the changes to the FBW model. The new datalink feature is really cool. I didn't get descent winds on my first attempt (INVALID FORECAST UPLINK) because I missed a step in ASN. But, after a quick reread of that section of the 777 Intro doc, I performed the missing step and all was well. There were no CBs enroute, so I didn't get to see the integrated WX radar in action. For datalink functions, I don't know if there's a list floating around of which airlines use it for flight plans and/or winds. In the JustPlanes videos for Air Canada's 777's, they entered the flight plans by hand (and I don't recall how they entered the winds). Overall, for me, adding the -300ER is a much bigger change than adding the 737-6/700 was for the NGX. I think it was a bargain at $29.99.
  10. 113MB. SP1 is 109MB
  11. LRW

    Your First 300ER Flight

    Virgin Australia KLAX-YMML 10 January 2012 ~11:30pm YMML-KLAX 31 January 2012 ~10:00am (My only flights on a 777)
  12. As someone who's about to become a grandfather for the first time, I'll try to make a couple of grandfatherly observations: If I were a developer/publisher who saw a release date (even a vague one) posted on a web site when I explicitly tell everyone that we don't post release dates, I would not be happy. That date would be taken as gospel by many people and would only add to the chorus of the impatient (and some would even later claim that we had promised it by that date). As a consumer I find the main page of ADX a useful source of information on products that have just been released and that are under development (with preview screen shots). They are mostly things I already know about but I occasionally find something new. I've purchased at least one product that I did not know about because I first saw it on ADX. I don't look at the Billboard with projected dates because I don't really care when something is going to come out. I can't control it, so why worry about it. Apparently, alot of alliteration is always allowable (at least by admins).
  13. LRW

    Saitek Hardware

    I have my Fuel Controls mapped in FSUIPC like this: Left Run = ctl+shft+F2 Left Cutoff = ctl+shft+F1 Right Run = ctl+shft+F4 Right Cutoff = ctl+shft+F3 How do you have your reverse buttons mapped. I don't have those working on my Saitek yet (but I haven't spent much time investigating either)
  14. For the non-US readers that may not be aware, this weekend is one of our major 3-day weekend holidays (Labor Day). It's the last holiday before winter and most people try to spend it relaxing with their families. Many people leave town if they are fortunate enough to have a getaway cabin on a lake somewhere. (and we don't get to take the month of August off like some people) I wish the PMDG crew would take the full 3 days off and hit it again on Tuesday, but I suspect that at least some (and probably most) of them will continue to work and test through the holiday.
  15. I am envious of companies that can refine a product until they feel it is ready for release. In the IT department of the large telecom where I work we have four releases each year at specified dates (we already know our release schedule for 2014). We release our software come Hell or high water on those dates. My group has an excellent defect rate in the company of 0.8 per 100 hours of development. But that means that, in an 8000 hour development cycle, we deliver 64 defects in each release (256 per year). And even for things that are not defects, we have to release code that we wish we could spend more time tuning and improving. If the "now, now" people had any appreciation of the high quality of your (and many other company's) software they would fall on their knees and thank you for waiting until you had all of your show-stoppers resolved and the product met your standards for release.
×
×
  • Create New...