Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 09/05/2014 in all areas

  1. 4 points
  2. Purchased Peter's A320 last night. As always, I'm very pleased with Peter and his creations.
    1 point
  3. Reminds me a guy who want to attend a historical fencing show but we already had a full car so we advised him to take a train. "How do I get there by a train?" "The train stops there - the train stop has the same name as the village. Sometimes the direct trains goes there, sometimes you have to change in [name of a city]". "How do I know if I have to change or not?" "If you aren't clever enough to use a timetable, conductor tells you." "How do I recognize him?" "He wears a uniform so he looks like a jerk." "Yes and do you have a GPS which I can borrow?" "Why?" "To find the place where the fencing show will be." "You are not able to find clearly visible castle ruins above a village?" "I don't know whether I must go to the left or right from the train stop and how far they are." "Go uphill." "Really?" "Lord of Wüstehube who built it wasn't that fool to build a castle in the valley. Hardly anybody in 14th century would do that."
    1 point
  4. Connecting iGoDispatch application with a plug-in in X-Plane.
    1 point
  5. virgin virtual flights gone wrong...
    1 point
  6. Yep - that file is basically the finished product of the instructions I posted earlier.
    1 point
  7. If you search the forum how to add it let's say to the B737-200, you can use the same procedure for DC-3. It just works. If you switch the GNS430 from "NAV" to "GPS" mode, it works as you would expect - doesn't couple with autopilot at all. ;-) Now seriously, it ruins much of the entertainment from flying this plane. If you really must fly to somewhere where there is no VOR/NDB coverage, why don't you just add some? It's even easier than adding the GNS430 to the DC-3 (= i.e. couldn't be easier) and doesn't ruin the entertainment. BTW if you are in range of 2 NDBs or 2 DMEs, you don't have to overfly them to preciesly navigate. Everything you need is a map, pencil and a ruler/protractor.
    1 point
  8. Just completed my KJFK-LFPG flight. ILS until 300 feet for runway 27L at Paris Charles De Gaulle. Descent towards LFPG AP Disconnect Beautiful chilly morning in Paris. Touchdown
    1 point
  9. Hi everyone, Work continues - as a matter of fact development speed has increased again over the last few days. There is really nothing big to reveal, on one end we are adressing the roughly 30 issues and remaining items we have, on the other hand we are fighting the uphill battle with the FMS routing structure. Before release there is also the documentation to be done - most of the content is there, it just needs streamlining and editing. Just last night we have improved the APU operation. We now have a moving air-inlet door, the FADEC will wait until the door is open before it engages the starter, and the APU can also be shut down with the firehandle or by switching off the battery bus - in that case the APU inlet door will stay open, though. A funny thing happened when testing the new behaviour - with repeated APU starts and insufficient time for battery recharge in-between, two of us have accidentially depleted the airplane battery. We initially thought we found a bug, as you couldn´t even connect the ground power anymore! But it turns out the behaviour of our simulation is correct, because without sufficient battery voltage you can not even close the relays to connect electrical ground power. This does happen in the real aircraft, too - if a pilot, eager to get to the hotel, forgets to properly shut down the aircraft in the evening (battery switch off), the next crew in the morning might find a dead battery. The only way to get the aircraft going in that case is to connect a DC source to the external DC connector. . We also worked on improving the GUI - up to now we had to go through the plugins menu to access preference or setup menus, now we have a state-of-the art sidebar that you can get to by bumping your mouse on the left edge of the screen. Some menus (ground and cabin-crew interaction) can also be triggered by following real procedures (selecting the correct interphone channel, enabling receive volume, toggling interphone or radio push-to-talk switch), but if you don´t feel like that, just use the nifty sidebar-menu. Our menu interface will be fairly spartanic, for example the "preflight" one will allow you to pick three states (cold and dark, turnaround, ready to fly), and specify zero-fuel-weight + CG and fuel distribution. We decided against some more elaborate "seat plan" where you can click on every single seat to place/remove a passenger. It would take too much time to make, novelty of it would wear off after using it once or twice, and really in the end all the real pilot cares about is the weight and the center of gravity. There will also be no "real time" boarding and deboarding of passengers, this is something that is very hard to get believable without actual 3D people moving onto the aircraft, which to my knowledge hasn´t been done totally believable on any flight-simulation to date. We do realistic fueling times (if the user chooses so), but weight adjustments (loading/unloading) is instantaneous. If you want to roleplay, use a stopwatch and a figure of roughly 5 passengers( = 500kg or 1100 lbs) per minute . With development speeding up again, I expect to start posting some more content and dev-blog type info more regularly. Jan
    1 point
×
×
  • Create New...