razer onza game pad issues

sorry for some reason i can't post a new thread on support. i am quite novice at this kind of stuff and was wandering if anyone else was having issues utilizing their gamepad. if so was there a fix or do i have to just try another controller?

i screen captured the console. towards the bottom of the screen it shows my gamepads "unbinding" failed. i tryed updating the drivers but it just uses the standard xbox 360 drivers anyway so that didn't change any thing. i seriously just don't
know what else to do.
from the small amount that i played off of the keyboard i can tell this is an awesome game/simulator and would love to give'r a go as its meant to be played. any input or advice would be appreciated, I'm sure im not gonna be the last bloke to
run into this issue

 

I am having the same problam with my Razer Onza let me know if you find a solution.

 

bump.

5char

 

i have same issue with my ps3 racing wheel so far log shows it loaded the input map but at the top it shows:
2.743314|*** gamepad0 ***
2.743369| (unbinding...)
2.743434| *** unbinding failed!

that's the only thing i can find that would be causing the my wheel not to work in game. So far this is the first game it has failed to work with.

 

I have discovered a solution to my Razer Onza issue and hope it will help everyone else as well. Just create the folder "custom" on C:\Users\...\AppData\Local\BeamNG\BeamNG-DRIVE-0.3\scripts\client\inputmaps" and put the following inputmap inside:

 

i followed the steps and unfortunately it didnt work . oh well ill just pickup a cheap logitech or something

 

The way I solved my problem was I checked the console, and it said in bright red what file it was trying to load to get my xbox360 controller (razer onza) to work. All I did was change the config file name to the one it was trying to load and put it on the directory it was showing on the console. Quite simple really, and I am pretty sure it will solve other controller related issues.

edit: after observing more carefully your screenshot I've realized that the errors appear to be different on your side. My apologies for not having noticed it before. Quite strange, according to your console your game-pad should be working as it is almost identical to mine. Good luck to you

 

Okay, so, first, go here: http://www.beamng.com/threads/1473-Post-Your-Inputmaps!?p=22610#post22610 and download my attachment.

Next, take a look at this.



This is all your information.

In the template, replace the product name with EXACTLY what you see in this.

Then, do the same with the GUID.

After, rename the Template to what it says in the bottom of my attached screenshot. You can place it in BeamNG-DRIVE-0.3\scripts\client\inputmaps

This should work for you! If not, come back and we can continue trying to help.

EDIT: Actually, I've done you a solid, and plugged it all in myself. TAKE MY ATTACHMENT!

 

AWESOME!!!!! this worked perfectly and just for the ultra computer nuuublets such as my self when renaming the input map dont put .cs on the end cause thats the file type and not the name. the directory will auto input that. im ashamed to say i did that twice. but seriously thank you guys

 

THANK YOU!

 

Not working agian after the update

 

Yup, same. Looking for an answer if anyone can help

 

I had to modify the thumblx line to say steer instead of joy_steer and it worked for me.

 

i hoped it will get resolved later, but still my razer onza is not working, would be cool if you could fix it before final release guys

 

Why did you do a gigantic bump.

 

sorry , found this thread on google didnt notice dates.

 

The onza does work with a custom inputmap, although it seems the next update may alleviate the need for these entirely (fingers crossed)

 

yeah i have it working on my old non-steam version of the game, but on the new steam version it still doesn't work(i hoped it will).I know i can edit inputmaps again but im too lazy and im sure everyone else who will buy the game later will be too(or just not that skilled)

 

The steam version is identical to the non steam version so the custom inputmap you had before should work fine when added to your steam install.

 

Don't apologize. You did the right thing posting in an old thread containing your issue. Much better than making a new one for the same issue.