Jump to content


  • Content Count

  • Donations

  • Joined

  • Last visited

Community Reputation

11 Neutral

About realpilotsimpilot

  • Rank

Profile Information

  • Gender
  • Location
    U.S. of A.

Flight Sim Profile

  • Commercial Member
  • Online Flight Organization Membership
  • Virtual Airlines
  1. Scot, tried to DM you about coolsky dc-9 and it said you don’t accept messages. DM me if you need a copy or if it will break the newest version of LINDA. best,
  2. Thanks, Dan. Presumably I should uninstall FS2Crew too? And then run the OC and the NGX once to check it before reinstalling FS2Crew? (I'll post this over there, too, but that seems like the best approach.) Edit: FYI, the reason for this post was there were a bunch of posts about errors, not working afterwards, etc.
  3. Howdy all, After a period of limited simming (and largely using the very awesome Coolsky DC-9 when I do), I've started flying the NGX again. I see that they have discontinued liveries and so on and gone to an operations center (which started with the 777 which I don't have and probably won't buy despite how awesome it apparently is). After searching the forum, it appears I need to re-download the NGX and run the files to update it. Apparently that will delete the liveries I have (which aren't very many) and I'll need to reinstall them and add others, etc. Any other tips or tricks for the unwary anyone can suggest? I use FS2Crew (non-reboot version), LINDA, and GSX, but I can't imagine other than FS2Crew that these would be affected. Suggestions on doing this welcome. Thanks a bunch.
  4. Ok, I got the MCP1 to work with 2.6.6 for all aircraft EXCEPT the Q400. I got this error. LUA Error: ....a-cfg/aircrafts/Majestic Dash 8 Q-400/config-hid.lua:3 attempt to index field (068E00510 (a nil value) So then, I deleted (actually renamed) the config.lua file in the linda-cfg folder for the Q400 (this is advice you gave me on a slightly different error I had in an earlier thread. It seems to work now. A couple nits: 1. Saved flights: do not work. I get a string of error messages. Not a big deal. I will try some new flights and saving them to ensure this is just for "old" flights and not some persistent issue. 2. The display is pretty simple, but it works, so I'm ok with that. It beats not working at all.
  5. Are you using 2.6.6 with MCP1? Scott seemed to say that had a display issue which I believe I experienced. Thanks, I don't think a new MCP is likely, but I will tinker with 2.6.3 v.2 and see if I can get that to work with the MCP1 and a version of the module. Maybe I can turn the MCP off if I'm using the Q400. Not ideal, but I have other hardware that I would like to work as well and it appears to. If you happen to fix (or think you have fixed) the MCP1 display issue on 2.6.6, let me know and I can test it for you. Best, Best,
  6. So, a few data points and clarifications here: To be clear, I have the original MCP Combo, the one that is listed as "untested" with v2.6.3 and that we should use 1.13 instead. I couldn't get the q400 module to work at all. I tried an older version of the module (not sure which one) as well as the new one with 1.13. I got an error message every time. I then tried installing versions 2.6.3 and it wouldn't work at all. I even got a display error that was so bad that I thought it had bricked my MCP, but I was able to fix it by a USB unplug/replug. Not sure what to do. I could send the error message (which was something like "60003446") if that would help. If there's an older version of the module you recommend, I'm certainly interested in trying it. I'll even try 2.6.6 if you think that would work. Best, EDIT: I noted there is a "2.6.3 v.2" that fixed the range check error. I don't think I used that one. Is that the one that has been reported to work successfully with the MCP1?
  7. Thanks, Scott. I'll double check, but my recollection is that the 2.6.3 caused the error message with the add-ons I used most. I'll double check when I'm in front my FS rig.
  8. I have been tinkering with my system and noted the Majestic module is missing and I was going to reinstall. I'm kind of confused what to do, since I use the older version of Linda (1.3?) so it will work with my MCP v.1 (2.6.X doesn't seem to work with it.) If I install the current module will it work with the older version of LINDA? (And by "work", I mean function enough to make my MCP usable enough to fly and not cause a CTD everytime.) As an aside, I recently bought the FS2Crew for it, but have not yet installed it. Thanks for any advice.
  9. Scot, Thanks for the help, that was indeed it! This is a rather unconventional bird in its mappings of things and the way it behaves.
  10. I was using Linda 1.1.1 Just upgraded to 1.1.3. Doesn't seem to matter. I have the VRInsight Boeing style MCP (first version). Looking at the list of commands in the first post, it doesn't appear that anyone has been able to isolate the range switching, feature (There's only 4 or 5 positions in the DASH.) A lot of the Autopilot functions also seem to be unavailable. The vertical navigation on this plane seems similar to the J41 (IAS, Alt SEL, etc.)
  11. Howdy all, just bought this craft and loaded the Linda module. It seems like the programming of the bird precludes using a MCP to its full potential. Much of the left side of the MCP (baro, range) and the autopilot (vnav) seems unavailable. I'm happy to go hunting to find other things, but it sounds like others have tried. If there's unexplored hunting, please let me know Best,
  12. Thanks Michel! The vision in my head was something similar, with a wooden back but with ABS plastic sheets screwed on the front. I can get 1/16 inch for like $8 and 1/8 for like $13 from Amazon, less if I shop around. If you want to PM me with the design software link, that would be awesome. I'm thinking essentially a glorified trapezoid. Thanks a bunch. I'm finally getting to where I am ready to move forward after a couple of small boxes in project boxes.
  13. Michael, Very nice. I've actually been quietly working on an MCP and an overhead. I'm using interfaces from Groovy Game Gear, since I didn't feel like having the extra expense of importing equipment from the U.K. (I'm in the U.S.) The hold up (other than lack of time), has been inability to commit to a box design. What did you use to build the enclosure and face? I was going to buy some sheets of ABS and make something, but hadn't decided completely. I also have this dream of putting in a display that will show crz alt and landing alt, but I think that might be impossible. I at least want to include the dials for both. Thanks for the continued inspiration. As with you, I started thinking about this when I saw LINDA.
  14. Dario, there's a thread in the Support sub-forum where Guenther gives me some pointers on how to use Tracer more effectively. My issue was that while the manual describes nicely how to find the functions, I was unclear on what to do with that information. I usually sim on the weekends only, so I will try playing with this in a few days.
  15. Dario, thanks. I'm trying to do this without mouse macros, but rather buy adding to the module to some other overhead functions I would want. I'm sort of toying with building a bit of an overhead, compacted down.
  • Create New...