PlayStation Development Network

Hello everybody, I have a question:
How to get controller state?

For example:
if PadStateFindPad = PAD_ONE {
box_a = 1;
}

else if PadStateFindPad = PAD_TWO {
box_b = 1;
}

else {
box_a = 0;
box_b = 0;
}

Or if there's a documentation, then post it here! Thanks in advance!

The simplest way to read controller input is through PadInit() and PadRead the latter of which would return a bit field of button states which you can mask off using PADL<direction> and PADR<direction> definitions. The more advanced way of reading controller input that also allows you to control the vibration motors is PadInitDirect() and PadStartCom().

Documentation of such functions are found in the libref PDF document and there are a number of sample programs (including my old ones) on this forum that use it. Details regarding the use of the advanced method of reading controller input is described in the libovr PDF document.

PadInit() Initializes Controller, and I want to know how to get Controller Slots! Example:

If PadPort1FindPad() {
port_a =1
}

If PadPort2FindPad() {
port_b = 1
}

Rhetorical question: did you bother to check the documentation LameGuy addressed you to?

LIBREF46.PDF, page 789 wrote: int PadGetState(int port)
[...]

Return value:
[...]

Value     Macro (libpad.h)          Controller connection state
0           PadStateDiscon           Controller disconnected

It took me literally 5 seconds to find it

I tried this:

ret_a=PadGetState(0);

switch(ret_a) {
case PadStateDiscon:
con_a = 0;
case PadStateFindPad:
con_a = 1;
}

ret_b=PadGetState(1);

switch(ret_b) {
case PadStateDiscon:
con_b = 0;
case PadStateFindPad:
con_b = 1;
}

But it shows an error like "Unknown opcode BFC0506C at 00008548" and that's in emulator!

That's a rather redundant way to check if controllers are connected, I'd advise to replace it with this: Notice that I used 0x10 since that's the correct code for pad 2 (you used 1 which is actually the code for Multi Tap B).
If it still gives an error you'd better host your project as an attachment, it's hard to say what's exactly causing it otherwise(might as well be something completely unrelated to this).

Still gives an error!
Here's the signature!
There are some codes that are used for STR and XA Files! Delete them first!

OK, it looks like PadGetState() isn't liked by emulators at all - the best I could achieve was with no$psx using an original BIOS instead of nocash BIOS clone and it gave no errors, but still freezes at a black screen nonetheless :/

I'll try it on a real psx tomorrow and see what happens.

No need to do that! Now it works! I need to use PadInitDirect First! Otherwise the game crashes! Thanks for helping me! And I'm sorry! You know I'm aproximatelly noob at coding and I still know how to code, cuz I learned! But I didn't know PadInitDirect must be used!

Ah, glad you sorted it out It could've been deduced from LIBOVR46.PDF that PadGetState is meant to be used with PadInitDirect and not with PadInit(even though it wasn't specified in an explicit manner), but I didn't read it thoroughly enough to figure that out

As for the noob part, that's alright - the fact you try to solve issues on your own rather than waiting for someone else to do everything for you is a good sign
If I may give some criticism I'd suggest you try to keep your code a little bit more tidy (prototypes not matching functions' definitions, PadInit() getting called twice, cluttered-up code, etc), but I suppose that will come later on with experience

Yes, anyway! I have one more problem: When I remove controller 2, the second box is not disappearing! I also tried with PadStateStable and PadStateFindCTP1, But everything is disappearing! How to fix this?

Example of code:

ret_a = PadGetState(0x00);

switch(ret_a) {
case PadStateDiscon: /If it's disconnected
con_a = 0; //The First Box disappears
case PadStateFindPad: //If it's connected
case PadStateStable: //If it's a Dual Shock Controller
con_a = 0; //The First Box disappears
case PadStateFindCTP1: //If it's a Normal Controller
con_a = 1; //The First Box appears
}

ret_b = PadGetState(0x10);

switch(ret_b) {
case PadStateDiscon: //If it's disconnected
con_b = 0; //The Second Box disappears
case PadStateFindPad: /If it's connected
case PadStateStable: //If it's a Dual Shock Controller
con_b = 0; //The Second Box disappears
case PadStateFindCTP1: //If it's a Normal Controller
con_b = 1; //The Second Box appears
}

if (con_a == 1) //Create the First Box
if (con_b == 1) //Create the Second Box

If the code's structure hasn't changed from the project you hosted it's pretty easy to figure out the issue:
That piece of code is located in initialize(), which means it's executed only once at startup and never executed again; try moving it at the beginning of update() (or create another function specifically for that piece of code, as long as you place it inside the infinite while(1) loop it doesn't really matter) and see what happens.

Oh also, your switch blocks lack breaks, which means that no matter which values ret_a and ret_b hold, it will always fallthrough below the correct case statement and eventually execute con_a = 1 and con_b = 1, respectively.
Here's how you should fix it:
Same thing for the switch(ret_b) block.
I allowed PadStateDiscon to fallthrough PadStateStable since they both set con_a to 0, so it's not a mistake .

Thank you! It worked perfectly! Now I'm ready to show the example! The example contains XA + STR Playback and controller detect! Is it good to post it? And where can I post this?

I suppose that the Examples (Psy-Q) section should do.

As for whether it's good or not to post it, that's highly subjective - I for one would say to go for it and let people judge for themselves (even though like I said in a previous post the code is a bit messy and with a lot of room for improvement, but all in all it's quite understandable )

Ok! Thank you! I'm going to post the example! And report if you got issues!

There's heaps of controller examples from Sony in the Psy-Q SDK. You gotta' tweak them to suit your needs, but they do work well. It becomes extremely messy however once you start adding in the Multitap, DUAL-SHOCK, Lightguns and other peripherals including the Memory Card (those are a bit of a nightmare to handle).