Chankast gamepad support?

[Optimummind]

I have the Saitek P880 digital+analog controller.

When I try to set the button config, I can only map the directional buttons to the analog stick but not to the traditional 8-way D-Pad. Is it b/c Chankast chooses the analog stick over the D-Pad by default when both options are detected?

If not, is there a way to map the UP, DOWN, LEFT, and RIGHT directions to my D-Pad instead of the analog stick? I tried hitting the "Digital" button on my controller to get Chankast to show D-Pad support but it didn't work.

Help me plz! It's hard to play with the analog stick.

[Optimummind]

Just saw in another thread about a program called "JoytoKey." I tried it but it doesn't work with my controller. Also, having JoytoKey on while running the emulator causes graphical glitches then eventually a crash.

[Velocity 7]

I have the same problem, man. The D-Pad is being referred to as the POV controls in Chankast, and can't be mapped to the usual D-Pad. My best guess is to use something like Wingman Profiler that allows buttons on the keyboard to be mapped to the POV, until Chanka or any other part of the development team implements a "D-PAD POV CONTROLS" type thing.

[Optimummind]

Ok, I got my D-Pad working. It's kinda of weird how it worked out though.

I bought a 4-port USB 2.0 hub today. I connected the hub to the mobo and connected the two gamepads to the hub.

Player 1 gamepad supports both digital and analog (this was the controller that wouldn't previously map to the digital pad). Player 2 gamepad supports only digital.

After hooking up these 2 controllers to the hub, I started Chankast. Surprisingly, the digital pads worked w/o me changing any settings.

[rich_is_bored]

Does anyone know where Chankast stores it's controller configuration settings?

I know Chankast.cfg only stores the drive letter. I've searched the registry for phrases like "P1 Analog X" and found nothing.

I'm using a Dual Shock 2 via a USB adapter and like alot of others I can't quite configure the controls like I'd like them. I'm pretty sure if I can find the place where this configuration information is stored, I might be able to edit it.

So far my efforts haven't been completely wasted. I found out how to rename the buttons on my controller so now all DirectInput applications report useful names like "Square", "Circle", "X", and "Triangle" instead of "Trigger", "Booster", ect. (I'll go into detail on that if anyone is curious.)

[Kanodin]

If you guys pay attention to their wevsite, their official forums, they say the next release is going to have a more user friendly controller configuration, compadibility so on so on. I wish them the best of luck.

[rich_is_bored]

I know all about the improvments I can expect in the next release.

I'm asking because until the next version is released, everyone has to make do with what they've got. I know we aren't all just sitting around waiting for the update to resolve our problems. The fact that people are hex editing CD images, instead of waiting for the next release, is proof of that.

In that respect, I'm not doing any harm asking if someone has found a workaround. I think it's far better that I ask around than pester the developers trying to find out when to expect the update.

[SlugZilla]

Are there any usb adaptor for DC controllers? I'd really like get my hands on one of those... especially if the VMU will work through it. I just have a knack for using the original controllers for their respective emus.

[rich_is_bored]

I only found one. I don't see anything in regards to reading VMUs and I think you'd be hard pressed to find an adapter that supports that.

http://www.lik-sang.com/list.php?nav...b&category=205

[astroduck]

Originally Posted by rich_is_bored

I know all about the improvments I can expect in the next release.

I'm asking because until the next version is released, everyone has to make do with what they've got. I know we aren't all just sitting around waiting for the update to resolve our problems. The fact that people are hex editing CD images, instead of waiting for the next release, is proof of that.

In that respect, I'm not doing any harm asking if someone has found a workaround. I think it's far better that I ask around than pester the developers trying to find out when to expect the update.

Just to let you know, the next release will be out next week so no rush.

[Grv]

Originally Posted by rich_is_bored

Does anyone know where Chankast stores it's controller configuration settings?

It's DirectX.. so: \Program Files\Common Files\DirectX\DirectInput\User Maps

[rich_is_bored]

I've seen these files before. They are the mappings DirectInput uses in general. They don't contain any program specific instructions.

For instance, here is my Dual Shock 2 configuration file...

[DirectInput]
DirectXVersion=0x800
Devices=VID_8631&PID_1128
[VID_8631&PID_1128]
VID=0x8631
PID=0x1128
Name=VID_8631&PID_1128
{67131587-3938-4857-8A2E-D99DC2C82068}.TimestampHigh=0x1C449E0
{67131587-3938-4857-8A2E-D99DC2C82068}.TimestampLow=0x1FF313E4
Controls=CTRL33554436,CTRL33554692,CTRL33554948,CTRL33555204,CTRL33555460,CTRL33555716,CTRL33555972,CTRL33556228,CTRL33556484,CTRL33556740,CTRL33556996,CTRL33557252,CTRL16777474,CTRL16777218,CTRL514,CTRL1282,CTRL16777986
[CTRL33554436]
Type=0x2000004
UsagePage=0x9
Usage=0x1
Name=TRIANGLE
[CTRL33554692]
Type=0x2000104
UsagePage=0x9
Usage=0x2
Name=CIRCLE	
[CTRL33554948]
Type=0x2000204
UsagePage=0x9
Usage=0x3
Name=X
[CTRL33555204]
Type=0x2000304
UsagePage=0x9
Usage=0x4
Name=SQUARE
[CTRL33555460]
Type=0x2000404
UsagePage=0x9
Usage=0x5
Name=L2
[CTRL33555716]
Type=0x2000504
UsagePage=0x9
Usage=0x6
Name=R2
[CTRL33555972]
Type=0x2000604
UsagePage=0x9
Usage=0x7
Name=L1
[CTRL33556228]
Type=0x2000704
UsagePage=0x9
Usage=0x8
Name=R1
[CTRL33556484]
Type=0x2000804
UsagePage=0x9
Usage=0x9
Name=Select
[CTRL33556740]
Type=0x2000904
UsagePage=0x9
Usage=0xA
Name=START
[CTRL33556996]
Type=0x2000A04
UsagePage=0x9
Usage=0xB
Name=LEFT STICK IN
[CTRL33557252]
Type=0x2000B04
UsagePage=0x9
Usage=0xC
Name=RIGHT STICK IN
[CTRL16777474]
Type=0x1000102
UsagePage=0x1
Usage=0x31
Name=LEFT STICK (UP/DOWN)
[CTRL16777218]
Type=0x1000002
UsagePage=0x1
Usage=0x30
Name=LEFT STICK (LEFT/RIGHT)
[CTRL514]
Type=0x1000202
UsagePage=0x1
Usage=0x32
Name=RIGHT STICK (UP/DOWN)
[CTRL1282]
Type=0x502
UsagePage=0x1
Usage=0x35
Name=Z ROTATION
[CTRL16777986]
Type=0x1000302
UsagePage=0x1
Usage=0x35
Name=RIGHT STICK (LEFT/RIGHT)
[VID_8631&PID_1128.Application.{67131587-3938-4857-8A2E-D99DC2C82068}.Genre.7]
NumActions=34
MapExists=1
CTRL33554948=0xFF004400
CTRL33555204=0xFF004401
CTRL33556740=0xFF004402
CTRL33554436=0xFF004403
CTRL33554692=0xFF004404
CTRL33556996=0xFF004409
CTRL33557252=0xFF00440A
CTRL33555460=0xFF00440B
CTRL33555716=0xFF00440C
CTRL33556228=0xFF00440D
CTRL33555972=0xFF00440E
CTRL16777218=0xFF004201
CTRL16777474=0xFF004202
CTRL16777986=0xFF004203
CTRL514=0xFF004204

I don't see any reference to Chankast.

[Grv]

In Chankast, you can apply a Windows username to your configuration, correct?
Let's say I choose klatch as the name, as it is one of the usernames on this Windows machine. Configurations have been made, I close Chankast, all is well.

In the before mentioned directory, there are files starting with X, but in my case, now also KLATCHX. One for my mouse, one for my keyboard (both easily identified), one for my Microsoft Sidewinder (10 buttons, which are found as Button 0 to 9 in the ini for my Sidewinder), and one for my Logitech Dual Action (12 buttons, which are found as Button 0 to 11 in the last ini, the one for the Dual Action).

The thing you posted in code is the way DirectInput maps buttons and axes. Believe it or not, but Chankast makes use of what you see. There is a reference to Chankast (I think), but you may not recognize it as it's not in an alphanumerical way assigned.

[rich_is_bored]

I'm aware that windows makes user specific maps. The file above is RICHARDX_VID_8631&PID_1128X_0.INI.

I know chankast makes use of this file. That's how it knows the names and type of each input on a gamepad or joystick. I know Chankast reads the file, but I don't think it stores anything here.

{67131587-3938-4857-8A2E-D99DC2C82068}

This is the only reference to an application or driver in the file. I'm not sure what it's referencing but since it's the only application reference in the file I'm pretty sure it's something related to DirectInput itself. Perhaps it's a reference to the joystick driver.

At any rate, these reference lines are not preceded or followed by Chankast's control map settings. It looks like that information is stored somewhere else.

I'm going to go get some tools from SysInternals to monitor Chankast when I make configuration changes. That should answer my question.

[Grv]

Suit yourself.

However, you'll only find out that..

[CTRL33555460]
Type=0x2000404
UsagePage=0x9
Usage=0x5
Name=L2

CTRL33555460=0xFF00440B

..is a a reference to the in Chankast programmed control that you bound to the L2 Trigger. And so on.

You must understand that Chankast is only like a profile to DirectInput, when it comes to control mappings. The creators chose to make use of DirectInput to store and configure it's controls. Saved them time on creating something of their own, I suppose. If I understand it correctly, 0xFF00440B is an address related to the Chankast exe. The address holds the actual value of the control you've bound.

I'm not 100% sure if this is how it works (with the address), since I've never done anything using DirectX and DirectInput. But it seems logical to me.


Edit:

Seems to me that this entire part of your file is about Chankast.

[VID_8631&PID_1128.Application.{67131587-3938-4857-8A2E-D99DC2C82068}.Genre.7]
NumActions=34
MapExists=1
CTRL33554948=0xFF004400
CTRL33555204=0xFF004401
CTRL33556740=0xFF004402
CTRL33554436=0xFF004403
CTRL33554692=0xFF004404
CTRL33556996=0xFF004409
CTRL33557252=0xFF00440A
CTRL33555460=0xFF00440B
CTRL33555716=0xFF00440C
CTRL33556228=0xFF00440D
CTRL33555972=0xFF00440E
CTRL16777218=0xFF004201
CTRL16777474=0xFF004202
CTRL16777986=0xFF004203
CTRL514=0xFF004204

If there is another program you've started that makes use of this, then you'll find another one of these beneath it, with different values for the addresses on the right side, and ID's in the first line regarding the application.

[rich_is_bored]

Okay, I see what you're saying now. Sorry if I was a bit stubborn. I wish you would have pointed out those references ealier.

I'll see what I can come up with. I just need to make sense of what each address is refering to.

EDIT:

Here is what I have so far ...

0xFF004400 = A
0xFF004401 = B
0xFF004402 = START
0xFF004403 = Y
0xFF004404 = X
0xFF004409 = JOY LEFT
0xFF00440A = JOY RIGHT
0xFF00440B = JOY UP
0xFF00440C = JOY DOWN
0xFF00440D = RIGHT TRIGGER
0xFF00440E = LEFT TRIGGER
0xFF004201 = P1 ANALOG X
0xFF004202 = P1 ANALOG Y

Now I just have to try setting them.

[Grv]

Sorry.

Anyway, here what's what for Player 1 controls:

0xFF004400 = DC's A
0xFF004401 = DC's B
0xFF004404 = DC's X
0xFF004403 = DC's Y
0xFF004402 = DC's START
0xFF00440E = DC's L Trigger
0xFF00440D = DC's R Trigger
0xFF004201 = DC's Analog X axis
0xFF004202 = DC's Analog Y axis
0xFF004405 = DC's D-Pad Up
0xFF004406 = DC's D-Pad Down
0xFF004407 = DC's D-Pad Left
0xFF004408 = DC's D-Pad Right

Hope it helps.

[rich_is_bored]

I did some plain text editing of the file. You just change the appropriate CTRLxxxxx line to equal the addresses posted above.

It works, but only in certain cases. Chankast only accepts values if they are considered acceptable button/axis/pov actions. It would work if I wanted to set my select button to act as the dreamcast's start button, because it is considered an acceptable button action. But, I don't see the point because if all I wanted to do was assign valid values to the control scheme, I'd use Chankast itself.

For example, in my case, I'd like to set the D-Pad up to work with the right analog stick. So I change my right analog stick's X and Y Axis to control JOY LEFT, JOY RIGHT, JOY UP, and JOY DOWN.

But, since neither the right analog stick's X or Y axis are acceptable "Button Actions", and are instead "Axis Actions", Chankast nulls those controls out.

It looks like there is no workaround and you have no choice but to wait for the next release. At least it's comming out sometime next week (hopefully).

[Grv]

I could have told you that aswell. I thought you couldn't configure your controls at all or something like that. Sorry about that.