SteveBurney

Members
  • Content Count

    7
  • Joined

  • Last visited

Community Reputation

0 Neutral

Flight Sim Profile

  • Commercial Member
    No
  • Online Flight Organization Membership
    none
  • Virtual Airlines
    No

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. SteveBurney

    MSG button

    Thank you, Ed & Glenn. I’ll try adding the 66375 event in Mobiflight & 0x132c in the GNS.ini & see if that combination works.
  2. SteveBurney

    MSG button

    Thank you for the help, Ed. I'll try to figure out how to use custom events, and if that doesn't work I'll keep looking. There has to be an answer somewhere.
  3. SteveBurney

    MSG button

    Ok, we’re getting closer, now I know what NOT to do. How about entering the offset values? Is that also a bad idea? What I really need, though, is to know what TO do. Do you have a recommendation on how to connect a hardware button through Mobiflight (or any other means, for that matter)? Would it work to assign custom event values? I sure I’m not the first to try this, but so far I haven’t found anything to point me in the right direction. I’d greatly appreciate any guidance you can provide.
  4. SteveBurney

    MSG button

    Thank you. That’s what I thought, but I figured it wouldn’t hurt to ask. On another topic, I’m working on controlling it with buttons/encoders connected through an Arduino Mega and Mobiflight. I’m stuck on the CDI button. When I assign the FSX event number for TOGGLE_GPS_DRIVES_NAV1 (66375) to the GPS_CDI event in the keyboard section of GNS.INI then it continuously flips the setting on the unit without the button being pressed. I’ve also tried adding a keystroke shortcut and having mobiflight call that keystroke, but that didn’t work at all. The closest I came was to leave the keyboard control section for the cdi function blank in the ini file and program the hardware button to send the 66375 code. The problem there was that each keypress caused it to flip twice so it went from gps right back to gps. That was a single button press, not on press then again on release. If I pressed the virtual button with the mouse, it went to vnav, then when I press the hardware button it did the same thing and landed back on vnav again. Do you have a recommended method for connecting a hardware button to function as the CDI key? (The other buttons I’ve programmed so far using the fsx control numbers work great, I’m just stumped by the CDI.)
  5. SteveBurney

    Hyper gauge problem

    Thank you for the reply. I think I've got it working now-it looks like the problem may have been that the gns didn't like the way the instances were set in the 5th parameter (done by default, not by design). I changed them to more closely match the order given in the instructions and it seems to have fixed the problem.
  6. I hate to be a pest, but I’ve done something and now the gns isn’t working. I was fooling with the panel.cfg file, and now when I start fsx-se I get an error about a problem with Hypergauge and asking if I want to run it. (Not the question about whether or not I trust the software, but ‘Flight simulator has detected an error...’. If I click yes the program closes. If I click no a message box pops up ‘Hypergauge interface- Failed to load Hypergauge. Check dll.xml and Modules folder.’ I don’t see a dll.xml that’s newer than the gns program (and I don’t know what to check for), and the Hypergauge.dll is in the Modules folder. If I click ‘ok’, the sim runs, but the gns just has a blank screen. Any idea what I’ve done to break it and how to fix it? I’m not even sure working on the panel.cfg is what did it, but that’s what I was working on this evening before it stopped working. Thank you.
  7. SteveBurney

    MSG button

    I just purchased the GNS 530/430 yesterday, and so far I think it's great that I can use a 'real' gps in the flight sim and fly departures, arrivals, and RNAV approaches. It's REALLY distracting and annoying, though, that the MSG keeps flashing. Near airspace, inside airspace, inside and near airspace, every few seconds while flying an approach it cries out for attention. The MSG light doesn't flash near as much on the real units (and then it usually wants me to change the heading on the OBS). Is there anyway to attenuate the function, have 1 acknowledgement last for the entire approach or disable it during approaches? I have a feeling I know what the answer is, but I'm hoping something can be done about an annoying feature of what looks to be an otherwise great product. Oh, and as long as I'm nit-picking, how about being able to use the CLR button to declutter the screen? Thank you.