fraser125 / x360ce

Automatically exported from code.google.com/p/x360ce
0 stars 1 forks source link

Unity engine compatiblity #1054

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
any upfates on that?
or is it never gonna happen?!

Original issue reported on code.google.com by agent22...@gmail.com on 3 Dec 2014 at 3:02

GoogleCodeExporter commented 9 years ago
Never happening.

Original comment by danialho...@gmail.com on 3 Dec 2014 at 6:28

GoogleCodeExporter commented 9 years ago
well im sure you know better.
keep up the good work guys

Original comment by agent22...@gmail.com on 3 Dec 2014 at 5:08

GoogleCodeExporter commented 9 years ago
Please test attached file in Unity3D games (x86).

Original comment by tapcio on 3 Dec 2014 at 6:53

Attachments:

GoogleCodeExporter commented 9 years ago
@danialhorton
Never say never ;p I think it should be possible because on some level managed 
functions should call unmanaged ones.

Original comment by tapcio on 3 Dec 2014 at 6:54

GoogleCodeExporter commented 9 years ago
PS: Can anyone check if combase.dll is loaded to process (use Process Hacker: 
http://processhacker.sourceforge.net).

Original comment by tapcio on 3 Dec 2014 at 6:56

GoogleCodeExporter commented 9 years ago
Tapcio, Unity Engine uses neither Xinput or Dinput, unless the developer 
specifically implements these, and if they do then x360ce should natively work 
with maybe hookcom necessary for function.

However, the only thing the base unity engine supports now via xinput is 
vibration functions.

There's nothing an xinput wrapper can do (unless we stoop to injecting the 
logic of a xbox 360 controller's driver)

Original comment by danialho...@gmail.com on 4 Dec 2014 at 3:35