Closed GoogleCodeExporter closed 9 years ago
I have the same issue both on Windows XP SP3 and Windows 7. I use a Logitech
Dual Action.
Original comment by kthoma...@gmail.com
on 12 Jul 2010 at 11:17
Onlive will never be supported because is nothing to support - games are run on
server ...
Original comment by tapcio
on 14 Jul 2010 at 7:00
Yes but the onlive system runs a process that detects the xinput device and if
you do not have one tells you "your gamepad is not supported" when launching.
meaning that in some fashion it is looking for either the DLL file that you
software produces in another directory, or is looking for the device in the
attached devices list, either way it is a strong candidate for your team to
look into as it gives your software the ability to be used on a up in coming
system. Just my thoughts.
Original comment by kthoma...@gmail.com
on 18 Jul 2010 at 6:11
If I may clarify kthomasms thoughts- even if it's rendered on the server
doesn't this require xinput from the local exe program?
And, pretty please with bacon on top?
Original comment by indoler...@gmail.com
on 18 Jul 2010 at 7:00
Sorry to be a troll but tapcio your full of crap. OnLive uses xinput 1.3 like
any other "game". OBVIOUSLY there is client software running and OBVIOUSLY it
must get input from the controller. Please mark this bug as active again as it
seems that the problem is that X360CE does not satisfy the requirements that
OnLive uses to check for a 360 controller when XInputGetCapabilities is called.
Here is the inner log file (that is the one from the
C:\Documents and Settings\wilahti\Local Settings\Application
Data\OnLive\clients\228.54793\x360ce_logs
directory where the client DLL is actually loaded from (not the launcher, which
is only used to download and load the client DLL):
16:29:51.53724750:: x360ce started by process OnLive.exe PID 8564
16:29:51.53725062:: XInputGetCapabilities send type 1
It ends there, and moments later OnLive displays the controller not supported
error. Either OnLive is discarding the available XInput device for some reason
and complaining about the HID device, or the XInput device emulated by X360CE
does not claim to offer the correct capabilities.
I have tried with the fake API option and the proper vendor/device IDs as well
to no avail.
Original comment by wila...@gmail.com
on 27 Jul 2010 at 8:55
same error with widows 7 and onlive, if I put the ddl onlive don't warm me
about my icompatible joystick but if I remove dll onlive warme about my
Joystick is no compatible. But in both case the joystick don't wok
Original comment by victor.g...@gmail.com
on 2 May 2011 at 5:37
Original comment by tapcio
on 2 May 2011 at 5:48
@Comment 5 by wila...@gmail.com, Jul 27, 2010
I marked this as invalid because issue report is indeed invalid (no log etc.
pure guesswork).
Original comment by tapcio
on 2 May 2011 at 5:53
You marked it as invalid because you didn't understand OnLive.
I poop on your crappy project management skillz.
I don't care, I bought a controller anyway.
Original comment by wila...@gmail.com
on 2 May 2011 at 10:47
[deleted comment]
If your theory is correct, then all onlive would consist of is a video player.
You wouldn't be 'playing' anything other then a video stream, and you would
have absolutely no control over the games you're playing. You might as well go
to youtube and start playing gameplay videos.
Instead, what happens is OBVIOUSLY THERE IS CLIENT SIDE CONTROLS. If you cannot
understand such a basic task because you read 'server side gaming' then that is
your fault, and you should not be in moderation if you cannot understand such a
basic functionality.
So in turn, onlive application is launched, captures keyboard, mouse and
gamepad buttons and sends them to the server. Then server sends back a image
stream and you have video that you can control. So in order to add 360 gamepad
emulation all you have to do is get onlive to think you have a 360 controller
and it will capture your real gamepad buttons client side, then send them off
to the server and you play normally.
Original comment by halflife...@gmail.com
on 3 May 2011 at 12:27
Regular games work client side as well, wouldn't you know? They do the same
thing and capture the buttons and key presses and then your character does
whatever the button is supposed to make them do. And this is how x360ce
functions is it sends 'fake' button presses of a genuine 360 controller and
because the game is looking for 'real 360' button presses, it captures them and
then allows you to play with a non genuine 360 controller.
There is no reason for this to not work with onlive and yet, it doesn't. It's
not capturing the proper 360 controls that x360ce is sending when it should,
onlive is supposed to support all sorts of 360 controllers and yet it's not
functioning as it should.
Original comment by halflife...@gmail.com
on 3 May 2011 at 12:30
And lastly, considering you're the supposed owner of x360ce, you really are a
embarrassment to a 'coding group' if you cannot grasp such a basic concept as
to how a application like onlive works [Client Side\Server Side] when you
supposedly coded a entire 360 CONTROLLER EMULATOR BY SCRATCH? Genius.
Original comment by halflife...@gmail.com
on 3 May 2011 at 12:32
I'am student, and this project is my hobby only, I have no much time/money to
search for strange apps and test it, so ANY issue WITHOUT LOGS WILL BE DELETED
INSTANTLY.
OnLive is strange app, and WILL NOT BE supported because of code protection
(seem to by using PC Guard).
Last, better buy better PC and buy games from steam, I do not think to play any
game in such way because of lags!
If you do not like it DO NOT USE IT! Or write you own better !
Original comment by tapcio
on 3 May 2011 at 9:50
I think halflife was too hostile in demanding service for a product you are
providing freely and maintaining in your own time. That said I don't understand
all of your objections to looking at the issue.
Wasn't a log posted in comment #5?
Doesn't make sense for someone to "buy better PC" to solve this problem. It
would be a lot cheaper just to buy a real X360 controller. The value of your
emulator is for people that already have a fine controller that is being
ignored by the developers writing code optimized for console game systems.
You may not find a personal use for Onlive, but it opens up ways for people to
play when and where they want to without incurring additional hardware costs.
Hey, that sounds a lot like the value proposition for the X360 controller
emulator.
It's also a useful system for demoing games that you don't yet own, since every
game lets you play for an hour at a time without saving progress. You can do
that an unlimited amount of time with no download, requiring much less
bandwidth than a traditional demo. So there could be a reason to use the
service even if you don't intend to buy.
Finally, Onlive is a viable choice for people that need to live and travel with
smaller PCs like netbooks. You don't expect them to buy and carry around a
gaming tower with two video cards, cooling system, and etc, do you? Think of
how many students like you are living and sharing space in dorms and etc.
The only real barrier may be that code protection you mentioned. No way to
tell.
Anyway, the controller emulator works well in many situations. I still hope you
will someday accidentally fix compatibility with Onlive while making other
improvements.
Original comment by JBor...@gmail.com
on 21 Oct 2011 at 7:52
I have objections, because OnLive is protected by custom DRM system, so making
hooks to work with this protection is not possible at all without violating
OnLive license.
So not blame x360ce developers for not supporting custom DRM protected OnLive,
blame developers/publishers for using DRM !
Original comment by tapcio
on 21 Oct 2011 at 8:22
Issue 252 has been merged into this issue.
Original comment by tapcio
on 20 Jan 2012 at 12:35
Because of this issue, I don't believe that I will put much more effort of
trying onlive, I won't buy a 360 controller, I already have a logitech dual
action one, that suits my gaming needs at it's best, why would I need to buy a
x360, because of onlive? C'mon, it's ridiculous.
Original comment by barkley...@gmail.com
on 29 Dec 2012 at 4:13
Original issue reported on code.google.com by
indoler...@gmail.com
on 11 Jul 2010 at 12:03