I use a USB controller to play GC and I went on a hiatus for a few weeks. Now that I'm back I discovered that my USB controller won't work for GC anymore. I know it's working because when I open up a notepad and use the controller to press certain keys like "z" it works. But in GC it won't move the character at all. Anybody else get this problem?
in GCPH u can use two(2) contoller
like keyboard and psp joystick controller
i quit using joystick so im not updated on it
i think its the configuration program that you are using
you must have a program that will configure the joystick
i forgot where to download that .. keep browsing the forum
I know the program. It's called joy2key. I have that updated always with my Grand Chase config files. But now it won't work with or without the program.
Dude I just stated that everything on my pc is always updated. :/
It's weird. Coz I'm using a CD-R King controller for my PC. It used to work just fine. But now it just won't work for Grand Chase.
I think that maybe Grand Chase is blocking Joy2key or something. Can anybody recommend a different macro program that would be easy to set up with a USB Controller?
All of them were not working anymore... 12/12/2009 - Soldier Front Philippines - 2 Replies wahhhh..... waht's the matter with all those cheats?
all them were detected....
wooooshhhhh....
hayyyyzzz......
:cool:
ALL CR AND CB ARE NOT WORKING ANYMORE 07/12/2008 - Cabal Hacks, Bots, Cheats, Exploits & Macros - 23 Replies this is no question threads ahah :D
so dont be rude :D
all Cr and Cb are not working anymore so cabal rider team will do something to have a new version .. i dont know when :D
cabal RIDER team go for more bot
SV Not working anymore 08/01/2007 - Conquer Online 2 - 15 Replies I dont know why, if its a new autopatch or something, but I had the cracked sv 1.15 running last night, and it was running fine, now i turn it on this morning, and it gives me an error message, so I restarted scriptvessel and cheat engine, and tried again and it still gives the error message. Maybe this is from an auto patch when I turned it on this morning? I'll restart conquer and try again, but is anyone else having this problem as of today ?