AGM65 Target Lock.

[StarWrecker]

Ok, I'm trying to attack a Shilka at long range before the thing shreds me. But I find that the AGM65 designation pipper won't go more than 1/8 of the way down the HUD without snapping back to the top. I have Lomac v 1.02, and my specs are:
Athlon64 3200+
Geforce 6600GT 128MB
1GB RAM

Am I doing something wrong, this is the first time I've had such problems, it worked fine before the update, and on the updated version before I formatted my drive.

Would the fact I'm using my X52's second hat to control the pipper cause any problems?

Any help would be appreciated.

[StarWrecker]

Ok, I'm trying to attack a Shilka at long range before the thing shreds me. But I find that the AGM65 designation pipper won't go more than 1/8 of the way down the HUD without snapping back to the top. I have Lomac v 1.02, and my specs are:
Athlon64 3200+
Geforce 6600GT 128MB
1GB RAM

Am I doing something wrong, this is the first time I've had such problems, it worked fine before the update, and on the updated version before I formatted my drive.

Would the fact I'm using my X52's second hat to control the pipper cause any problems?

Any help would be appreciated.

[konkussion]

Some thoughts from the top of my head.

If you reformatted & reinstalled- you will have a bunch of things default-mapped to your X52 by LOMAC. Check to see if the aiming pipper is an axis- I can't remember or check here at work. If it is- clear it & remap. It may not work mapped as an axis at all. The "trim roll" sure doesn't. It "snaps back" as you described above.

Along those same lines- you really should use the SST software to program your stick for everything EXCEPT AXIS- pitch roll rudder thrust and maybe a couple of other things like MFD display. My aiming reticle is controlled by the mouse cursor on my throttle- this is mapped in SST- NOT from within LOMAC. Refer to this site for tips on setting up your stuff. It will help you avoid common conflicts caused by more than one command being sent to the same button by the two different programs (LOMAC & SST).

http://www.freewebs.com/konkussion/x45helpdesk.htm

[WhiskeyRomeo]

Try using just the key commands (not the JS Hat) to move the Mav pipper.
; & . (semi-colon & period) up & down
, & / (comma & slash) left & right
Use Cntrl+I to re-center.

If you're able to use the full range of motion with the keyboard it means it's a JS programming issue.

[mhbeney]

i will just add:

make sure you also assign the diagonal hat buttons to the target designator... i didnt have this and everytime i accidentaly moved the pipper at an angle, my view would jump up. (if u get what i mean)

so in summary.. if u continue scrolling down in the input/joystick/combat section there is also an option to assign;

Move target designator up/right
Move target designator right/down
etc...

FYI i have the target designator as SHIFT+Hat (with shift as leftshift button on my cyborg evo)

Martin

[StarWrecker]

Thanks, I found the problem - I was using the SST software to set everything but the axes already, but I somehow had the hat set to something else within LOMAC. I disabled the SST programming for the second hat, and I set it to the designator cursor ingame. It works flawlessly now, thanks for all of the help.