Patent Description:
Handheld controllers are used in an array of architectures for providing input, for example, to a remote computing device. For instance, handheld controllers are utilized in the gaming industry to allow players to interact with a personal computing device executing a gaming application, a game console, a game server, and/or the like. Handheld controllers may find use in virtual reality (VR) environments and may mimic natural interactions such as grasping, throwing, squeezing, etc., as much as possible. While current handheld controllers provide a range of functionality, further technical improvements may enhance user experiences.

<CIT> discloses a system for adapting input/output operation of an electronic device for left-handed and/or right-handed scenarios. Sensors are applied to respective outer edges of a device to determine whether a device is in a user's left hand and/or right hand. Based on this determination, respective points along the sensors can be mapped to soft keys to automatically optimize input for left-handed and/or right-handed operation.

<CIT> discloses a game controller with a communications interface, at least one touch sensitive pad having a plurality of touch sensitive elements, and processing circuitry coupled to the communications interface and the at least one touch sensitive pad.

<CIT> and <CIT> disclose handheld input devices.

Described herein are, among other things, handheld controllers having touch-sensitive controls, methods for using outputs of the touch-sensitive controls, and methods for dynamically adjusting the touch-sensitive controls based on a hand size and/or grip of a user operating the handheld controller. In some instances, the handheld controller described herein may control a remote device (e.g., a television, audio system, personal computing device, game console, etc.), to engage in video game play, and/or the like.

The handheld controller may include one or more controls such as one or more joysticks, trackpads, trackballs, buttons, or other controls that are controllable by the user operating the handheld controller. Additionally, or alternatively, the handheld controller may include one or more controls that include a touch sensor configured to detect a presence, proximity, location, and/or gesture of the user on respective controls of the handheld controller. The touch sensor may comprise a capacitive touch sensor, a force resistive touch sensor, an infrared touch sensor, a touch sensor that utilizes acoustic soundwaves to detect a presence or location of an object, a proximity of an object, and/or any other type of sensor configured to detect touch input at the handheld controller or a proximity of one or more objects relative to the handheld controller. Additionally, in some instances, the touch sensor may comprise capacitive pads.

The touch sensor communicatively couples to one or more processors of the handheld controller to send touch sensor data indicative of touch input at the handheld controller. The touch sensor data may also indicate a closeness or proximity of one or more fingers relative to the handheld controller. The touch sensor data may indicate a location of the touch input on the handheld controller and/or may indicate a location of the fingers relative to the handheld controller, potentially as they change over time. For instance, if the fingers of the user hover or are disposed away from the handheld controller, the touch sensor data may indicate how extended or close the fingers are with respect to the handheld controller.

The handheld controller may also include logic (e.g., software, hardware, firmware, etc.) that is configured to receive the touch sensor data and determine the presence of a finger of the user and/or a location (or "position") of the finger(s) on the handheld controller(s). For example, in instances where the touch sensor comprises the capacitive pads, different regions or groups of capacitive pads may represent or correspond to different fingers of the user and the logic may determine which region(s) and/or group(s) of capacitive pads detect a capacitance. The handheld controller may provide this information to a game or other application for performing one or more actions at the handheld controller, such as a gesture performed by finger(s) touching or in close proximity to the handheld controller. For instance, the handheld controller may transmit the touch sensor data or other indications to a gaming console, a remote system, other handheld controller(s), or other computing devices. The computing devices may utilize the touch sensor data and/or indications to perform one or more actions, such as generating image data corresponding to a hand gesture of the user.

The logic of the handheld controller (or a computing device communicatively coupled to the handheld controller) may use the touch sensor data, such as the capacitance values, to identify a controller configuration for the user. The handheld controller, or the computing device, may store different controller configurations that represent a different assignment of capacitive pads for respective fingers of the user. That is, as noted above, the capacitive pads of the touch sensor may be segmented into groups and each group may correspond to or associate with a respective finger of the hand (e.g., pinky finger, ring finger, middle finger, and index finger). For respective controller configurations capacitive pads of the touch sensor may be associated with respective fingers of the hand. As such, when receiving data from the touch sensor, the logic may associate the touch sensor data with a corresponding finger of the user, which may in turn be utilized to identify a hand gesture. In other words, knowing which capacitive pad(s) correspond to respective fingers of the hand allows the logic to determine a corresponding hand gesture of the user, such as which fingers grip the handheld controller and/or which fingers do not grip the handheld controller. For instance, the logic may determine the user grips the handheld controller with the middle finger and the ring finger, but not the pinky finger. As such, knowing which capacitive pad(s), or group of capacitive pad(s) correspond to the respective fingers of the hand, the logic may provide an indication of this gesture to an application configured to perform a predefined action associated with the gesture or generate image data corresponding to the gesture (e.g., middle finger and ring finger grip an object, while the pinky finger does not grip the object). Moreover, through utilizing touch sensor data associated with a proximity of the fingers relative to the handheld controller, such as detected capacitance values, the logic of the handheld controller may determine an amount of curl or extension associated with each finger (e.g., how far the fingers are disposed away from handheld controller).

The handheld controller may dynamically adjust, detect, and accommodate for varying grips of the user or different users that operate the handheld controller. For instance, as the grip of the user may change depending on how the user holds the handheld controller, what game the user plays, and/or physical features of the hand of the user (e.g., length of finger, width of finger, etc.). The touch sensor may therefore adapt to different grips of the user. Additionally, as users may hold the handheld controller differently, the touch sensor may adapt to the grip of users. In other words, even for different users with similar hands, or as a user progresses throughout gameplay, the grip of the user may change (e.g., the fingers of the user may grip different parts of handheld controller). To accommodate for the varying grips and to enhance a gameplay experience, the logic may remap or re-associate the capacitive pads of the touch sensor according to different controller configurations. In doing so, the logic of the controller may associate the touch sensor data with certain fingers of the user to accurately portray a hand gesture of the user.

To briefly illustrate, the handheld controller or the computing device communicatively coupled to the handheld controller (e.g., gaming console) may generate scores using a machine learning approach and the touch sensor data. The handheld controller, or the computing device, may select a controller configuration with the highest score (or closely matched controller configuration) and configure the handheld controller according to the selected controller configuration. Such configuring may map certain capacitive pads of touch sensor to fingers of the user (e.g., middle, ring, pinky, etc.). That is, to accurately portray hand gestures of the user in gameplay (e.g., a VR environment), the handheld controller (or the computing device) may configure, based on selecting the controller configuration, capacitive pads of the touch sensor to correspond to certain fingers. Subsequently, in receiving touch sensor data, the handheld controller may associate capacitive pad(s) with a corresponding finger, thereby knowing the relative locations and/or proximity of the finger in relation to the handheld controller. However, the capacitive pads may also measure a proximity of the fingers relative to the handheld controller, for instance, through measuring capacitance. Through continuously scoring the controller configurations, the handheld controller may dynamically adapt to the grip of the user and associated the capacitive pads with respective fingers of the user. The handheld controller may therefore reassign or remap certain capacitive pads of the touch sensor to associate with certain fingers of the user. In turn, the touch sensor data may be used to accurately portray the hand of the user (e.g., in a VR environment).

The handheld controller may also sense, detect, or measure, via the touch sensor and/or a pressure sensor, an amount of force associated with touch input at the handheld controller. For instance, as a finger of a user presses against the handheld controller, a portion of the controller, such as a cover disposed above the touch sensor and/or the pressure sensor, may deflect to contact the touch sensor and/or the pressure sensor. The pressure sensor may couple to the one or more processors such that touch input of the finger may result in force data being provided to the one or more processors. The pressure sensor may provide force data indicative of an amount of force of the touch input to the one or more processors. In some instances, the pressure sensor may comprise a force-sensing resistor (FSR) sensor, a piezoelectric sensor, a load cell, a strain gauge, a capacitive-type pressure sensor that measures capacitive force measurements, or any other type of pressure sensor. Additionally, in some instances, the touch sensor data and/or the force data may be interpreted together and associated with a predefined command (e.g., squeezing).

While traditional handheld controllers may include sensors to sense touch input, traditional controllers statically map the touch sensor to associate with certain fingers. Such mapping, however, does not reassign portions of the touch sensor, such as the capacitive pads, to certain fingers or dynamically adapt the touch sensor to different fingers depending on the grip of the user. This static mapping may lead to a user experience within a gameplay environment that is less than ideal. For instance, if the touch sensor data does not accurately map to a respective finger of the user, the generated hand image may not accurately depict the hand of the user operating the handheld controller. The techniques and systems described herein improve upon existing technology to dynamically assign capacitive pads of the touch sensor or correlate the capacitive pads to certain fingers of the user. In doing so, image data generated from touch sensor data may accurately depict the fingers of the user, which may enrich gameplay experience and/or other applications being controlled by the handheld controller.

<FIG> is a front view of an example controller <NUM> that may include one or more touch-sensitive controls. As will be discussed herein, the touch-sensitive controls may generate touch sensor data utilized by the controller <NUM> and/or other computing devices to generate hand gestures of the user. The touch sensor data may indicate a presence, location, closeness, and/or gesture of a finger(s) of a user operating the controller <NUM>. In some instances, the controller <NUM> may be utilized by an electronic system such as a VR video gaming system, robot, weapon, or medical device.

As illustrated, the controller <NUM> may include a controller body <NUM> having a handle <NUM>, and a hand retainer <NUM>. The controller body <NUM> may include a head disposed between the handle <NUM> and a distal end <NUM> of the controller <NUM>, which may include one or more thumb-operated controls <NUM>, <NUM>, <NUM>. For example, a thumb-operated control may include a tilting button, or any other button, knob, wheel, joystick, or trackball conveniently manipulated by a thumb of a user during normal operation when the controller <NUM> is held in the hand of the user.

The handle <NUM> may include a substantially cylindrical tubular housing. In this context, a substantially cylindrical shape need not have constant diameter, or a perfectly circular cross-section.

The handle <NUM> includes a proximity sensor and/or a touch sensor having a plurality of capacitive sensors that may be spatially distributed partially or completely around an outer surface of the handle <NUM>. For example, the capacitive sensors may be spatially distributed beneath the outer surface of the handle <NUM> and/or may be embedded under the outer surface of the handle <NUM>. The capacitive sensors may be responsive to a user touching, gripping, or grasping the handle <NUM> to identify the presence, position, and/or gestures of one or more fingers of the user. Additionally, the capacitive sensors may be responsive to one or more fingers hovering or being disposed above the handle <NUM>. For instance, one or more fingers of the user may not grasp or wrap around the controller <NUM> but instead, may be displaced above the outer surface of the handle <NUM>. To accommodate such and detect a proximity of the fingers and/or touch input, the outer surface of the handle <NUM> may comprise an electrically insulative material.

The hand retainer <NUM> may couple to the controller <NUM> to bias the palm of the hand of the user against the outside surface of the handle <NUM>. As shown in <FIG>, the hand retainer <NUM> is in the open position. The hand retainer <NUM> may optionally bias in the open position by a curved resilient member <NUM> to facilitate the insertion of the hand of the user between the hand retainer <NUM> and the controller body <NUM> when the user grasps the controller <NUM>. For example, the curved resilient member <NUM> may include a flexible metal strip that elastically bends, or may comprise an alternative plastic material such as nylon, that may bend substantially elastically. A fabric material <NUM> (e.g., a neoprene sheath), may partially or completely cover the curved resilient member <NUM> to cushion or increase a comfort of the user. Alternatively, the cushion or fabric material <NUM> may adhere to only the side of the curved resilient member <NUM> facing the hand of the user.

The hand retainer <NUM> may adjust in length, for example, by including a draw cord <NUM> that is cinched by a spring-biased chock <NUM>. The draw cord <NUM> may optionally have an excess length for use as a lanyard. In some examples, the cushion or fabric material <NUM> may attach to the draw cord <NUM>. In addition, the curved resilient member <NUM> may be preloaded by the tension of the cinched draw cord <NUM> and in such embodiments, the tension that the curved resilient member <NUM> imparts to the hand retainer <NUM> (to bias it in the open position) may cause the hand retainer <NUM> to automatically open when the draw cord <NUM> is un-cinched. However, alternative conventional ways to adjust the length of a hand retainer <NUM>, such as a cleat, an elastic band (that temporarily stretches when the hand is inserted, so that it applies elastic tension to press against the back of the hand), a hook & loop strap attachment that allows length adjustment, etc. may be used.

The hand retainer <NUM> may be disposed between the handle <NUM> and a tracking member <NUM>, and may contact the back of the hand of the user. The tracking member <NUM> may affix to the controller body <NUM> and may optionally include two noses <NUM>, <NUM>, where each nose may protrude from a corresponding one of two opposing distal ends of the tracking member <NUM>. In some instances, the tracking member <NUM> may include an arc having a substantially arcuate shape. In some instances, the tracking member <NUM> may include tracking transducers disposed therein, for example, with at least one tracking transducer disposed in each protruding nose <NUM>, <NUM>. The controller body <NUM> may include additional tracking transducers, such as a tracking transducer disposed adjacent the distal end <NUM>.

The controller <NUM> may include a rechargeable battery disposed within the controller body <NUM>, and the hand retainer <NUM> may include an electrically-conductive charging wire electrically coupled to the rechargeable battery. The controller <NUM> may also include a radio frequency (RF) transmitter for communication with the rest of an electronic system (e.g., gaming console). The rechargeable battery may power the RF transmitter and the RF transmitted may respond to the thumb-operated controls <NUM>, <NUM>, <NUM>, the touch sensor (e.g., the capacitive sensors) in the handle <NUM>, and/or tracking sensors in the tracking member <NUM>.

In some instances, the controller body <NUM> may comprise a single piece of injection molded plastic or any other material rigid enough to transfer a force from a finger of the user to the touch sensor and thin enough to allow for capacitive coupling between a finger of the user and the touch sensor. Alternatively, the controller body <NUM> and the tracking member <NUM> may be fabricated separately, and then later assembled together.

<FIG> is a front view of the controller <NUM>, showing the controller <NUM> during operation with the left hand of the user inserted therein but not grasping the controller body <NUM>. In <FIG>, the hand retainer <NUM> is cinched over the hand of the user to physically bias the palm of the user against the outside surface of the handle <NUM>. Here, the hand retainer <NUM>, when closed, may retain the controller <NUM> within the hand of the user even when the hand is not grasping the controller body <NUM>. As shown, when the hand retainer <NUM> is closed tightly around the hand of the user, the hand retainer <NUM> may prevent the controller <NUM> from falling out of hand of the user. Hence, in some embodiments, the hand retainer <NUM> may allow the user to "let go" of the controller <NUM> without the controller <NUM> actually separating from the hand, being thrown, and/or dropped to the floor, which may enable additional functionality. For example, if the release and restoration of the user grasping the handle <NUM> of the controller body <NUM> is sensed, the release or grasping may be incorporated into the game to display throwing or grasping objects (e.g., in VR environment). The hand retainer <NUM> may allow such a function to be accomplished repeatedly and safely.

The hand retainer <NUM> may also prevent fingers of the user from excessively translating relative to the touch sensor to more reliably sense finger motion and/or placement on the handle <NUM>.

<FIG> and <FIG> depict the controller <NUM> during operation when the hand retainer <NUM> is cinched while the hand of the user grasps the controller body <NUM> to retain the controller <NUM> in the hand of the user. As shown in <FIG> and <FIG>, the thumb of the user may operate one or more of the thumb-operated controls <NUM>, <NUM>, <NUM>.

<FIG> illustrates that in certain embodiments, the controller <NUM> may be the left controller in a pair of controllers that includes a similar right controller <NUM>. In certain embodiments, the controllers <NUM> and <NUM> may (together) track the motion and grip of both of the hands of the user, simultaneously, for example, to enhance a VR experience.

<FIG> illustrates a proximity sensor or a touch sensor <NUM> having a plurality of capacitive pads <NUM> configured to detect touch input on a controller (e.g., the controller <NUM>) as well as a proximity of one or more objects (e.g., finger) relative to the controller <NUM>. In some embodiments, the touch sensor <NUM> may additionally or alternatively include different types of sensors configured to detect touch input at the controller <NUM> or a proximity of a finger(s) relative to the controller <NUM>, such as an infrared or acoustic sensor. As shown in <FIG>, the capacitive pads <NUM> of the touch sensor <NUM> are not necessarily of equal size and do not necessarily have substantially equal spacing therebetween. However, in some embodiments, the capacitive pads <NUM> may comprise a grid, with substantially equally spacing therebetween, and of substantially equal size.

The touch sensor <NUM> may include a flexible printed circuit assembly (FPCA) <NUM> on which the capacitive pads <NUM> are disposed. The FPCA <NUM> may include a connector <NUM> for connecting to a printed circuit board (PCB) of the controller <NUM> that includes one or more processors. The capacitive pads <NUM> may communicatively connect to the connector <NUM> via traces <NUM> disposed on the FPCA <NUM>. The capacitive pads <NUM> may provide touch sensor data (capacitance values) to the one or more processors of the controller <NUM> via the traces <NUM> and the connector <NUM>. As discussed in more detail herein, the touch sensor data may indicate the proximity of the finger relative to the controller <NUM>. That is, the touch sensor <NUM> may measure the capacitance of individual capacitive pads <NUM>, where the capacitance may be associated with a proximity of the fingers relative to the controller <NUM> (e.g., touching or being disposed above the handle <NUM> of the controller <NUM>).

The touch sensor <NUM> may couple to an interior surface within the controller body <NUM>, such as a structure mounted within the handle <NUM> of the controller body <NUM>, or a structure mounted underneath the handle <NUM> of the controller body <NUM>. In doing so, touch sensor <NUM> may be disposed beneath the outer surface of the handle <NUM> detect a proximity of the fingers relative to the handle <NUM>. When coupled to the controller <NUM>, the touch sensor <NUM> may angularly span around a circumference or a portion of the handle <NUM>. For instance, the FPCA <NUM> may couple (e.g., adhesion) to the inner surface of the controller body <NUM> at the handle <NUM> to detect the proximity of the fingers relative to the handle <NUM>. In some embodiments, the touch sensor <NUM> may extend at least <NUM> degrees but not more than <NUM> degrees around the circumference of the handle <NUM>. Additionally, or alternatively the touch sensor <NUM> may couple to the outer surface of the controller <NUM>, such as an outer surface of the handle <NUM>.

The capacitive pads <NUM> may be spaced apart from one another to detect a proximity of different fingers relative to the controller <NUM>, or different portions of the finger(s) of the user (e.g., fingertip). As shown in <FIG>, the capacitive pads <NUM> are arranged into rows and columns and may be arranged into a grid, sets, subsets, or groups <NUM>. In some instances, individual groups <NUM> of the capacitive pads <NUM> may correspond to a particular finger of the user (e.g., index finger, middle finger, ring finger, pinky finger). Additionally, or alternatively, multiple groups <NUM> of the capacitive pads <NUM> or capacitive pads <NUM> from multiple groups <NUM> may correspond to a single finger of the user. For instance, two or more groups <NUM> may correspond to a finger of the user (e.g., middle finger).

As shown in <FIG>, the touch sensor <NUM> may include six groups <NUM> of capacitive pads <NUM>, where the groups <NUM> extend horizontally across a surface of the FPCA <NUM>. However, in some embodiments, the touch sensor <NUM> may include more than six groups <NUM> or less than six groups <NUM>.

Through arranging the capacitive pads <NUM> into the groups <NUM>, or assigning certain capacitive pads <NUM> to certain groups <NUM>, the controller <NUM> (or another communicatively coupled computing device) may utilize touch sensor data (capacitance values) from the capacitive pads <NUM> to generate hand gestures of the user. That is, the touch sensor <NUM> may generate touch sensor data for use in detecting a presence, location, and/or gesture of the finger(s) of the user that grip the controller <NUM>. In these instances, as the user grips the controller <NUM> with certain fingers and hovers certain fingers above the controller <NUM>, a voltage is applied to the capacitive pads <NUM> that results in an electrostatic field. Accordingly, when a conductor, such as a finger of a user touches or nears the capacitive pads <NUM>, a change in capacitance occurs. The capacitance may be sensed by connecting an RC oscillator circuit to touch sensor <NUM> and noting that a time constant (and therefore the period and frequency of oscillation) will vary with the capacitance. In this way, as a user releases finger(s) from the controller <NUM>, grips the controller <NUM> with certain finger(s), or nears the controller <NUM>, the controller <NUM> may detect a change in capacitance.

The capacitance values of the capacitive pads <NUM>, or individual capacitive sensors within a grid on each capacitive pad <NUM>, are used to determine the location of the conductor as well as the proximity of the conductor relative to the capacitive pad <NUM>. That is, as a user grips the controller <NUM>, certain fingers and/or portions of the fingers may contact the handle <NUM> of the controller <NUM>. As the finger(s) act as a conductor, those capacitive pads <NUM> underlying the handle <NUM> where the user touches the handle <NUM> measure a capacitance value. These capacitance values are measured over time for use in identifying a gesture of the user. However, in instances where the user hovers their fingers or certain portions of their finger away from the controller <NUM>, the capacitance value may represent or be associated with how far the finger is disposed away from the controller <NUM>. The touch sensor data may therefore be utilized to determine the proximity and/or location of the fingers with respect to the controller <NUM>. As the grip of the user may change throughout a gameplay experience, or between different users, it may become beneficial to associate the fingers with different capacitive pads <NUM> of the touch sensor <NUM>. For example, at a first instance, a user may have a wide grip and all capacitive pads <NUM> of the touch sensor <NUM> may detect a capacitance value for use in generating image data. At a second instance, the grip of the user may narrow, and less than all of the capacitive pads <NUM> of the touch sensor <NUM> may detect a capacitance value for use in generating the image data. That is, to generate accurate image data depicting the gesture of the hand, the capacitive pads <NUM> may dynamically correlate or associate with certain fingers of the hand. In other words, to generate a corresponding hand gesture of the user, the controller <NUM> or a communicatively coupled computing device, may utilize the touch sensor data (capacitance values). Knowing which capacitive pads <NUM> of the touch sensor <NUM> are associated with respective fingers of the hand allows for the generation of a corresponding hand gesture using the capacitance values detected by the touch sensor <NUM>. Therefore, with a changing grip of the user, the capacitive pads <NUM> may regroup or associate with different fingers such that their capacitance values produce accurate image data depicting a hand gesture.

The one or more processors may include algorithms and/or machine-learning techniques embodying anatomically-possible motions of fingers, to better use the touch sensor data to detect the opening the hand of a user, finger pointing, or other motions of fingers relative to the controller <NUM> or relative to each other. In this way, the movement of the controller <NUM> and/or fingers of the user may help control a VR gaming system, defense system, medical system, industrial robot or machine, or another device. In VR applications (e.g. for gaming, training, etc.), the touch sensor data may be utilized to render the release of an object based on the sensed release of the fingers of the user from the outer surface of the handle <NUM>. Additionally, or alternatively, one or more processors of a communicatively coupled computing device (e.g., a host computing device, a game console, etc.) that the controller <NUM> is interacting with may detect the gesture(s) using the touch data.

In some instances, the capacitive pads <NUM> may also detect a capacitance value that corresponds to an amount of force applied to an associated portion of the controller <NUM> (e.g., a force applied to an outer surface of the handle <NUM>, to at least one thumb-operated control <NUM>, <NUM>, <NUM>, etc.). Additionally, or alternatively, the touch sensor <NUM>, or other portions of the controller <NUM> (e.g., the handle <NUM>), may include a force sensing resistor (FSR), which uses variable resistance to measure an amount of force applied to the FSR. As the controller <NUM> may be configured to be held by a hand of a user, the FSR may mount on a planar surface of a structure within the controller body <NUM>, such as a structure that is mounted within the handle <NUM> of the controller body <NUM>, or a structure that is mounted underneath the controller body <NUM>. In certain embodiments, the FSR, in conjunction with the capacitive pads <NUM>, may facilitate sensing of both the onset of grasping by the user, and the relative strength of such grasping by the user, which may be facilitate certain gameplay features. In either instance, the FSR may generate force data for use in detecting a presence, location, and/or gesture of the finger(s) of the user that grasp the controller <NUM>. When implemented in the controller <NUM>, the FSR and/or the capacitive pads <NUM> may measure a resistance value, or a capacitance value, respectively, that correspond to an amount of force applied to an associated portion of the controller <NUM>.

In some embodiments, the one or more processors of the controller <NUM> may utilize the touch sensor data and/or the force data to detect a hand size of a hand grasping the handle <NUM> and/or to adjust the threshold force required for registering a touch input at the capacitive pads <NUM> and/or the FSR according to the hand size. This may be useful for making force-based input easier for users with smaller hands (and harder, but not difficult, for users with larger hands).

<FIG> illustrate various controller configurations. As noted above, depending on the grip of the user, capacitive pads <NUM> of the touch sensor <NUM> may correspond to or associated with a particular finger of the user. The various controller configurations may map capacitive pads <NUM> to a respective finger and a corresponding portion of the finger (e.g., base, tip, middle, and so forth). In doing so, the touch sensor data generated from the touch sensor <NUM>, or the capacitance values from individual capacitive pads <NUM>, may be associated with a respective finger of the user for use in generating image data representing a gesture of the hand.

<FIG> illustrates a first controller configuration <NUM>, showing those capacitive pads <NUM> of the touch sensor <NUM> whose capacitance values are utilized when generating image data of a hand gesture. That is, in <FIG>, the "shaded-in" capacitive pads <NUM> represent those capacitive pads <NUM> whose touch sensor data is utilized to generate image data corresponding to the gesture of the hand. Comparatively, the capacitive pads <NUM> not shaded-in represent those capacitive pads <NUM> whose capacitance values are not utilized in generating image data corresponding to the gesture of the hand. However, the capacitive pads <NUM> not shaded-in may still measure capacitance values for the purpose of changing controller configurations. For instance, in the first controller configuration <NUM>, if the user touches one of the capacitive pads <NUM> that are not shaded-in, the controller <NUM> or a communicatively coupled computing device may use this information to determine whether to change controller configurations.

Turning to the specifics of the first controller configuration <NUM>, a first row <NUM>, a second row <NUM>, and a third row <NUM> of the touch sensor <NUM> may correspond to a first finger (e.g., middle finger) of the user. A fourth row <NUM> and a fifth row <NUM> of the touch sensor <NUM> may correspond to a second finger (e.g., ring finger) of the user. A sixth row <NUM> of the touch sensor <NUM> may correspond to a third finger (e.g., pinky finger) of the user. Through corresponding the rows of the touch sensor <NUM> with certain fingers of the user, and certain capacitive pads <NUM> of the rows with certain fingers, the capacitance values generated by the capacitive pads <NUM> of the touch sensor <NUM> may be utilized to generate image data depicting a gesture of the hand (i.e., how the user is holding the controller <NUM>). For instance, if the user grips the controller <NUM> while the controller <NUM> is configured according to the first controller configuration <NUM>, and the user does not grip the controller <NUM> with his or her first finger, the capacitance values received at rows <NUM>, <NUM>, and <NUM> may indicate that the first finger is not touching the controller <NUM>.

In other words, the capacitance values for the first row <NUM>, the second row <NUM>, and the third row <NUM>, which are associated with the first finger, may indicate that the first finger is not touching the controller <NUM>. Instead, the capacitance values from capacitance pads <NUM> of the first row <NUM>, the second row <NUM>, and/or the third row <NUM> may indicate touching distance or proximity the first finger hovers above the controller <NUM>. Additionally, the capacitive pads <NUM> associated with the fourth row <NUM>, the fifth row <NUM>, and the sixth row <NUM> may detect capacitance values that indicate the second and third fingers touch the controller <NUM>. Such capacitance values received by the respective capacitive pads <NUM> may be utilized to generate image data of the hand showing the index finger extended (e.g., pointing), as compared to curled around an object, for instance. Accordingly, the capacitance values from the individual capacitive pads <NUM> may be utilized to determine how far the fingers of the user are disposed from the controller <NUM>. However, as noted above, those capacitive pads <NUM> whose capacitance values are not utilized to generate the image data may be utilized by the controller <NUM> determined whether to configure the controller <NUM> according to another controller configuration.

<FIG> illustrates a second controller configuration <NUM>, showing those capacitive pads <NUM> of the touch sensor <NUM> whose capacitance values are utilized when generating image data. For instance, in <FIG>, the "shaded-in" capacitive pads <NUM> represent those capacitive pads <NUM> whose capacitance values are utilized to generate image data corresponding to a gesture of the hand. Comparatively, the capacitive pads <NUM> not shaded-in represent those capacitive pads <NUM> whose capacitance values are not utilized to generate image data corresponding to the gesture of the hand. However, the capacitive pads <NUM> not shaded-in may still measure capacitance values for the purpose of determining whether to switch between controller configurations.

In the second controller configuration <NUM>, a first row <NUM>, a second row <NUM>, and a third row <NUM> of the touch sensor <NUM> may correspond to a first finger of the user. A fourth row <NUM> may correspond to the second finger of the user and a fifth row <NUM> of the touch sensor <NUM> may correspond to the third finger of the user. Compared to the first controller configuration <NUM>, the second controller configuration <NUM> may represent a smaller grip (or hand size) of the user operating the controller <NUM>. In other words, for the second controller configuration <NUM>, the grip of the user may not touch a sixth row <NUM> of the touch sensor <NUM>. Through corresponding the rows of touch sensor <NUM> with certain fingers the capacitance values generated by the touch sensor <NUM> are utilized to generate image data depicting a gesture of the hand (i.e., how the user is holding the controller). By way of illustration and comparing the second controller configuration <NUM> to the first controller configuration <NUM>, because the second controller configuration <NUM> may correspond to a smaller grip of the handle <NUM>, a generated hand according to the second controller configuration <NUM> may be smaller than a generated hand according to the first controller configuration <NUM>.

By dynamically remapping the capacitive pads <NUM> of the touch sensor <NUM>, the capacitive pads <NUM> may be associated with different fingers of the user or may not be associated with fingers of the user. As such, the second controller configuration may better match a user with a smaller hand size and/or a smaller finger size, as compared to the first controller configuration <NUM>. For instance, using the first controller configuration <NUM> for the user with smaller hands not may accurately depict a hand gesture of the user as the user may be able to touch the sixth row <NUM> and as different rows of the first controller configuration <NUM> correspond to different fingers of the user. Accordingly, the second controller configuration <NUM> may more accurately associate the capacitive pads <NUM> with certain fingers of the user.

<FIG> illustrates a third controller configuration <NUM>, showing those capacitive pads <NUM> of the touch sensor <NUM> whose capacitance values are utilized when generating image data. That is, in <FIG>, the "shaded-in" capacitive pads <NUM> represent those capacitive pads <NUM> whose capacitance values are utilized to generate image data corresponding to a gesture of the hand. Comparatively, the capacitive pads <NUM> not shaded-in represent those capacitive pads <NUM> whose capacitance values are not utilized to generate image data corresponding to the gesture of the hand. However, the capacitive pads <NUM> not shaded-in may still measure capacitance values and generate touch sensor data for the purpose of determining whether to switch between controller configurations.

In the third controller configuration <NUM>, all of the capacitive pads <NUM> of the touch sensor <NUM> are shown shaded-in. In doing so, for instance, image data depicting the representation of the hand may be generated from capacitance values from all the capacitive pads <NUM>. The third controller configuration <NUM>, compared to the second controller configuration <NUM>, may represent a large hand size or a large grip on the handle <NUM> of the controller <NUM>. Additionally, compared to the first controller configuration <NUM>, the controller third configuration <NUM> may correspond to a hand having larger finger lengths, as indicated by all the capacitive pads <NUM> in the rows being shaded in (as compared to the first controller configuration <NUM>). In the third controller configuration <NUM>, a first row <NUM>, a second row <NUM>, and a third row <NUM> of the touch sensor <NUM> may correspond to the first finger of the user. A fourth row <NUM> and a fifth row <NUM> of the touch sensor <NUM> may correspond to the second finger of the user. A sixth row <NUM> of the touch sensor <NUM> may correspond to the third finger of the user.

With the above description, the capacitive pads <NUM> of the touch sensor <NUM> may remap to correspond to different fingers of the user. Depending on the grip of the user or the hand size of the user, a particular row or rows, for instance, of the touch sensor <NUM> may correspond to a particular finger of the user (e.g., middle finger), while in other instances, may correspond to a different finger of the user (e.g., ring finger). Through receiving touch sensor data (e.g., capacitance values) indicative of the grip or finger positions of the user, the capacitive pads <NUM> of the touch sensor <NUM> may remap and correspond to different fingers of the user(s). In other words, the capacitive pads <NUM> may be designated in some instances to correspond to different fingers of the user depending on the grip of a particular user with the handle <NUM> of the controller <NUM>. In this sense, the controller <NUM> may include different controller configurations (i.e., the first controller configuration <NUM>, the second controller configuration <NUM>, and the third controller configuration <NUM>) to correspond different capacitive pads <NUM> with different fingers. Compared to conventional techniques, this dynamic adapting of capacitive pads <NUM> to certain fingers may allow for accurate gestures of the user to be generated in a VR environment.

Additionally, while <FIG> illustrate certain controller configurations or a certain amount of capacitive pads, the touch sensor <NUM> may embody additional controller configurations. For instance, any combination of the capacitive pads <NUM>, groups <NUM>, or rows of capacitive pads <NUM>, may correspond to a particular finger or grip of the user. Further, the touch sensor <NUM> may include mappings or capacitive pads <NUM> for more than three fingers. The touch sensor <NUM> may therefore associate with the grip of the user and the capacitive pads <NUM> may map to certain fingers of the user.

<FIG> illustrate various processes as a collection of blocks in a logical flow graph, which represent a sequence of operations that can be implemented in hardware, software, or a combination thereof. In the context of software, the blocks represent computer executable instructions that, when executed by one or more processors, perform the recited operations. Generally, computer-executable instructions include routines, programs, objects, components, data structures, and the like that perform particular functions or implement particular abstract data types. The order in which the operations are described is not intended to be construed as a limitation, and any number of the described blocks can be combined in any order and/or in parallel to implement the processes.

<FIG> is a flow diagram of an example process <NUM> for calibrating and configuring a touch sensor <NUM> for different controller configurations. At <NUM>, logic of a controller <NUM> may receive touch sensor data from the touch sensor <NUM>. For instance, an object (e.g., finger, thumb, etc.) may contact the controller <NUM> or come within a proximity of the controller <NUM> (e.g., above the handle <NUM>). The touch sensor data may indicate a capacitance value detected or measured by the capacitive pads <NUM> of the touch sensor <NUM>. For instance, if the finger is touching the controller <NUM>, the capacitance value may be larger than compared to a finger that hovers above the controller <NUM> without touching the controller <NUM>. In this sense, the capacitance value may indicate a proximity of the fingers relative to the controller <NUM>. The logic of the controller <NUM> may convert the capacitance value into a digitized value.

In some instances, the touch sensor data received at <NUM> may represent raw data that is not calibrated and/or normalized with other the touch sensor data provided from other capacitive pads <NUM>. That is, the touch data received at <NUM> may represent raw data in the sense that for a particular capacitive pad <NUM>, the capacitive pad <NUM> may detect capacitance values or a range of capacitance values depending on the size of the capacitive pad <NUM> and the size of the finger(s) and/or hand of the user touching the controller <NUM>.

At <NUM>, logic of the controller <NUM> may normalize the touch sensor data. For instance, through iteratively receiving touch sensor data from the touch sensor <NUM> (e.g., as a user interacts with the controller <NUM>), the touch sensor data may indicate capacitance values measured by the capacitive pads <NUM>. Over time, the capacitance values may indicate a range of capacitance values detected or measured by the individual capacitive pads <NUM> of the touch sensor <NUM>. For instance, the capacitive pads <NUM> may detect a high capacitance value when the user grips a portion of the controller <NUM> residing above the capacitive pad <NUM>, and may detect a low capacitance value when the user does not grip the portion of the controller <NUM> residing above the capacitive pad <NUM>. Accordingly, at <NUM>, for respective capacitive pads <NUM> of the touch sensor <NUM>, logic of the controller <NUM> may analyze the touch sensor data and determine the range of capacitance values received, the maximum capacitance value received, the minimum capacitance value received, the average capacitance value, and/or the median capacitance value. In some instances, the capacitance value may be normalized in a range of [<NUM>,<NUM>].

At <NUM>, logic of the controller <NUM> may calibrate the touch sensor <NUM>. As shown by the sub-blocks in <FIG>, the process <NUM> may involve more detailed operations for calibrating the touch sensor <NUM>. For example, calibrating the touch sensor <NUM> may include sub-blocks <NUM> and <NUM>. As shown by sub-block <NUM>, calibrating the touch sensor <NUM> may include a discrete gesture recognition. The discrete gesture recognition may correspond to a discrete gesture performed by the user at the controller <NUM>. For instance, if all or a majority of the capacitance values of the capacitive pads <NUM> suddenly drop, the logic may associate this drop with the user releasing his or her hand from the controller <NUM> or releasing a particular finger from the controller <NUM>. The capacitance values received as the user suddenly releases his or her finger from the controller <NUM> may correspond to a low-level value of a range of capacitance values detected for a particular capacitive pad <NUM> (e.g., the capacitance value represents when the finger is not touching the controller <NUM>). The capacitance values received prior to the sudden drop may correspond to a high-level value of the range of capacitance values detected for the particular capacitive pad <NUM> (e.g., the capacitance value represents when the finger is touch the controller <NUM>). With the range of capacitance values, the logic of controller <NUM> may calculate a bias and a scale factor for capacitance values received by the controller <NUM>. That is, knowing the scale factor for a capacitive pad <NUM> allows for the normalization of capacitance values received.

As shown by sub-block <NUM>, calibrating the touch sensor <NUM> may also include a continuous low-level and/or high-level adjustment. As the logic of the controller <NUM> continuously receives touch sensor data from the touch sensor <NUM>, the logic may continuously monitor the touch sensor data to re-calibrate the low-level capacitance value and/or the high-level capacitance value for the range of capacitance values of a given capacitive pad <NUM>. For instance, through continuously receiving the touch sensor data from the individual capacitive pads <NUM>, logic of the controller <NUM> may determine whether the received capacitance values are lower than or higher than the previously determined low-level capacitance value and/or the high-level capacitance value, respectively. Based on this determination, the logic of the controller <NUM> may update the low-level capacitance value or the high-level capacitance value, thereby adjusting the range of capacitance values for a particular capacitive pad <NUM>. In doing so, the bias and/or scale factor may be updated for use in normalizing the capacitance values.

Calibrating the touch sensor <NUM> may therefore aid in calculating the bias and scale factor for a particular capacitive pad <NUM> and for a particular user operating the controller <NUM>.

At <NUM>, the logic of the controller <NUM> may configure the touch sensor <NUM>, whereby the capacitive pads <NUM> are assigned to certain fingers of the user based on the particular controller configuration. For instance, knowing that the middle finger is disposed above the ring finger and the ring finger is disposed above the pinky finger the controller <NUM> may map certain capacitive pads <NUM> and their capacitance values to certain fingers of the user. This mapping may occur for each controller configuration whereby the capacitive pads <NUM> are respectively mapped to a corresponding finger and/or a corresponding portion of the finger. However, as noted above, not all capacitive pads <NUM> may be assigned to a finger. As shown by the sub-blocks in <FIG>, the process <NUM> may involve more detailed operations to configure the touch sensor <NUM>. For example, configuring the touch sensor <NUM> may involve filtering noise at the low-level range capacitance values, at sub-block <NUM>, and a capacitive pad and finger rejection, at sub-block <NUM>, each of which are discussed in turn.

At sub-block <NUM>, the process <NUM> may filter noise within a low-level range of capacitance values. For instance, when a finger is not touching the controller <NUM> (e.g., hovering above the handle <NUM> or in close proximity to the handle <NUM>), those capacitive pads <NUM> associated with the finger may be susceptible to noise. In other words, at the low-level range of capacitance values for a capacitive pad <NUM>, a small amount of measured capacitance may result in changes of the finger position of the user. Generating image data corresponding to these changes may result in unpleasant finger twitching within a VR environment. Instead, in instances where the capacitance values from the touch sensor <NUM> for individual capacitive pads <NUM> fall below a certain threshold, are below threshold change from previous capacitance values, or if the capacitance values are within a certain threshold of the low-level capacitance value for the capacitive pad <NUM>, the logic of the controller <NUM> may suppress the capacitance value. In doing so, the controller <NUM> may ignore minor spurious touch inputs at the touch sensor <NUM> that may otherwise result in finger twitching within the VR environment.

The capacitive pad and finger rejection, at sub-block <NUM>, may include identifying capacitive pads <NUM> whose low-level capacitance value or high-level capacitance value are within a threshold range of one another. For instance, if the low-level and high-level capacitance values are separated by a small range, the capacitive pad may be unable to accurately sense and detect the finger positions of the user in sufficient detail. Here, as a capacitive pad <NUM> may detect capacitance values within a threshold range, the measured capacitance values may not accurately correspond to the finger position.

Additionally, or alternatively, certain fingers may be associated with a number of capacitive pads <NUM> that decreases the reliability of the detected capacitance values. In these scenarios, capacitance values received by the capacitive pads <NUM> may introduce noise. Disregarding certain capacitive pads <NUM>, or groups of capacitive pads <NUM>, may increase a reliability that the capacitance values correspond to the hand gesture of the user.

From <NUM>, the process may continue to "A," which is discussed is turn with regard to <FIG> and process <NUM>. Additionally, while the process <NUM> is described being performed by the controller <NUM>, in some instances, the one or more communicatively coupled computing devices may perform all of or a portion of the blocks of the process <NUM>. For instance, as the one or more computing devices may include increased processing, the controller <NUM> may transmit the touch data received from touch sensor <NUM> to the computing device for calibrating and normalizing the capacitance values.

<FIG> is a flow diagram of an example process <NUM> for calculating a score for a controller configuration and configuring a controller <NUM> according to a selected controller configuration. In some instances, the process <NUM> may continue from "A" of process <NUM>. At <NUM>, logic of the controller <NUM> may score a plurality of controller configuration(s) using the capacitance values received from the touch sensor <NUM> (and after normalizing the capacitance values as discussed hereinabove). For instance, logic may access, from a datastore of the controller <NUM> or from another communicatively coupled computing device, data associated with individual controller configurations of the plurality of controller configurations. The logic may then provide, as inputs to the controller configuration, the touch sensor data. For example, individual controller configurations may have been previously trained and/or calibrated using the process <NUM> described above. Discussed above, individual controller configurations may designate which capacitive pads <NUM> of the touch sensor <NUM> correspond to the fingers of the user. For instance, a first controller configuration may associate first capacitive pads <NUM> with the middle finger of the user, while a second controller configuration may associate second capacitive pads <NUM> with the middle finger, where the first capacitive pads <NUM> and the second capacitive pads <NUM> are different or represent different combinations of capacitive pads <NUM>.

As shown in the process <NUM>, determining the score for the controller configuration(s) may involve sub-blocks, such as calculating a variance within each finger group of a controller configuration, at <NUM>, and/or calculating a variance between each finger group of a controller configuration, at <NUM>. In some instances, the score for the controller configuration may represent the ratio of the variance within each finger group to the variance between each finger group, which may include an "f-statistic" or an "f-test. " The scores may indicate a probability of the controller configuration matching the hand size, finger position, and/or grip of the user. In other words, the controller configuration may represent how closely the fingers of the user align or otherwise associate with the controller configuration. A high score may indicate a closely matched or matched controller configuration whereas a low score may indicate a controller configuration not likely matching the grip of the user. For example, a first score is attributed to a first controller configuration, a second score is attributed to a second controller configuration, and so on and so forth, for any suitable number of controller configurations.

In some instances, the scores for the controller configurations may be initialized (i.e., zeroed) when the controller <NUM> powers on. As the controller <NUM> receives the touch sensor data, the logic may calculate the scores for the controller configurations. In doing so, the logic may receive touch sensor data, update the scores for the controller configurations, and over time, as scores for controller configurations are calculated, the logic may select a controller configuration. The controller configuration best matching the grip of the user will have a higher score than the other controller configurations that do not best match the grip of the user.

To illustrate determining the score for a controller configuration, as the user grips the controller <NUM>, the capacitive pads <NUM> may detect a change in capacitance based on which areas of the controller <NUM> the user grips or the proximity of the fingers of the user relative to the controller <NUM>. After the touch data is normalized and the touch sensor <NUM> is calibrated and/or configured (e.g., the process <NUM>), the touch sensor data is used to calculate scores for respective controller configurations. In general, knowing that a user grips the controller <NUM> with his or her middle finger disposed above the ring finger and his or her ring finger disposed above the pinky finger the capacitance values received at the controller <NUM> may be associated with the middle finger, the ring finger, and the pinky finger, respectively. Additionally, each of the controller configurations may include a predetermined layout where certain capacitive pads <NUM> are associated with a certain finger of the user. That is, a group of capacitive pads <NUM> may correspond to a particular finger. For instance, a large hand configuration may include multiple rows of the capacitive pads <NUM> associated with the middle finger whereas a small hand configuration may include a single row of the capacitive pads <NUM> associated with the middle finger.

As the capacitive pads <NUM> are grouped together and as the user touches or lifts his or her fingers from the controller body <NUM>, those capacitive pads <NUM> associated with a particular finger of a controller configuration may or may not detect capacitance values. For instance, when the user lifts his or her middle finger from the controller body <NUM>, for a correct controller configuration, those capacitive pads <NUM> assigned to the middle finger may not measure a capacitance value or may measure low capacitance values. In some instances, the capacitance values of the capacitive pads <NUM> of the middle finger group may experience a capacitance change in substantially the same amount and at substantially the same time. For instance, for a correct controller configuration (e.g., a controller configuration with a high score), the capacitive pads assigned to a particular finger would experience the substantially the same capacitance or substantially the same change in capacitance at approximately the same time. The capacitive pads <NUM> for the correct controller configuration associated with the middle finger would therefore statistically correlate with each other and indicate a high correlation with each other or a low variance between one another. Calculating the variance within each finger group, for the individual controller configurations, may represent the variance between those capacitive pads <NUM> assigned to a particular finger (e.g., "f-statistic" or an "f-test"). Comparatively, a controller configuration having high variances within a finger group may indicate an incorrect controller configuration or a controller configuration not well suited for the grip of the user. That is, controller configurations with high variance within a finger group of capacitive pads <NUM> may indicate an improper assignment of capacitive pads <NUM> for respective fingers of the user.

Calculating the variance between finger groups may indicate a variation between one finger group of capacitive pads <NUM> and another finger group of capacitive pads <NUM> (e.g., "f-statistic" or an "f-test"). For instance, returning to the above example, as the user lifts his or her middle finger from the controller body <NUM> but keeps his or her pinky finger in contact with the controller body <NUM>, a high variance may exist between the capacitance values of the capacitive pads <NUM> assigned to the middle finger and the capacitance values of the capacitive pads <NUM> assigned to the pinky finger. For each finger and for the different controller configurations, a variance score may be generated. Accordingly, for the middle finger, a variance between middle finger group and pinky finger group is calculated and a variance between middle finger group and ring finger group is calculated. Likewise, a variance may be calculated between the ring finger group and the pinky finger group is. This process may continue for each finger and for each controller configuration. However, while the above example is described with regard to three fingers (e.g., middle, ring, and pinky), the touch sensor <NUM> may be configured for more or less fingers.

As each controller configuration includes a plurality of determined scores, an aggregation (e.g., sum) of the scores may indicate how closely a specific controller configuration matches the grip of the user. Additionally, in some instances, the process <NUM> may determine the score for the controller configuration in instances where the capacitance values indicate a high degree of disparity compared to historical capacitance values. For instance, the score for a controller configuration may include a running average, and determining a new score for the controller configuration may update the running average. Here, the average for the controller configuration may be updated if a large disparity, or a disparity above a threshold, exists between the determined score and the previous or average score for the controller configuration. In this sense, a single score for a controller configuration may not skew or improperly weighed against previously calculated scores. Additionally, where large disparities exist, the scores for a controller configuration may be weighted.

At <NUM>, logic of the controller <NUM> ranks the controller configurations based at least in part on the determined scores. As discussed above, the score associated with an individual controller configuration relates to a probability that the assignment of capacitive pads <NUM> of the controller configuration maps or represents the grip of the user. That is, the assignment of capacitive pads <NUM> for the controller configuration matches the respective fingers of the hand.

At <NUM>, logic of the controller <NUM> selects a controller configuration. The controller configuration may indicate which capacitive pads <NUM> are associated with each finger of the user. In doing so, as the controller <NUM> continues to receive touch sensor data from the touch sensor <NUM>, the touch sensor data is associated with particular fingers and particular parts of the finger (e.g., base, tip, etc.) of the user. Knowing which capacitive pads <NUM> of the touch sensor <NUM> correspond to a respective finger of the user may assist in accurately generating image data (using the touch sensor data and/or force data) depicting a hand gesture of the user.

At <NUM>, logic of the controller <NUM> may determine whether the selected controller configuration is different than a current controller configuration of the controller <NUM>. For instance, the controller <NUM> may include a default controller configuration, and at <NUM>, the process <NUM> may determine whether the selected controller configuration is different than the default controller configuration. If the controller configurations are the same, meaning that the selected controller configuration (the highest ranked controller configuration) is already configured on the controller <NUM>, there may be no need to update or assign a different controller configuration. If so, the process <NUM> may follow the "NO" route and proceed to <NUM>.

Alternatively, if the controller configurations are not the same, meaning that the selected controller configuration (the highest ranked controller configuration) is not currently implemented on the controller <NUM>, a need exists to update or assign a different controller configuration. In other words, as the grip of the user may change, or the controller <NUM> may switch between users, the controller configuration may update to assign capacitive pads <NUM> with respective fingers of the user. If so, the process <NUM> may follow the "YES" route to <NUM>.

At <NUM>, logic of the controller <NUM> configures the controller <NUM> according to the selected controller configuration. At <NUM>, depending on which controller configuration is selected (at <NUM>), the capacitive pads <NUM> of the touch sensor <NUM> may correlate with different fingers or different portions of the finger. Accordingly, in future instances, using the touch sensor data, the logic of the controller <NUM> may determine which fingers and/or which portions of individual fingers are touching the controller <NUM> as well as the proximity of certain fingers to the controller <NUM>. Configuring the controller <NUM> according to the controller configuration may involve assigning capacitive pads <NUM> of the touch sensor <NUM> to correspond to certain fingers of the user. The assignment of capacitive pads <NUM> may include mapping capacitive pads <NUM> to associate the capacitive pads <NUM> with a respective finger of the user. In some instances, not all capacitive pads <NUM> of the touch sensor <NUM> may map to a respective finger of the user. For instance, if the user has a small hand or a small grip the grip of the user may span a subset of the capacitive pads <NUM> of the touch sensor <NUM>. In such instances, the capacitance values received from the remaining capacitive pads <NUM> may not be used when generating image data depicting the hand gesture. By contrast, a large hand may span an entirety of the touch sensor <NUM>, and, in this case, all (or at least a number above a threshold number) of the capacitive pads <NUM> may provide the touch sensor data for use in generating the image data.

At <NUM>, logic of the controller <NUM> may normalize the capacitance values of the capacitive pads <NUM> using a set of weights applied to the individual capacitive pads <NUM> of a group of capacitive pads <NUM> associated with a finger. For instance, the weight assigned to individual pads of the capacitive pads <NUM> may be associated with the controller configuration. For instance, if four capacitive pads <NUM> of the touch sensor <NUM> are associated with the middle finger of a user, an equal weight may be assigned to all four capacitive pads <NUM>. Therefore, the capacitance values received from these four capacitive pads <NUM> may include a weight of one-quarter. In doing so, the capacitance values from these capacitive pads <NUM> may include an equal weight that is used when determining a finger position. Additionally, in some instances, the weight of a particular capacitive pad <NUM> may be set to zero based on the capacitive pad and finger rejection indicating which capacitive pads <NUM> to ignore or have a reliability below a certain threshold.

Normalizing the touch sensor data at <NUM> may also involve summing the capacitance values from the capacitive pads <NUM> for each group of capacitive pads <NUM>. As an example, for a certain controller configuration, if the middle finger is represented by four capacitive pads <NUM>, each capacitance value of the capacitive pad <NUM> of the middle finger may carry a weight of one-fourth. The logic may weigh the capacitance value for respective capacitive pads <NUM> for a finger to indicate the influence that the capacitance value for a given capacitive pad <NUM> has on the summed capacitance values for the finger.

Additionally, or alternatively, normalizing the touch sensor data may include normalizing the touch sensor data according to weights previously applied to the capacitive pads <NUM>. Through the capacitive pad and finger rejection (sub-block <NUM>), not all capacitive pads <NUM> within a group of capacitive pads <NUM> may carry an equal weight. As an example, a user might not contact certain capacitive pads <NUM> with a group. In turn, the logic may reject or not factor the capacitance value of a particular capacitive pad <NUM> the user does not touch, for instance, if the hand of the user is small or the user places his or her hands differently on the controller <NUM>. For instance, as noted above, if the low-level capacitance value and high-level capacitance value are narrow (i.e., the range is small), the capacitive pad <NUM> may be susceptible to high amounts of noise. Here, the logic of the controller <NUM> may disregard certain capacitance values of a capacitive pad <NUM> within the weighted sum. In instances were capacitance values are not used, the capacitance values being used may be summed and divided by the sum of the weights being used. For instance, if four capacitive pads <NUM> are assigned to a particular finger, each capacitive pad <NUM> may have a weight of one-quarter. However, if the capacitance value for one of the capacitive pads <NUM> is unreliable (e.g., contains a large amount of noise) the weight of the one capacitive pad <NUM> may be disregarded such that the remaining three capacitive pads have a weight of one-third. Therein, the capacitive values are summed and divided by the sum of the weights of the capacitive pads <NUM> being used.

At <NUM>, the logic of the controller <NUM> may assign a finger value to respective fingers of the user based at least in part on the touch sensor data. For instance, after normalizing the touch sensor data and associating the touch sensor data with particular fingers, the controller <NUM> may determine a finger value on a scale of [<NUM>,<NUM>]. The finger value assigned to fingers of the user may indicate a relative position or curl of the finger relative to the controller <NUM>. In this sense, the controller <NUM>, using the capacitance values detected from individual capacitive pads, may determine the finger positions of the user relative to the controller <NUM>. In some instances, the controller <NUM> may determine finger values for each finger of the user or those fingers for which the touch sensor <NUM> is configured.

At <NUM>, the logic of the controller <NUM> may transmit the finger values (e.g., indication) to one or more computing devices. In some instances, the one or more computing devices may utilize the finger values to generate image data depicting a gesture of the hand of the user on the controller <NUM>. In some embodiments, the one or more computing devices may perform additional analysis on the finger value. For instance, the one or more computing devices may utilize curl logic when generating a curl of the finger in the image data. Moreover, in some instances, the controller <NUM> may transmit additional data captured and/or received by the controller, such as force data from a pressure sensor of the controller <NUM> upon a press of the surface by the at least one finger.

From <NUM>, the process <NUM> may loop to step <NUM> of the process <NUM>. Accordingly, the controller <NUM> may continuously receive capacitance values for use in generating image data according to the grip of the user and for use in determining whether to update the controller configuration of the controller <NUM>.

While some or all of the process <NUM> is described being performed by the controller <NUM>, in some instances, the one or more communicatively coupled computing device may perform all of or a portion of the blocks of the process <NUM>. For instance, as the computing device may include increased processing power, the controller may transmit the touch data received from touch sensor <NUM> to the computing device for determining the scores for the controller configuration. In turn, the computing device may transmit the controller configuration to the controller <NUM>, or transmit an indication of the controller configuration to the controller <NUM>.

<FIG> illustrates an example process <NUM> for configuring a controller <NUM> according to one or more controller configurations. At <NUM>, the process <NUM> may receive touch sensor data from a touch sensor <NUM> of the controller <NUM>. In some embodiments, the touch sensor data may indicate the capacitance values detected by respective capacitive pads <NUM> of the touch sensor <NUM>.

At <NUM>, the process <NUM> may analyze the touch sensor data. In some instances, analyzing the touch sensor data may include the processes <NUM> and/or <NUM> described herein above, whereby the touch sensor data is normalized and the touch sensor <NUM> is calibrated. For instance, logic of the controller <NUM> may analyze the touch sensor data and determine a score for respective controller configurations. Selecting the controller configuration may involve determining a ratio of (<NUM>) the variance of capacitance values within a group of capacitive pads <NUM> assigned to a particular finger and (<NUM>) the variance of capacitance values between groups of capacitive pads. For instance, determining a variance within a finger group may include determining a variance in capacitance between a first capacitive pad and a second capacitive pad assigned to a first finger (e.g., "f-statistic" or an "f-test"). Determining a variance between a finger group may include determine a variance in capacitance between a summed capacitance value of the first capacitive pad and the second capacitive pad, and then comparing the summed capacitance value to the summed capacitance values of another group of capacitive pads <NUM> assigned to a second finger. A ratio is calculated for each controller configuration to determine a most likely matched configuration for the grip of the user. In some instances, the controller <NUM> may transmit the touch sensor data to a computing device (e.g., game console) for analysis, and the computing device may determine the score for respective controller configurations.

At <NUM>, the process <NUM> may select a first controller configuration <NUM>. For instance, after analyzing the touch sensor data (block <NUM>), the process <NUM> may select a controller configuration (e.g., the first controller configuration <NUM>) that best matches the hand size, finger size, and/or grip of the user. In instances where the computing device selects the first controller configuration <NUM>, the computing device may transmit, to the controller <NUM>, an indication of the selection.

At <NUM>, the process <NUM> may configure the controller <NUM> according to the first controller configuration <NUM>. As discussed herein, and as illustrated in <FIG>, configuring the controller <NUM> according to the first controller configuration <NUM> may include associating certain capacitive pads <NUM> of the touch sensor <NUM> with certain fingers and/or certain portions of the fingers. Associating capacitive pads <NUM> with certain fingers may also involve grouping one or more capacitive pads <NUM> together and associating the group of capacitive pads <NUM> with the finger. Also, as noted above, depending on the hand size and/or grip of the user, not all capacitive pads <NUM> of the touch sensor <NUM> may be mapped or otherwise assigned to a finger.

At <NUM>, the process <NUM> may receive touch sensor data from the touch sensor <NUM> of the controller <NUM> and at <NUM>, the process <NUM> may analyze the touch sensor data. The touch sensor data may also be utilized to generate image data utilizing the first controller configuration.

At <NUM>, the process <NUM> may select a second controller configuration <NUM>. For instance, after analyzing the touch sensor data (block <NUM>), the process <NUM> may select a controller configuration (e.g., the second controller configuration <NUM>) that best matches the hand size and/or grip of the user. For instance, the grip of the user may change or a different user, having a different grip, may operate the controller <NUM>. In these instances, the controller configuration may update to accurately sense, detect, or otherwise associate different capacitive pads <NUM> of the touch sensor <NUM> with fingers of the user.

At <NUM>, the process <NUM> may configure the controller <NUM> according to the second controller configuration <NUM>. Configuring the controller <NUM> according to the second controller configuration <NUM> may include remapping or re-associating certain capacitive pads <NUM> of the touch sensor to remap to certain fingers of the user, as compared to the first controller configuration <NUM>.

<FIG> illustrates a process <NUM> for calibrating a touch sensor of a controller, such as the touch sensor <NUM> of the controller <NUM>, reducing noise within the touch sensor data, and utilizing the touch sensor data to generate image data representative of hand gestures performed by the user. In some instances, the process <NUM> may output a finger value or indication representative of a position of the finger, such as how much a finger curls or extends.

At <NUM>, the process <NUM> may receive touch sensor data from the touch sensor <NUM>, where the touch sensor data represents or indicates raw capacitance values detected by capacitive pads (e.g., the capacitive pads <NUM>) of the touch sensor <NUM>. As illustrated in <FIG>, in some instances, the process <NUM> may receive capacitance values from individual capacitive pads <NUM>, as illustrated by a<NUM>, ai, and aN. In some instances, the process <NUM> may receive the raw capacitive values from the touch sensor <NUM> for each frame displayed in a VR environment.

At <NUM>, the process <NUM> may perform a factory normalization to normalize the raw capacitance values. For instance, the capacitive pads <NUM> may have different biases, scale factors, and offsets depending on manufacturing conditions, a size of the capacitive pad <NUM>, and so forth. In some instances, the factory normalization may involve a first order calibration to remove the bias within the capacitance value and normalizing the capacitance value.

At <NUM>, the process <NUM> may perform a grip calibration. As shown, the grip calibration may involve sub-blocks <NUM>, <NUM>, and <NUM>, which are discussed in detail in turn.

At sub-block <NUM>, the process <NUM> may perform a statistical analysis to observe a range of capacitance values, the maximum capacitance value received, the minimum capacitance value received, the average capacitance value, and/or the median capacitance value for respective capacitive pads <NUM>.

At <NUM>, the process <NUM> may perform a discrete gesture detection. Here, the process <NUM> may analyze the touch sensor data (i.e., the capacitance values), after being normalized according to the factory normalization, to detect a discrete gesture at the controller <NUM>. For instance, if the touch sensor data indicates that capacitance values of the capacitive pads <NUM>, or a portion thereof, suddenly drop, the process <NUM> may associate this drop of capacitance values with the user releasing his or her hand from the controller <NUM> or releasing a particular finger from the controller <NUM>. The capacitance values received as the user suddenly releases his or her finger from the controller <NUM> may correspond to a low-level value for a range of capacitance values detected by a particular capacitive pad <NUM> (e.g., where the capacitance value represents when the finger is not touching the controller <NUM>). The capacitance values received prior to the sudden drop may correspond to a high-level value of the range of capacitance values detected by a particular capacitive pad <NUM> (e.g., where the capacitance value represents when the finger is touching the controller <NUM>). With the range of capacitance values, the process <NUM> may determine a bias and a scale factor for capacitance values of the capacitive pads <NUM> to normalize the capacitance values received at respective capacitive pads <NUM>.

At <NUM>, the process <NUM> may perform a continuous calibration update and decay. As the process <NUM> may continuously receive touch sensor data from the touch sensor <NUM>, the process <NUM> may continuously monitor the touch sensor data to re-calibrate or reset the low-level capacitance value and/or the high-level capacitance value for the range of capacitance values for a given capacitive pad <NUM>. In other words, through continuously receiving the touch sensor data from the individual capacitive pads <NUM>, the process <NUM> may determine whether the capacitance values are lower than or higher than the previously determined low-level capacitance value of the range and/or the high-level capacitance value of the range, respectively. For instance, as the capacitance changes through a gameplay experience (e.g., hands become sweaty or dry, humidity, temperature, etc.), the process <NUM> may determine, or set, a new low-level capacitance value or a new high-level capacitance value, thereby adjusting the range of capacitance values detected by a capacitive pad <NUM>. Additionally, in some instances, the continuous calibration may reduce a dependence on the process <NUM> determining the discrete gesture detection at <NUM>.

In some instances, the process <NUM> may assign a weight or percentage to a newly detected low-level capacitance value or a newly detected high-level capacitance value to update the low-level capacitance value or high-level capacitance value, respectively. For instance, if the process <NUM> detects a capacitance value below a previously detected low-level capacitance value for a certain amount of time, the process <NUM> may weigh the capacitance value to update the low-level capacitance value.

Additionally, the low-level capacitance value or high-level capacitance value may decay over time depending on how the user grips the controller <NUM>, environmental conditions (e.g., humidity), or other properties (e.g., skin wetness). The amount the low-level capacitance value and the high-level capacitance value may decay may be limited, such that the low-level capacitance value and the high-level capacitance value are separated by a threshold amount of range to reduce sensor noise. In some instances, the decay may depend on time and/or a rate of change in the capacitance values. For instance, if the user taps their fingers on the controller <NUM>, or the controller <NUM> switches users, thereby potentially causing a change in the capacitance values received, the rate of decay may increase to reduce an amount of time required to update the low-level and/or the high-level capacitance values.

As a result of the grip calibration at <NUM>, and the sub-blocks <NUM>-<NUM>, the capacitive values sensed from each capacitive pad <NUM> may be normalized on a scale of [<NUM>,<NUM>]. The scale of [<NUM>,<NUM>] may represent, for a particular grip of a user and for the individual capacitive pads <NUM>, the high and low levels for the capacitance values sensed from the touch sensor <NUM>.

At <NUM>, the process <NUM> may perform a weighted sum of the capacitive values. As the capacitive values are normalized on the scale of [<NUM>,<NUM>], the process <NUM> may assign a weight to capacitance values from the capacitive pads <NUM> depending on the controller configuration. That is, the capacitance values are normalized between [<NUM>,<NUM>] and weights are assigned to individual capacitance values received the individual capacitive pads <NUM>. For instance, if a certain controller configuration includes five capacitive pads <NUM> assigned to a particular finger, the capacitance values may include an equal weight (e.g., one-fifth). In other words, when the capacitive pads <NUM> detect a maximum capacitance value, the output of the weighted sum may equal one.

As shown, determining the weighted sum may involve sub-blocks <NUM>, <NUM>, <NUM>, and <NUM>. Sub-block <NUM> may include the controller configuration models for the controller <NUM>. Noted above, the controller configurations designate a mapping of capacitive pads <NUM> of the touch sensor <NUM> to associate certain capacitive pads <NUM> with certain fingers of the user.

At sub-block <NUM>, the process <NUM> may perform a dynamic controller configuration selection, where the process <NUM> inputs the capacitance values into the controller configuration model(s) to determine a best match, or highest matched, controller configuration according to the grip of the user. Selecting the controller configuration may involve determining a ratio of (<NUM>) the variance of capacitance values for a group of capacitive pads <NUM> assigned to a particular finger and (<NUM>) the variance of capacitance values between groups of capacitive pads. A ratio is calculated for each controller configuration to determine a most likely matched configuration for the grip of the user.

At sub-block <NUM>, the process <NUM> may filter noise contained within the capacitance values. For instance, when a finger is not touching the controller <NUM>, such as when a finger is fully extended, those capacitive pads <NUM> associated with the finger not touching the controller <NUM> may be susceptible to noise. Here, detecting a small amount of capacitance may cause a large amount of noise within the received capacitance value. In instances where the capacitance values from the touch sensor <NUM> for individual capacitive pads <NUM> fall below a certain threshold, or if the capacitance values are within a certain limit of the low-level capacitance value for the capacitive pads <NUM>, the process <NUM> may suppress a detected capacitance. In other instances, in such scenarios, the process <NUM> may assign a low weight to the capacitance values.

At sub-block <NUM>, the process <NUM> may reject certain capacitance values from capacitive pads <NUM> of the touch sensor <NUM> and/or fingers associated with respective capacitive pads <NUM>. For instance, at <NUM> the process <NUM> may identify capacitive pads <NUM> that have a small range between the low-level capacitance value or high-level capacitance value. In these scenarios, capacitance values received by the capacitive pads <NUM> may introduce noise and disregarding certain capacitive pads <NUM>, or groups of capacitive pads <NUM>, may increase a reliability that the touch sensor data corresponds to the hand gesture of the user. That is, if the range of capacitance values detected by a capacitive pad <NUM> is small, the capacitive pad <NUM> may be susceptible to large amounts of noise.

Additionally, or alternatively, certain fingers may be associated with a number of capacitive pads <NUM> having a low reliability. Rejecting certain fingers, or a group of capacitive pads <NUM>, introduces a contingency behavior for controller configurations for small hand. In these scenarios, a respective finger may associate with adjacent fingers (e.g., pinky finger associates with ring finger).

At <NUM>, the process <NUM> may perform a final normalization. For example, in some instances, a capacitive pad <NUM> assigned to a particular finger may not detect a capacitance value or the capacitance values may be unreliable. Here, the user may not touch certain capacitive pads <NUM> of the touch sensor <NUM> because of the size of the hand or in instances where the user readjusted his or her grip. Additionally, in some instances where the low-level and high-level capacitance values are narrow, or separated by a small range, the capacitance values may be unreliable and noise may significantly impact finger motion. To eliminate or decrease noise from these capacitive pad(s) <NUM>, the final normalization <NUM> may determine a reliability of the capacitance values, and if a reliability is low, the weight of a capacitive value from a capacitive pad <NUM> is removed from the weighted sum. Therein, the capacitive values are summed and divided by the sum of the weights of the capacitive pads <NUM> being used.

At <NUM>, the process <NUM> may filter and curve fit the touch sensor data to represent a hand gesture of the user. The filtering and curve fitting may involve linearizing the final normalization of the touch data on the [<NUM>,<NUM>] scale to achieve a linear relationship between the touch sensor data and a position of a finger (e.g., curled, extended, half-way extended, etc.). For instance, the final normalization values determined at <NUM> may follow an exponential curve, such that as the hand of the user comes into proximity of the controller <NUM>, or grips the controller <NUM>, the final normalized values exponentially increase. In other words, the summed capacitance value may be exponentially related to the proximity with the finger disposed on/around the controller <NUM>. Linearizing the values on a [<NUM>,<NUM>] scale such that the capacitance values are correlated with a finger position may reduce sensitivity and an impact that noise may have when a finger is extended from the controller <NUM>, as well as when a finger touches or is in close proximity to the controller <NUM>.

As shown, the filtering and curve fitting may involve various sub-blocks to achieve final values that are utilized to generate hand gestures. At the filtering and curve fit stage <NUM>, the process <NUM> may apply filtering before or after the curve fit. For instance, the sub-blocks may involve filtering capacitance values within the low-level range of capacitance values when the capacitive pads <NUM> are susceptible to noise. In other words, within the high-level capacitance range, such as when the fingers grip the controller <NUM> or are in close proximity to the controller <NUM>, the capacitive pads <NUM> are less susceptible to noise.

The process <NUM> may apply adaptive filtering at <NUM> to adjust the amount of filtering performed on the capacitance values. The adaptive filtering may adaptively filter to more aggressively filter the capacitance values within the low-range of capacitance values compared to the capacitance values are within the high range of capacitance values. As shown, the adaptive filtering may involve sub-blocks <NUM>, <NUM>, and <NUM>. In general, the adaptive filtering at <NUM> may utilize the results of sub-blocks <NUM>, <NUM>, and <NUM> to determine how much noise exists in the normalized value to determine an amount of filtering to be applied to the normalized capacitance values. Determining an amount of noise that exists in the capacitance values may involve determining which capacitive pads <NUM> are being used to generate the capacitance values, as well as the high-level and low-level capacitance values for the respective capacitive pads <NUM>. For instance, the capacitive pads <NUM> may have a baseline noise and if the range between the high-level and low-level capacitance values for a capacitive pad <NUM> is low, the baseline noise of the capacitive pad <NUM> may equate to a large amount of finger movement (i.e., baseline noise is a large fraction of the range of capacitance values the capacitive pad <NUM> is able to sense). Here, the signal to noise ratio may be high. Comparatively, if the range between the high-level and low-level capacitance values for a capacitive pad <NUM> is large, then the baseline noise of the capacitive pad <NUM> may not introduce a large amount of finger movement. In these scenarios, to reduce the noise within the capacitance values, when the range of capacitance values is small, the process <NUM> may filter capacitance values more heavily than when the range of capacitance values is larger. The filtering and curve fit <NUM> may be repeated for each capacitive pad <NUM> as each capacitive pad <NUM> may include respective high and low level capacitance values. Additionally, the amount of filtering applied at <NUM> may depend on which capacitive pads <NUM> and/or which capacitive pads <NUM> have been rejected (e.g., pad and finger rejection <NUM>).

The sum noise prediction at <NUM> may filter the capacitance values based on which capacitive pads <NUM> are being used, the weights assigned the capacitive pads <NUM>, as well as the respective baseline noise for the capacitive pads <NUM>. For instance, the process <NUM> may include a default capacitive pad noise at <NUM>, which may represent an estimated baseline noise for individual capacitive pads <NUM>. The sum noise prediction step at <NUM> may therefore determine, for those capacitive pads <NUM> being used, their respective baseline noise values. The sum noise prediction step may also determine the expected or predicted noise for the capacitive pads <NUM>. For instance, if the capacitive pads <NUM> being used sense capacitive values over a large range (i.e., between the low level and high level capacitance values), the capacitance values may include a low amount of noise and less filtering may be applied. However, if the range of capacitance values for a capacitive pad <NUM> is narrow (i.e., between the low level and high level capacitance values), then the capacitance values may include a large amount of noise and the process <NUM> may apply a greater amount of filtering.

The dNorm/dt at <NUM> may take into consideration a change in capacitance value over time. For instance, if the received capacitance values from a capacitive pad <NUM> change significantly over a short period of time (e.g., one frame), the potential noise introduced within the capacitance values may be disregarded or weighted accordingly. That is, instead of filtering the capacitive values and introducing latency, if the capacitance values change over a threshold amount over a threshold amount of time, less filtering may be applied to the capacitive values. In this sense, less filtering may be applied when greater finger movement is detected and more filtering may be applied when less finger movement is detected.

The dCurl/dNorm at <NUM> may filter the normalized capacitance value based on an amount of capacitance detected. For instance, in the high-range of capacitance values, where the finger grips the controller, less filtering may be applied because the noise may have less of an impact on finger position. However, at the low range of capacitance values, where the finger is displaced from the controller, or in close proximity, more filtering may be applied because small changes in capacitance values may have a significant impact on the position of the finger. Here, a small change in capacitance values may result in a large change of the finger gesture.

At sub-block <NUM>, the lo-pass filter may represent a tunable lo-pass mean filter that adjusts the amount of filtering on detected capacitance values. In some instances, the amount of filtering may be on a scale of [<NUM>,<NUM>] and may be based on the result of the amount of filtering determined at the adaptive filter <NUM>. That is, the lo-pass filter may filter the capacitance values as determined from the adaptive filtering.

At sub-block <NUM>, the process <NUM> may curve fit the capacitance values on a [<NUM>,<NUM>] scale to associate the capacitance values with a position of the finger, or a hand animation. For each finger, the output of the curve fit may include a number for each finger, where the number indicates the finger position of each finger of the hand.

At sub-block <NUM>, the process <NUM> may apply a backlash filter after the curve to filter changes in capacitance values that fall below a threshold. For instance, if the capacitance values do not change by a threshold amount on the [<NUM>,<NUM>] scale, the capacitance values may be filtered. Such filtering may reduce perceived finger twitching and motion by the user.

At sub-block <NUM>, the joint model may correspond to a hand animation (e.g., a hand skeleton). For instance, the joint model may generate a hand animation corresponding to the number assigned to individual fingers of the hand from the curve fit at <NUM>.

<FIG> illustrates example components of a controller <NUM>, such as the controller <NUM>. As illustrated, the controller <NUM> includes one or more input/output (I/O) devices <NUM>, such as the controls described above (e.g., joysticks, trackpads, triggers, etc.), and/or potentially any other type of input or output devices. For example, the I/O devices <NUM> may include one or more microphones to receive audio input, such as user voice input. In some implementations, one or more cameras or other types of sensors (e.g., inertial measurement unit (IMU)) may function as input devices to receive gestural input, such as motion of the controller <NUM>. In some embodiments, additional input devices may be provided in the form of a keyboard, keypad, mouse, touch screen, joystick, control buttons and the like. The input device(s) may further include control mechanisms, such as basic volume control button(s) for increasing/decreasing volume, as well as power and reset buttons. The output devices, meanwhile, may include a display, a light element (e.g., LED), a vibrator to create haptic sensations, a speaker(s) (e.g., headphones), and/or the like. There may also be a simple light element (e.g., LED) to indicate a state such as, for example, when the controller <NUM> is powered on. While a few examples have been provided, the controller <NUM> may additionally or alternatively comprise any other type of output device.

In some instances, output by the one or more output devices may be based on input received by one or more of the input devices. For example, selection of a control touch input at the controller <NUM> may result in the output of a haptic response by a vibrator located adjacent (e.g., underneath) the control and/or at any other location. In some instances, the output may vary based at least in part on a characteristic of the touch input on a touch sensor <NUM>, such as the capacitive pads <NUM> disposed on/within the handle <NUM> of the controller <NUM>. For example, a touch input at a first location on the handle <NUM> may result in a first haptic output, while a touch input at a second location on the handle <NUM> may result in a second haptic output. Furthermore, a particular gesture on the handle <NUM> may result in a particular haptic output (or other type of output). For instance, a tap and hold gesture (detected by the touch sensor <NUM>) on the handle <NUM> may result in a first type of haptic output, while a tap and release gesture on the handle <NUM> may result in a second type of haptic output, while a hard tap of the handle <NUM> may result in a third type of haptic output.

In addition, the controller <NUM> may include one or more communication interfaces <NUM> to facilitate a wireless connection to a network and/or to one or more remote systems (e.g., a host computing device executing an application, a game console, other controllers, etc.). The communication interfaces <NUM> may implement one or more of various wireless technologies, such as Wi-Fi, Bluetooth, radio frequency (RF), and so on. Additionally, or alternatively, the controller <NUM> may include physical ports to facilitate a wired connection to a network, a connected peripheral device, or a plug-in network device that communicates with other wireless networks.

In the illustrated implementation, the controller <NUM> further includes one or more processors <NUM> and computer-readable media <NUM>. In some implementations, the processors(s) <NUM> may include a central processing unit (CPU), a graphics processing unit (GPU), both CPU and GPU, a microprocessor, a digital signal processor, or other known processing units or components. Additionally, or alternatively, the functionally described herein can be performed, at least in part, by one or more hardware logic components. For example, and without limitation, illustrative types of hardware logic components that can be used include field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), application-specific standard products (ASSPs), system-on-a-chip systems (SOCs), complex programmable logic devices (CPLDs), etc. Additionally, each of the processor(s) <NUM> may possess its own local memory, which also may store program modules, program data, and/or one or more operating systems.

The computer-readable media <NUM> may include volatile and nonvolatile memory, removable and non-removable media implemented in any method or technology for storage of information, such as computer-readable instructions, data structures, program modules, or other data. Such memory includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, RAID storage systems, or any other medium which can be used to store the desired information and which can be accessed by a computing device. The computer-readable media <NUM> may be implemented as computer-readable storage media ("CRSM"), which may be any available physical media accessible by the processor(s) <NUM> to execute instructions stored on the computer-readable media <NUM>. In one implementation, CRSM may include random access memory ("RAM") and Flash memory. In other implementations, CRSM may include, but is not limited to, read-only memory ("ROM"), electrically erasable programmable read-only memory ("EEPROM"), or any other tangible medium which can be used to store the desired information and which can be accessed by the processor(s) <NUM>.

Several modules such as instruction, datastores, and so forth may be stored within the computer-readable media <NUM> and configured to execute on the processor(s) <NUM>. A few example functional modules are shown as stored in the computer-readable media <NUM> and executed on the processor(s) <NUM>, although the same functionality may alternatively be implemented in hardware, firmware, or as a system on a chip (SOC). An operating system module <NUM> may be configured to manage hardware within and coupled to the controller <NUM> for the benefit of other modules. In addition, the computer-readable media <NUM> may store a network-communications module <NUM> that enables the controller <NUM> to communicate, via one or more of the communication interfaces <NUM>, with one or more other devices, such as a personal computing device executing an application (e.g., a game application), a game console, a remote server, other controller(s), computing devices, or the like. The computer-readable media <NUM> may further include a game-session database <NUM> to store data associated with a game (or other application) executing on the controller <NUM> or on a computing device coupled to the controller <NUM>.

The computer-readable media <NUM> may also include a device record database <NUM> that stores data associated with devices coupled to the controller <NUM>, such as the personal computing device, game console, remote server, or the like. The computer-readable media <NUM> may further store game-control instructions <NUM> that configure the controller <NUM> to function as a gaming controller, and universal-control instructions <NUM> that configure the controller <NUM> to function as a controller of other, non-gaming devices. The computer-readable media <NUM> may additionally store controller configuration(s) <NUM>. The controller configuration(s) <NUM> may represent or include data associated with the assignment of the capacitive pads <NUM> of the touch sensor <NUM> to associate certain capacitive pads <NUM> with respective fingers of a user operating the controller <NUM>.

Claim 1:
A method, executed by one or more processors (<NUM>) of a controller (<NUM>; <NUM>), comprising:
receiving (<NUM>) capacitance values provided by a proximity sensor (<NUM>) of a handle (<NUM>) of the controller (<NUM>; <NUM>), wherein the proximity sensor has capacitive pads (<NUM>), at least some of which are arranged into columns and rows, and the capacitive values are provided by the capacitive pads when one or more objects are in proximity to the handle of the controller;
determining (<NUM>) a first score for a first controller configuration (<NUM>) based at least in part on the capacitance values;
determining (<NUM>) a second score for a second controller configuration (<NUM>) based at least in part on the capacitance values;
ranking (<NUM>) the first score and the second score;
selecting (<NUM>) the first controller configuration based on the first score having a higher ranking than the second score; and
configuring (<NUM>) the controller according to the selected first controller configuration.