ApacheHunter

I'm not sure, I'd like to know as well. Maybe in FSUIPC you can assign an axis to the tiller? I used this all the time with FSX. Haven't tested it with MSFS2020 though.

Modded Bonanza? What is changed and where can I get the mod?

I think that could be true and then the culprit would be PFPX. Are the RTE files for the 747 any different from the NGX/777 ones? As soon as I find time for another flight, I will! :wink: I see. However, in my case it didn't allow me to change anything.

Kyle, I tend to agree with you, as I have never had any problems with saved panel states before (in the NGX, that is). What could be wrong with the route?

Yes, I did use a saved panel state. I guess that was the problem. It was my second 'real' flight with the new 747. The first was from EHAM to KJFK; this one was the other way around. After landing at KJFK I saved the flight, loaded it and flew back to Amsterdam. I use this practice with the NGX all the time. I always load a saved flight (and thus a saved panel state) and never have any problems. It's probably dozens of flights since I last started a flight from scratch in the NGX. Never had any issues with that plane.

Thank you all for your replies! Dan, thanks for your suggestion, but neither of those things worked in this situation. Anything I tried to add, change, delete, etc. was just ignored by the FMC, without messages or anything. Kyle, the route was generated by PFPX and loaded into the FMC through the request flight plan feature on the RTE page. When I used RTE2 as a workaround I used the same procedure.

I'm currently in a situation where I can't solve a route discontinuity. In fact, I'm unable to do anything on the LEGS or RTE pages at all. It just ignores every input and I can only navigate using HDG SEL. I can hardly imagine this is correct behavior. I hope you can help me! EDIT: I just now tried selecting a DEP/ARR to try if that would resolve the problem. However, even when I try the LSK for a specific runway, it displays 'INVALID ENTRY' on the scratchpad. EDIT2: I found a workaround by loading the route into RTE2, so I can resume LNAV navigation. However, when trying to load the route into RTE1 again, I get 'NO ROUTES AVAILABLE'. Kevin Schepers

I've found another slightly annoying issue with this module: while flying, the MCP displays the magnetic heading. When turning the HDG knob on the MCP to change the Sperry AP course, the module first sets the course to the displayed magnetic heading value. Is there some way to keep the AP course at the current value when turning the HDG knob, instead of first switching to this other value?

Jens, that's indeed the case, but it's no problem at all! However, it could be you get a user module creation error. In that case, follow the instructions above and the module will work.

Thanks a lot; that did the trick! :wink:

Thank you, that's very kind!

Thanks for your reply! There actually is, but it seems to be a dummy: Any thoughts?

Thanks for the module! However, when I select it in LINDA, I get this: Does anybody know what could be the issue? I tried (re)installing LINDA 2.8.7, but I still get the error. I found out that my download of the module only contains a linda folder and not a linda-cfg folder.

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?