RvETito Posted June 11, 2007 Posted June 11, 2007 Here's the deal. Not long time ago I was flying online when I noticed a strange behavior of the estimated range to target setting(the number in the bottom center part of the HUD) in the russian fighters BVR mode. As you know, when you switch the radar on by default this range is 10km, and with Ctrl-- and Ctrl-+ you can change in increments of 5 and 10 (beyond 40km). So I noticed that on my HUD this range is 97km and periodically changing (flashing) to 98km and back. During that I'm completely unable to control it, i.e. set it manualy to the range I want. Only when it's not 'flashing' I have control on this. But it has completely random nature. After having cunsultations from =RvE=--A.S-- and making my own tests I figured out that the slider which I was using as a zoom view has something to do with it. As we know the slider has a poor design that gives flickering inputs all the time but I really can't see any connection between zoom function and estimated range to target. Why this bug affects only this parameter? And why 97-98km? So I removed the slider and assigned the zoom funstion to the smaller rotary. Initial tests showed normal operation but in a few the bug reapeared. This time only the range was diferent- 47-48km. Then I completely removed all commands from the rotaries and the slider. The bug is still there at 47km. I'm using the vanilla Saitek drivers that came with the CD, haven't modded anything on my X52. I've read that sometimes unplugging and replugging fixes such bugs but I haven't heard of anything like that so far and I thought it's worth report it. Any opinion is welcome. "See, to me that's a stupid instrument. It tells what your angle of attack is. If you don't know you shouldn't be flying." - Chuck Yeager, from the back seat of F-15D at age 89. =RvE=
Ven Posted June 11, 2007 Posted June 11, 2007 I have X52 Pro so it might be different but any keystroke you assign using the band in SST is repeated. You need to make them macro for it to be press once and release. For zoom, I use the mouse wheel on the throttle. This works really well because unlike slider or rotary, the wheel clicks and doesn't flicker. To use the mouse wheel as zoom, don't assign any profile to it and choose mouse as controller in LOMAC. Not X52. Then assign mouse wheel axis to zoom. Also in axis setting in LOMAC, make sure no axis assignment is duplicated with other controllers.
RvETito Posted June 11, 2007 Author Posted June 11, 2007 Copy that. Well I was about to reprogram my entire command layout in LO in order to use the less key combos as possible. Also thought about the mouse scroll as a zoom replacement but what bothers me the most is why this thing keeps on bugging even when I've unassigned all commands from the slider and the rotaries. I haven't noticed any bugs with the other planes in LO, only this with the russian flighters BVR mode. "See, to me that's a stupid instrument. It tells what your angle of attack is. If you don't know you shouldn't be flying." - Chuck Yeager, from the back seat of F-15D at age 89. =RvE=
SuperKungFu Posted June 11, 2007 Posted June 11, 2007 Also you said you are running on the stock drivers from the cd? You should update that. I never touched the cd, when i got mine, i downloaded both the driver and SST program from the main website. [sIGPIC][/sIGPIC]
RvETito Posted June 11, 2007 Author Posted June 11, 2007 Hmmm, actualy I already got the opposite advice. I heard that all updates afterwards have been corrupted. But looks like you have a working one. Anyway, the vanilla driver/STT package was working without any remarks for 1 year and 3 months for me. I might try reinstall it. "See, to me that's a stupid instrument. It tells what your angle of attack is. If you don't know you shouldn't be flying." - Chuck Yeager, from the back seat of F-15D at age 89. =RvE=
Ven Posted June 11, 2007 Posted June 11, 2007 Well beware that the latest beta drivers use different formats and you need to create brand new profile if you're gonna update. As for that bug, I'd try unplugging saitek and flying with keyboard to make sure if it's your saitek that's causing it first. If it works fine with keyboard, then try plugging in X52 but don't run the SST. Just use it as regular joystick. If it works fine again, then it's probably some mapping in SST causing it. So start disabling button maps few at a time. Elimination process. 1
RvETito Posted June 11, 2007 Author Posted June 11, 2007 Thanks, very good point taken :thumbup: Rep inbound. "See, to me that's a stupid instrument. It tells what your angle of attack is. If you don't know you shouldn't be flying." - Chuck Yeager, from the back seat of F-15D at age 89. =RvE=
rattler Posted June 11, 2007 Posted June 11, 2007 Thanks, very good point taken :thumbup: Rep inbound. I assign Macros to the Throttle Hat> right to increase , left to decrease. Works great. Stay with the original CD software. People are right the SST updates are corrupted. Slider I never use. everything else ok, some use the rotory's but I don't, but they work. Slider has been an issue if not programed right and it is difficult for some reason, so I think most users stay away from it. To be honest if all your functions are programmed correctly, then I would begin to doubt it is an X52 problem. I have one of the originals and it has never failed to perform according to my Profiles. Hope you can track the problem down. Cheers.
Recommended Posts