(11-12-2012 12:50 PM)Squall Leonhart Wrote:  can you screenshot the XBCD setup utility for me, your 360ce settings appear right.

Yep, here ya go. What 'cha think?

Nothing wrong there, Its possible you have a faulty controller, and only the PC/XBCD demonstrates it.
i've borrowed a bunch of official/third party 360 controls from friends to test and never seen this happen
Currently im using a Madcats MLG pad myself.

This isn't one of those usb wireless versions is it? - answering that myself, this controller is 100% wired.

You might want to contact Madcats and try to organise a RMA/Replacement under warranty.

VBA-M | NGOHQ | Post Impact Productions | TNHW | XBCD 0.2.7

Hey everybody,

thanks for this topic and i hope it´s not to late.
I have Win 7 64Bit with the original xBox 360 wireless controller.
x360ce is working and i can save the .dll files and i put these into the system32 folder,
but when i open joy.clp the trigger is on the same axis
What can i do?

Did i miss something?
Is there something more i need to modify?

The Problem is that Fifa 13 needs own axis for the Triggers.
So i cant play the game

Would be awesome if someone can help me.

Best regards!

   

   

   

in no way were you ever told you put the x360ce dll's into system directories.

and this forum addresses x360ce when used with XBCD, please utilise the ngemu x360ce board for support.

hi,
There is a very small issue with huge consequences related to xbcd (already tested the xbox360 controller with its ms regular driver and the issue is not present under such conditions)
(it is application independent also as i tested with different games and the windows calibration and xbcd config app):

when turning/cycling left stick right way on directions X and Y (from x=0 , -y=max to +x=max, y=o) the input tends to be received/written with imprecision.

that makes it very hard to use the sticks for steering
but the ms driver is not an option because of its merged triggers in brake/throttle:





when turned straight to +x=max or after few "small shaking" movements the axis input is written correctly

Please, how can I fix it?
(already tried scales, different axis assigned for the right stick etc)

and thank you very much for all of your work!

the common class driver has a deadzone of around 15 and 30% (left and right sticks respectively) hard coded into it.

it may also have a different threshold value before slight off center is measured as movement.

Different pads react differently to xbcd, the old s types tended to have lots of jitter without setting a deadzone of around 20%, where most 360 pads have a solid stick with very little jitter.

I'm still having trouble with the triggers, they're always pressed on x369ce and register as buttons 11 and 12.

http://vba-m.com/forum/Thread-x360ce-set...00#pid5500

VBA-M | NGOHQ | Post Impact Productions | TNHW | XBCD 0.2.7

x360ce is baffling me.

Even with the proper XBCD layout...


...and the proper settings chosen in x360ce...


...the emulator program still displays my controller as greyed out...


...which means it's not working properly. What's going on?

your xinput dll is invalid.

bottom right corner indicates a system version of xinput 1_3

VBA-M | NGOHQ | Post Impact Productions | TNHW | XBCD 0.2.7

(06-03-2013 02:48 AM)Squall Leonhart Wrote:  your xinput dll is invalid.

bottom right corner indicates a system version of xinput 1_3

Okay, and the solution to this is...?

Note that one of the games I'm trying to use the emulator for (Awesomenauts) already comes with a xiinput1_3.dll.

you replace the version it comes with, with the version xbcd comes with.

VBA-M | NGOHQ | Post Impact Productions | TNHW | XBCD 0.2.7

(06-04-2013 01:19 AM)Squall Leonhart Wrote:  you replace the version it comes with, with the version xbcd comes with.

Very well, but where is it located? Searching my C drive turns up two such files, one in System32 and other in SysWOW64.

then you aren't using a recent release of xbcd.

VBA-M | NGOHQ | Post Impact Productions | TNHW | XBCD 0.2.7