Patent Description:
Amusement parks and/or theme parks are designed to provide entertainment to guests. Areas of the amusement park may have different themes that are specifically targeted to certain audiences. For example, some areas may include themes that are traditionally of interest to children, while other areas may include themes that are traditionally of interest to more mature audiences. Generally, such areas having themes may be referred to as an attraction or a themed attraction. It is recognized that it may be desirable to enhance the immersive experience for guests in such attractions, such as by augmenting the themes with virtual features.

<CIT> discloses amusement park attractions where the users can wear a head mounted display (HMD) in order to provide AR or VR experiences along with the ride. The HMD may include a number of orientation and position sensors (e.g., accelerometers, magnetometers, gyroscopes, Global Positioning System [GPS] receivers) that may be used to track position, orientation, and motion during the ride.

<CIT> discloses an HMD comprising inertial sensors, e.g. gyros, accelerometers.

<CIT> discloses a wearable device for elderly care patients where sensor readings can alert care personnel if the wearer falls.

An amusement park may include an augmented reality (AR), a virtual reality (VR), and/or a mixed reality (a combination of AR and VR) system (e.g., AR/VR system) that is configured to enhance a guest experience of an amusement park attraction by providing guests with AR/VR experiences (e.g., AR experiences, VR experiences, or both). Indeed, combinations of certain hardware configurations, software configurations (e.g., algorithmic structures and/or modeled responses), as well as certain attraction features may be utilized to provide guests with AR/VR experiences that may be customizable, personalized, and/or interactive. For example, the AR/VR system may include a wearable visualization device, such as a head mounted display (e.g., electronic goggles or displays, eyeglasses), which may be worn by a guest and may be configured to enable the guest to view virtual features. In particular, the wearable visualization device may be utilized to enhance a guest experience by overlaying virtual features onto a real-world environment of the amusement park, by providing adjustable virtual environments to provide different experiences in an attraction, and so forth.

Advantageously, the disclosed embodiments provide a detection system (e.g., drop detection system) that is configured to monitor whether the wearable visualization device has been improperly handled (e.g., experienced an adverse or potentially damaging event, such as a drop or a throw). In particular, the detection system may include a sensor (e.g., inertial measurement unit [IMU]) that is coupled to the wearable visualization device and that is configured to monitor one or more parameters (e.g., accelerations and/or decelerations) indicative of the wearable visualization device being improperly handled. The sensor may provide signals indicative of the parameters to a controller (e.g., electronic controller), which may process the signals to determine whether the wearable visualization device has been improperly handled and may cause one or more actions in response to the determination that the wearable visualization device has been improperly handled. For example, the controller may cause illumination of lights (e.g., light emitters; light emitting diodes [LEDs]) on the wearable visualization device, on a ride vehicle of the attraction, at an operator station of the attraction, or otherwise provide a notification that the wearable visualization device has been improperly handled. In some embodiments, the controller may count a number of times that the wearable visualization device has been improperly handled (e.g., a number of times that an acceleration of the wearable visualization device has exceeded an acceleration threshold, as indicated by the signals from the sensor) over time, and the controller may cause the one or more actions in response to the number of times that the wearable visualization device has been improperly handled exceeding a count threshold. Thus, the detection system may facilitate efficient removal of any wearable visualization device that may be damaged due to being improperly handled and may facilitate operation of the AR/VR system so that the guests are able to experience the attraction with functioning wearable visualization devices.

With the foregoing in mind, <FIG> is a perspective view an embodiment of an AR/VR system <NUM> (e.g., a wearable visualization system) configured to enable a user (e.g., a guest, an amusement park employee, an operator of an attraction, a passenger of a ride vehicle) to experience (e.g., view, interact with) AR/VR scenes. As shown, the AR/VR system <NUM> includes a wearable visualization device <NUM> (e.g., a head mounted display) and a guest interface device <NUM> that may be removably coupleable to one another to facilitate usage of the AR/VR system <NUM>.

In the illustrated embodiment, the wearable visualization device <NUM> includes a lens portion <NUM> that is coupled to a housing <NUM> of the wearable visualization device <NUM>. The lens portion <NUM> may include one or more lenses <NUM> (e.g., displays; transparent, semitransparent, or opaque). In some embodiments, the lenses <NUM> may enable the user to view a real-world environment <NUM> (e.g., physical structures in the attraction) through the lenses <NUM> with certain virtual features <NUM> (e.g., AR features) overlaid onto the lenses <NUM> so that the user perceives the virtual features <NUM> as being integrated into the real-world environment <NUM>. That is, the lens portion <NUM> may at least partially control a view of the user by overlaying the virtual features <NUM> onto a line of sight of the user. To this end, the wearable visualization device <NUM> may enable the user to visualize and perceive a surreal environment <NUM> (e.g., a game environment) having certain virtual features <NUM> overlaid onto the real-world environment <NUM> viewable by the user through the lenses <NUM>.

By way of non-limiting example, the lenses <NUM> may include transparent (e.g., see-through) light emitting diode (LED) displays or transparent (e.g., see-through) organic light emitting diode (OLED) displays. In some embodiments, the lens portion <NUM> may be formed from a single-piece construction that spans a certain distance so as to display images to both eyes of the user. That is, in such embodiments, the lenses <NUM> (e.g., a first lens <NUM>, a second lens <NUM>) may be formed from a single, continuous piece of material, where the first lens <NUM> may be aligned with a first eye of the user and the second lens <NUM> may be aligned with a second eye of the user. In other embodiments, the lens portion <NUM> may be a multi-piece construction that is formed from two or more separate lenses <NUM>.

In some embodiments, the wearable visualization device <NUM> may completely control the view of the user (e.g., using opaque viewing surfaces). That is, the lenses <NUM> may include opaque or non-transparent displays configured to display virtual features <NUM> (e.g., VR features) to the user. As such, the surreal environment <NUM> viewable by the user may be, for example, a real-time video that includes real-world images of the real-world environment <NUM> electronically merged with one or more virtual features <NUM>. Thus, in wearing the wearable visualization device <NUM>, the user may feel completely encompassed by the surreal environment <NUM> and may perceive the surreal environment <NUM> to be the real-world environment <NUM> that includes certain virtual features <NUM>. In some embodiments, the wearable visualization device <NUM> may include features, such as light projection features, configured to project light into one or both eyes of the user so that certain virtual features <NUM> are superimposed over real-world objects viewable by the user. Such a wearable visualization device <NUM> may be considered to include a retinal display.

As such, it should be appreciated that the surreal environment <NUM> may include an AR experience, a VR experience, a mixed reality experience, a computer-mediated reality experience, a combination thereof, or other similar surreal environment. Moreover, it should be understood that the wearable visualization device <NUM> may be used alone or in combination with other features to create the surreal environment <NUM>. Indeed, as discussed below, the user may wear the wearable visualization device <NUM> throughout a duration of a ride attraction in the amusement park or during another time, such as during a game, throughout a particular area or attraction of the amusement park, during a ride to a hotel associated with the amusement park, at the hotel, and so forth. In some embodiments, the wearable visualization device <NUM> may be physically coupled to (e.g., tethered via a cable <NUM>) to a structure (e.g., the ride vehicle) to block separation of the wearable visualization device <NUM> from the structure and/or may be electronically coupled to (e.g., via the cable <NUM>) to a computing system to facilitate operation of the wearable visualization device <NUM> (e.g., to display the virtual features <NUM>; to monitor whether the wearable visualization device <NUM> has been improperly handled and provide related notifications).

As shown, the wearable visualization device <NUM> is removably coupleable (e.g., toollessly coupleable; coupleable without tools; coupled without threaded fasteners, such as bolts; separable without tools and without breaking the components of the wearable visualization device <NUM> or the guest interface device <NUM>) to the guest interface device <NUM> to enable the wearable visualization device <NUM> to quickly transition between an engaged configuration <NUM>, in which the wearable visualization device <NUM> is coupled to the guest interface device <NUM>, and a disengaged configuration <NUM> (see, e.g., <FIG>), in which the wearable visualization device <NUM> is decoupled from the guest interface device <NUM>. In the illustrated embodiment, the guest interface device <NUM> is configured to be affixed to the user's head and, thus, enable the user to comfortably wear the wearable visualization device <NUM> throughout various attractions or while traversing certain amusement park environments. For example, the guest interface device <NUM> may include a head strap assembly <NUM> that is configured to span about a circumference of the user's head and configured to be tightened (e.g., constricted) on the user's head. In this manner, the head strap assembly <NUM> facilitates affixing the guest interface device <NUM> to the head of the user, such that the guest interface device <NUM> may be utilized to retain the wearable visualization device <NUM> on the user (e.g., when the wearable visualization device <NUM> is in the engaged configuration <NUM>).

Such a configuration may enable the user or another person (e.g., an operator, a maintenance technician) to efficiently couple and decouple the wearable visualization device <NUM> to the guest interface device <NUM> (e.g., upon a determination that the wearable visualization device <NUM> should be serviced, such as due to being improperly handled). However, it should be appreciated that the wearable visualization device <NUM> and/or the guest interface device <NUM> may have any of a variety of forms or structures that enable the wearable visualization device <NUM> to function in the manner described herein. For example, the wearable visualization device <NUM> may be used without the separate guest interface device <NUM> and/or the wearable visualization device <NUM> may be integrally formed with the guest interface device <NUM>. As shown, the wearable visualization device <NUM> may include a sensor <NUM> (e.g., IMU) and/or one or more lights <NUM> (e.g., LEDs). As discussed in more detail below, the sensor <NUM> may be configured to monitor one or more parameters (e.g., accelerations and/or decelerations) indicative of the wearable visualization device <NUM> being improperly handled and the lights <NUM> may be configured to illuminate, such as in response to a determination (e.g., by a controller) that the wearable visualization device <NUM> has been improperly handled. In this way, the wearable visualization device <NUM> may be identified as being potentially damaged and may be flagged for maintenance operations, even if the wearable visualization device <NUM> does not appear to be damaged (e.g., upon visual inspection).

<FIG> is a perspective view of an embodiment of the AR/VR system <NUM> illustrating the wearable visualization device <NUM> and the guest interface device <NUM> in the detached configuration <NUM>. In some embodiments, the housing <NUM> may be assembled from multiple panels (e.g., housing sections; molded and/or machined panels), such as a lid <NUM>, a chassis <NUM>, and a lens mount <NUM> (e.g., a panel configured to support the lens portion <NUM>), which may collectively form the housing <NUM>. As discussed below, some of or all of the panels may include component mating features (e.g., machined and/or molded features on surfaces of the panels) that are configured to receive and/or couple to various sub-components (e.g., the sensor <NUM>; the lights <NUM>; other electronic components, such as a controller) of the wearable visualization device <NUM>.

As discussed below, after installation of the sub-components on one or more of the panels, the panels may be assembled (e.g., coupled to one another via fasteners, adhesives, and/or other techniques) to form the housing <NUM>. The housing <NUM> may therefore support the sub-components and/or encapsulate the sub-components to substantially seal (e.g., hermetically seal) at least a portion of the sub-components within the housing <NUM> to shield these sub-components from direct exposure to ambient environmental elements (e.g., moisture) surrounding the wearable visualization device <NUM>. It be understood that, in other embodiments, the housing <NUM> may be assembled from additional or fewer panels than the lid <NUM>, the chassis <NUM>, and the lens mount <NUM>. Indeed, in certain embodiments, the housing <NUM> may include <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, or more than six individual panels that, in an assembled configuration, may collectively form the housing <NUM>.

It should also be understood that the sensor <NUM> may be positioned at any location of the wearable visualization device <NUM> and/or that any number (e.g., <NUM>, <NUM>, <NUM>, <NUM>, or more) of sensors <NUM> may be provided. As a non-limiting example, the sensor <NUM> may be a position and/or impact sensor, such as an accelerometer, magnetometer, gyroscope, global positioning system receiver, motion tracking sensor, electromagnetic and solid-state motion tracking sensor, and/or IMU. When the sensor <NUM> is an IMU, the IMU may include a nine degree of freedom system on a chip equipped with accelerometers, gyroscopes, a magnetometer, and a processor for executing sensor fusion algorithms. As such, the signals from the IMU may be used to determine an acceleration and/or an orientation of the wearable visualization device <NUM> (e.g., relative to a gravity vector). The wearable visualization device <NUM> may include different types of sensors <NUM>, such as different types of sensors <NUM> that detect different parameters (e.g., an IMU that detects acceleration of the wearable visualization device <NUM> and one or more impact sensors that detect a location of impact on the wearable visualization device <NUM>).

Similarly, the lights <NUM> may be positioned at any location of the wearable visualization device <NUM> and/or any number (e.g., <NUM>, <NUM>, <NUM>, <NUM>, or more) of lights <NUM> may be provided. The lights <NUM> may be positioned to be visible while the wearable visualization device <NUM> is coupled to the guest interface device <NUM>, visible while the wearable visualization device <NUM> is docked (e.g., coupled to or stored on a structure, such as a ride vehicle), visible to the user while the user is wearing the wearable visualization device <NUM>, and/or visible to an operator (e.g., a person other than the user) to facilitate visualization of the lights <NUM> while the lights <NUM> are illuminated.

<FIG> is a schematic diagram of components of a detection system <NUM> (e.g., drop detection system) for the wearable visualization device <NUM>. As shown, the detection system <NUM> may include the sensor <NUM> and the lights <NUM> of the wearable visualization device <NUM>. The detection system <NUM> may also include a controller <NUM> having a processor <NUM> and a memory device <NUM>. As shown, the controller <NUM> is located on the wearable visualization device <NUM>; however, it should be understood that the controller <NUM> may be located off of the wearable visualization device <NUM>, such as on a ride vehicle or on a system located remotely from the wearable visualization device <NUM>. Furthermore, the functions and processing steps described herein as being carried out by the controller <NUM> may be divided between the controller <NUM> and any other suitable controller or processing system (e.g., of the sensor <NUM>, a ride vehicle, a system located remotely from the wearable visualization device <NUM>; the controller <NUM> may be or may be part of a distributed control system having multiple processors). For example, the sensor <NUM> may be an IMU having a first processor that is configured to count a number of accelerations over an acceleration threshold, and the sensor <NUM> may provide the number to a second processor for further processing and/or to enable the second processor to carry out certain actions, such as illuminating the lights <NUM>. Thus, the processor <NUM> may include one or more processors located in any suitable location and the memory device <NUM> may include one or more memory devices located in any suitable location.

The memory device <NUM> may include one or more tangible, non-transitory, computer-readable media that store instructions executable by the processor <NUM> and/or data (e.g., parameters; a number of events) to be processed by the processor <NUM>. For example, the memory device <NUM> may include random access memory (RAM), read only memory (ROM), rewritable non-volatile memory such as flash memory, hard drives, optical discs, and/or the like. Additionally, the processor <NUM> may include one or more general purpose microprocessors, one or more application specific processors (ASICs), one or more field programmable gate arrays (FPGAs), or any combination thereof. Further, the memory device <NUM> may store instructions executable by the processor <NUM> to perform the methods and control actions described herein. The controller <NUM> may also include a communication device <NUM> that enables communication with other devices or systems, such as an operator system <NUM> (e.g., having a computing system with a processor and a memory device) and/or an attraction system <NUM> (e.g., having a computing system with a processor and a memory device), via a communication network.

The sensor <NUM> may be configured to detect the one or more parameters indicative of the wearable visualization device <NUM> being improperly handled. For example, if the user drops the wearable visualization device <NUM> (e.g., in free fall toward the ground/along a gravity vector), the sensor <NUM> may detect an acceleration (e.g., a sudden acceleration or deceleration). The sensor <NUM> may provide signals to the processor <NUM>, which may process the signals by comparing the acceleration (e.g., maximum acceleration value) to an acceleration threshold (e.g., acceleration threshold value). The processor <NUM> may be configured to determine that the wearable visualization device <NUM> has been dropped in response to determining that the acceleration exceeds the acceleration threshold. It should be appreciated that the acceleration are broad terms that encompass various ways of detecting dropping and/or throwing, and thus, the acceleration may be negative and the acceleration threshold may be a negative acceleration threshold (e.g., due to falling) or the acceleration threshold may be considered to be a deceleration threshold (e.g., due to a sudden stop due to an impact). The processor <NUM> may also be considered to determine and analyze the acceleration and/or other parameters over time (e.g., acceleration pattern or signature) to determine whether the wearable visualization device <NUM> has been improperly handled (e.g., and to characterize the event, as discussed below).

The acceleration being over the acceleration threshold may generally indicate that a severity (e.g., severity level) of the drop exceeds a severity threshold (e.g., the motion of the wearable visualization device <NUM> is enough to be considered a drop, which may be potentially damaging to the wearable visualization device <NUM>). Thus, the acceleration threshold may represent the severity threshold. In some embodiments, the processor <NUM> may compare the acceleration to multiple acceleration thresholds, which may each represent a different severity threshold and may enable the processor to more precisely determine the severity of the drop. For example, if the acceleration is above a first acceleration threshold and below a second acceleration threshold, the processor <NUM> may determine that the drop occurred and has a first, lower severity level. And if the acceleration is above both the first and the second acceleration thresholds, the processor <NUM> may determine that the drop occurred and has a second, higher severity level. The processor <NUM> may be configured to determine that the wearable visualization device <NUM> has been thrown and determine a severity of the throw in a similar manner (e.g., comparison to one or more acceleration thresholds). It should be appreciated that the sensor <NUM> may additionally or alternatively detect various other parameters, such as deceleration, an angular rate, and/or an orientation of the wearable visualization device <NUM> (e.g., relative to the gravity vector). The processor <NUM> may process signals from the sensor <NUM> in a similar manner (e.g., comparison to one or more thresholds) to determine whether the wearable visualization device <NUM> has been dropped or otherwise improperly handled, as well as the associated severity level.

In some embodiments, regardless of the parameters and regardless of the number of parameters, the processor <NUM> may process the signals from the sensor <NUM> to determine characteristics of the motion of the wearable visualization device <NUM> (e.g., to characterize the event and/or the improper handling, such as to characterize the event as a drop or a throw). For example, the processor <NUM> may determine that the signals indicate that the wearable visualization device <NUM> was dropped, a velocity of the wearable visualization device <NUM> during the drop, a time and/or a distance traveled during the drop, that the wearable visualization device <NUM> was thrown, a velocity at which the wearable visualization device <NUM> was thrown, a time and/or a distance of the throw, a location of impact, or the like. The drop may generally have a lower acceleration than the throw, as well as other parameters that are different than the throw. Thus, the processor <NUM> may characterize the event as a drop or a throw based on comparison of the parameter(s) to known parameters (e.g., stored in the memory device <NUM>) that correlate to a drop or a throw.

As noted above, in some embodiments, the processor <NUM> may be configured to compare the parameter(s) and/or the characteristic(s) to respective thresholds (e.g., one or more acceleration thresholds, one or more velocity thresholds, one or more time thresholds, one or more distance thresholds) to determine the severity of the event and/or the improper handling. For example, a short drop with a lower acceleration may be less severe than a high-speed throw with a higher acceleration. In some cases, the processor <NUM> may be configured to input the parameter(s) and/or the characteristic(s) into a model that is configured to output the severity or to otherwise classify (e.g., categorize) the event and/or the improper handling based on the parameter(s) and/or the characteristic(s). For example, the model may account for certain combinations of parameters that have historically resulted in damage or impaired the operation of similar wearable visualization devices <NUM>. In some embodiments, the processor <NUM> may account for the location of the impact (e.g., based on signals from impact sensors) to determine the severity, as an impact at the lenses <NUM> may be more severe and may be more likely to cause damage than an impact at the housing <NUM> (<FIG>). The processor <NUM> may also be configured to determine a motion of the wearable visualization device <NUM> relative to a ride vehicle (e.g., to isolate the motion of the wearable visualization device <NUM> from the motion of the ride vehicle, such as from expected or known motions or accelerations of the ride vehicle during a course of a ride and/or from motions or accelerations of the ride vehicle during a course of the ride as detected by a ride vehicle sensor configured to monitor the motions of the ride vehicle). In this way, a sudden motion or acceleration of the ride vehicle (e.g., at a portion of the ride that is designed to move the ride vehicle in this manner) may be ignored or not counted as improper handling by the processor <NUM>.

In response to determining that the wearable visualization device <NUM> been dropped or otherwise improperly handled (e.g., with a severity that exceeds the severity threshold), the processor <NUM> may then cause one or more actions, such as illumination of at least one of the lights <NUM>. The illumination of at least one of the lights <NUM> may prompt the user or the operator to carry out a maintenance operation, such as to inspect the wearable visualization device <NUM>, to carry out a test of the wearable visualization device <NUM>, to separate the wearable visualization device <NUM> from the guest interface device <NUM>, to separate the wearable visualization device <NUM> from any structure (e.g., the ride vehicle), to replace the wearable visualization device <NUM>, and/or to send the wearable visualization device <NUM> to a maintenance technician for repair. In some cases, the controller <NUM> may instruct the light <NUM> to illuminate with a particular color based on the parameters, the characteristics, and/or the severity of the event. For example, the short drop with the lower acceleration may result in the light <NUM> illuminating with a yellow color, while the high-speed throw with the higher acceleration may result in the light <NUM> illuminating with a red color. Any number of colors may be utilized to convey various types of events (e.g., yellow indicates a drop; red indicates a throw) and/or severity (e.g., yellow indicates an acceleration below a first acceleration threshold; red indicates an acceleration over the first acceleration threshold). In some embodiments, the light <NUM> may be capable of illuminating with different colors and/or multiple different lights may be provided.

In some embodiments, the processor <NUM> may be configured to count a number of events (e.g., a number of events in which the wearable visualization device <NUM> has been improperly handled) over time. For example, once a certain number of drops or throws (e.g., each with an acceleration over the acceleration threshold; each with a severity over the severity threshold) is reached, the processor <NUM> may instruct at least one of the lights <NUM> to illuminate. In some cases, the processor <NUM> may instruct one light <NUM> to illuminate for each event. For example, the wearable visualization device <NUM> may include five lights, a first light may illuminate upon a first drop of the wearable visualization device <NUM>, a second light may illuminate upon a second drop of the wearable visualization device <NUM>, a third light may illuminate upon a throw of the wearable visualization device <NUM>, and so forth. In some embodiments, the processor <NUM> may instruct one or more lights <NUM> to illuminate for each event, and the number of lights <NUM> may be based on the severity of each event. For example, the wearable visualization device <NUM> may include five lights, a first light may illuminate upon a first short drop of the wearable visualization device <NUM>, a second light and a third light may illuminate upon a high-speed throw of the wearable visualization device <NUM>, and so forth. Then, when a certain number (e.g., all) of the lights <NUM> of the wearable visualization device <NUM> are illuminated, the operator may be notified to taken the action (e.g., by viewing the lights <NUM>). In some embodiments, the wearable visualization device <NUM> may include a speaker, and the one or more actions may include providing an audible output via the speaker.

In addition to or as an alternative to the illumination of the at least one light <NUM>, the processor <NUM> may take one or more other actions, such as sending a notification to the operator system <NUM> and/or the attraction system <NUM>. Various actions (e.g., automated actions) are envisioned. For example, upon determination that an event has occurred (e.g., an event having a severity over a severity threshold; a certain number of such events has occurred), the processor <NUM> may turn off the wearable visualization device <NUM> or at least certain features of the wearable visualization device <NUM> (e.g., turn off the lenses <NUM>; block display of virtual features on the lenses <NUM>). In some embodiments, the processor <NUM> may block display of virtual features on the lenses <NUM> in response to determining that the event had a first, higher severity (e.g., a high-speed throw; a first, higher acceleration), but the processor <NUM> may continue to enable display of virtual features on the lenses <NUM> in response to determining that the event had a second, lower severity (e.g., a short drop; a second, lower acceleration).

In some embodiments, the wearable visualization device <NUM> may be coupled (e.g., removably coupled; temporarily locked) to the guest interface device <NUM> and/or to a structure, such as a ride vehicle. For example, the wearable visualization device <NUM> may be locked to the guest interface device <NUM> via an electromagnetic system. In such cases, in response to determining that the event has occurred, the power to the electromagnetic system may be blocked (e.g., the electromagnets may be deactivated), thereby enabling separation of the wearable visualization device <NUM> from the guest interface device <NUM>. In some such cases, the power to the electromagnetic system may be blocked only while the ride vehicle is in a loading/unloading zone and/or while the ride vehicle is stationary. Similarly, a locking device that couples the wearable visualization device <NUM> to the ride vehicle may be unlocked in response to determining that the event has occurred and/or while the ride vehicle is in the loading/unloading zone and/or while the ride vehicle is stationary. The wearable visualization device <NUM> may then be coupled to the guest interface device <NUM> and/or to the structure only via mechanical connections (e.g., hooks, key/slot interfaces) that can be quickly, manually disconnected. Such techniques may enable the wearable visualization device <NUM> that has experienced the event to be quickly removed for maintenance operations and replaced with another wearable visualization device <NUM> without slowing down the throughput (e.g., unloading and loading of the users) at the attraction, for example. As another example, the processor <NUM> may be configured to initiate (e.g., run) a test (e.g., health test) in response to determining that the event has occurred. The test may include displaying an image (e.g., pattern, line) on the lenses <NUM> of the wearable visualization device <NUM>, and using a camera <NUM> of the wearable visualization device <NUM> to determine that the image is displayed correctly on the lenses <NUM>. The processor <NUM> may receive an image from the camera <NUM> and may process the image (e.g., via template or pattern matching) to determine whether the wearable visualization device <NUM> is functioning properly after the event. The test may include providing information (e.g., a question and/or an image) on the lenses <NUM> for visualization by the user, and then receiving a gesture input from the user (e.g., a nod of the head of the user) that is detected by the sensor <NUM>, as discussed in more detail below with respect to <FIG>.

In some embodiments, the processor <NUM> may be configured to send (e.g., via the communication device <NUM>) an indication to the operator system <NUM>, which may be remotely located from the wearable visualization device <NUM> (e.g., a tablet held by an operator of the attraction, a computer accessed by an operator overseeing operations of the amusement park). The indication may include a text message or other notification (e.g., illumination of a light) that the wearable visualization device <NUM> has been improperly handled. The indication may further include data related to the parameters, characteristics, and/or the severity of the event.

It should be appreciated that data related to a number of events, as well as data related to the parameters, characteristics, and/or the severity of each event, may be used to generate an event report (e.g., table) for each wearable visualization device <NUM> and/or may enable an operator of the amusement park to keep track of a reliability and/or durability of the wearable visualization devices <NUM>. For example, if the wearable visualization devices <NUM> used in the attraction generally experience impaired functionality after only a few minor drops, the operator may be able to focus efforts on improving the reliability and/or durability even in the presence of drops and/or taking steps to reduce drops. If the wearable visualization devices <NUM> experience multiple severe drops and/or throws, the operator may be able to focus efforts on taking steps to reduce drops and/or throws. Furthermore, if the wearable visualization devices <NUM> experience impaired functionality without any drops, the operator may be able to focus efforts on improving other features of the wearable visualization devices <NUM> and/or seek replacement under a warranty.

In some embodiments, the processor <NUM> may be configured to send (e.g., via the communication device <NUM>) an indication to the attraction system <NUM> to cause the attraction system <NUM> to illuminate lights (e.g., on a ride vehicle) and/or to adjust operation of features of the attraction, such as to adjust a path or a movement of a ride vehicle. For example, in response to a determination that the event has occurred, the attraction system <NUM> may divert the ride vehicle (e.g., to a maintenance bay and/or loading/unloading zone) to facilitate maintenance operations. The diversion may occur during the ride, so as to avoid the user experiencing the ride with a potentially malfunctioning wearable visualization device <NUM>. Thus, the user or an operator may inspect, repair, and/or replace the wearable visualization device <NUM> and/or the user may unload from the ride vehicle and reload into another ride vehicle with a properly functioning wearable visualization device <NUM> so that the user can enjoy the AR/VR experience throughout the remainder of the ride. The diversion may occur after the ride to enable the wearable visualization device <NUM> to be inspected, repaired, and/or replaced between ride cycles and/or between users to avoid the users experiencing the ride with a potentially malfunctioning wearable visualization device <NUM>. The diversion may include blocking forward movement of the ride vehicle out of the loading/unloading zone until the wearable visualization device <NUM> is inspected or otherwise addressed. In some embodiments, in response to a determination that the event has occurred, the attraction system <NUM> may be configured to enhance physical features, such as displays, animatronics, light shows, or the like, on the ride vehicle and/or within the attraction (e.g., so that the user is able to view text or images, such as on the displays, and to generally enjoy the attraction even without a properly functioning wearable visualization device <NUM>).

<FIG> is a perspective view of an attraction <NUM> in which the AR/VR system <NUM> may be employed. As shown, users <NUM> are positioned within a ride vehicle <NUM> that travels along a path <NUM>. At least at certain times of the ride, the users <NUM> may be able to view physical structures <NUM> in the real-world environment <NUM> through the lenses of the wearable visualization device <NUM>. At least at certain times of the ride, the users <NUM> may be able to view virtual features <NUM> on the lenses of the wearable visualization device <NUM>. As represented in <FIG>, the virtual features <NUM> may be overlaid onto the real-world environment <NUM> so that the users are able to view both the physical structures <NUM> in the real-world environment <NUM> and the virtual features <NUM> simultaneously. Each user <NUM> may be presented with different virtual features <NUM> so that each user <NUM> has a different experience on the ride. The users <NUM> may board the ride vehicle <NUM> in a loading zone and exit from the ride vehicle <NUM> in an unloading zone (e.g., a loading/unloading zone <NUM>). However, in the excitement of the ride, it is possible that the user <NUM> may drop the wearable visualization device <NUM> or that the wearable visualization device <NUM> may otherwise fall off of the user <NUM>. It is also possible that the user <NUM> may throw the wearable visualization device <NUM> and/or that the wearable visualization device <NUM> may otherwise be improperly handled.

With reference to <FIG> and <FIG>, each wearable visualization device <NUM> may include components that are part of the detection system <NUM>, which may monitor whether the wearable visualization device <NUM> is improperly handled during the ride. In some embodiments, during the ride, the detection system <NUM> may illuminate at least one light <NUM>, provide a notification to the operator system <NUM>, and/or cause an action to be taken by the attraction system <NUM>. Additionally or alternatively, the detection system <NUM> may count or log the event within the memory device <NUM>. Additionally or alternatively, the detection system <NUM> may illuminate at least one light <NUM>, provide a notification to the operator system <NUM>, and/or cause an action to be taken by the attraction system <NUM> only after the conclusion of the ride (e.g., in the loading/unloading zone <NUM>) so as to not interrupt the ride.

In some embodiments, the processor <NUM> may count a total number of events and/or may periodically cause one or more actions based on the event(s), such as after a time period (e.g., hourly, daily, weekly), each time the wearable visualization device <NUM> is coupled to or uncoupled from the guest interface device <NUM>, each time the wearable visualization device <NUM> is docked to the structure (e.g., to the ride vehicle <NUM>, which may be detected via a position sensor), each time the ride vehicle <NUM> is in the loading/unloading zone <NUM> (e.g., after each ride cycle), and/or in response to a request by the user or other person (e.g., operator, maintenance technician). While <FIG> illustrates the attraction <NUM> with the ride vehicle <NUM>, it should be appreciated that the attraction <NUM> may not include the ride vehicle <NUM>. Instead, the attraction <NUM> may include a path over which the user <NUM> walks while wearing the wearable visualization device <NUM>, a theatre in which the user <NUM> sits or stands while wearing the wearable visualization device <NUM>, or any other suitable type of attraction. Furthermore, the attraction <NUM> may be configured such that the user <NUM> wears and/or carries the wearable visualization device <NUM> outside of the ride vehicle <NUM>, such as while in line to board the ride vehicle <NUM>, after unloading from the ride vehicle <NUM>, or the like. Thus, it may be possible for the user <NUM> or another person (e.g., an operator, a maintenance technician) to drop the wearable visualization device <NUM> at other locations relative to the ride vehicle <NUM> and/or at other times outside of the ride. The detection system <NUM> may be configured to detect the events, to count the events, and/or to cause the one or more actions disclosed herein while the wearable visualization device <NUM> is at the other locations relative to the ride vehicle <NUM> and/or at the other times outside of the ride.

<FIG> is a method <NUM> of using the detection system <NUM> to monitor an event (e.g., improper handling) of the wearable visualization device <NUM>. 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 system, such as any of the detection system <NUM> disclosed herein. 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 (e.g., from the sensor <NUM>, at the processor <NUM>) a signal indicative of an event for the wearable visualization device <NUM>. As discussed above, the processor <NUM> may be configured to receive and to process the signal to determine that the event has occurred and/or to characterize the event (e.g., a type, a time, a distance, a velocity, a severity, a location of impact). In step <NUM>, the processor <NUM> may count a number of events over time. The data related to the parameters, characteristics, severity, and/or the number of events may be stored in the memory device <NUM>, for example.

In step <NUM>, the processor <NUM> may instruct at least one light <NUM> on the wearable visualization device <NUM> to illuminate. For example, the processor <NUM> may instruct the at least one light <NUM> to illuminate in response to detection of a drop with a severity over a severity threshold and/or in response to detection of a number of drops over a count threshold. In step <NUM>, the processor <NUM> may provide a notification to the operator system <NUM>, which may be remotely located from the wearable visualization device <NUM>. In step <NUM>, the processor <NUM> may communicate with the attraction system <NUM>, which may cause the attraction system <NUM> to adjust a feature of an attraction, such as to illuminate a light on a ride vehicle, to adjust a path of the ride vehicle, or the like.

The sensor <NUM> of the wearable visualization device <NUM> may enable the user to provide gesture inputs. With this in mind, <FIG> is a schematic diagram of a question that may be presented on the lenses <NUM> of the wearable visualization device <NUM>. For example, the question may be "Can you see the image below?" and the image may be a geometric shape or other image. The user may shake their head up and down to answer "yes," and the user may shake their head side to side to answer "no.

With reference to both <FIG> and <FIG>, while the wearable visualization device <NUM> is worn by the user, the sensor <NUM> may be able to detect the motion of the head of the user. The sensor <NUM> may provide signals indicative of the motion to the processor <NUM>, which may determine the response or the answer from the user based on the signal. In this case, the processor <NUM> may characterize the response based on comparison of the parameter(s) to known parameters (e.g., stored in the memory device <NUM>) that correlate to a "yes" or a "no" motion. The illustrated example may be used as part of a test to test whether the wearable visualization device <NUM> is functioning, such as after being improperly handled. The test may be initiated automatically by the processor <NUM> in response to the determination that the wearable visualization device has been improperly handled. For example, if the user responds "yes," then the processor <NUM> may determine that the wearable visualization device <NUM> is functioning after being improperly handled. However, if the user responds "no," then the processor <NUM> may determine that the wearable visualization device <NUM> is not functioning properly after being improperly handled. In such cases, the processor <NUM> may take one or more actions, including the one or more actions disclosed herein (e.g., illuminating the lights <NUM>; notifying the operator system <NUM> and/or the attraction system <NUM>). It should be appreciated that the test may be initiated in response to an input (e.g., by the user or operator), or that the test may be initiated at any other time (e.g., in response to coupling the wearable visualization device <NUM> to the guest interface device <NUM>), prior to leaving the loading zone of the ride, or the like.

The gesture inputs may be used to provide various responses to various questions or other prompts, the gesture inputs may be used as part of a game, and/or the gesture inputs may be used to control other aspects of the wearable visualization device <NUM> and/or the attraction. Indeed, different motions of the head of the user may correspond to different responses or inputs. For example, moving the head of the user one way may be one input (e.g., to brighten the images on the lenses <NUM>, to cause display of one image as part of a game, to adjust motion of a ride vehicle in one way), and moving the head of the user another way may be another input (e.g., to dim images on the lenses <NUM>, to cause display of another image as part of a game, to adjust motion of the ride vehicle in another way).

The gesture inputs may also be used to enable the operator and/or the maintenance technician to unlock certain features of the wearable visualization device <NUM> (e.g., by moving the wearable visualization device <NUM> in a certain way and/or in certain patterns of movements). The gesture inputs may enable the operator and/or the maintenance technician to interact with the wearable visualization device <NUM> and/or the attraction (e.g., game) in order to diagnose problems and/or to see information that is not available to guests. The gesture inputs may enable the operator and/or the maintenance technician to access a menu (e.g., visible on the lenses <NUM> of the wearable visualization device <NUM>; visible on a display connected to the wearable visualization device <NUM>, such as a display on the ride vehicle), move through the menu, make selections on the menu, and/or carry out maintenance tests and/or steps using gesture inputs (e.g., only gesture inputs and motion of the wearable visualization device <NUM>; without an auxiliary device, such as a mouse or a keyboard). In some cases, the gesture inputs may enable the operator and/or the maintenance technician to carry out maintenance and/or provide inputs to a computing system coupled to the wearable visualization device <NUM>, such as a computing system of the ride vehicle (e.g., the attraction system <NUM> of <FIG>), to thereby adjust operation of the computing system.

The sensor <NUM> of the wearable visualization device <NUM> may also enable other operations, such as head tracking of the head of the user. The sensor <NUM> (e.g., IMU) may be used to obtain data indicative of the way in which the head of the user is traveling through space. However, in certain settings the user may be positioned on a moving ride vehicle (e.g., translating and/or rotating relative to the ground). Accordingly, the AR/VR system <NUM> may include additional features and/or be configured to carry out processing steps to isolate the movement of the head of the user from the movement of the ride vehicle. For example, the AR/VR system <NUM> may use a solid state cabin tracking system and may secondarily use the sensor <NUM> (e.g., if needed) for additional input to a prediction algorithm (e.g., a Kalman filter).

The sensor <NUM> may also be utilized for off-board development (e.g., desktop development) because it provides a low-cost way of having head tracking in the wearable visualization device <NUM>. Developers may utilize the basic tracking provided by the sensor <NUM> to look around a virtual scene; however, developers may not align the virtual scene to the real world in order to create the virtual scene. Thus, the developers may not utilize ride vehicle/cabin tracking systems, which may be more expensive, use a lot of equipment, and be time-consuming to set up as compared to the sensor <NUM>, which may operate to obtain data indicative of the movement of the head of the user upon being plugged into a cable (e.g., USB cable; cable <NUM>).

Claim 1:
A detection system (<NUM>) configured to detect improper handling of a wearable visualization device (<NUM>), wherein improper handling is an indication that the wearable visualization device (<NUM>) has been dropped or thrown, the detection system (<NUM>) comprising:
a sensor (<NUM>) coupled to the wearable visualization device (<NUM>);
a light emitter (<NUM>) coupled to the wearable visualization device (<NUM>); and
a processor (<NUM>) configured to:
receive a signal from the sensor (<NUM>), wherein the signal indicates an acceleration of the wearable visualization device (<NUM>);
receive data from a ride vehicle sensor indicative of acceleration of a ride vehicle (<NUM>) of an amusement park attraction (<NUM>) during the course of a ride;
determine whether the signal indicates improper handling of the wearable visualization device (<NUM>), wherein the determination comprises:
determining acceleration of the wearable visualization device (<NUM>) relative to the ride vehicle (<NUM>) based on the received signal from the sensor (<NUM>) and received data from the ride vehicle sensor; and,
determining that the signal indicates improper handling of the wearable visualization device (<NUM>) in response to the acceleration of the wearable visualization device (<NUM>) relative to the ride vehicle (<NUM>) exceeding an acceleration threshold; and,
in response to determining that the signal indicates improper handling of the wearable visualization device (<NUM>):
instruct illumination of the light emitter (<NUM>); and,
instruct an attraction system (<NUM>) to adjust a path or a movement of the ride vehicle (<NUM>) during the course of the ride.