Patent Description:
An amusement park may include various attractions that are useful in providing guests with motion experiences and/or visual experiences. For example, an attraction may include a ride vehicle that travels along a path (e.g., a ride track) to provide motion experiences to the guests. In some cases, an attraction may include a ride vehicle that is configured to roll, pitch, and/or yaw while remaining fixed at a location (e.g., without traveling along a path) to provide motion experiences to the guests. In some cases, an attraction may include virtual reality (VR) devices that are worn by the guests to provide visual experiences to the guests. It is presently recognized that it may be desirable to enhance motion experiences and/or visual experiences for the guests of the amusement park.

<CIT> describes an amusement ride having a track with a curved portion, a carriage for holding an occupant that is movable along the track, and a braking system. At least part of the carriage will move in response to at least one inertial force acting upon the carriage as the carriage traverses the curved portion of the track, in the absence of a counteraction by an occupant of the carriage. The braking system operates in response to the movement of the at least part of the carriage to induce a braking force. Upon an action by an occupant of the carriage to counteract the induction of the braking force, the braking force acting on the carriage is reduced or substantially avoided.

These embodiments are not intended to limit the scope of the disclosure, which is determined by the appended claims, but rather these embodiments are intended only to provide a brief summary of certain disclosed embodiments. Indeed, the present disclosure may encompass a variety of forms that may be similar to or different from the embodiments set forth below, but which are within the scope of the appended claims.

According to an aspect of the present invention, a ride vehicle control system for a ride vehicle of an attraction includes multiple sensors that are configured to monitor a guest supported by the ride vehicle. The ride vehicle control system also includes an actuator system configured to couple to the ride vehicle. The ride vehicle control system further includes one or more processors that are configured to receive signals from the multiple sensors, wherein the signals are indicative of a position of the guest, a movement of the guest, or both. The one or more processors are also configured to determine an intended movement for the ride vehicle based on the signals and to control the actuator system to adjust a resistance to movement of the ride vehicle to facilitate the intended movement.

According to another aspect of the present invention there is provided a method of operating a ride vehicle control system for a ride vehicle of an attraction. The method comprises receiving, at one or more processors, signals from a plurality of sensors configured to monitor a guest supported by the ride vehicle, wherein the signals are indicative of a position of the guest, a movement of the guest, or both. The method further comprises determining, using the one or more processors, an intended movement for a ride vehicle based on the signals, and controlling, using the one or more processors, an actuator system coupled to the ride vehicle in use, to adjust a resistance to movement of the ride vehicle, to adjust a force applied to the ride vehicle, or both to facilitate the intended movement.

Present embodiments are directed to a ride vehicle control system for an attraction of an amusement park. The ride vehicle control system is configured to control an actuation system of a ride vehicle that accommodates a guest (e.g., rider) to provide a motion experience to the guest. Generally, the guest may provide inputs to the ride vehicle control system by moving relative to the ride vehicle, and the ride vehicle control system may control the actuation system of the ride vehicle based on the inputs to provide the motion experience to the guest. More particularly, the ride vehicle control system may include one or more sensors that monitor head position and/or movement, eye position and/or movement, and/or body position and/or movement (e.g., hands, limbs, and/or shifting weight) of the guest. A vehicle controller may receive, from the one or more sensors, signals that are indicative of the position(s) and/or movement(s) of the guest. Then, the vehicle controller may determine an intent of the guest based on the position(s) and/or movement(s) of the guest, and the vehicle controller may control the ride vehicle in accordance with the intent of the guest. As discussed in more detail below, the vehicle controller may receive additional inputs that relate to ride elements (e.g., physical ride elements, such as animatronic characters; virtual ride elements, such as virtual characters that are presented to the guest via a virtual reality (VR) device), and the vehicle controller may determine the intent of the guest based on the additional inputs. Advantageously, the disclosed techniques may provide the guest with a more responsive and/or immersive experience.

As illustrated in <FIG>, an attraction <NUM> includes a ride vehicle control system <NUM> having a vehicle controller <NUM> and a ride vehicle <NUM> (e.g., a motion simulator). In an embodiment, the ride vehicle <NUM> may include a seat <NUM> that is configured to accommodate a guest <NUM> (e.g., rider). While the guest <NUM> is in the ride vehicle <NUM>, the guest <NUM> may also receive a virtual experience via a VR device <NUM> (e.g., VR headset, wearable visualization device, head-mounted sensor device) that includes or is coupled to a VR controller <NUM> (e.g., additional controller).

It should be appreciated that the ride vehicle <NUM> may take any suitable form or appearance, such as one including a sled, a motorcycle, a car, an animal, a surfboard, a skateboard, and so forth. Additionally, while the ride vehicle control system <NUM> is discussed herein with reference to the ride vehicle <NUM> that supports one guest <NUM> to facilitate discussion, it should be appreciated that similar techniques may be applied to adapt the ride vehicle control system <NUM> for a multi-passenger ride vehicle that supports multiple guests. It should also be appreciated that the VR device <NUM> is optional and may not be provided as part of the attraction <NUM>. For example, the guest <NUM> may not wear (e.g., on their head) any device that is integrated as part of the ride vehicle control system <NUM> and/or the guest <NUM> may not be presented with virtual features (e.g., the guest <NUM> may view a real-world environment). Furthermore, in an embodiment, the guest <NUM> may wear a non-VR device (e.g., eye-glasses, head-mounted strap) that includes head-mounted sensors that monitor the guest <NUM> to facilitate the disclosed techniques. In such cases, the VR controller <NUM> is not configured to coordinate the virtual experience, but instead may be utilized to receive signals from the head-mounted sensors that monitor the guest <NUM> and/or to provide the signals or other data (e.g., based on processing the signals from the head-mounted sensors) to the vehicle controller <NUM> (thus, the VR controller may be referred to as any type of additional controller, such as a guest-tracking controller, instead of the VR controller).

The ride vehicle <NUM> may have any of a variety of configurations that enable the guest <NUM> to provide inputs (e.g., by moving their head, eyes, and/or body) to control movement of the ride vehicle <NUM>. For example, in an embodiment, the seat <NUM> may be coupled to a top surface <NUM> of a spring plate <NUM> (e.g., solid plate; open framework) of the ride vehicle <NUM>. Springs <NUM> may be engaged with or coupled to a bottom surface <NUM> of the spring plate <NUM>. The springs <NUM> may provide resistance to movement of the spring plate <NUM> (e.g., relative to other components of the ride vehicle <NUM>). The ride vehicle <NUM> may include a base <NUM> that is coupled to a support beam <NUM> via struts <NUM>, and the support beam <NUM> is also coupled to the bottom surface <NUM> of the spring plate <NUM> via a pivot joint <NUM>. The pivot joint <NUM> may enable the spring plate <NUM> to rotate via roll <NUM> (e.g., roll movement) and pitch <NUM> (e.g., pitch movement) relative to the base <NUM>. In an embodiment, the base <NUM> may be generally stationary relative to a ground surface <NUM>. However, it should be appreciated that the base <NUM> may move relative to the ground surface <NUM>, such as when the base <NUM> is part of a larger ride vehicle that traverses a path (e.g., a track).

In an embodiment, the pivot joint <NUM> may be a spherical bearing joint or universal joint that also enables the spring plate <NUM> to rotate via yaw <NUM> (e.g., yaw movement; about an axis that is parallel to a vertical axis <NUM>) relative to the base <NUM>. However, the pivot joint <NUM> may be configured to only enable movement along a single axis (e.g., corresponding to a single degree of freedom) or two axes (e.g., corresponding to two degrees of freedom), which may be suitable for simplified attractions. For example, to provide rotation around the single axis, the pivot joint <NUM> may be a gimbal or a hinged gimbal expansion joint. In any case, the base <NUM>, the support beam <NUM>, and the pivot joint <NUM> generally form a support assembly <NUM> that supports the spring plate <NUM>, while allowing one or more degrees of freedom of pivotal movement of the spring plate <NUM>.

The VR device <NUM> that may be worn by the guest <NUM> utilizes VR techniques, augmented reality (AR) techniques, and/or mixed reality (e.g., a combination of VR and AR) techniques to render a virtual experience for the guest <NUM>. For example, the VR controller <NUM> may include a processor <NUM> and a memory <NUM>, and the processor <NUM> may execute instructions stored in the memory <NUM> to instruct a display of the VR device <NUM> to present a set of virtual images corresponding to the virtual experience. The VR controller <NUM> and the vehicle controller <NUM> may be communicatively coupled to one another via respective communication components <NUM> (e.g., wireless or wired). In this way, the virtual experience provided via the VR device <NUM> and motion of the ride vehicle <NUM> may be coordinated with one another. For example, the VR controller <NUM> may adjust the virtual images that are presented to the guest <NUM> based on settings for and/or the movement of the spring plate <NUM>. Furthermore, the virtual experience provided via the VR device <NUM> may be selected to correspond with a physical appearance of the ride vehicle <NUM> and/or a theme of the attraction <NUM> to thereby provide an immersive experience to the guest <NUM>. For example, in an embodiment in which the attraction <NUM> is themed as a jungle, the seat <NUM> of the ride vehicle <NUM> may be designed as an animal, and the virtual experience may be displayed to the guest <NUM> as a race through the jungle.

In an embodiment, the ride vehicle <NUM> may include components that enable semi-passive control of the ride vehicle <NUM>, which may provide advantages with respect to the experience of the guest <NUM> (e.g., compared to entirely passive or entirely active systems). For example, the ride vehicle <NUM> may include resistance-adjusting features, such as an actuator plate <NUM> (e.g., solid plate; open framework) positioned between the spring plate <NUM> and the base <NUM>, relative to the vertical axis <NUM>. In an embodiment, actuators <NUM> are coupled between the actuator plate <NUM> and the base <NUM> to adjust a position of the actuator plate <NUM> relative to the base <NUM> based on instructions from the vehicle controller <NUM>. In particular, the vehicle controller <NUM> may include a processor <NUM> and a memory <NUM>, and the processor <NUM> may execute instructions stored in the memory <NUM> to instruct the actuators <NUM> to contract or extend to any suitable actuator length, between a fully contracted length and a fully extended length, to position the actuator plate <NUM> at a particular separation distance <NUM> from the spring plate <NUM>. The actuators <NUM> may be any suitable components that facilitate movement of the actuator plate <NUM>, including electric actuators, hydraulic actuators, pneumatic actuators, magnetic actuators, mechanical actuators, and/or servo motors, and so forth. In an embodiment, the actuator plate <NUM> may not be directly coupled to the spring plate <NUM> (e.g., the actuator plate <NUM> and the spring plate <NUM> may be physically separated from one another along the vertical axis <NUM> at least in certain positions and/or at certain times during operation).

The springs <NUM> may selectively contact and compress against the actuator plate <NUM> in response to movements of the guest <NUM>. For example, when the guest <NUM> leans to shift their weight relative to the support beam <NUM>, the pivot joint <NUM> enables the spring plate <NUM> to rotate (e.g., tilt) accordingly, thus placing a corresponding portion of the springs <NUM> in contact (e.g., engaged) with a top surface <NUM> of the actuator plate <NUM>. As the guest <NUM> continues to lean to shift their weight, the springs <NUM> that are in contact with the top surface <NUM> compress and provide resistance to slow and eventually stop the movement of the spring plate <NUM>. By adjusting the separation distance <NUM> between the spring plate <NUM> and the actuator plate <NUM>, the ride vehicle control system <NUM> may effectively adjust the effective spring constant of the springs <NUM> to tune the ride vehicle <NUM> to provide a feeling of neutral buoyancy and/or appropriate responsiveness to the guest <NUM> that is suited for any one of multiple VR experiences delivered by the VR device <NUM>.

Although two springs <NUM> and two actuators <NUM> are illustrated for simplicity, it should be understood that these are representative of any number of such features. Indeed, any suitable number of springs <NUM> and actuators <NUM> may be included in the ride vehicle <NUM>, including one spring <NUM> and/or one actuator <NUM>. For example, in embodiments having a single actuator <NUM>, the single actuator <NUM> may include any suitable four-bar linkage, scissor linkage, guide rails combined with wheels, or any other suitable linkage mechanism that enables the single actuator <NUM> to adjust the position of the actuator plate <NUM> in one or multiple dimensions. Additionally, in embodiments having a single spring <NUM>, the single spring <NUM> may be disposed at a central position corresponding to an expected center of mass of the guest <NUM>. It should also be understood that the springs <NUM>, which are illustrated as mechanical, helical, or coil springs, may include or represent any suitable biasing members or resistance devices (e.g., gas springs, air springs, elastomers, leaf springs, stiff air bladders, conical spring washers, such as Belleville washers, gas struts, or magnetic repulsion assemblies, or any combination thereof). That is, any suitable device that applies a variable force as a function of a dimension of the suitable device is presently contemplated for use in the ride vehicle control system <NUM>.

Additionally, although illustrated with the springs <NUM> of the spring plate <NUM> separated from the actuator plate <NUM>, in other embodiments, the springs <NUM> may be coupled between the spring plate <NUM> and the base <NUM> to provide a normalizing bias to the spring plate <NUM>. Moreover, it should be understood that the springs <NUM> may be coupled at any suitable position in the ride vehicle <NUM> that enables selective engagement of the springs <NUM>, including positions in which the springs <NUM> engage with any suitable surface of the actuator plate <NUM>, via cantilever action or any other suitable force-distributing components. That is, the suitable position may be any suitable position from which the springs <NUM> are engaged in response to rotation of the spring plate <NUM> beyond a threshold angle. In an embodiment, one or both ends of the springs <NUM> may be coupled to the spring plate <NUM> and selectively compressed between the spring plate <NUM> and the actuator plate <NUM>. In an embodiment, the springs <NUM> may be coupled to the top surface <NUM> of the actuator plate <NUM>. Together, the springs <NUM>, the actuators <NUM>, and related components may form a spring-based actuation system. Furthermore, it should be appreciated that any of a variety of spring-based actuation systems (e.g., having springs) may be implemented in the ride vehicle <NUM>.

<FIG> illustrates an embodiment of a motor-based actuation system that may be used in the ride vehicle <NUM> of the attraction <NUM>. As shown, the motor-based actuation system includes motors <NUM> and linkage systems <NUM> that operate to drive movement of the spring plate <NUM> about the pivot joint <NUM> of the support beam <NUM> (e.g., to drive movement of the spring plate <NUM> relative to the base <NUM>). Each motor <NUM> (e.g., an electromechanical motor, a pneumatic motor, a hydraulic motor) may operate to adjust resistance to movement of the spring plate <NUM> about the pivot joint <NUM>. In an embodiment, each motor <NUM> is coupled to a respective gearbox <NUM> and/or a respective linkage system <NUM>. For example, the motor <NUM> may be coupled to the gearbox <NUM>, and the gearbox <NUM> may be coupled to a first bracket <NUM> of the linkage system <NUM>. Thus, a torque output by the motor <NUM>, such as to cause rotation of a shaft of the motor <NUM>, may drive rotation of gears of the gearbox <NUM> to cause rotation of the first bracket <NUM>. As an example, the motor <NUM> may utilize a keyless bushing to rotate the shaft and the gearbox <NUM> to enable smooth movement of the spring plate <NUM>. The first bracket <NUM> is coupled to a linkage <NUM> of the linkage system <NUM> at a first end <NUM> of the linkage <NUM>. Further, a second end <NUM> of the linkage <NUM> may be coupled to a second bracket <NUM> of the linkage system <NUM>, and the second bracket <NUM> may be coupled to a section (e.g., a corner, a side) of the bottom surface <NUM> of the spring plate <NUM>.

The motor <NUM> may be configured to output a torque that may control and/or drive rotational movement of the first bracket <NUM> about a respective horizontal axis <NUM> or a respective axis parallel to the horizontal axes <NUM>. Such rotational movement of the first bracket <NUM> may cause corresponding movement of the linkage <NUM> generally along an axis parallel to the vertical axis <NUM> to impart a force onto a respective section of the spring plate <NUM>. The imparted force may move (e.g., rotate, such as pitch and/or roll) the spring plate <NUM> relative to the base <NUM>. The linkage <NUM> may be rotatably coupled to the first bracket <NUM> and the second bracket <NUM>, such as via rotatable fasteners <NUM> (e.g., a shoulder screw) of the linkage system <NUM> to enable rotational movement between the linkage <NUM> and the brackets <NUM>, <NUM> about the respective horizontal axes <NUM>. The rotation between the linkage <NUM> and the brackets <NUM>, <NUM> may enable greater control of movement of the spring plate <NUM> relative to the base <NUM>. Moreover, the coupling between the linkage <NUM> and the brackets <NUM>, <NUM> may enable additional movement between the linkage <NUM> relative to the brackets <NUM>, <NUM> to facilitate movement of the spring plate <NUM> relative to the base <NUM>. As an example, the linkage <NUM> may linearly translate along the rotatable fasteners <NUM> and/or may rotate relative to the brackets <NUM>, <NUM> about another axis (e.g., via additional fasteners of the linkage system <NUM>).

In an embodiment, the linkage system <NUM> is supported via a plate <NUM> that extends between the base <NUM> and the actuator plate <NUM> (e.g., coupled to the support beam <NUM>). For instance, the plate <NUM>, which may be a part of the support assembly <NUM>, may be fixedly coupled to the actuator plate <NUM>, the base <NUM>, and/or the support beam <NUM>. The gearbox <NUM> may be fixedly coupled to the plate <NUM> to block movement between the gearbox <NUM> and the support assembly <NUM>, thereby stabilizing the linkage system <NUM>. In this manner, the plate <NUM> may facilitate provision, by the motors <NUM>, of desirable movement of the spring plate <NUM> relative to the base <NUM>.

In an embodiment, each motor <NUM> may be back-drivable. That is, sufficient force (e.g., caused by the guest <NUM> shifting their weight) imparted onto the spring plate <NUM> may cause movement of the spring plate <NUM> relative to the base <NUM> opposite the movement of the spring plate <NUM> caused by the torque output by the motors <NUM>. In other words, sufficient force may be used to cause rotation of any of the first brackets <NUM> in a direction opposite a direction of rotation caused by the torque output by the motors <NUM>. In this manner, the amount of torque output by the motors <NUM> to impart a force onto the spring plate <NUM> may adjust the amount of a counter-force needed to move the spring plate <NUM> relative to the actuator plate <NUM> against the torque output by the motors <NUM>. Thus, the torque output by the motors <NUM> sets a resistance to movement of the spring plate <NUM>. In particular, increasing the torque output may increase the resistance to movement, and reducing the torque output may reduce the resistance to movement. Each motor <NUM> may be communicatively coupled to the vehicle controller <NUM>, and the processor <NUM> may execute instructions stored in the memory <NUM> to control the motors <NUM> to output a particular torque to effectively adjust or to set the resistance to movement for the spring plate <NUM>. While the motor-based actuation system of <FIG> includes two motors and two linkage systems, it should be appreciated that any suitable number of motors and linkage systems may be utilized within the ride vehicle <NUM>. For example, <FIG> illustrates an embodiment of a motor-based actuation system that may be used in the ride vehicle <NUM>, wherein the motor-based actuation system includes three motors and three linkage systems. The three motors <NUM> may enable greater control of the movement of the spring plate <NUM> as compared to controlling the spring plate <NUM> via two motors <NUM>. As an example, in addition to pitching and/or rolling the spring plate <NUM> relative to the base <NUM>, the vehicle controller <NUM> may translate the spring plate <NUM> along an axis parallel to the vertical axis <NUM>, such as to heave the spring plate <NUM>.

<FIG> provide examples of components that may be included in the ride vehicle <NUM> to facilitate discussion; however, it should be appreciated that the ride vehicle <NUM> may have any of a variety of components and configurations.

With the foregoing in mind, <FIG> illustrates an embodiment of the ride vehicle <NUM> having an actuator system <NUM> (e.g., mechanical system) that may be controlled to adjust a resistance to movement of the spring plate <NUM> (e.g., to make it more difficult or to make it easier for the guest <NUM> to move the spring plate <NUM> by shifting their weight) and/or to actively adjust the spring plate <NUM> (e.g., to drive the spring plate <NUM>; adjust a force applied to the spring plate <NUM>). It should be appreciated that the actuator system <NUM> may include a spring-based actuator system (e.g., <FIG>), a motor-based actuator system (e.g., <FIG> and <FIG>), or any other suitable type of actuator system or mechanical system. The spring plate <NUM> may support the seat <NUM> for the guest <NUM>. The guest <NUM> may wear the VR device <NUM>, which may include or be coupled to the VR controller <NUM> having the processor <NUM> and the memory <NUM>.

It is presently recognized that each guest <NUM> may have different characteristics (e.g., weight, activity level, mobility), which may affect a manner in which each guest <NUM> moves during the ride cycle. Thus, the vehicle controller <NUM> may be configured to control the actuator system <NUM> (e.g., the actuators <NUM> of <FIG>; the motors <NUM> of <FIG>) to adjust the resistance to the movement of the spring plate <NUM> and/or to actively adjust the spring plate <NUM> to account for the different characteristics of each guest <NUM> so that each guest <NUM> may enjoy the attraction <NUM> (e.g., be provided with a motion experience in the ride vehicle <NUM>; feel like they are controlling the ride vehicle <NUM>). For example, the vehicle controller <NUM> may be configured to control the actuator system <NUM> based on inputs related to head position and/or movement, eye position and/or movement, and/or body position and/or movement (e.g., hands, limbs, and/or shifting weight) of the guest <NUM>.

In an embodiment, the vehicle controller <NUM> may be configured to receive signals from one or more sensors (e.g., the signals may be indicative of head position and/or movement, eye position and/or movement, and/or body position and/or movement), to process the signals to determine an intent of the guest <NUM>, and then to control the actuator system <NUM> in accordance with the intent of the guest <NUM>. For example, detection of the guest <NUM> leaning back and to the left may be interpreted as an intent of the guest <NUM> to control the ride vehicle <NUM> to travel up and to the left. As another example, detection of a head of the guest <NUM> tilting and/or turning to the left may be interpreted as an intent of the guest <NUM> to control the ride vehicle <NUM> to travel to the left.

In an embodiment, the ride vehicle control system <NUM> may include a head position sensor <NUM> (e.g., head tracking sensor) that is configured to monitor a position and/or movement of a head of the guest <NUM>. The position may be the position (e.g., angular position) relative to the body of the guest <NUM> and/or the position relative to the ground surface <NUM> or a gravity vector, and the movement may be a velocity, an acceleration, and/or a direction of movement. As shown, the head position sensor <NUM> may be worn on the head of the guest <NUM>. For example, the head position sensor <NUM> may be integrated into and/or coupled to the VR device <NUM> or other device that is worn on the head of the guest <NUM>. In some such cases, the head position sensor <NUM> may be an accelerometer and/or a gyroscope. However, it should be appreciated that the head position sensor <NUM> may be any other suitable type of sensor, such as an image sensor (e.g., LIDAR, infrared, camera-based, blob trackers, skeletal trackers, optical trackers, RFID readers that read RFID tags worn by the guest <NUM>) that is mounted onto the ride vehicle <NUM> or otherwise in proximity to the ride vehicle <NUM> so as to obtain images that indicate a relative position and/or movement of the head of the guest <NUM>. Regardless of a location and/or a type of the head position sensor <NUM>, the head position sensor <NUM> may provide signals indicative of the position and/or movement of the head of the guest <NUM> to the vehicle controller <NUM> (e.g., via wireless communication with the vehicle controller <NUM> and/or via the VR controller <NUM>).

As discussed above, the guest <NUM> may generally move (e.g., rotate) the spring plate <NUM> by moving their body (e.g., leaning their body; shifting their weight). However, the guest <NUM> may begin such movements (e.g., leaning movements) with their head. For example, the guest <NUM> may lead with their head, such that their head moves in a direction and then their body (e.g., center of gravity) moves in the direction. The vehicle controller <NUM> may process the signals from the head position sensor <NUM> to determine an intent of the guest <NUM> (e.g., intended movement for the ride vehicle <NUM>). For example, if the signals indicate that the guest <NUM> suddenly tilts their head to their left side, the vehicle controller <NUM> may determine that the guest <NUM> intends to tilt the spring plate <NUM> downward to their left side (e.g., roll). In response to determining the intent and the corresponding intended movement, the vehicle controller <NUM> may then reduce the resistance of the spring plate <NUM> to the intended movement (e.g., to enable the guest <NUM> to more easily tilt the spring plate <NUM> downward to their left side) and/or may actively adjust the spring plate <NUM> to achieve the intended movement (e.g., to tilt the spring plate <NUM> downward to their left side).

Advantageously, determining the intent of the guest <NUM> based on the signals from the head position sensor <NUM> (e.g., alone or in combination with other signals) may enable the ride vehicle <NUM> to move more easily for the guest <NUM> and/or may provide the guest <NUM> with a responsive ride experience even if the guest <NUM> has difficulty shifting their weight. Furthermore, because the guest <NUM> may tend to lead with their head, determining the intent of the guest <NUM> based on the signals from the head position sensor <NUM> may enable the vehicle controller <NUM> to anticipate (e.g., predict) how the guest <NUM> is likely to move their body. As a result, the resistance of the spring plate <NUM> and/or the adjustment to the spring plate <NUM> may occur prior to the movement of the body of the guest <NUM> and/or during an initial or beginning period of the movement of the body of the guest <NUM>. In this way, the guest <NUM> may feel like the spring plate <NUM> is moving with their body (e.g., without delay), and the guest <NUM> may have a more responsive, realistic motion experience.

The ride vehicle control system <NUM> may include other types of sensors that monitor features of the guest <NUM>, and the features of the guest <NUM> may be processed by the vehicle controller <NUM> to determine the intent of the guest <NUM>. For example, the ride vehicle control system <NUM> may include an eye position sensor <NUM> (e.g., eye tracking sensor) that is configured to monitor a position and/or movement of one or both eyes of the guest <NUM>. As shown, the eye position sensor <NUM> may be integrated into and/or coupled to the VR device <NUM> or other device that is worn on the head of the guest <NUM>. However, in an embodiment in which the guest <NUM> does not wear the VR device <NUM> or other device that is worn on the head of the guest <NUM>, the eye position sensor <NUM> may be mounted onto the ride vehicle <NUM> or otherwise in proximity to the ride vehicle <NUM> so as to monitor the position and/or movement of one or both eyes of the guest <NUM>. As an example, the eye position sensor <NUM> may be an image sensor that is configured to obtain images indicative of a point of gaze (e.g., where the guest <NUM> is looking) and/or motion of the eye relative to the head of the guest <NUM>. Regardless of a location and/or a type of the eye position sensor <NUM>, the eye position sensor <NUM> may provide signals indicative of the position (e.g., the point of gaze) and/or movement of one or both eyes of the guest <NUM> to the vehicle controller <NUM> (e.g., via wireless communication with the vehicle controller <NUM> and/or via the VR controller <NUM>).

As discussed above, the guest <NUM> may generally move (e.g., rotate) the spring plate <NUM> by moving their body (e.g., leaning their body; shifting their weight). However, the guest <NUM> may begin such movements (e.g., the leaning movements) with their head and/or their eyes. For example, the guest <NUM> may glance with their eyes in the direction that they want to move or lean, such that their eyes move in the direction and then their body (e.g., center of gravity) moves in the direction. The vehicle controller <NUM> may process the signals from the eye position sensor <NUM> to determine the intent of the guest <NUM>. For example, if the signals indicate that the guest <NUM> suddenly shifts their point of gaze to their left side, the vehicle controller <NUM> may determine that the guest <NUM> intends to rotate the spring plate <NUM> to their left side (e.g., yaw). In response to determining the intent and the corresponding intended movement, the vehicle controller <NUM> may then reduce the resistance of the spring plate <NUM> to the intended movement (e.g., to enable the guest <NUM> to more easily rotate the spring plate <NUM>) and/or may actively adjust the spring plate <NUM> to achieve the intended movement (e.g., to rotate the spring plate <NUM>).

It is also presently recognized that tracking one or both eyes of the guest <NUM> may be particularly useful with respect to determining that the guest <NUM> intends to lean backward (e.g., pitch; rotate the spring plate <NUM> backward such that a rear portion of the spring plate <NUM> behind the guest <NUM> is lower (e.g., closer to the ground surface <NUM>) than a front portion of the spring plate <NUM> in front of the guest <NUM>), as the guest <NUM> may be hesitant or have difficulty leaning their head and/or their body backward while being positioned in the ride vehicle <NUM>. Therefore, such movement of one or both eyes of the guest <NUM> may result in the vehicle controller <NUM> reducing the resistance of the spring plate <NUM> to make it easier for the guest <NUM> to rotate the spring plate <NUM> backward (e.g., with relatively little shift in weight) and/or actively adjusting the spring plate <NUM> to rotate the spring plate <NUM> backward.

Advantageously, determining the intent of the guest <NUM> based on the signals from the eye position sensor <NUM> (e.g., alone or in combination with other signals, such as the signals from the head position sensor <NUM>) may enable the ride vehicle <NUM> to move more easily for the guest <NUM> and/or may provide the guest <NUM> with a responsive ride experience even if the guest <NUM> has difficulty shifting their weight. Furthermore, because the guest <NUM> may tend to lead with their eyes, determining the intent of the guest <NUM> based on the signals from the eye position sensor <NUM> may enable the vehicle controller <NUM> to anticipate (e.g., predict) how the guest <NUM> is likely to move their body. As a result, the resistance of the spring plate <NUM> and/or the adjustment to the spring plate <NUM> may occur prior to the movement of the body of the guest <NUM> and/or during the initial or beginning period of the movement of the body of the guest <NUM>. In this way, the guest <NUM> may feel like the spring plate <NUM> is moving with their body (e.g., without delay), and the guest <NUM> may have a more responsive, realistic motion experience.

In an embodiment, the ride vehicle control system <NUM> may include an array of weight sensors <NUM> (e.g., in the seat <NUM> and/or in the spring plate <NUM>) that is configured to monitor a position and/or movement of a body of the guest <NUM> (e.g., shifting weight; shifting center of gravity). The weight sensors <NUM> may be pressure sensors that are spaced apart from one another and/or that extend across a seating surface for the guest <NUM>. In an embodiment, the ride vehicle control system <NUM> may include one or more grip sensors <NUM> that are configured to detect a grip strength (e.g., a force exerted by a hand of the guest <NUM>), a grip position (e.g., hand position; a direction of the force exerted by the hand of the guest <NUM>), and/or a grip movement (e.g., hand movement; a change in the force exerted by the hand of the guest <NUM>) of one or both hands of the guest <NUM>. The grip sensors <NUM> may be pressure sensors that are positioned on one or more handles of the ride vehicle <NUM> or on another portion of the ride vehicle <NUM> that is configured to be gripped by the guest <NUM> during the ride cycle. In an embodiment, the ride vehicle control system <NUM> may include one or more skeletal sensors <NUM> that are configured to monitor a position and/or movement of skeletal features (e.g., limbs) of the guest <NUM>. The skeletal sensors <NUM> may include image sensors (e.g., LIDAR, infrared, camera-based, blob trackers, skeletal trackers, optical trackers, RFID readers that read RFID tags worn by the guest <NUM>). The image sensors may be positioned on the ride vehicle <NUM> or in proximity to the ride vehicle <NUM> so as to monitor the position and/or movement of the skeletal features of the guest <NUM>. Regardless of a location and/or a type of the weight sensors <NUM>, the grip sensors <NUM>, and/or the skeletal sensors <NUM>, these sensors may provide signals indicative of the position and/or movement of the body of the guest <NUM> to the vehicle controller <NUM>.

As discussed above, the guest <NUM> may generally move (e.g., rotate) the spring plate <NUM> by moving their body (e.g., leaning their body; shifting their weight) relative to the seat <NUM>. The vehicle controller <NUM> may process the signals from the array of weight sensors <NUM> to determine the intent (e.g., intended movement) of the guest <NUM>. For example, the guest <NUM> may shift their weight to a left lateral edge of the seat <NUM> when the guest <NUM> wants to rotate the spring plate <NUM> downward on the left lateral side of the seat <NUM> (e.g., roll).

During the ride, the guest <NUM> may also adjust their grip (e.g., hand grip) at the grip sensors <NUM> in a manner that indicates their intent. For example, the guest <NUM> may grip the handles more tightly and/or push forward against the handles while the guest <NUM> wants to rotate forward (e.g., pitch), and/or the guest <NUM> may grip the handles more loosely and/or pull backward against the handles while the guest <NUM> wants to rotate backward (e.g., pitch). Similarly, the guest <NUM> may push forward against one of the handles and pull back against one of the handles while the guest <NUM> wants to rotate to one side or turn (e.g., yaw). During the ride, the guest <NUM> may adjust their skeletal features (e.g., limbs) in a manner that indicates their intent. For example, the guest <NUM> may bend their arms at their elbows while the guest <NUM> wants to rotate forward (e.g., pitch), and/or the guest <NUM> may straighten their arms at their elbows while the guest <NUM> wants to rotate backward (e.g., pitch). Similarly, the guest <NUM> may bend one elbow and straighten the other elbow while the guest <NUM> wants to rotate to one side or turn (e.g., yaw).

The vehicle controller <NUM> may process the signals from the array of weight sensors <NUM>, the grip sensors <NUM>, and/or the skeletal sensors <NUM> (e.g., alone or in combination with other signals, such as the signals from the head position sensor <NUM> and/or the eye position sensor <NUM>) to determine the intent of the guest <NUM>. As noted above, in response to determining the intent and the corresponding intended movement, the vehicle controller <NUM> may then reduce the resistance of the spring plate <NUM> to the intended movement (e.g., to enable the guest <NUM> to more easily move the spring plate <NUM>) and/or may actively adjust the spring plate <NUM> to achieve the intended movement (e.g., to move the spring plate <NUM>).

In an embodiment, the vehicle controller <NUM> may receive additional inputs (e.g., signals) that relate to ride elements, such as virtual features that are being presented to the guest <NUM> via the VR device <NUM>. The vehicle controller <NUM> may utilize the additional inputs to determine the intent of the guest <NUM>. For example, if the additional inputs indicate that the guest <NUM> is being presented with a virtual road that turns to their left, then the vehicle controller <NUM> may determine that the intent of the guest <NUM> is to turn to their left (e.g., yaw). In response to determining the intent and the corresponding intended movement, the vehicle controller <NUM> may then reduce the resistance of the spring plate <NUM> to the intended movement (e.g., to enable the guest <NUM> to more easily turn the spring plate <NUM>) and/or may actively adjust the spring plate <NUM> to achieve the intended movement (e.g., to turn the spring plate <NUM>).

It should be appreciated that the ride elements may be utilized as one of many inputs (e.g., in addition to the signals from the one or more sensors) to determine the intent of the guest <NUM>. In an embodiment, the ride elements may be utilized as a secondary input, such as in cases in which the signals from the one or more sensors conflict with one another (e.g., with respect to the intent of the guest <NUM>). For example, if the signals from at least a first sensor (e.g., the head position sensor <NUM>) indicate that the intent of the guest <NUM> is to turn to their left, but the signals from at least a second sensor (e.g., the grip sensors <NUM>) indicate that the intent of the guest <NUM> is to turn to their right, the vehicle controller <NUM> may consider the ride elements to determine the intent of the guest <NUM> and/or an appropriate way to control the actuator system <NUM> to provide the guest <NUM> with an enjoyable ride experience (e.g., that is most consistent or coordinated with the ride elements, such as to turn to their left where the virtual road turns to their left).

It should be appreciated that the ride elements may be virtual elements that are presented via the VR device <NUM>. In an embodiment, such as when the VR device <NUM> is not used during the ride cycle, the ride elements may include real, physical elements within the attraction <NUM>. Regardless of whether the ride elements are virtual elements or real, physical elements, the ride elements may include any of a variety of objects and/or effects, such as a road, a building, a character (e.g., an animal, robot), a flash of light, a sound, or the like. For example, depending on the ride element, the vehicle controller <NUM> may determine or consider that the intent of the guest <NUM> is to lean toward the ride element (e.g., so as to follow the character due to being interested in the character) or to lean away from the ride element (e.g., so as to avoid the sound due to being frightened by the sound).

The vehicle controller <NUM> may also control the actuator system <NUM> in different ways throughout the ride cycle (e.g., while the guest <NUM> is in the ride vehicle <NUM>; between boarding onto and deboarding from the ride vehicle <NUM>). For example, the ride cycle may include a first portion in which the actuator system <NUM> operates in a semi-passive mode to enable the guest <NUM> to control the movement of the ride vehicle <NUM> (e.g., by shifting weight), and the ride cycle may include a second portion in which the actuator system <NUM> operates in an active mode to actively drive the movement of the ride vehicle <NUM> and/or to block the guest <NUM> from controlling the movement of the ride vehicle <NUM> (e.g., by shifting weight). As another example, the ride cycle may include a first portion in which the actuator system <NUM> operates in the semi-passive mode with relatively low resistance (e.g., across a relatively low resistance range) to enable the guest <NUM> to control the movement of the ride vehicle <NUM> with relatively minor movements of their body (e.g., by shifting weight), and the ride cycle may include a second portion in which the actuator system <NUM> operates in the semi-passive mode with relatively high resistance (e.g., across a relatively high resistance range) to enable the guest <NUM> to control the movement of the ride vehicle <NUM> with relatively major movements of their body (e.g., by shifting weight). Thus, a movement (e.g., weight shift) during the first portion of the ride cycle may result in a first movement of the spring plate <NUM>, but the movement during the second portion of the ride cycle may result in a second movement of the spring plate <NUM> (or no movement of the spring plate <NUM>). The vehicle controller <NUM> may also adjust the resistance over a duration of the ride cycle by increasing the resistance in response to determining that the ride cycle is nearing completion, that the guest <NUM> is entering a particular region of a simulated environment supported by the VR device <NUM>, that the guest <NUM> has performed a certain task within the simulated environment, that the guest <NUM> has provided user input indicative of a requested resistance adjustment, and so forth. Varying the type of control (e.g., semi-passive, active) and/or the resistance may simulate different experiences during the ride cycle, such as driving along a road with easy control of the ride vehicle <NUM> during fair weather conditions and then being swept along the road with low control (or no control) of the ride vehicle <NUM> during poor weather conditions. In this way, the vehicle controller <NUM> controls the actuator system <NUM> in a manner that is coordinated with the ride cycle and/or the ride elements being presented to the guest <NUM>.

In an embodiment, the vehicle controller <NUM> may control the actuator system <NUM> to encourage and/or to result in certain outcomes. Furthermore, the VR controller <NUM> may also present the virtual features to encourage and/or to result in certain outcomes. For example, the vehicle controller <NUM> may control the actuator system <NUM> to reduce resistance to movement in a direction (e.g., reduced relative to other directions) to encourage the guest <NUM> to shift their weight to direct the ride vehicle <NUM> in the direction (e.g., by making it easier for the guest <NUM>). The VR controller <NUM> may at the same time present the virtual features, such as road blocks, that encourage the guest <NUM> to shift their weight to direct the ride vehicle <NUM> in the direction to avoid the virtual features. In this way, the vehicle controller <NUM> and/or the VR controller <NUM> may influence the movement of the ride vehicle <NUM>, while still allowing the guest <NUM> to feel like they are in control of the ride vehicle <NUM>.

As noted above, the intent of the guest <NUM> may be determined based on various factors (e.g., inputs; signals), such as the head position and/or movement, the eye position and/or movement, the body position and/or movement, and/or the ride elements. The vehicle controller <NUM> may input the various factors into algorithms, which may include lookup tables (e.g., that associate the various detected movements with corresponding changes to resistance and/or actions for the actuator system <NUM>), to determine the intent of the guest <NUM>. In an embodiment, the algorithms may apply different weights to the various factors. For example, the position and/or movement of the head of the guest <NUM> may be weighted most heavily. In an embodiment, machine learning may be utilized to associate the various factors with the intent. As used herein, machine learning may refer to mathematical models that may be used to perform a task (e.g., make predictions or decisions) without using explicit instructions, instead relying on patterns and inference. The mathematical models may be generated using training data (e.g., sample data, historical data).

In an embodiment, it may be desirable to control the actuator system <NUM> in a manner that is customized (e.g., personalized) for the guest <NUM>. As noted above, each guest <NUM> may have certain characteristics that affect their ability to shift their weight to move the ride vehicle <NUM>. For example, a first guest may have a low weight, a low activity level, and/or low mobility. However, a second guest may have a high weight, a high activity level, and/or high mobility. Without the disclosed embodiments (e.g., without dynamically adjusting the resistance to movement of the spring plate <NUM>), it may be difficult to provide an enjoyable experience to both the first guest and the second guest given their different characteristics. For example, the first guest may have difficulty moving the ride vehicle <NUM> by shifting their weight, while the second guest may be able to easily move the ride vehicle <NUM> by shifting their weight. Thus, in an embodiment, the vehicle controller <NUM> may access and/or identify characteristics of the guest <NUM> and may then control the actuator system <NUM> in a manner that is appropriate for the characteristics of the guest <NUM>. The vehicle controller <NUM> may set the resistance to be appropriate for the characteristics of the guest <NUM>, set limit positions (e.g., maximum roll, pitch, and/or yaw) of the spring plate <NUM> that are appropriate for the characteristics of the guest <NUM>, a rate of change in position of the spring plate <NUM> when actively driving the spring plate <NUM>, or the like. The vehicle controller <NUM> may also access and/or identify a skill level of the guest <NUM>, which may be based on a number of times that the guest <NUM> has previously completed the ride cycle. In this way, the vehicle controller <NUM> may accommodate guests with less skill or experience by adjusting for extremes of motion that suggest a different intent than for guests with more skill or experience. Generally, the algorithms (e.g., look up tables) may account for the variation in motion by different guests (e.g., by considering characteristics, including skill level), since one motion by one guest may suggest a different intent than the same motion by another guest.

In an embodiment, the vehicle controller <NUM> may determine characteristics of the guest <NUM> during an initial portion of the ride cycle (e.g., during boarding and/or during a first time period after boarding; during a calibration portion of the ride cycle). For example, during the initial portion of the ride cycle, the array of weight sensors <NUM> may obtain a weight of the guest <NUM> and the skeletal sensor <NUM> may determine a size (e.g., height) of the guest <NUM>. Furthermore, during the initial portion of the ride cycle, the guest <NUM> may move in various ways (e.g., in response to instructions, which may be presented via the VR device <NUM>; as encouraged by the actuator system <NUM> and/or the VR device <NUM>). Then, the one or more sensors (e.g., the head position sensor <NUM>, the eye position sensor <NUM>, the array of weight sensors <NUM>, the grip sensors <NUM>, and/or the skeletal sensor <NUM>) may monitor the position(s) and/or the movement(s) of the guest <NUM>. This may be indicative of the activity level and/or mobility of the guest <NUM> (e.g., strength of inputs that the guest <NUM> is able to and/or is likely to provide while in the ride vehicle <NUM>). Finally, the vehicle controller <NUM> may determine the activity level and/or the mobility of the guest <NUM> based on the signals received from the one or more sensors.

The weight, the size, the activity level, and/or mobility of the guest <NUM> may influence or affect how the guest <NUM> moves while positioned on the ride vehicle <NUM>. In an embodiment, the vehicle controller <NUM> may classify the guest <NUM> (e.g., based on the characteristics), and/or the vehicle controller <NUM> may control the actuator system <NUM> throughout at least some or all of the remainder of the ride cycle (e.g., after the initial portion of the ride cycle) based on the characteristics of the guest <NUM>. For example, the actuator system <NUM> may be controlled to provide varying resistance across a lower range of resistance values for the first guest, and the actuator system <NUM> may be controlled to provide varying resistance across a higher range of resistance values for the second guest.

In an embodiment, during the initial portion of the ride cycle, the vehicle controller <NUM> may also determine which input(s) the guest <NUM> utilizes or favors to attempt to control the ride vehicle <NUM>. For example, the vehicle controller <NUM> may determine that the first guest primarily uses one type of input (e.g., changing their grip) and/or minimally uses or does not use another type of input (e.g., shifting weight). In such cases, the actuator system <NUM> may be controlled to actively drive the spring plate <NUM> in response to changes in the grip of the first guest, instead of relying on the first guest to shift their body weight. Or, the actuator system <NUM> may be controlled to reduce the resistance in response to determining the intent of the user based on changes in the grip of the first guest, to thereby make it easier for the first guest <NUM> to subsequently move the spring plate <NUM> with their body weight. Thus, each guest may be provided with a motion experience in which they feel like they are in control of the ride vehicle <NUM> (e.g., the ride vehicle <NUM> is responsive to their movements) by shifting their weight and/or by moving in other ways (e.g., changing their grip). Importantly, each guest may be provided with the motion experience even if they have certain limits to their physical abilities and/or without overexerting themselves, thereby providing for a more enjoyable experience for all guests.

Additionally, the vehicle controller <NUM> may operate the ride vehicle <NUM> in an active mode for certain guests, but not for other guests. Or the vehicle controller <NUM> may operate the ride vehicle <NUM> in the active mode more frequently for certain guests, and less frequently for other guests. For example, the active mode may be used more frequently to provide motion for the first guest, and the active mode may be used less frequently to provide motion for the second guest (since the second guest has a greater ability to shift their weight to move the ride vehicle <NUM>). In an embodiment, the vehicle controller <NUM> may switch from operating the ride vehicle <NUM> in the semi-passive mode to operating the ride vehicle <NUM> in the active mode in response to failing to detect shifting weight of the guest <NUM> and/or in response to failing to detect movement of the ride vehicle <NUM> (e.g., expected movement; in a direction) after determining the intent of the guest <NUM> is to move the ride vehicle <NUM> (e.g., in the direction). For example, after determining the intent based on signals indicative of one or more of movement of the head of the guest <NUM>, movement of the eyes of the guest <NUM>, a change in grip of the guest <NUM>, and/or a change in limb positioning of the guest <NUM>, the vehicle controller <NUM> may reduce the resistance to movement of the ride vehicle <NUM>. However, if the ride vehicle <NUM> does not move within a time period after the reduction in the resistance, the vehicle controller <NUM> may switch to operating in the active mode and may drive movement of the ride vehicle <NUM> (e.g., in the direction).

In some embodiments, the characteristics of the guest <NUM> may be stored in a database (e.g., as a stored profile for the guest <NUM>). An identifier of the guest <NUM> may be stored with the characteristics of the guest <NUM>. Then, during subsequent rides by the guest <NUM>, the vehicle controller <NUM> may access the characteristics from the database and may control the actuator system <NUM> in an appropriate manner for the guest <NUM> (e.g., without monitoring during the initial portion of the ride cycle and/or in addition to such monitoring). For example, the guest <NUM> may wear an identification device (e.g., a wearable device having a radiofrequency identification (RFID) tag that is unique to the guest <NUM>). In such cases, an RFID reader that is communicatively coupled to the vehicle controller <NUM> may read the identifier (e.g., code) from the RFID tag when the guest <NUM> is in the ride vehicle <NUM>, and the identifier may be associated and stored with the characteristics of the guest <NUM>. Then, during the subsequent rides by the guest <NUM>, the RFID reader may again read the identifier from the RFID tag, provide the identifier to the vehicle controller <NUM> so that the vehicle controller may access the characteristics for the guest <NUM> from the database. It should also be appreciated that the guest <NUM> may input the identifier and/or the characteristics via an input device (e.g., a touch screen on the ride vehicle <NUM> or in a queue for the attraction <NUM>; prior to entering the amusement park). In an embodiment, the guest <NUM> may input preferences related to the resistance (e.g., low or high levels of resistance) and/or movement (e.g., low or high levels of movement) that they would like to experience in the ride vehicle <NUM>. The preferences may be stored in the database and may be associated with the identifier.

It should be appreciated that the vehicle controller <NUM> may also receive signals from one or more ride vehicle sensors <NUM>, wherein the signals are indicative of a position (e.g., incline) and/or movement of the ride vehicle <NUM>. For example, the ride vehicle sensors <NUM> may include an inclinometer, an accelerometer, and/or a position sensor. The vehicle controller <NUM> may then control the actuator system <NUM> based on the signals from the one or more ride vehicle sensors <NUM> and the intent of the guest <NUM>. In this way, the vehicle controller <NUM> may account for a current position of the ride vehicle <NUM> when controlling the actuator system <NUM> to reduce the resistance to movement of the spring plate <NUM> and/or to actively drive the spring plate <NUM>. For example, if the ride vehicle <NUM> is already at a limit position in a direction (e.g., a maximum roll, pitch, and/or yaw), the vehicle controller <NUM> may not further reduce the resistance in the direction and/or may not actively drive the spring plate <NUM> to move in the direction. Similarly, if the ride vehicle <NUM> is already rotated to the left and the intent of the guest <NUM> (e.g., as determined by the vehicle controller <NUM>) is to move to the right, the vehicle controller <NUM> may adjust the resistance and/or drive the ride vehicle <NUM> to reach a centered or neutral position (e.g., rather than to rotate the ride vehicle <NUM> to the right). The signals from the one or more ride vehicle sensors <NUM> may also be utilized by the VR controller <NUM> to provide the virtual images to the guest <NUM> in a manner that corresponds to the movement of the ride vehicle <NUM>.

As noted above, the actuator system <NUM> may operate in a semi-passive mode to impart a resistance to movement of the spring plate <NUM> (e.g., via movement of the actuator plate <NUM> in <FIG>; via torque output of the motors <NUM> in <FIG> and <FIG>). In some such cases, the vehicle controller <NUM> may refer to a resistance setting database <NUM> to determine a particular target resistance (e.g., that is appropriate for the characteristics of the guest <NUM> and/or the ride cycle) and settings for the actuator system <NUM> (e.g., the position of the actuator plate <NUM> in <FIG>; the torque output of the motors <NUM> in <FIG> and <FIG>) to achieve the particular target resistance. Additionally or alternatively, the actuator system <NUM> may operate in an active mode in which the spring plate <NUM> is driven to move (e.g., in <FIG> and <FIG>, one or more motors <NUM> are instructed to output a torque that overcomes the force imparted by the guest <NUM> onto the spring plate <NUM>) to thereby position the spring plate <NUM>. Indeed, in the active mode, the vehicle controller <NUM> may operate the actuator system <NUM> to drive the spring plate <NUM> to move in a desirable manner (e.g., to a target position or orientation), instead of enabling the guest <NUM> to drive movement of the spring plate <NUM> (e.g., as in the semi-passive mode). For instance, the vehicle controller <NUM> may operate in the active mode to move the spring plate <NUM> and impart a certain sensation and ride experience to the guest <NUM>. The vehicle controller <NUM> may utilize the intent of the guest <NUM> and a current position of the spring plate <NUM> to determine the appropriate way to control the actuator system <NUM> to move the spring plate <NUM> (e.g., the appropriate torque to be output by the one or more motors <NUM> to cause the desirable movement of the spring plate <NUM>). It should be appreciated that the vehicle controller <NUM> may receive feedback or inputs that indicate a current resistance as well (e.g., the length of the actuators <NUM> in <FIG>; the torque output by the motors <NUM> in <FIG> and <FIG>) to enable the vehicle controller <NUM> to appropriately adjust the resistance for the guest <NUM>.

The vehicle controller <NUM> may be included in a housing or chassis of the ride vehicle <NUM>, or the vehicle controller <NUM> may be remote to the ride vehicle <NUM> and coordinate operation of multiple ride vehicles <NUM>. The vehicle controller <NUM> includes the processor <NUM> that provides instructions to the actuator system <NUM> and the memory <NUM> that stores the instructions for the processor <NUM>. The memory <NUM> may also store the resistance setting database <NUM>. However, it is to be understood that any components can be suitably stored in and updated from any suitable location, such as within a cloud database. The processor <NUM> may include one or more processors that can execute instructions for carrying out the presently disclosed techniques, such as a general-purpose processor, system-on-chip (SoC) device, an application-specific integrated circuit (ASIC), or some other similar processor configuration. In some embodiments, these instructions are encoded in programs or code stored in a tangible, non-transitory, computer-readable medium, such as the memory <NUM> and/or other storage circuitry or device. It should be appreciated that processing steps and techniques disclosed herein may be carried out by the vehicle controller <NUM> alone or in conjunction within another controller that is communicatively coupled to the vehicle controller <NUM> (e.g., in conjunction with the VR controller <NUM> and/or any other type of additional controller, such as a guest tracking controller that receives, transmits, and/or processes signals indicative of the position and/or movement of the guest <NUM>).

<FIG> is a flow diagram illustrating an embodiment of a method <NUM> for controlling the actuator system of the ride vehicle. The method <NUM> disclosed herein includes various steps represented by blocks. It should be noted that at least some steps of the method <NUM> may be performed as an automated procedure by a computing system, such as by the vehicle controller. Although the flow chart illustrates the steps in a certain sequence, it should be understood that the steps may be performed in any suitable order and certain steps may be carried out simultaneously, where appropriate. Additionally, steps may be added to or omitted from the method <NUM>.

As shown, in step <NUM>, the method <NUM> may begin by receiving signals indicative of a position and/or movement of a guest that is supported in the ride vehicle. The signals may include signals from a head position sensor, wherein the signals are indicative of a position and/or movement of a head of the guest. Additionally or alternatively, the signals may include signals from an eye position sensor, wherein the signals are indicative of a position and/or movement of one or both eyes of the guest. Additionally or alternatively, the signals may include signals from an array of weight sensors, wherein the signals are indicative of weight shifting of the guest. Additionally or alternatively, the signals may include signals from a grip sensor, wherein the signals are indicative of a grip strength, hand position, and/or hand movement of the guest. Additionally or alternatively, the signals may include signals from a skeletal sensor, wherein the signals are indicative of a skeletal position and/or movement (e.g. limb position and/or movement) of the guest. For example, one or more signals indicative of one or more positions and/or movements of the guest may be received at the vehicle controller.

As shown in step <NUM>, the method <NUM> may then proceed to determine an intent of the guest (e.g., how the guest wants or intends to move the ride vehicle; the intended movement for the ride vehicle) based on the signals. It is presently recognized that the position(s) and/or movement(s) may be indicative of the intent of the guest. For example, the guest may move their head to their left when the guest wants to rotate or move the ride vehicle to their left. The vehicle controller may use one or more algorithms to determine the intent of the guest based on the signals. As noted herein, the vehicle controller may also consider ride elements to determine the intent of the guest.

As shown in step <NUM>, the method <NUM> may also include receiving signals indicative of a position (e.g., incline) of the ride vehicle. The signals may include signals from a ride vehicle sensor that is coupled to the ride vehicle, and the signals may be received at the vehicle controller. In step <NUM>, the method <NUM> may include controlling an actuator system based on the intent of the guest and the position of the ride vehicle. For example, the vehicle controller may instruct the actuator system to adjust a resistance to movement of a spring plate of the ride vehicle to adjust the ride vehicle's response to weight shifting by the guest (e.g., to make it easier or to make it more difficult for the guest to rotate the spring plate). In an embodiment, the vehicle controller may instruct the actuator system to actively drive the spring plate of the ride vehicle. As noted herein, the vehicle controller may carry out other steps, such as determining characteristics of the guest, accessing a resistance setting database, determining appropriate resistance settings based on the characteristics of the guest and/or ride cycle, and the like to provide a motion experience to the guest. Furthermore, the vehicle controller may control the actuator system so that the motion experience is coordinated with a visual experience, which may be presented to the guest via a VR device. For example, the vehicle controller may adjust the resistance to movement of the spring plate based on the visual experience (e.g., to provide less control to the guest during some portions of the ride cycle and to provide more control to the guest during other portions of the ride cycle).

Technical effects of the disclosed ride vehicle control system include enabling dynamic adjustment of a resistance of a ride vehicle and/or actively controlling movement of the ride vehicle based on various inputs from a guest in the ride vehicle. The disclosed ride vehicle control system provides an improved experience for guests having a wide range of characteristics.

Claim 1:
A ride vehicle control system (<NUM>) for a ride vehicle (<NUM>) of an attraction (<NUM>), the ride vehicle control system (<NUM>) comprising:
a plurality of sensors configured to monitor a guest supported by the ride vehicle (<NUM>);
an actuator system (<NUM>) configured to couple to the ride vehicle (<NUM>); and
one or more processors (<NUM>) configured to:
receive signals from the plurality of sensors, wherein the signals are indicative of a position of the guest (<NUM>), a movement of the guest (<NUM>), or both;
determine an intended movement for the ride vehicle (<NUM>) based on the signals; and
control the actuator system (<NUM>) to adjust a resistance to movement of the ride vehicle (<NUM>), to adjust a force applied to the ride vehicle (<NUM>), or both to facilitate the intended movement.