Jump to content

Recommended Posts

Posted

I recently tried to map the rotary encoder to the trim function, but it didn't work, because the function was directly mapped with some random button. Just like there were some button constanly activated, but there isn't. So i tried to map a normal on/off switch to the function, but that didn't work either. Same behaviour as decribed above. I should mention that everytime i try to assign the function a different random button gets mapped. For example button 49, button 52, button 34. I don't even have that many buttons icon_smile.gif

 

Plasma lite axis work perfectly with lockon. Also i don't have any problem in other games.

Is there any known bug with lockon or incompatible issue? I'm using lockon 1.12a flaming cliffs.

 

Screen from the controller menu.

http://www.web109.server-drome.org/lockonbutton.jpg

 

Controller: Plasma Lite V2 from betainnovations.com

Posted

What about the cockpit builders? What usb devices do they use to connect multiple buttons? Did they experience any problems?

How many buttons per device does lockon support?

 

I just want to know if there is problem with lockon or with my controller. Since i don't have issues in other games it is likely there is a problem with lockon.

Posted

I use USB controller that can have 8 axis and 32 buttons and 1 HAT switch but I don't have this problem. I'm using normal electrical toggle switches for buttons.

No longer active in DCS...

Posted

no its not, its a common problem for all X-52 users. Please do not map out your joystick in the lock on options menu. Its not efficient since you are not taking advantage of all 3+ modes. Map it out through the SST software for the X-52.

[sIGPIC][/sIGPIC]

Posted
no its not, its a common problem for all X-52 users. Please do not map out your joystick in the lock on options menu. Its not efficient since you are not taking advantage of all 3+ modes. Map it out through the SST software for the X-52.

Do you mean the x52 causes this problem?

I'm using the sst software to map the buttons* of my joystick and i already uninstalled the x52 software, but it didn't help.

 

*Some buttons were by default mapped to the x52. I will fix that tonight and see ift it helps.

Posted
I have the same Controller. What Software do you use, to map Buttons and Macros (Alt+Key...) on a Button of the USB Controller. Yoy2Key only can map one Button?!

 

I don't use any software for it... I use it as simple directx buttons

No longer active in DCS...

Posted
no its not, its a common problem for all X-52 users. Please do not map out your joystick in the lock on options menu. Its not efficient since you are not taking advantage of all 3+ modes. Map it out through the SST software for the X-52.

 

Okay i deleted all mappings regarding the x52 in the controller menu, but unfortunately the problem still occurs. Can you tell something more about the x52 issue?

Posted
Originally Posted by grandsurf viewpost.gif

I have the same Controller. What Software do you use, to map Buttons and Macros (Alt+Key...) on a Button of the USB Controller. Yoy2Key only can map one Button?!

 

JoyToKey accepts up to three keys for each button, ie: CTRL+Shift+1

SVMapper accepts one key for each button plus modifiers, ie: LShift+1

 

S!

 

Sokol1_Br

Posted
Okay i deleted all mappings regarding the x52 in the controller menu, but unfortunately the problem still occurs. Can you tell something more about the x52 issue?

 

 

This is the case with the X-52 joystick with lock on. If you go into the options menu and try to map out a key, it would always jump to button 33 or 34 because that is the wheel function. The only thing you can do it map out your axies function. For keys, once you install the X-52 driver, and the SST driver, then map out your keys in the SST program. Tell me which driver you are running on and I'll just send you my profile.

[sIGPIC][/sIGPIC]

Posted
This is the case with the X-52 joystick with lock on. If you go into the options menu and try to map out a key, it would always jump to button 33 or 34 because that is the wheel function. The only thing you can do it map out your axies function. For keys, once you install the X-52 driver, and the SST driver, then map out your keys in the SST program. Tell me which driver you are running on and I'll just send you my profile.

 

Yes, button 33 and 34 are familar to me...also i get button 53 and 54 by trying to map a button to my USB controller.

I know how to use the SST programm and i use it to map different functionss to the x52 keys. But i also want to make use of my USB Controller (Plasma Lite) to add even more keys. And this doesn't work. As far as i understand you this issue refers to the x52 which seems to be a very dominant^^ controller that doesn't accept any other device around.

Now what i need is a solution to operate both controller at the same time.

Posted

you should have 4 input devices in LockOn settings for Input

 

1. Keyboard

2. Mouse

3. X-52 (or what ever name it comes under)

4. your USB controller

 

you sellect your USB controller under DEVICE then map its buttons... is this what you're trying to do in the first place and it doesn't work? Other than that if you're using some software to programm your USB controller to emulate keyboard then you should have nothing mapped to it in input settings.

No longer active in DCS...

Posted
you should have 4 input devices in LockOn settings for Input

 

1. Keyboard

2. Mouse

3. X-52 (or what ever name it comes under)

4. your USB controller

 

you sellect your USB controller under DEVICE then map its buttons... is this what you're trying to do in the first place and it doesn't work?

I know how to setup a controller, it just doesn't work for my USB device. I go into the input menu, chosse my USB controller, pick a function for example "Autopilot" and then press change. Usually a small window opens now which says somehting like "Choose your button" and then you press that specific button and you are done.

But in my case the small window opens and instantly is closed again and mapped automatically to a random button (mostly button 34, 35 or 54, 53). This behaviour occurs only with my USB controller.That's the problem. Axis mapping works fine.

Posted

hm... and those buttons 34, 35 etc are of USB controller? Are there maybe any buttons what are constantly pressed? Did you wire the buttons yourself or is everything already preassambled?

No longer active in DCS...

Posted

I have a USB Hub and had problems when I put in the new USB hub with my Saitek X52 Pro and Saitek Pedals. This is what I did to fix it. I unistalled alt he Saitek software. I cleaned al the Saitek files using the procedures:

 

http://www.saitekforum.com/

 

I then installed the Saitek SST software and Drivers while the staick and pedals were connected throught the D-Link 8 connector self powered (plug in the A/C power adapter to the hub ) Hub. I had no mpre oblems with those parts. I am now kind of pissed waiting for the Next Beta or hopefully Saitek final version of software and drivers. :joystick:

ASUS Strix Z790-H, i9-13900, WartHog HOTAS and MFG Crosswind

G.Skill 64 GB Ram, 2TB SSD

EVGA Nvidia RTX 2080-TI (trying to hang on for a bit longer)

55" Sony OLED TV, Oculus VR

 

Posted
hm... and those buttons 34, 35 etc are of USB controller? Are there maybe any buttons what are constantly pressed? Did you wire the buttons yourself or is everything already preassambled?

 

I don't think they are from my usb controller because there are only 24 buttons supported (without extension card). Also there is no button which is constantly activated. I guess it is some issue with the x25. Wiring etc is perfect. Lockon is the only game where the problem occurs.

 

@Rammstein

I think you had a different problem than me.

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...