voske

3 hours ago, SaenchaySor said:

Name des fehlerhaften Moduls: menus.dll

Some suggestions for dealing with that issue: http://www.prepar3d.com/forum/viewtopic.php?t=121964#p145169

You don't have to remove the airway in PFPX. It's possible to solve this issue by changing "Cruise Altitude/FL" in PFPX from OPEN to OPEN OPT. 

Saitek Yoke, Throttle and Rudder Pedals work without issue for me in P3D and W10.

I think the first question is whether your Yoke and Throttle do show up in your W10 Devices screen.

Don't have the sim open, but I believe that after you request a route you get the options to either load or purge that route (but obviously only if there's a route available).

How do you load the cargo and fuel? Might sound like a stupid question, but just to rule something out.

Did three flights this weekend. Today was the first time I used autobrakes 2. The results:

Friday: landing at MPTO, Vref 137, idle reverse thrust and manual braking - no issues, 

Saturday: landing at EHAM, Vref 137, idle reverse thrust and autobrakes 1 - no issues (brake temp value was 1.1 after landing).

Sunday: landing at HTKJ, Vref 137, idle reverse thrust and autobrakes 2 - brake temps through the roof and tires deflated

13 hours ago, voske said:

doing another long flight later today, and will try the storm lights again.

Three attempts. Each time the sim froze for a few seconds, but no CTDs today.

382.53, GTX 970, and in my case the 777-200LR. I'll be doing another long flight later today, and will try the storm lights again.

I might have had a similar issue: I had two CTDs in a row tonight, both happened immediately after I switched the storm lights on. According to the Event Viewer the first CTD involved nt.dll and the second sound.dll.

Just thinking out loud (no RW experience whatsoever).

FCOM2 15.20.4 indicate the eight amber lights that are related to AIR COND on the system annunciator panel. Amber lights indicate conditions which require the timely attention of the flight crew (according to FCOM2 15.20.1). If there are no amber lights accompanying the indication on the system annuciator panel, I'd think it wouldn't be an issue that requires any action by the flight crew but that it would be just a maintenaince issue.

I think the FMC is actually trying to draw a line from ODDEL to HAMMY to TUFFY and then to 18R, but it simply can't. Flying straight from ODDEL to HAMMY to TUFFY and then land on 18R is (in my opinion, but who am I) simply impossible. I think the only solution would be to create a PBD waypoint if you want to remove the vectors.

I think ACF means Analyzed Contingency Fuel. My guess would be something like:

90% of the samples = 5 minutes

99% of the samples = 6 minutes

Number of samples = 64

Standard deviation = 0 minutes

- I'm struggling to reset the baro. I can switch between Baro and Radios and adjust the values just fine. However, when I click reset, nothing happens. Not sure if this is how-is and I'm doing something wrong or a small bug.

 

Page 44 of the introduction manual provides the answer.

1309 is the 9th AIRAC "cycle" of 2013.

1 Charts for airports outside Europe, North America and Australia

2 Charts that are not available on the websites you mentioned (in particular parking charts for the USA)

3 One type of layout for all charts

4 Only one source needed for all charts

I don't believe there are freeware navdata updates. I use Navigraph for navdata updates.

What is the date of the navdata of the 737? I believe you can find that on the FMC init page (I am 3000 miles away from my flight sim PC, so I can't check it).

OTHH was opened in 2014. Perhaps the navdata is older than that. In that case, OTHH will not be included in the navdata. The only solution would be to update the navdata.

British Airways still flies 767s.  I know because I recently flew direct from Heathrow to Grand Cayman on one!

 

Since August, British Airways no longer uses the 767 on longhaul flights. Most of their longhaul 767s are retired now.

No issues here with the Anniversary update. Just had to register the 777 again.

That's just a placeholder. Latest update from the developer:

Guys, I don't want to ruin your day, but the CRJ release is NOT imminent. We're still busy testing and fixing things and we don't have a release candidate yet. I hope it won't be much longer but I still can't give you an estimate because finding and fixing bugs always takes exactly as much time as it takes and not a second less.

http://forum.aerosoft.com/index.php?/topic/33966-aerosoft-da-crj-preview/&do=findComment&comment=768062

The normal cruising speed of the Constellation was about 280 knots, according to what I can find. Also, the planned duration includes taxi times.

According to the legend, flights PA130 and PA131 were flown with the Lockheed Constellation and the others with the DC-4. Also, the times are local times according to page 17 and 18 of the timetable. Time in New York is GMT-5 and time in Bermuda is GMT-4. Keeping that in mind, you get the following result.

Planned duration of the direct flight from New York to Bermuda

DC-4: 4h05m

Constellation: 3h15m

Planned duration of the direct flight from Bermuda to New York

DC-4: 4h35m

Constellation: 3h50m

I think it's IFP/MODESASP. According to the following quote this is automatically added to the flightplan by Eurocontrol's Integrated Initial Flight Plan Processing System:

The IFPS checks the profile of a flight to determine whether or not a Mode S equipped flight remains entirely within Mode S airspace and if so IFPS adds the IFP/MODESASP indicator to the flight plan distributed to ATC units.

[uR.FPL.SEQPT.002]new (added in CTOR)

The IFPS mechanisms should be adapted such that compliance with Mode S checking can be achieved when one or more of the indications 'E', 'H', 'L', ‘S’ or ‘I’ is present in Field 10b.

Source: page 18 of https://www.eurocontrol.int/sites/default/files/article/content/documents/nm/flight-planning/icao-2012/icao-2012-fpl-2012-urd-latest.pdf

You're right according to this remark on the Lido chart:

Rwy 04L: E arrivals

Rwy 04R: A arrivals

Rwy 12: B arrivals

Rwy 22L: F arrivals

Rwy 22R: C arrivals

Rwy 30: D arrivals

Therefore, the arrival should have been the ALM1F to ULTIS.

There is also a remark on the chart though that, traffic permitting, direct routing to ABEGI, ADOVI, LAMOX, and ULTIS for rwy 22L/R may occur. If flying offline or with no ATC on VATSIM, I would probably go from ALM direct to ADOVI, and then LAMOX to intercept the ILS.

www.flightstats.com provides the departure gate (and sometimes also the arrival gate) for a lot of airports, including airports outside the US. I just tried it with flights departing from Amsterdam, Beijing and Hong Kong.