• Content count

  • Joined

  • Last visited

Community Reputation

245 Excellent


About Bjoern

  • Rank
    Member - 1,000+
  • Birthday 04/24/1986

Flight Sim Profile

  • Commercial Member
  • Online Flight Organization Membership
  • Virtual Airlines

Profile Information

  • Gender
  • Location
  • Interests

About Me

  • About Me
  1. Douglas Driver

    In case you're wondering if the DC-6's damage module works: Yes, it does. Quadruple engine failure after takeoff. I was a bit too optimistic with the 59" MAP near 5000 ft airfield elevation. Should have picked high blowers and 51" as in the reference charts. RIP DC-6, RIP Otto, RIP 19000 lbs of cargo at a pretty good going rate. Just when you thought you had it all nailed down... All that's left is this memorial shot taken just a few hours before:
  2. AI GA Aircraft

    Fair enough. I've converted all of the other models a few years ago. If you can live with a slow turning prop (akin to a slow-scan camera effect) and don't need visibility items like tie-downs, making them FSX native is definitely possible.
  3. AI GA Aircraft

    Not quite sure what the point of this thread is supposed to be, but there's other models from the following authors out there: Klaus Brosemann Andras Neumann Dee Waldron Henry Tomkiewicz Mike Cronin Richard Faith(?) Unless he updated them accordingly, Todd's models usually do not feature LOD models, which may cause quite a bit of a performance hit in some situations. Flight plans can be auto-generated with Markus Brunner's "GA Traffic" (quite an old tool that requires workarounds) or Traffic Database Builder from the SDK (requires some time for setting up, but works flawlessly after that),
  4. You'll want to look or post here:
  5. ...and that's why there are check rides and recurrent training for real pilots.
  6. These controls are hydraulically powered. That should be enough of a hint.
  7. Qualitywings or Captain Sim 757?

    Don't confuse the 757s offered by JustFlight. The FS2004 version is PSS', while the one for FSX is an in-house, freemium development. And I've never gotten that far with the QW version, but its flight dynamics are supposedly better than CaptainSim's.
  8. Qualitywings or Captain Sim 757?

    I can only speak for the QW 757: + Excellent framerates + Lower price than the CS 757 - Not all systems are modeled (or at least not all switches are interactive) - Highly annoying copy protection/licensing system Plus some weird clickspots on some control knobs, but I've created modifications to improve that. Of the CS757, I've heard that it's hard on framerates, expensive and slightly buggy, but otherwise fully featured.
  9. Razbam Metroliner Released

    It's not perfect (high memory consumption due to large textures), but for only $10, there's not much risk involved.
  10. Douglas Driver

    The praise for the screenshots is a bit surprising, considering that I can't see much of them myself (at daylight). Yep, Ernie definitely was/is an influence. As are Serling's airline biographies. Going transatlantic isn't much of an option, considering 10+ hour flying times.
  11. Normally, cylinder head temperatures, spark plug fouling, torque, carburetor icing, vapor lock, superchargers and supertanker sized oil comsumption at speeds that send you right to sleep isn't much to get me excited. But sometimes, you just need a change of pace after reading an airline biography that mostly seems to deal with the formative and exciting years when aeronautical progress moved at the speed of every new exciting flying prop-driven contraption devised, financed and introduced into service. (Yes, books still work as a source for inspiration. Who'd have thought?) Anyway, why not take the evolutionary peak of those aeronautical dinosaurs for a spin and throw some economy into the mix while one's at it? Well, enter the DC-6A. Unlike the swan song airliners of its era with its engines that exhibit equally swan-like touchiness (do not mess with these avians, ever!), you can probably take a sledgehammer to the airframe and its R2800s and still fly around the world - if you take enough oil along, that is. Anyway, the DC-6A/B works in FSX with the usual model-related drawbacks (prop disks vs clouds) and after some more modifications (new, experimental autopilot; automixture gauge; textures converted to .dds files; MI Tool installation), "Douglas Freight"'s DC-6A in vintage American Airlines Cargo colors is ready at Burbank and waiting for its first assignment. The mobile phone buzzes. "Please get 13112 lbs of unspecified cargo to Grand Junction and do not mess up. It's already ready for loading. Bye." Burbank - Grand Junction. Out of the busy L.A. metropolitan area and over a whole lot of mountains. 570 nm. 2+ hours at economy cruise. Well, alright. Actually, the plan was to channel the 50s and go to Tulsa just like AA did back in the day, but apparently dispatch couldn't find suitable airway maps from back then. So GJT it is. No need for a GPS today, since the navigator's seat is occupied by LittleNavMap, a capable android that doesn't talk, won't pull pranks and doesn't consume any beverages, leaving more for me and myself. The right seat is occupied by Otto's brother Otto (name spelled backwards; terribly creative family). Inflatable, flexible, used to be in the weather observation business in the armed forces before hitting it big with his cargo driver job here. A bit shy, but never judges and never complains. Nice wife, too. Flight engineering has to be done by yours truly since I have an engineering degree and the boss is scottish. Since this is a modern company, a loadmaster is not on the payroll. Outsourced. Tough times indeed. Still, the cargo sheet books 600 lbs for the crew, regardless of occupancy. No, I'm not that large. Most of it is oil for the engines and other...things (ssssh!). Anyway, while the ground service personnel loads the cargo and contrab-...other things without violating any center of gravity regulations, I plot the route. Owing to the limited avionics aboard, routing is old fashioned - navaid to navaid. No waypoints or standard approach/departure routes. To stay clear of other airspace, the first fix is the NDB in El Monte that serves as a beacon to Pomona VORTAC (POM) while keeping me away from the San Gabriel mountains, which is not the most unpopular location for involuntary disassembly of man and flying machine. After that, it's a turn northeast toward Daggett VORTAC (DAG), trying my luck to leave as much of the terrain above and below me (this would become a very short-lived career otherwise). Should the plan not work, my contingency is following State Route 210 and then taking a left turn onto Interstate 15 through the valley before slumbering on - just need to make sure not to stop at red lights or for traffic (lack of airspeed is apparently not popular with wings). Singing overrated, stereotypical songs, the next fix is LAS VORTAC. No technical stops. ("Had to inspected the roulette gear and blackjack lines. No more money for fuel. Kidneys already sold. Send help!") After that, it's straight onward toward an apparently well-smelling or tasting VORTAC (MMM) not too far from Lake Mead. Cutting right through Bob Marley Nationa-...erm, Iron, Lion, Zion National Park, is the (air)way to Bryce Willis Canyon VORTAC (BCE). While already pretty well covered by tough terrain, on the leg toward Hanksville VORTAC (HVE), the peaks of the Aquarius Plateu constitute a welcome invitation to turn an engine out situation into a spontaneous invitation to camping and mountaineering trip (provided the apt pilot finds a place to park). Finally, skimming the northern tip of the Canyonlands National Park and roughly keeping alongside the Grand Valley, the last fix is Grand Junction VORTAC (JNC), before it's a quite literal dive into the valley to land at the destination, Grand Junction, Walker (Texas Ranger) airport. Overall, it's a picturesque route over some breathtaking landscapes and with a rich history. Too bad it's already 7:30 p.m. And pitch dark outside. But hey, at least the weatheris supposed to be good all the way! Meanwhile, the outsourced ground handlers have finished loading, the fuel planning is done (8000 something lbs of oil for the engines, 200 gallons of wait, the other way around), the route is ready to be cleared by ATC and I've studied the checklists and reference documents. I may be crazy to practically solo a 100000 lbs aircraft, but I'm not dumb. At least not *that* dumb. The smart notepad app shows that gross weight is well within limits, that take off speeds are reasonable, that CHT and oil temperatures are dangerously low and that the pilot is the best there is (I know!). After a bit of unprepared switch-searching ont he endless panels, I manage to gracefully start the engines - in the wrong order (3-4-1-2? 4-3-2-1? 1-1-4-23?). Doesn't matter, they now produce an average coastal breeze each and convert oil and fuel to flames and blue smoke. ATC assigns runway 08 for departure, which is practical, because it points me right toward El Monte. Has FSX ATC finally done something right? Tune in at five to find out more! Since BUR is a busy airport (Seriously, where do all the aircraft come from?! And where do they go? Does the universe know about them?), mandated interruptions in taxi operations are used for my favourite part of piston aircraft flying - run-up checks. Prop full forward, prop full aft, left magneto, right magneto, no magneto and a 0.0001 drop in RPM...zzzZzzz. ATC wakes me from my well deserved nap. Checks are completed (talk about doing them in your sleep) and awaiting takeoff clearance from the tower. Put the airplane into "Christmas Tree" mode, line up, set take off power, check flaps, CHT and release brakes. 5700 feet to go. In a jet, I'd be a bit worried, but the four R2800s and the rather low weight really make this thing go. Lift off occurs with several hundred feet to spare and besides, there's that drop at the end of the runway that might provide a gentle bump when push comes to shove. Gear goes up, nose goes down for acceleration (at least that's what the book says) and at one point, power is reduced to METO. Or at least what I perceive as METO. It turns out that the end of green arc on the MAP gauge does NOT constitute METO, but at that moment, I don't care. CHT is within limits and I need this thing to climb, climb and climb some more. Flaps go up to 1 to decrease drag and by now, El Monte ADF is picked up and that's where I'll go. Below, the lights of the Los Angeles megalopolis stretch out to infinity and back and I don't want to think about what would happen if I lost a substantial amount of power and...nope, not going to happen. Not on my watch. This is not an Ernie Gann novel. Just look at this...lights EVERYWHERE. I'm still climbing and waiting to intercept the 081 radial to Pomona. The pistons are still giving everything they've got because I really want to make that climb! So much that I forgot about the flaps, which are still at 1. After passing Pomona, I turn onto the 037 radial to Daggett. This will be the moment of truth. All or nothing. Aviator or something with "a". Moment of glory or PILS (problem in left seat). Still hammering the engines, still climbing. A glance to my ten o' clock shows Mount San Antonio's peak staring right back into the cockpit. (Uh, hi.) But on the other hand, I can clearly see the glimmering lights of the settlements in the Mojave ahead, so I figure I am going to be fine. Phew! As I triumphantly soar across the Cucamonga Wilderness and its ~8500 ft peaks, I go into mental overload between wondering why the Mojave is that illuminated, flying the aircraft and finally setting up proper climb power. Crossing 13 or 14000 ft, I put the superchargers into high gear as the checklist tells me to, but since I'm still hand flying, the process throws me off the radial and my flight path starts to resemble a snake after an evening in a liquor container. Deciding I've had enough, I switch on the autopilot and let it do its thing. This frees me up to talk ATC out of clearing me all the way up to FL280, which my flightplan is still filed for. It's best for both sides to decrease it to something more sensible, like 190 or so. Fortunately, ATC doesn't need impassioned pleas or other Oscar-nominee acting skills to approve my request. Arriving at cruising altitude, I show some mercy on the engines and pull back to economy cruise. I've got a tailwind anyway and what is time, after all. Flying at night might be boring, but a clear desert sky offers some interesting vistas, for example in the form of the Great Las vegas Blotch of Light(TM; you heard it here first!) appearing on the horizon and slowly drifting by beneath me. The urge for a technical stop is nonexistant because Vegas could not look better than from up here. The Sperry A12 does its thing, Otto is still silent as a rock and my faithful navigator LittleNavMap tells me the frequency and radial of the next VORTAC to tune in. If I was a stereotypical propliner pilot, I'd go for some coffee, a whistle of "The High and The Mighty" and stories from great piloting adventures from "ye goode olde time" by now, but I'll settle for tea, Guns 'N' Roses and Wikipedia instead. Welcome to the jungle! The only thing that worries me is that MI Tool shows that the cost of this flight starts to outrun its revenue. And it's not the fuel use or crew salary that's the biggest factor, but "other costs". Premium insurance, I guess. Note to self: Fire financial officer (or retweak the settings). Past Vegas, the route across National Park Country is composed of darkness below and the stars above, interspersed by the lights of the odd settlement. I'm comfortably at FL210 by now to improve cruise economy, but considering that airlines used to fly this route at no more than 10000 ft at night at half the speed in any weather... Speaking of weather, somewhere between Mormon Mesa, Bryce Willis and Hanksville, things get mildly cloudy. This could get bumpy, but despite skimming the tops of the taller towers, the ride stays smooth. Not that the cargo would complain, but I just don't know what exactly is stowed back there. Otto handled the paperwork. On the eastern fringes of Zion National Park, I spot snow on the mountain tops. Totally mesmerizing when I saw it, mildly interesting by the time I'm typing this. Worth a mention anyway? You betcha! Around this time, ATC kicked me out of IFR because I was away and failed to respond to a frequency change command. Downgrading to flight following was my only option. Suit yourself, airway-gestapo. I am a mature and self-reliant pilot who don't need no vectors to final! Speaking of vectors, time to descend. Because what goes up, must come down. (Tom Petty was a wise man.) Using the infinite knowledge of the checklists, I bring RPM back up and reduce MAP step by step while starting down, as usual closely monitoring CHT. The road back from the heavens is not rocky, but agonizingly long. No way I can make it down to 7000 ft (~2000 ft AGL) required for an ILS approach. Weather would permit coming in exclusively visual, but as the world's greatest pilot, I'm playing it safe! There's a catch though. LittleNavMap-igator has me coming in from the west, across Grand Junction VORTAC, which sits comfortably on terrain at ~7000 ft. Since the suggested minimum descent altitude is 8500 ft, I do the smart thing and heed that warning, descend to 9000 ft and then try to cover the remaining ~4000 ft during the approach and final phase. After all, controlled flight into terrain and the resulting wreckage only results in interesting paragraphs in Wikipedia articles and hobby archeologist's hiking guides. Fortunately enough, speed management isn't much of an issue in such a giant from times long past (amazingly enough, a 737-600 is just as large as a DC-6). Grand Junction Tower invites me to land on runway 11, which is a bit of a relief since I won't have to fly the offset ILS approach for runway 29. Still, I am way too high to make the descent into the valley on the first shot, so I do a lazy descending circle around JNC. I could have played this way more in style and simply follow Grand Valley while descending, but nah, I'm not feeling particularly cool today. Upon attaining my MDA, I head off into the valley and see if my judgement holds up with my amazing piloting skills. Having crossed the localizer, a turn to the left brings me onto the back course for the approach. By now, I am also well on my way toward my final approach altitude. Near Mack Mesa airfield, I begin a turn onto an westward heading to get a bit of clearance between me and the terrain to the east for the upcoming turn onto final. Throwing the big bird around to the right and onto the localizer, I begin preparations for final. Flaps, cowl flaps, girlie flaps, flapjacks...the usual. Crossing the glideslope, more flaps are applied to the headwind and the gear comes down. Final checks and it's showtime! Expecting a bitter fight of man vs machine to keep the ILS needles where they belong on the instrument (middle, but I'm absolutely not sure about that), I am disappointed to experience that the DC-6 is as tame as a toothless tiger. Too low? Add instantly available power and lift. Too high? Do the opposite. Even the speed is in the ballpark. Come on, there's got to be a challenge! Ask and ye shall receive. After a smooth, but decisive touchdown, I find that challenge in the prop reverse function. A person known for mercilessly appling the "RTFM!"-whip to innocent forum members should have read the readme more thoroughly. Irony can be pretty ironic sometimes (Thanks, Captain Kirk!). Anyway, a bit of "What does that button do?" and application of throttle does provide some overdue prop-based braking - not that it would have been particularly necessary, considering a 10500 ft runway underneath the wheels. Some taxiing, blah-blahing to the ground controller and lots more checklist items later, I'm parked safe and sound at my destination. While the local, outsourced freight handler is being shushed away with a "Yes, yes, do that.", I attend things that really matter - flight performance and virtual MONEY. MI Tool grades my performance with a straight A, giving the company's reputation a nice and much needed boost to obtain better contract or tons more leeway to absorb the contract renegotiation penalty. On the financial side, however, this trip was a clear flop, since "other costs" ate up what little revenue there was. But the plane is still in good condition, the company is only getting started and big contracts with big bucks will soon be no more wishful, drunk fantasy anymore! So there's no reason not to accept these flight results and await the next adventure. Or at least daylight. And some sleep. Because that grog I had before descent is making me ti-...*ZzzzZZ* The end. Fin. Ende. (Maybe) Until next time! (Author's note: I hope the entertainment value was a bit higher than propliner cruise speed.) P.S: I think I'll upgrade to a DC-7 because (air)screw engine reliability! And screw swans! (Please don't.) P.P.S: The approach to Grand Junction.
  12. HP quite often has deals on their laptops. In any case, get something with a GeForce MX150 or GTX960M or equivalent, a SSD and the fastest CPU you can find (3 GHz+). That should do for FSX.
  13. This: gauge10=..\0_DM_1-11_510ED_FSX!APU_PROCESS, 1,1,1,1 gauge11=..\0_DM_1-11_510ED_FSX!510_PROCESSING, 5,5,1,1 //gauge11=..\0_DM_1-11_510ED_FSX!BAC_1-11-510_Systems, 5,5,1,1 gauge20=..\0_DM_1-11_FSX!APU_PROCESS, 1,1,1,1 gauge21=..\0_DM_1-11_FSX!PROCESSING, 5,5,1,1 //gauge21=..\0_DM_1-11_FSX!BAC_1-11_Systems, 5,5,1,1 using 510_PROCESSING.xml, PROCESSING.xml as well as any file that has "APU_" in it from the original FS9 releases and using the [GeneralEngineData] section from the original, unmodified, FS9 aircraft.cfg files are the keys of getting the APU back while retaining the switch sounds, but killing most of my system improvement. No guarantees that it'll work, but it's the only shot you have. This is all I want to do for you. Now please promise me that you will figure this out on your own and not come back with questions. I really don't want to write how-to novels or add a new layer to package version control logistics and support because of a single FS9 user.
  14. Mods for the Feelthere ERJ v2

    I don't own the E-Jets. Maybe I'll go for them when I can get them for as little as I got the ERJs on Steam ($15).
  15. While the Feelthere ERJs are a well rounded package, there is, as usual, some room for improvement. So I've yet again tried to enhance the product value a bit. You will have to own the Feelthere ERJ v2 (regular or Steam release) in order to use this. There is partial FS9 compatibilitiy, albeit untested. FSX mods should also work in the P3D releases, but are untested as well. Features: Replacement of the practically useless approach chart in the VC with the speed limit page from the manual Pop-up displays now use their bezel, improving functionality and making the "no yoke" model superfluous Modified night lighting, doing away with the light splashes and adding a 3D flood light Aircraft Manager that plays along with the FMS and is used for loading and fueling Slightly improved eyepoints and cameras Fix for the annoying fuel pump sound A scientific paper on how to set up shared texture folders for the ERJ Instructions on how to fix the Steam Release of the ERJ as much as possible Pointers to other useful mods Pictures: Download: The latest revision of the modifications is always available here. Read the included documentation and read it carefully!