Closed GoogleCodeExporter closed 9 years ago
Disable logging, and you must use only that many gamapads as configured in ini
because because enumeration will cause high CPU usage, so if you use one
gamepad delete any other for ini, best - create new ini (delete it and run
config app).
Original comment by tapcio
on 16 Nov 2010 at 7:57
Please retest using x360ce Lib 32bit 3.3.1.361.
Original comment by tapcio
on 12 Dec 2010 at 11:10
Original comment by tapcio
on 20 Dec 2010 at 1:26
Yeah, same issue(Low FPS - Dead Rising 2 - FPS cut in half..), newest release..
(ie, x360ce.App-2.0.2.96.zip)
I have no idea what you meant by this..
"and you must use only that many gamapads as configured in ini because because
enumeration will cause high CPU usage"
I get "enumeration", and I understand .ini files, however, I have no idea what
you are trying to tell me to do with the .ini file.. I tried deleting
PAD2-PAD4, but that just caused problems, so I don't think that's what you
meant for me to do.. ?
Original comment by AmonBelo...@Hotmail.com
on 22 Jan 2011 at 1:32
PS: Here is a config for a PS2 controller ran via a "PSXTOUSB" adapter(Radio
Shack)... (This lacks force feedback\dead zones, I figure the end user can set
that up themselves..)
[PAD1]
ProductName=USB Joystick
ProductGUID=00030e8f-0000-0000-0000-504944564944
InstanceGUID=16093450-ee5f-11df-8001-444553540000
Native=0
Left Analog X=1
Left Analog Y=-2
Right Analog X=6
Right Analog Y=-3
Left Analog X+ Button=
Left Analog X- Button=
Left Analog Y+ Button=
Left Analog Y- Button=
Right Analog X+ Button=
Right Analog X- Button=
Right Analog Y+ Button=
Right Analog Y- Button=
D-pad POV=1
D-pad Up=UP
D-pad Down=DOWN
D-pad Left=LEFT
D-pad Right=RIGHT
A=3
B=2
X=4
Y=1
Left Shoulder=7
Right Shoulder=8
Back=9
Start=10
Left Thumb=11
Right Thumb=12
TriggerDeadzone=0
Left Trigger=5
Right Trigger=6
UseForceFeedback=0
FFBType=0
SwapMotor=0
ForcePercent=100
ControllerType=2
AxisToDPad=0
AxisToDPadDeadZone=256
AxisToDPadOffset=0
LeftMotorPeriod=60
RightMotorPeriod=120
Left Analog X DeadZone=0
Left Analog Y DeadZone=0
Right Analog X DeadZone=0
Right Analog Y DeadZone=0
RightTriggerDeadZone=0
Left Analog X AntiDeadZone=0
Left Analog Y AntiDeadZone=0
Right Analog X AntiDeadZone=0
Right Analog Y AntiDeadZone=0
---
(Also, please set "Console=1 to Console=0" by default, or at least add an
option in the .exe to toggle it on\off, it made it very hard to setup my
profile, because the cmd window kept popping up every time I made a change(ie,
buttons\dpad\etc).)
Original comment by AmonBelo...@Hotmail.com
on 22 Jan 2011 at 2:03
Sorry for the triple post... :(
A quick update, the problem only occurs if the .exe is running, when it's off,
the game runs fine, and the controller still works. (Logging was disabled, so
it must be something else, ie, COnsole=1, etc,..)
Thanks for working on this btw, it's a useful program, and I'm sure it will
come in handy for a number of newer games.. :)
Original comment by AmonBelo...@Hotmail.com
on 22 Jan 2011 at 2:38
exe is not needed to running in background when playing, is only config app.
Original comment by tapcio
on 22 Jan 2011 at 2:54
Still happening on the latest version. The performance decrease is very
noticeable in Just Cause 2. I'm not running the configuration application; I
only have the .dll and .ini in the game folder.
Any ideas?
Original comment by beswe...@gmail.com
on 11 Jul 2011 at 8:54
Disable all unused gamepads, r431 and newer should resolve this issue by
pass-trough all unused gamepads to native xinput instead of trying to enumerate
it.
Original comment by tapcio
on 12 Jul 2011 at 12:09
Original comment by tapcio
on 1 Sep 2011 at 9:07
Original comment by danialho...@gmail.com
on 16 Feb 2013 at 7:11
Original issue reported on code.google.com by
beswe...@gmail.com
on 16 Nov 2010 at 7:45