WingRider

A big DITTO from me. And I have still not figured it out! Could you please explain it to me because Keven Menard doesn't seem to be able to explain anything other that draw arrows to the same thing over and over. OK, I know I'm dense, but this looks like it could really add a lot of help and utility to the seemingly endless job of tying to keep MSFS 2020 up to date and with no new conflict every time they bring out an update. Sure hope 2024 does as better job in this regard

Totally useless video when it comes to figuring out how to use with addon linker. The guy says he uses it himself and then moves on and NEVER explains just how to use it. Not only that, but this guys just aggravating and annoying.

totally useless answer can't count the number of times I've clicked this, so what? How do I actually use it.

I'm running the E Jet V2 Emb 175 in FSX accel pack under Win 7 64bit. Climbing to cruise altitude the FMA shows LNAV and VALT reaching cruise altitude as long as the FMA shows a magenta VALT altitude stays stable. However, if VALT is changed to either a green FPA or ALT neither of these modes will hold the altitude stable - the aircraft starts porpoising up and down by a hundred feet or so. It is continuous. Switch back to VALT stable as a rock. Several observations: 1. Porpoising does not occur if FPA or ALT is reached by changing altitude via the altitude set switch and VS switch. Absolutely stable after that. 2. For some reason VALT changes to FPA every time I switch views, i.e. an S command is issued. I can't find any list of commands specifically used by feelthere for these jets. I was under the impression the they used standard FSX keyboard commands. 3. On forums I found two references to this problem. On one the suggestion was given to uncheck the "Enable support of GF-MCP" in the EMB configuration file. To which the person responded, that solved the problem. In the other case, the exact opposite advice was given, to which the person responded, that solved the problem. I've tried it both checked and unchecked and it made no difference. So any suggestions/comments on: A. Why should FPA or ALT be porpoising at cruise altitude, and how to fix? B. Why should issuing an "S" command to change views switch the autopilot from VALT to FPA, and how to fix. Many thanks

I'm running the E Jet V2 Emb 175 in FSX accel pack under Win 7 64bit. Climbing to cruise altitude the FMA shows LNAV and VALT reaching cruise altitude as long as the FMA shows a magenta VALT altitude stays stable. However, if VALT is changed to either a green FPA or ALT neither of these modes will hold the altitude stable - the aircraft starts porpoising up and down by a hundred feet or so. It is continuous. Switch back to VALT stable as a rock. Several observations: 1. Porpoising does not occur if FPA or ALT is reached by changing altitude via the altitude set switch and VS switch. Absolutely stable after that. 2. For some reason VALT changes to FPA every time I switch views, i.e. an S command is issued. I can't find any list of commands specifically used by feelthere for these jets. I was under the impression the they used standard FSX keyboard commands. 3. On forums I found two references to this problem. On one the suggestion was given to uncheck the "Enable support of GF-MCP" in the EMB configuration file. To which the person responded, that solved the problem. In the other case, the exact opposite advice was given, to which the person responded, that solved the problem. I've tried it both checked and unchecked and it made no difference. So any suggestions/comments on: A. Why should FPA or ALT be porpoising at cruise altitude, and how to fix? B. Why should issuing an "S" command to change views switch the autopilot from VALT to FPA, and how to fix. Many thanks

I'm running the E Jet V2 Emb 175 in FSX accel pack under Win 7 64bit. Climbing to cruise altitude the FMA shows LNAV and VALT reaching cruise altitude as long as the FMA shows a magenta VALT altitude stays stable. However, if VALT is changed to either a green FPA or ALT neither of these modes will hold the altitude stable - the aircraft starts porpoising up and down by a hundred feet or so. It is continuous. Switch back to VALT stable as a rock. Several observations: 1. Porpoising does not occur if FPA or ALT is reached by changing altitude via the altitude set switch and VS switch. Absolutely stable after that. 2. For some reason VALT changes to FPA every time I switch views, i.e. an S command is issued. I can't find any list of commands specifically used by feelthere for these jets. I was under the impression the they used standard FSX keyboard commands. 3. On forums I found two references to this problem. On one the suggestion was given to uncheck the "Enable support of GF-MCP" in the EMB configuration file. To which the person responded, that solved the problem. In the other case, the exact opposite advice was given, to which the person responded, that solved the problem. I've tried it both checked and unchecked and it made no difference. So any suggestions/comments on: A. Why should FPA or ALT be porpoising at cruise altitude, and how to fix? B. Why should issuing an "S" command to change views switch the autopilot from VALT to FPA, and how to fix. Many thanks

I'm running the E Jet V2 Emb 175 in FSX accel pack under Win 7 64bit. Climbing to cruise altitude the FMA shows LNAV and VALT reaching cruise altitude as long as the FMA shows a magenta VALT altitude stays stable. However, if VALT is changed to either a green FPA or ALT neither of these modes will hold the altitude stable - the aircraft starts porpoising up and down by a hundred feet or so. It is continuous. Switch back to VALT stable as a rock. Several observations: 1. Porpoising does not occur if FPA or ALT is reached by changing altitude via the altitude set switch and VS switch. Absolutely stable after that. 2. For some reason VALT changes to FPA every time I switch views, i.e. an S command is issued. I can't find any list of commands specifically used by feelthere for these jets. I was under the impression the they used standard FSX keyboard commands. 3. On forums I found two references to this problem. On one the suggestion was given to uncheck the "Enable support of GF-MCP" in the EMB configuration file. To which the person responded, that solved the problem. In the other case, the exact opposite advice was given, to which the person responded, that solved the problem. I've tried it both checked and unchecked and it made no difference. So any suggestions/comments on: A. Why should FPA or ALT be porpoising at cruise altitude, and how to fix? B. Why should issuing an "S" command to change views switch the autopilot from VALT to FPA, and how to fix. Many thanks

Thanks again Paul J. I think I get it now. The fundamental thing I was not aware of was that the "other settings" were essential being saved in the fsx.cfg rather than an individual settings .cfg file.So one last question. Are "other settings" saved to the fsx.cfg file when:1. You save a flight as a default flight2. Anytime you save a flight3. Each time you make a change and exit settings. I.e., this is where FSX remembers what other settings you've made so you can open and close the program and retain the last settings.Thanks.

Hi Paul J. - Thanks for responding. I'm not totally sure of everything you are saying but it sounds to me like your .bat file launches flights, and maybe other programs that you want along with them, and FSUIPC that saves the control settings for specific aircraft. But what then saves other settings in the "other settings" section such as voice sound on/off, ATC window on/off, using Directx10 or not, etc.?As to FSUIPC it appears to me that there is about a 50/50 split in these forums as to whether using FSUIPC, FSX settings, or the control program that comes with your input device is the best way to go. I have a registered version of FSUIPC, so guess I could try that, on the other hand I've got some Saitek stuff coming in next week, so will probably wait to see if their software offers me some functionality that I would otherwise lose, such as what they call their mode switch. I thing there software also may save aircraft specific settings, not clear on the yet.So I'm still left mainly with the "Other settings" question.Again, thanks.

Forgive me if this topic has been covered before, I did search, but could not find exactly what I'm looking for after trying numerous search parameters. Also, if it has, and you want to make that comment, please don't just give a snide "That's been covered before." Fine, give the url for it. (OK, obviously one of my pet peeves on a number of forums.OK, what I'm after. All this time I've thought I've been saving my settings in various permutations for different planes, with and without VoXATC, and various for ORBX FTX. Tonight I find that no, most of what I thought I was saving is not in the various setting .cfg files. In retrospect maybe I should have realized this as I now see that the settings panel has a left side labeled "Display Settings," and a right panel labeled "Other Settings," and all the save/load buttons are in the left panel. The savings I most wanted saved are all in the right panel. (For instance sound or ATC settings for when using VoXATC, or the joystick settings for different aircraft, and they are NOT saved in the .cfg file. What a waste!So, the question: Is there a way to save ALL settings (in one or more files) that would represent ALL the data from BOTH panels? If so, how, what are the files involved, and where can they be found - in a Win7 OS? I want my control settings different for different aircraft. I need different settings for VoXACT and not using VoX. How can I accomplish this?Many thanks.

I downloaded and installed Ziggy's Beechcraft Baron 58 TC (turbocharged). Works fine. I then wanted to modify it to use the Garmin 1000 that comes in the FSX package.Now I know next to nothing about doing this other than seat of the pants, so compared the basic aircraft.cfg files from both aircraft root folders. Modified the 58TC cfg to have another fltsim that I dropped in from the default baron's Garmin 1000 section. Copied the appropriate model, texture, and panel folders over into the 58TC's folder, and compared other areas of the two cfg files to tidy up needed areas.Pretty much works great except: In the original default G1000 Baron, on the IAS strip the division from green to yellow occurs at 195 KIAS and the division from yellow to red occurs at 225. When I fly the 58TC these two divisions occur at 125 and 160 KIAS respectively. I've searched both the aircraft and panel cfg files for anything related to all numbers and can find nothing. Have a hard time believing it's in the .bmp files as they all come from the default baron for the Garmin. I'm stumped.Any suggestions?I also tend to get a fuel flow usage alert, but that may be legit as I was pushing the 58TC hard to check it's climb and speed rates.ThanksAttached file is from the 58TC

According to the Captain Mike Ray manuals I have for the Wilco 777, when I'm flying I should be able to open up the LEGS page of the CDU, type in a new VOR or waypoint, and then click on the Line Select button where a previous VOR was stored, and it should replace that VOR, moving that VOR down in the LEGS list. When I do that, nothing happens.Anyone else had this issue? Comments?Thanks

Thanks Jim. Every reference I'd found was to the BIOS screen, or so I thought. Unfortunately, I cannot use the F8 option because all our keyboards are wireless. I can get into safe mode via the msconfig boot.ini page, but that just puts me into safe mode, while it is my understanding th disable driver signing is in the pre-windows start up screen itself.That said, if I could get to that screen, does that option do anything different than entering this Bcdedit.exe /set nointegritychecks ON into a command prompt? I.e., does disabling digital signature in the F8 screen simply throw windows into the same TEST mode that the command prompt string does?Again, many thanks!! Bob

Hello all.After I install Tileproxy on a system running Win7 64 bit I get the following.I also recieved this error msg during the install.And yes, I have read all the other posts and all the suggestions about overcoming this problem. Here is what I've done so far: Read more websites, and posts in this forum, about overcoming digital signature issues than I ever hope to read again. UAC is OFF I am running in Windows Test mode. My bios does NOT have the F8 option either at startup, or in the bios configuration reached via F2. There is no disable digital security feature in my bios. I ran DSEO and signed the tileproxy.sys file in the root Tileproxy directory. I then copied this signed file into the Windows\system32 folder so that it exists in both locations I downloaded the proxyuser.ini file from Ed Truthans site, modified it for the map server I wanted, and place it in the folder Ed specified. I ran DSEO on tileproxy.exe and proxyuser.ini though I have no idea if it affects them as they are not .sys files. I restarted the computer (actually multiple times). I've done all of the above and I still get this result. Any other comments/suggestions PLEASE?

I am running Win7 64bit Home Premium. I get the exact same message in the command window, and during the install, as referenced in the start of this post above. I have read all the suggestions about overcoming this problem. Here is what I've done so far: Read more websites and posts in this forum about overcoming digital signature issues than I ever hope to read again. UAC is OFF I am running in Windows Test mode. My bios does NOT have the F8 option either at startup, or in the bios configuration reached via F2. There is no disable digital security feature in my bios. I ran DSEO and signed the tileproxy.sys file in the root Tileproxy directory. I then copied this signed file into the Windows\system32 folder so that it exists in both locations I downloaded the proxyuser.ini file from Ed Truthans site, modified it for the map server I wanted, and place it in the folder Ed specified. I restarted the computer (actually multiple times). I've done all of the above and I still get this result.