C# Xna Made Easy Tutorial 6 - Controller Input Video Lecture | C# Game Development: Game Making made Easy (English)

you
hello everybody and welcome to your next
XNA tutorial now this one is going to be
a lot cooler than your first I'm
keyboard input tutorial because now it
is on the gamepad tutorial or that xbox
360 controller tutorial now this there's
always something about the controller
that just makes things cooler when you
can play games with your controller just
adds that amazingness to it just because
you can use your controller so right now
I'm going to be showing you tutorial
about using the gamepad or xbox 360
controller or whatever right now I'm
using something called motion joy the
gamepad tool and since it's for XNA I
set it to xbox 360 controller emulator
in fact i'm using a ps3 controller
because real and reality out like xbox
that much so i have a ps3 but i'm using
if you look right here i'm using a ps3
controller and I'm i said to xbox 360
controller emulator and i had to
download all my patch or plugin or
something xbox 360 device thing driver
or something so that neighborhood
recognizes the xbox 360 controller
there's enough to toys on the internet
for you to search up about it so I won't
tell you about it so um it's enabled set
xbox 360 controller so now our what this
is the same code as last time everything
the same except i put rectangle and i
put player 1 and player 2 and you'll see
my use for this later
so the initialize method is the same
load content method is the same and our
update method has changed so just like
um our other tutorial normally I would
clear gamepad arm state pad 1 normally I
would declare it arm over out here just
like I the credit keyboard state right
but it doesn't really matter where I
declare it I'm declaring it update mess
and update method and I put gamepad
state pad 1 is equal to gamepad cat
state now the difference with this dog
cat state is that you have to specify
which control the number you want to get
the state for because you can't get this
day for it you can't try and get it from
every single controller you have to
declare which controller you want so you
do play index dot 1 to control the first
controller so um this is this is another
thing too that I met I forgot to mention
in my last tutorial for the key state
arm when you do that gets that gets stay
home with my back key state equal to
keyboard dock at state there's an
overload function that also can get
player index and that's in case the
person has a chat pad and you want them
to be able to use a chat pad to do
certain things as well then you can
declare which player index it is but
normally that's if you're making just an
xbox 360 specific game so anyways arm
right now we're getting the state of
controller number one so I said pad 1
dot d-pad dot right is equal to button
state pressed so if the right button is
being pressed then we want to move X
towards the right and this code
same code is the last tutorial so I do
not need to blame this so basically if I
click the d-pad the right bone on the
d-pad then you move towards the right
same with if i press the d-pad left we
move towards the left if i press it up
you move up and if i press it down you
move down towards the screen de troyes
the bottom of the screen simple enough
and if you want to see a lot of this
functionality you can go on the
Microsoft website or you can do pad one
and you can see you could check the
different buttons if like if you want
button um a is pressed or all my
laptop's almost dead I'm going to pause
it for a second to get my charger okay
I'm back so as I was saying that you can
use these arm keys pad one to check if
the actual controller is connected
before you even do something with it um
thumb sticks oh I guess that'll be the
analog sticks i believe and you can
check if the button is up or if the
button is down just like you do is key
up or is key down but um you could do
button state that pressed also and also
the keyboard state I think has um
something state dot pressed also i'm not
sure if or has it don't quote me on that
you can research that but it's just
showing you that there's different
methods of going about different things
when it comes to programming there's
never one set way to go about something
in programming there's always multiple
ways to do one thing and it's always
good to learn multiple ways because if
you get trapped in one way then you can
use an alternate method right so that's
a real good lesson to learn a real good
skill to them so anyways about the
player one and the player to basically i
put a rectangle around each of my images
as um yeah one of these rectangles and
we learned about rectangles and tutorial
for belief and basically the rectangles
run
Shin got X you have to put the ink cast
because um rectangles deal with integers
but our vectors deal with floats and
doubles and stuff so you have to set the
cast to end superposition got X for the
position position not why for the
position and for the width is the image
the actual image width and the images
height and same for plan number two we
do position to x position to da y and
get the width and the height since at
the same image right so another good
thing is that we have vibration now on
the xbox 360 controller the ps3
controller all those controllers
contained vibration and then certain
moments in your games white might want
you control it to vibrate either if you
want to create a suspense moment or when
you collide with something you want it
to vibrate so right now arm in the my
vector xand rectangles tutorial it's
coming tutorial number four I was
teaching about different functions of
the rectangles and the vectors and are
one of them I believe was the intersects
method and if I never showed you this
one doing this is a special method
between triangles so basically i put
player 1 dot intersects player too so if
the first is the first play of rectangle
intersects with the player to rectangle
then that means you have a collision if
not then you don't have a collision so
right here you see something says game
pad set vibration right and all
basically I'm um this there's three
properties within this method so you put
several raishin the first one is obvious
player index one the controller number
you want to vibrate arm this is the left
motor arm you can put a number between 0
and 1 right like you with 0.1 0.2 0.1
ever ever between 0 and 1 and that is on
the left motor is for low frequency
motor and the same thing for this side
you could put between 0 and 1 and this
is for the high frequency motor and if
you all know that means you could test
both amount with your xbox 360
controller I don't know if you could
hear with my controller but basically
you would you can hear a difference and
feel the difference in the two different
frequencies and if you want both them to
go off you can do both get set both 21
so another thing about vibration is that
when you turn on the vibration it's a
good habit to turn it off also and in
your exit or meth or when you when you
click the exit it you should make
another thing to make the vibration stop
in the old x-mas it didn't stop by
default so if you were to exit the
program and not stop the vibration then
we'll keep on vibrating until you stop
it with the program now it has a
built-in method I believe in the exit um
method in order to stop the vibration
but just to be on the safe side you
could still do it anyways or to make it
more compatible with other x-mas anyways
let's continue so basically when the
player collides with player number two
we want the controller to vibrate and
then when it is not come like when it
hasn't collided then there's no
vibration involved so that's basically
it so let me run the controller I mean
run the game and I'm going to be playing
my controller so I'm pressing right on
the d-pad and when I go to hit the
player my controller vibrates and I know
you can't hear it but my control is
vibrating when it touches the player
right and that is it for the two toy
oh thanks for watching hope you really
enjoyed this and I hope you look forward
to the next tutorial thanks for watching
and bye