fschrewe

While a magdev update reflects changes in the earth's magnetic field that changes the difference between true north and magnetic north and writes these changes into a .bgl file to be displayed in the sim, an airac update wil give you updated SIDs and STARs, airways and intersections - all those things you need for your FMC - but its just data for your planes computer, nothing will be changed in the simulator itself. An airac update will give you the actual runway heading for your FMC, but it doesn't change the numbers in your airport's .bgl file. I think the magdev update will do this, but I'm not sure. If it doesn't, at least PMDGs B737NGX has the option to read the airport headings from the .bgl and use them instead of those written in the Navdata for approach...

It is definitely possible to use the SIOC script linked in the opencockpits download section. As you are using the CDU V2, you will have to make some minor changes in the script and in the SIOC.ini to tell the system you have an USB keys card connected instead of an CDU V3, but the rest of the script is the same (as I remember, I used the CDU V2 some time ago before I switched to V3 beacuse of some issues with the graphics adapter)

There won't be an SDK for the old 747, but PMDG will bring up an completely new "B747 v2" using the advanced code they developed for the NGX and the 777. And this new 747 wil have an SDK. I think the SDK for the 777 will come as soon as the few bugs are fixed...

I Just tried to print out the manuals for the B772LR, but it seem that only the Introduction and the tutorial are printable. Opening the other documents the printer symbol is greyed out. Does that mean we have to open these documents on an additional monitor or computer if we need them for reference, as printing doesn't seem to be possible?

Flaps=0,16380 means two things: you have assigned an axis (joystick / hardware throttle or similar) for flap control only a part of this axis is assigned, as the normal range of this values is about -16380,16380 If you move your flap lever outside the assigned range, FSUIPC does not know how to interprete this and goes nuts. Just try to recalibrate your flap axis within FSUIPC and the prolbem should be gone...

If you are working with Oencockpits IO-Cards and SIOC, you don't need FSUIPC for this. Roar Kristensen made a driver for this, which can be found here: www.flightsim4fun.com/download. For Plug-and-Play-modules he delivers even complete scripts, and two documents with all necessary events and offsets to make your own SIOC-scripts for non Plug-and-play instruments.

Please keep in mind that different countries have different regulations. In Germany for example, therw is no Speed limit below FL100 for IFR Traffic in Airspace C. And even outside Airspace C it's not uncommon to get a "highspeed approved" by ATC. Before a discussion about FL100 starts: In Germany the Transition Altitude is at 5000 ft, not 18000 ft like in the USA!

Hello Thomas, The explanation is quite simple. Innsbruck is located in the valley of the "Inn" river and is surrounded by high mountains. If you are arriving from the east with RWY 26 active you can use a LLZ approach with a 5° offset to the runway. For arrival from the west the mountains are so close to the runway that you have to fly over the runway at 500ft MSL and make a turn for a visual approach. For the same reason approaches for RWY 08 are also flown visual as you have to stick very close to the mountains south and west of the airfield. As these procedures are supposed to be flown by hand, they are actually not even part of up-to-date Navdata to prevent pilots from trying to fly them by autopilot... For your RNAV approach: Although the MAP is 12.7 miles away from the airfield, you are already down to 5000 ft MSL at that point, while the mountains around have more than 9000 ft, possibly blocking some GPS signals. From this point you have to follow the valley visually. In real life many airlines have company procedures allowing their pilots only to use the LOC DME east approach for RWY26 - or reroute to an alternate airport for safety reasons. A complete Chart package for LOWI (including the visual approach chart) can be found here: http://www.vacc-austria.org/?page=content/chartlist&icao=LOWI Frank P.S.: sorry for my english, it's not my first language...

Hello Gerard, I suggest you go the easy way and download the Driver you find in the downloads-section of the Opencockpits CDU V3. That driver uses the NGX SDK and SIOC 4.2Beta2 (or higher) and works perfectly. You don't need FSUIPC for this anymore.. Regards Frank

That looks interesting. Is there a chance that the CDU will be supported by your driver in a future version (in the near future). Up to now, that is the only OC hardware I have, and at the moment it only works with the 767...

Two more tools for Flightplans:VATroute (especially for routes to or from Austria/Germany/Switzerland) orvroute (worldwide routes) for Charts: chartviewer.at (uses the VATEUD charts database)

I usually use either VATroute or vroute to get a flightplan.The VATroute flightplans are supported by a team of admins, who check the routes for changes after every airac cycle. They usually have the routes like they are used in real world, but they are only covering flight plans with destination or departure in one of the following countries: Egypt, Netherlands, Autria, Switzerland and Germany. vroute has a much larger database, but here most of the routes are entered by users - sometimes you get 10 gifferent routes between 2 airports, and not all of them make sense.Both tools normally do not provide SIDs and STARs, because (at least in Germany) most of them depend on the runway in use, so the SIDs and STARs (at least the designators) change withe the weather Frank Schrewe