Jump to content

glcm1961

Members
  • Posts

    27
  • Joined

  • Last visited

Everything posted by glcm1961

  1. I assigned zoom to the slider on the throttle, but did it from the games input options, not the SST programming thing. If you use the rotaries, make sure you have a band in the center ident that doesn't have a key assigned to it, otherwise your controller will constantly be sending a keystroke to the game. And lastly, I HIGHLY recommend picking up a set of rudder pedals for the x-52. I hated the twisty stick and since flying with pedals it makes lining up those strafing runs on the A-10 a thing of beauty!
  2. After flying a couple of missions, I begin to get weird graphic glitches and textures all out of whack. I noticed when I end a mission and the dialogue box appears asking me if I want to save, quit, or cancel, the mouse cursor blinks rapidly between the normal arrow and an hourglass. Somewhere, somehow I'm getting inputs from somewhere that is slowly strangling my game but I don't know where they are coming from. I'm flying LOMAC ver 1.02 with a saitek x-52 and rudder pedals with Track IR 1. I know I have a problem with the "33" and "34" key on my saitek (well known bug) but I use a profile from the SST program that doesn't use either one of those inputs so I wouldn't think those keys spiking would be the cause. At any rate, I was wondering if there is a log file that keeps track of all inputs? Any and all help is welcome. Thanks. Update: I think I found the problem. I didn't have a blank band set on one of the rotary knobs on my x-52 and even when it was at it's centered ident position it was still sending out commands to the computer.
×
×
  • Create New...