ApacheHunter

Thanks all of you! It makes a lot more sense now.

So, all times are local times? From the following text from page 17 I understood that all times are in GMT, but I can be mistaken, as English is not my native language: If the times are local times and taxi time etc. is included, it comes a lot closer to what I found in the sim. Thanks a lot!

Hopefully one of you can help me with something I don't understand! In anticipation of the upcoming A2A Simulations Lockheed Constellation, I pulled their Boeing 377 Stratocruiser out of its virtual hangar. I haven't done a lot with it in the past, so I decided to try and fly some historic flights with it, using a Pan Am timetable I found over at http://timetableimages.com. Below is a section of this timetable, the flight New York - Bermuda. As you can see, it says the flight time is about 5 hours and 5 minutes (from 10:00h until 15:05h GMT). According to my calculations the flight time should be 2 hours and 34 minutes (without wind correction) and after flying the actual flight time turned out to be 02:25h. Can anybody explain to me why it says so much longer in the timetable? Did I misinterpret something? The complete timetable can be found at http://timetableimages.com/ttimages/pa/pa50/pa50.pdf. Who can explain this to me? :wink:

Thanks a lot! I found the file and removed it (and thus the sticker).

Recently I installed a new livery for the PMDG 737NGX (KLM Royal Dutch Airlines 'new livery' PH-BXZ; from the library) and noticed there are yellow stickers below both navigation displays saying: "AD 2002-24-51: fuel usage restrictions required". I've never noticed this before. How did this sticker appear there and is it part of this particular repaint? Can it be removed?

Version 1.xx, I don't know it exactly. I think 1.11, but I don't know for sure.

That's right, I recently changed that setting. I didn't know it would affect FS2Crew. I'm setting the units of measurement back to feet. Thanks for your help!!

Thanks for investigating. The problem is not that big; as I've said before I already started using FSUIPC for this. However, how come it did work in the old version of LINDA?

For some reason, FS2Crew suddenly only uses the standard U.S. 18000 ft/FL180 as the transition altitude/transition level, regardless of my input in the FMC. Also for the minimums it started to use a default value, instead of what I fill in on the approach brief page of the settings window. What could cause this and how can I solve this problem? EDIT: The above was for yesterday's flight. On today's flight I found out that FS2Crew used 7000 ft instead of 2000 ft for the FAF, FL100 instead of FL030 for the transition level and > 500 ft instead of 187 ft for the minimums. I am 100% positive I filled everything in correctly in both the FMC and the FS2Crew settings. It never did this before. Very strange...

That sounds great! I hope it can be fixed.

Below is a screenshot of the settings window of my old LINDA installation, so I guess it was a pretty old version! I didn't update it earlier because it did exactly what it needed to. Last week I needed to update because the profile for the Aerosoft Airbus didn't work with the older version. I use the hat switch for trimming as it's meant for that particular function and I use TrackIR, so no need to use it for viewing around. That's exactly what it doesn't do on my pc. The repeat function keeps continuing, even after I've used some other buttons. It only stops when restarting FSX or selecting another aircraft. I've already tried a clean LINDA installation. As I said, it works perfectly when configured directly in FSUIPC, but since I have 99% of buttons and switches configured in LINDA it would be nice if also these functions could be configured there.

Before I updated LINDA to 2.6.6, I've always used the hat switch on my Thrustmaster Hotas Warthog joystick to control the elevator and aileron trim. Since I'm using the new version, this is no longer possible, because it keeps trimming endlessly. In the settings, it looks like this: In the past, after I for example pressed up on the hat switch and let go, you could see in LINDA that LINDA selected H1: 0 again. Now this doesn't happen anymore and it seems that LINDA keeps sending trim commands. In previous versions of LINDA the text "DO NOT USE" behind H1: 0 wasn't there. Also, when I don't assign anything in the second column (on repeat) it just works, but then I have to keep pressing the hat switch while trimming, which isn't realistic. When I program the same in FSUIPC (latest version 4.948e) everything works fine. Any thoughts on this?

Thanks for helping! I commented 'Display Resync' out in D:\Microsoft Games\Microsoft Flight Simulator X\Modules\linda\aircrafts\A2A_Piper_PA28_180_Cherokee\actions.lua and now the error is gone.

Thanks, but I can't find 'Display Resync' in the common.lua file.

Thanks for helping me! I'm not sure about the LINDA version. I use the VRI MCP Combo II (Boeing style) panel. It happened to me yesterday, I then shut down the MCP Combo, restarted LINDA and continued flying without any issues. Today I got the same error, but kept on flying without any issues. The MCP works, only the display keeps showing the same information:

Whenever I load the A2A Simulations Piper PA-28-180 Cherokee I get the following error in the LINDA Console: Does anybody know what this means and how I can get rid of the error?

The ones PMDG supplies are the original Boeing checklists. Those are the ones that are used in the real life aircraft. The 'checklists' Carsten Rau makes are extremely long. In fact, they aren't checklists at all, but more like a summary of the normal procedures.

They are in the PMDG documentation, QRH, chapter NC. Page 31 for the 777 and page 25 for the 737.

You can acces the charts for ENAT, KSAN and ZJSY for free as a demo, so you can see what the charts look like for yourself. I believe they are updated four times a year.

Alright, I understand what you mean. I've sat in the cockpit of a B747-300 several times and the windows are indeed a lot smaller than you'd expect. Never noticed it in the PMDG, though. Thanks for your reply!

May I ask what exactly is wrong with the shape of the windshield as it is now?

The "panel switcher" bar comes standard with the PMDG 747X add-on.

To make LINDA work with the PMDG P-8A Poseidon, all you have to do is add a single line to one of the configuration files. To do this, navigate to C:\...\<your FSX folder>\Modules\linda\aircrafts\PMDG 737NGX and open ident.lua with notepad. Below the line already present, add simfolder="PMDG 737" and save. Now LINDA (and thus the MCP Combo, should you have one) works with the PMDG P-8A Poseidon.

Sometimes a second [DISPLAY.Device.xxx] section is created in fsx.cfg, although only one monitor is used. This cuts fps in half. Deleting the old fsx.cfg and letting FSX create a new one cures this.

You know that, in order for the WX RDR to work, you have to use Active Sky Next by HiFi Technologies, Inc.?