Jump to content

Bumblefox

Members
  • Content Count

    11
  • Joined

  • Last visited

About Bumblefox

  • Rank
    Junior Member
  • Birthday 05/16/1979

Personal Information

  • Flight Simulators
    DCS, MSFS2020, IL2:GB, "Elite Dangerous"
  • Location
    Dallas, TX
  • Interests
    Aerospace tech, History, Computing, Tabletop Gaming

Recent Profile Visitors

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

  1. No worries, mang. If you, or anyone else, have any insight about why the target box on the HUD would appear depressed from the TGP line of sight, I’d appreciate it.
  2. As an aside, while setting the mission QNH to standard aligns the steerpoint altitudes, the target box still appears significantly depressed compared to the TGP line of sight. is that something else?
  3. Rock on, thanks mang. I can try to get you a track if you need it, but I’m working for a few more hours
  4. Can’t you already achieve that by setting a button up as a Modifier in the DCS controls menu?
  5. Methinks it’s a function of the keybinds tables being imported from the earlier A10C. The knee board/mirror toggle/HMCS power switch etc. keybinds aren’t built into the table yet. Hopefully they will overhaul it at some point x.x
  6. Ah, Ok, I get you. Tried it with the mission pressure set to the standard, and yee, the steerpoint/TGP symbology now aligns with the ground elevation. I imagine this is a bug, or known issue then? Shouldn't dialing in the QFE/going through the alignment process account for that?
  7. yeah, Correct altitude to flight plan, and altimeter set to the QFE from the mission; in this case, 29.53. I input the runway threshhold coordinates and correct elevation for the south end of Krymsk, for example, and the steerpoint mark is on point in lat-long, but apparently several hundred feet below ground level, and adjusting altimeter setting or even trying to change the elevation on the steerpoint doesn't seem to fix it. -and I don't have this issue with the F-18 or A-10C
  8. Having jumped back into the viper in the last week, I've noticed that my steerpoint diamonds and TGP box on the HUD seem to be displayed at an apparent altitude several hundred feet lower than set (i.e. set steerpoint at coordinates for the runway threshold, and lat/long position appears correct, but diamond seems to be indicating a spot underground.) Is this related to the SPI issue or, am I just doing it wrong, somehow?
  9. Well, that's really weird then. Any suggestions on how to remedy this? Disregard! apparently wiping out the binding completely, then reapplying it fixed it. No idea what happened there.
  10. Just passing this bug along: I've tried binding the UFC CLR Key to keyboard and other controllers, and it does not respond in the sim. it -does- respond by highlighting the row on the control settings page when the key combo or controller button is pressed, but the UFC CLR key in the sim does not respond to the input, either by controller or keyboard. it is mouse clickable though. Anyone else seen this?
×
×
  • Create New...