Patent Grant
11200656
This section is intended to introduce the reader to various aspects of art that may be related to various aspects of the present techniques, which are described and/or claimed below. This discussion is believed to be helpful in providing the reader with background information to facilitate a better understanding of the various aspects of the present disclosure. Accordingly, it should be understood that these statements are to be read in this light, and not as admissions of prior art.
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.
A summary of certain embodiments disclosed herein is set forth below. It should be understood that these aspects are presented merely to provide the reader with a brief summary of these certain embodiments and that these aspects are not intended to limit the scope of this disclosure. Indeed, this disclosure may encompass a variety of aspects that may not be set forth below.
In one embodiment, a detection system is configured to detect improper handling of a wearable visualization device. The detection system includes a sensor coupled to the wearable visualization device, a light emitter coupled to the wearable visualization device, and a processor configured to receive a signal from the sensor. The processor is also configured to determine whether the signal indicates improper handling of the wearable visualization device, and to instruct illumination of the light emitter in response to determining that the signal indicates improper handling of the wearable visualization device.
In one embodiment, a wearable visualization device includes a housing, a sensor supported by the housing and configured to detect a motion of the wearable visualization device, a light emitter supported by the housing, and a processor configured to receive a signal from the sensor, determine whether the signal indicates that the wearable visualization device has been dropped or thrown based on a detected motion of the wearable visualization device, and instruct illumination of the light emitter in response to determining that the signal indicates that the wearable visualization device has been dropped.
In one embodiment, a method of using a detection system to detect improper handling of a wearable visualization device includes receiving, at a processor, a signal from a sensor coupled to the wearable visualization device. The method also includes determining, using the processor, that the signal indicates improper handling of the wearable visualization device. The method further includes counting, using the processor, a number of events of improper handling of the wearable visualization device over time. The method further includes instructing, using the processor, illumination of a light emitter in response to determining that the number of events exceeds a count threshold.
Various refinements of the features noted above may be undertaken in relation to various aspects of the present disclosure. Further features may also be incorporated in these various aspects as well. These refinements and additional features may exist individually or in any combination.
These and other features, aspects, and advantages of the present disclosure will become better understood when the following detailed description is read with reference to the accompanying drawings in which like characters represent like parts throughout the drawings, wherein:
One or more specific embodiments will be described below. In an effort to provide a concise description of these embodiments, not all features of an actual implementation are described in the specification. It should be appreciated that in the development of any such actual implementation, as in any engineering or design project, numerous implementation-specific decisions must be made to achieve the developers' specific goals, such as compliance with system-related and business-related constraints, which may vary from one implementation to another. Moreover, it should be appreciated that such a development effort might be complex and time consuming, but would nevertheless be a routine undertaking of design, fabrication, and manufacture for those of ordinary skill having the benefit of this disclosure.
When introducing elements of various embodiments of the present disclosure, the articles “a,” “an,” and “the” are intended to mean that there are one or more of the elements. The terms “comprising,” “including,” and “having” are intended to be inclusive and mean that there may be additional elements other than the listed elements. Additionally, it should be understood that references to “one embodiment” or “an embodiment” of the present disclosure are not intended to be interpreted as excluding the existence of additional embodiments that also incorporate the recited features.
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,
In the illustrated embodiment, the wearable visualization device 12 includes a lens portion 16 that is coupled to a housing 18 of the wearable visualization device 12. The lens portion 16 may include one or more lenses 20 (e.g., displays; transparent, semi-transparent, or opaque). In some embodiments, the lenses 20 may enable the user to view a real-world environment 22 (e.g., physical structures in the attraction) through the lenses 20 with certain virtual features 24 (e.g., AR features) overlaid onto the lenses 20 so that the user perceives the virtual features 24 as being integrated into the real-world environment 22. That is, the lens portion 16 may at least partially control a view of the user by overlaying the virtual features 24 onto a line of sight of the user. To this end, the wearable visualization device 12 may enable the user to visualize and perceive a surreal environment 26 (e.g., a game environment) having certain virtual features 24 overlaid onto the real-world environment 22 viewable by the user through the lenses 20.
By way of non-limiting example, the lenses 20 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 16 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 20 (e.g., a first lens 28, a second lens 30) may be formed from a single, continuous piece of material, where the first lens 28 may be aligned with a first eye of the user and the second lens 30 may be aligned with a second eye of the user. In other embodiments, the lens portion 16 may be a multi-piece construction that is formed from two or more separate lenses 20.
In some embodiments, the wearable visualization device 12 may completely control the view of the user (e.g., using opaque viewing surfaces). That is, the lenses 20 may include opaque or non-transparent displays configured to display virtual features 24 (e.g., VR features) to the user. As such, the surreal environment 26 viewable by the user may be, for example, a real-time video that includes real-world images of the real-world environment 22 electronically merged with one or more virtual features 24. Thus, in wearing the wearable visualization device 12, the user may feel completely encompassed by the surreal environment 26 and may perceive the surreal environment 26 to be the real-world environment 22 that includes certain virtual features 24. In some embodiments, the wearable visualization device 12 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 24 are superimposed over real-world objects viewable by the user. Such a wearable visualization device 12 may be considered to include a retinal display.
As such, it should be appreciated that the surreal environment 26 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 12 may be used alone or in combination with other features to create the surreal environment 26. Indeed, as discussed below, the user may wear the wearable visualization device 12 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 12 may be physically coupled to (e.g., tethered via a cable 32) to a structure (e.g., the ride vehicle) to block separation of the wearable visualization device 12 from the structure and/or may be electronically coupled to (e.g., via the cable 32) to a computing system to facilitate operation of the wearable visualization device 12 (e.g., to display the virtual features 24; to monitor whether the wearable visualization device 12 has been improperly handled and provide related notifications).
As shown, the wearable visualization device 12 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 12 or the guest interface device 14) to the guest interface device 14 to enable the wearable visualization device 12 to quickly transition between an engaged configuration 34, in which the wearable visualization device 12 is coupled to the guest interface device 14, and a disengaged configuration 36 (see, e.g.,
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 12 to the guest interface device 14 (e.g., upon a determination that the wearable visualization device 12 should be serviced, such as due to being improperly handled). However, it should be appreciated that the wearable visualization device 12 and/or the guest interface device 14 may have any of a variety of forms or structures that enable the wearable visualization device 12 to function in the manner described herein. For example, the wearable visualization device 12 may be used without the separate guest interface device 14 and/or the wearable visualization device 12 may be integrally formed with the guest interface device 14. As shown, the wearable visualization device 12 may include a sensor 40 (e.g., IMU) and/or one or more lights 42 (e.g., LEDs). As discussed in more detail below, the sensor 40 may be configured to monitor one or more parameters (e.g., accelerations and/or decelerations) indicative of the wearable visualization device 12 being improperly handled and the lights 42 may be configured to illuminate, such as in response to a determination (e.g., by a controller) that the wearable visualization device 12 has been improperly handled. In this way, the wearable visualization device 12 may be identified as being potentially damaged and may be flagged for maintenance operations, even if the wearable visualization device 12 does not appear to be damaged (e.g., upon visual inspection).
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 18. The housing 18 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 18 to shield these sub-components from direct exposure to ambient environmental elements (e.g., moisture) surrounding the wearable visualization device 12. It be understood that, in other embodiments, the housing 18 may be assembled from additional or fewer panels than the lid 44, the chassis 46, and the lens mount 48. Indeed, in certain embodiments, the housing 18 may include 1, 2, 3, 4, 5, 6, or more than six individual panels that, in an assembled configuration, may collectively form the housing 18.
It should also be understood that the sensor 40 may be positioned at any location of the wearable visualization device 12 and/or that any number (e.g., 1, 2, 3, 4, or more) of sensors 40 may be provided. As a non-limiting example, the sensor 40 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 40 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 12 (e.g., relative to a gravity vector). The wearable visualization device 12 may include different types of sensors 40, such as different types of sensors 40 that detect different parameters (e.g., an IMU that detects acceleration of the wearable visualization device 12 and one or more impact sensors that detect a location of impact on the wearable visualization device 12).
Similarly, the lights 42 may be positioned at any location of the wearable visualization device 12 and/or any number (e.g., 1, 2, 3, 4, or more) of lights 42 may be provided. The lights 42 may be positioned to be visible while the wearable visualization device 12 is coupled to the guest interface device 14, visible while the wearable visualization device 12 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 12, and/or visible to an operator (e.g., a person other than the user) to facilitate visualization of the lights 42 while the lights 42 are illuminated.
The memory device 56 may include one or more tangible, non-transitory, computer-readable media that store instructions executable by the processor 54 and/or data (e.g., parameters; a number of events) to be processed by the processor 54. For example, the memory device 56 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 54 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 56 may store instructions executable by the processor 54 to perform the methods and control actions described herein. The controller 52 may also include a communication device 58 that enables communication with other devices or systems, such as an operator system 60 (e.g., having a computing system with a processor and a memory device) and/or an attraction system 62 (e.g., having a computing system with a processor and a memory device), via a communication network.
The sensor 40 may be configured to detect the one or more parameters indicative of the wearable visualization device 12 being improperly handled. For example, if the user drops the wearable visualization device 12 (e.g., in free fall toward the ground/along a gravity vector), the sensor 40 may detect an acceleration (e.g., a sudden acceleration or deceleration). The sensor 40 may provide signals to the processor 54, 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 54 may be configured to determine that the wearable visualization device 12 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 54 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 12 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 12 is enough to be considered a drop, which may be potentially damaging to the wearable visualization device 12). Thus, the acceleration threshold may represent the severity threshold. In some embodiments, the processor 54 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 54 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 54 may determine that the drop occurred and has a second, higher severity level. The processor 54 may be configured to determine that the wearable visualization device 12 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 40 may additionally or alternatively detect various other parameters, such as deceleration, an angular rate, and/or an orientation of the wearable visualization device 12 (e.g., relative to the gravity vector). The processor 54 may process signals from the sensor 40 in a similar manner (e.g., comparison to one or more thresholds) to determine whether the wearable visualization device 12 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 54 may process the signals from the sensor 40 to determine characteristics of the motion of the wearable visualization device 12 (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 54 may determine that the signals indicate that the wearable visualization device 12 was dropped, a velocity of the wearable visualization device 12 during the drop, a time and/or a distance traveled during the drop, that the wearable visualization device 12 was thrown, a velocity at which the wearable visualization device 12 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 54 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 56) that correlate to a drop or a throw.
As noted above, in some embodiments, the processor 54 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 54 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 12. In some embodiments, the processor 54 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 20 may be more severe and may be more likely to cause damage than an impact at the housing 18 (
In response to determining that the wearable visualization device 12 been dropped or otherwise improperly handled (e.g., with a severity that exceeds the severity threshold), the processor 54 may then cause one or more actions, such as illumination of at least one of the lights 42. The illumination of at least one of the lights 42 may prompt the user or the operator to carry out a maintenance operation, such as to inspect the wearable visualization device 12, to carry out a test of the wearable visualization device 12, to separate the wearable visualization device 12 from the guest interface device 14, to separate the wearable visualization device 12 from any structure (e.g., the ride vehicle), to replace the wearable visualization device 12, and/or to send the wearable visualization device 12 to a maintenance technician for repair. In some cases, the controller 52 may instruct the light 42 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 42 illuminating with a yellow color, while the high-speed throw with the higher acceleration may result in the light 42 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 42 may be capable of illuminating with different colors and/or multiple different lights may be provided.
In some embodiments, the processor 54 may be configured to count a number of events (e.g., a number of events in which the wearable visualization device 12 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 54 may instruct at least one of the lights 42 to illuminate. In some cases, the processor 54 may instruct one light 42 to illuminate for each event. For example, the wearable visualization device 12 may include five lights, a first light may illuminate upon a first drop of the wearable visualization device 12, a second light may illuminate upon a second drop of the wearable visualization device 12, a third light may illuminate upon a throw of the wearable visualization device 12, and so forth. In some embodiments, the processor 54 may instruct one or more lights 42 to illuminate for each event, and the number of lights 42 may be based on the severity of each event. For example, the wearable visualization device 12 may include five lights, a first light may illuminate upon a first short drop of the wearable visualization device 12, a second light and a third light may illuminate upon a high-speed throw of the wearable visualization device 12, and so forth. Then, when a certain number (e.g., all) of the lights 42 of the wearable visualization device 12 are illuminated, the operator may be notified to taken the action (e.g., by viewing the lights 42). In some embodiments, the wearable visualization device 12 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 42, the processor 54 may take one or more other actions, such as sending a notification to the operator system 60 and/or the attraction system 62. 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 54 may turn off the wearable visualization device 12 or at least certain features of the wearable visualization device 12 (e.g., turn off the lenses 20; block display of virtual features on the lenses 20). In some embodiments, the processor 54 may block display of virtual features on the lenses 20 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 54 may continue to enable display of virtual features on the lenses 20 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 12 may be coupled (e.g., removably coupled; temporarily locked) to the guest interface device 14 and/or to a structure, such as a ride vehicle. For example, the wearable visualization device 12 may be locked to the guest interface device 14 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 12 from the guest interface device 14. 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 12 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 12 may then be coupled to the guest interface device 14 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 12 that has experienced the event to be quickly removed for maintenance operations and replaced with another wearable visualization device 12 without slowing down the throughput (e.g., unloading and loading of the users) at the attraction, for example. As another example, the processor 54 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 20 of the wearable visualization device 12, and using a camera 64 of the wearable visualization device 12 to determine that the image is displayed correctly on the lenses 20. The processor 54 may receive an image from the camera 64 and may process the image (e.g., via template or pattern matching) to determine whether the wearable visualization device 12 is functioning properly after the event. The test may include providing information (e.g., a question and/or an image) on the lenses 20 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 40, as discussed in more detail below with respect to
In some embodiments, the processor 54 may be configured to send (e.g., via the communication device 58) an indication to the operator system 60, which may be remotely located from the wearable visualization device 12 (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 12 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 12 and/or may enable an operator of the amusement park to keep track of a reliability and/or durability of the wearable visualization devices 12. For example, if the wearable visualization devices 12 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 12 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 12 experience impaired functionality without any drops, the operator may be able to focus efforts on improving other features of the wearable visualization devices 12 and/or seek replacement under a warranty.
In some embodiments, the processor 54 may be configured to send (e.g., via the communication device 58) an indication to the attraction system 62 to cause the attraction system 62 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 62 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 12. Thus, the user or an operator may inspect, repair, and/or replace the wearable visualization device 12 and/or the user may unload from the ride vehicle and reload into another ride vehicle with a properly functioning wearable visualization device 12 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 12 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 12. The diversion may include blocking forward movement of the ride vehicle out of the loading/unloading zone until the wearable visualization device 12 is inspected or otherwise addressed. In some embodiments, in response to a determination that the event has occurred, the attraction system 62 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 12).
With reference to
In some embodiments, the processor 54 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 12 is coupled to or uncoupled from the guest interface device 14, each time the wearable visualization device 12 is docked to the structure (e.g., to the ride vehicle 74, which may be detected via a position sensor), each time the ride vehicle 74 is in the loading/unloading zone 80 (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
As shown, in step 92, the method 90 may begin by receiving (e.g., from the sensor 40, at the processor 54) a signal indicative of an event for the wearable visualization device 12. As discussed above, the processor 54 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 94, the processor 54 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 56, for example.
In step 96, the processor 54 may instruct at least one light 42 on the wearable visualization device 12 to illuminate. For example, the processor 54 may instruct the at least one light 42 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 98, the processor 54 may provide a notification to the operator system 60, which may be remotely located from the wearable visualization device 12. In step 100, the processor 54 may communicate with the attraction system 62, which may cause the attraction system 62 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 40 of the wearable visualization device 12 may enable the user to provide gesture inputs. With this in mind,
With reference to both
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 12 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 20, 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 20, 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 12 (e.g., by moving the wearable visualization device 12 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 12 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 20 of the wearable visualization device 12; visible on a display connected to the wearable visualization device 12, 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 12; 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 12, such as a computing system of the ride vehicle (e.g., the attraction system 62 of
The sensor 40 of the wearable visualization device 12 may also enable other operations, such as head tracking of the head of the user. The sensor 40 (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 10 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 10 may use a solid state cabin tracking system and may secondarily use the sensor 40 (e.g., if needed) for additional input to a prediction algorithm (e.g., a Kalman filter).
The sensor 40 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 10. Developers may utilize the basic tracking provided by the sensor 40 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 40, 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 32).
As set forth above, embodiments of the present disclosure may provide one or more technical effects useful for facilitating performance of maintenance activities on the wearable visualization device and for facilitating integration of the wearable visualization device in an amusement park. It should be understood that the technical effects and technical problems in the specification are examples and are not limiting. Indeed, it should be noted that the embodiments described in the specification may have other technical effects and can solve other technical problems.
While the embodiments set forth in the present disclosure may be susceptible to various modifications and alternative forms, specific embodiments have been shown by way of example in the drawings and have been described in detail herein. However, it should be understood that the disclosure is not intended to be limited to the particular forms disclosed. The disclosure is to cover all modifications, equivalents, and alternatives falling within the spirit and scope of the disclosure as defined by the following appended claims.
The techniques presented and claimed herein are referenced and applied to material objects and concrete examples of a practical nature that demonstrably improve the present technical field and, as such, are not abstract, intangible or purely theoretical. Further, if any claims appended to the end of this specification contain one or more elements designated as “means for [perform]ing [a function] . . . ” or “step for [perform]ing [a function] . . . ”, it is intended that such elements are to be interpreted under 35 U.S.C. 112(f). However, for any claims containing elements designated in any other manner, it is intended that such elements are not to be interpreted under 35 U.S.C. § 112(f).
This application claims priority to and the benefit of U.S. Provisional Application No. 62/791,735, entitled “AUGMENTED REALITY (AR) HEADSET FOR HIGH THROUGHPUT ATTRACTIONS,” filed Jan. 11, 2019, which is hereby incorporated by reference in its entirety for all purposes.
| Number | Name | Date | Kind |
|---|---|---|---|
| 6243207 | Kawamura et al. | Jun 2001 | B1 |
| 6259565 | Kawamura et al. | Jul 2001 | B1 |
| 6384983 | Yamazaki et al. | May 2002 | B1 |
| 7012756 | Takagi et al. | Mar 2006 | B2 |
| 7019909 | Yamazaki et al. | Mar 2006 | B2 |
| 7059182 | Ragner | Jun 2006 | B1 |
| 7350394 | Flynn et al. | Apr 2008 | B1 |
| 7375645 | Tsai | May 2008 | B2 |
| 7450332 | Pasolini et al. | Nov 2008 | B2 |
| 7477469 | Cook | Jan 2009 | B2 |
| 7492544 | Jeansonne | Feb 2009 | B2 |
| 7495638 | Lamvik et al. | Feb 2009 | B2 |
| 7549335 | Inoue | Jun 2009 | B2 |
| 8025581 | Bryan et al. | Sep 2011 | B2 |
| 8212859 | Tang et al. | Jul 2012 | B2 |
| 8330305 | Hart | Dec 2012 | B2 |
| 8408041 | Ten Kate | Apr 2013 | B2 |
| 8477425 | Border et al. | Jul 2013 | B2 |
| 8511827 | Hua et al. | Aug 2013 | B2 |
| 8576276 | Bar-Zeev et al. | Nov 2013 | B2 |
| 8694251 | Janardhanan | Apr 2014 | B2 |
| 8705177 | Miao | Apr 2014 | B1 |
| 8767014 | Vaught et al. | Jul 2014 | B2 |
| 8810482 | Abdollahi et al. | Aug 2014 | B2 |
| 8866870 | Smith | Oct 2014 | B1 |
| 8867139 | Gupta | Oct 2014 | B2 |
| 8905177 | Grossman | Dec 2014 | B2 |
| 8907865 | Miyawaki et al. | Dec 2014 | B2 |
| 8941559 | Bar-Zeev et al. | Jan 2015 | B2 |
| 8964298 | Haddick et al. | Feb 2015 | B2 |
| 9037125 | Kadous | May 2015 | B1 |
| 9052505 | Cheng et al. | Jun 2015 | B2 |
| 9088787 | Smith et al. | Jul 2015 | B1 |
| 9253524 | Kaburlasos et al. | Feb 2016 | B2 |
| 9268138 | Shimizu et al. | Feb 2016 | B2 |
| 9285871 | Geisner et al. | Mar 2016 | B2 |
| 9286730 | Bar-Zeev et al. | Mar 2016 | B2 |
| 9292973 | Bar-Zeev et al. | Mar 2016 | B2 |
| 9310591 | Hua et al. | Apr 2016 | B2 |
| 9310610 | Border | Apr 2016 | B2 |
| 9316834 | Makino et al. | Apr 2016 | B2 |
| 9342610 | Liu et al. | May 2016 | B2 |
| 9354446 | Abdollahi et al. | May 2016 | B2 |
| 9360671 | Zhou | Jun 2016 | B1 |
| 9366870 | Cheng et al. | Jun 2016 | B2 |
| 9366871 | Ghosh et al. | Jun 2016 | B2 |
| 9383582 | Tang et al. | Jul 2016 | B2 |
| 9389423 | Bhardwaj et al. | Jul 2016 | B2 |
| 9395811 | Vaught et al. | Jul 2016 | B2 |
| 9402568 | Barfield | Aug 2016 | B2 |
| 9451915 | Wong | Sep 2016 | B1 |
| 9454007 | Smith et al. | Sep 2016 | B1 |
| 9454010 | Passmore et al. | Sep 2016 | B1 |
| 9497501 | Mount et al. | Nov 2016 | B2 |
| 9519144 | Lanman et al. | Dec 2016 | B2 |
| D776110 | Gribetz et al. | Jan 2017 | S |
| D776111 | Baldassi et al. | Jan 2017 | S |
| 9569886 | Akenine-Moller et al. | Feb 2017 | B2 |
| 9576399 | Lo et al. | Feb 2017 | B2 |
| 9581819 | Boggs et al. | Feb 2017 | B1 |
| 9582922 | Lanman et al. | Feb 2017 | B2 |
| 9588341 | Bar-Zeev et al. | Mar 2017 | B2 |
| 9606362 | Passmore et al. | Mar 2017 | B2 |
| 9638836 | Harrison et al. | May 2017 | B1 |
| 9638921 | Miller et al. | May 2017 | B2 |
| 9645396 | Andes et al. | May 2017 | B2 |
| 9658457 | Osterhout | May 2017 | B2 |
| 9658460 | Lee et al. | May 2017 | B2 |
| 9667954 | Tang | May 2017 | B2 |
| 9690371 | Saito | Jun 2017 | B2 |
| 9690374 | Clement et al. | Jun 2017 | B2 |
| 9690375 | Blum | Jun 2017 | B2 |
| 9696552 | Goergen et al. | Jul 2017 | B1 |
| 9715257 | Manullang | Jul 2017 | B2 |
| 9720505 | Gribetz et al. | Aug 2017 | B2 |
| 9733477 | Gupta | Aug 2017 | B2 |
| 9733480 | Baek et al. | Aug 2017 | B2 |
| 9733481 | Carollo et al. | Aug 2017 | B2 |
| 9741125 | Baruch et al. | Aug 2017 | B2 |
| 9763342 | Long et al. | Sep 2017 | B2 |
| 9773438 | Gribetz et al. | Sep 2017 | B1 |
| 9778467 | White et al. | Oct 2017 | B1 |
| 9839857 | Wagner | Dec 2017 | B2 |
| D807882 | Gribetz et al. | Jan 2018 | S |
| 9864406 | Miller et al. | Jan 2018 | B2 |
| 9869862 | Cheng et al. | Jan 2018 | B2 |
| 9874749 | Bradski et al. | Jan 2018 | B2 |
| 9877016 | Esteban et al. | Jan 2018 | B2 |
| 9885871 | Abdollahi et al. | Feb 2018 | B2 |
| D812612 | Gribetz et al. | Mar 2018 | S |
| 9928661 | Kinstner et al. | Mar 2018 | B1 |
| 9933624 | White et al. | Apr 2018 | B1 |
| 9939650 | Smith et al. | Apr 2018 | B2 |
| 9958951 | Gribetz | May 2018 | B1 |
| 9983697 | Gribetz | May 2018 | B1 |
| 9984505 | Rimon et al. | May 2018 | B2 |
| 9984510 | Kinstner et al. | May 2018 | B1 |
| 9990779 | Kinstner et al. | Jun 2018 | B2 |
| 9990872 | Gribetz et al. | Jun 2018 | B1 |
| 10026231 | Gribetz et al. | Jul 2018 | B1 |
| 10026232 | Lo et al. | Jul 2018 | B2 |
| 10037629 | Kinstner et al. | Jul 2018 | B2 |
| D825560 | Gribetz et al. | Aug 2018 | S |
| D825561 | Gribetz et al. | Aug 2018 | S |
| 10043305 | Lo et al. | Aug 2018 | B2 |
| 10057968 | Gribetz et al. | Aug 2018 | B2 |
| D830359 | Gribetz et al. | Oct 2018 | S |
| 10088685 | Aharoni et al. | Oct 2018 | B1 |
| 10127727 | Yuan et al. | Nov 2018 | B1 |
| 10168768 | Kinstner | Jan 2019 | B1 |
| 10168789 | Soto et al. | Jan 2019 | B1 |
| 10168791 | Gribetz et al. | Jan 2019 | B2 |
| 10186088 | Kinstner et al. | Jan 2019 | B2 |
| 10212517 | Beltran et al. | Feb 2019 | B1 |
| 10260864 | Edwin et al. | Apr 2019 | B2 |
| 10306030 | Zeng | May 2019 | B1 |
| 10685515 | Hazebrouck | Jun 2020 | B2 |
| 20040201484 | Cox | Oct 2004 | A1 |
| 20050279165 | Yuasa | Dec 2005 | A1 |
| 20060072206 | Tsuyuki et al. | Apr 2006 | A1 |
| 20060250322 | Hall et al. | Nov 2006 | A1 |
| 20070030159 | Stoev | Feb 2007 | A1 |
| 20100172052 | Shibata | Jul 2010 | A1 |
| 20100319434 | Weber | Dec 2010 | A1 |
| 20110149431 | Shibata | Jun 2011 | A1 |
| 20120188149 | Yamada | Jul 2012 | A1 |
| 20120232823 | Baggen | Sep 2012 | A1 |
| 20120320100 | Machida et al. | Dec 2012 | A1 |
| 20130137076 | Perez et al. | May 2013 | A1 |
| 20130141419 | Mount et al. | Jun 2013 | A1 |
| 20130197856 | Barfield | Aug 2013 | A1 |
| 20130218058 | Ceoldo | Aug 2013 | A1 |
| 20130245986 | Grokop | Sep 2013 | A1 |
| 20130278631 | Border | Oct 2013 | A1 |
| 20130300636 | Cunningham | Nov 2013 | A1 |
| 20140118829 | Ma et al. | May 2014 | A1 |
| 20140146394 | Tout et al. | May 2014 | A1 |
| 20140168264 | Harrison et al. | Jun 2014 | A1 |
| 20140188426 | Fastert | Jul 2014 | A1 |
| 20140253284 | Peterson | Sep 2014 | A1 |
| 20140364208 | Perry | Dec 2014 | A1 |
| 20140364209 | Perry | Dec 2014 | A1 |
| 20150003819 | Ackerman et al. | Jan 2015 | A1 |
| 20150103152 | Qin | Apr 2015 | A1 |
| 20150301565 | Manullang | Oct 2015 | A1 |
| 20150312561 | Hoof et al. | Oct 2015 | A1 |
| 20160011341 | Smith | Jan 2016 | A1 |
| 20160048203 | Blum et al. | Feb 2016 | A1 |
| 20160062454 | Wang et al. | Mar 2016 | A1 |
| 20160093230 | Boggs et al. | Mar 2016 | A1 |
| 20160097929 | Yee et al. | Apr 2016 | A1 |
| 20160097930 | Robbins et al. | Apr 2016 | A1 |
| 20160098095 | Gonzalez-Banos et al. | Apr 2016 | A1 |
| 20160109710 | Smith et al. | Apr 2016 | A1 |
| 20160154439 | Rothkopf | Jun 2016 | A1 |
| 20160171779 | Bar-Zeev et al. | Jun 2016 | A1 |
| 20160188943 | Franz | Jun 2016 | A1 |
| 20160210784 | Ramsby et al. | Jul 2016 | A1 |
| 20160240013 | Spitzer | Aug 2016 | A1 |
| 20160346704 | Wagner | Dec 2016 | A1 |
| 20160353089 | Gallup et al. | Dec 2016 | A1 |
| 20160364907 | Schoenberg | Dec 2016 | A1 |
| 20160370855 | Lanier et al. | Dec 2016 | A1 |
| 20160377869 | Lee et al. | Dec 2016 | A1 |
| 20160379417 | Mount et al. | Dec 2016 | A1 |
| 20170053445 | Chen et al. | Feb 2017 | A1 |
| 20170053446 | Chen et al. | Feb 2017 | A1 |
| 20170053447 | Chen et al. | Feb 2017 | A1 |
| 20170059831 | Hua et al. | Mar 2017 | A1 |
| 20170108696 | Harrison et al. | Apr 2017 | A1 |
| 20170116950 | Onal | Apr 2017 | A1 |
| 20170131581 | Pletenetskyy | May 2017 | A1 |
| 20170158118 | Lenker | Jun 2017 | A1 |
| 20170171538 | Bell et al. | Jun 2017 | A1 |
| 20170176747 | Vallius et al. | Jun 2017 | A1 |
| 20170178408 | Bavor, Jr. et al. | Jun 2017 | A1 |
| 20170188021 | Lo et al. | Jun 2017 | A1 |
| 20170193679 | Wu et al. | Jul 2017 | A1 |
| 20170206713 | Lo et al. | Jul 2017 | A1 |
| 20170208318 | Passmore et al. | Jul 2017 | A1 |
| 20170212717 | Zhang | Jul 2017 | A1 |
| 20170220134 | Burns | Aug 2017 | A1 |
| 20170221264 | Perry | Aug 2017 | A1 |
| 20170236320 | Gribetz et al. | Aug 2017 | A1 |
| 20170236332 | Kipman et al. | Aug 2017 | A1 |
| 20170237789 | Harner et al. | Aug 2017 | A1 |
| 20170242249 | Wall et al. | Aug 2017 | A1 |
| 20170255011 | Son et al. | Sep 2017 | A1 |
| 20170262046 | Clement et al. | Sep 2017 | A1 |
| 20170262047 | Saito | Sep 2017 | A1 |
| 20170270464 | Morgenthau | Sep 2017 | A1 |
| 20170270841 | An et al. | Sep 2017 | A1 |
| 20170277256 | Burns et al. | Sep 2017 | A1 |
| 20170285344 | Benko et al. | Oct 2017 | A1 |
| 20170293144 | Cakmakci et al. | Oct 2017 | A1 |
| 20170305083 | Smith et al. | Oct 2017 | A1 |
| 20170316607 | Khalid et al. | Nov 2017 | A1 |
| 20170323416 | Firmila | Nov 2017 | A1 |
| 20170323482 | Coup | Nov 2017 | A1 |
| 20170336863 | Tilton et al. | Nov 2017 | A1 |
| 20170337737 | Edwards et al. | Nov 2017 | A1 |
| 20170345198 | Magpuri et al. | Nov 2017 | A1 |
| 20170352226 | Matsuzawa et al. | Dec 2017 | A1 |
| 20170363872 | Border et al. | Dec 2017 | A1 |
| 20170363949 | Valente et al. | Dec 2017 | A1 |
| 20170364145 | Blum et al. | Dec 2017 | A1 |
| 20180000385 | Heaton et al. | Jan 2018 | A1 |
| 20180003962 | Urey et al. | Jan 2018 | A1 |
| 20180018515 | Spizhevoy et al. | Jan 2018 | A1 |
| 20180024370 | Carollo et al. | Jan 2018 | A1 |
| 20180032101 | Jiang | Feb 2018 | A1 |
| 20180033199 | Eatedali et al. | Feb 2018 | A9 |
| 20180054502 | Wilson | Feb 2018 | A1 |
| 20180059715 | Chen et al. | Mar 2018 | A1 |
| 20180059776 | Jiang et al. | Mar 2018 | A1 |
| 20180095498 | Raffle et al. | Apr 2018 | A1 |
| 20180104601 | Wagner | Apr 2018 | A1 |
| 20180126116 | White | May 2018 | A1 |
| 20180164594 | Lee et al. | Jun 2018 | A1 |
| 20180196262 | Cage | Jul 2018 | A1 |
| 20180203240 | Jones et al. | Jul 2018 | A1 |
| 20180263534 | Lee | Sep 2018 | A1 |
| 20180293041 | Harviainen | Oct 2018 | A1 |
| 20180367952 | Devdas | Dec 2018 | A1 |
| 20190094554 | Benesh et al. | Mar 2019 | A1 |
| 20190318706 | Peng et al. | Oct 2019 | A1 |
| 20190324280 | Yildiz | Oct 2019 | A1 |
| 20190357618 | Zheng | Nov 2019 | A1 |
| 20200162844 | Itoh | May 2020 | A1 |
| 20200174558 | Gui | Jun 2020 | A1 |
| Number | Date | Country |
|---|---|---|
| 1643501 | Jun 2013 | EP |
| 2834718 | Oct 2018 | EP |
| 2562758 | Nov 2018 | GB |
| 2012141461 | Jul 2012 | JP |
| 5790187 | Oct 2015 | JP |
| 5801401 | Oct 2015 | JP |
| 2015228050 | Dec 2015 | JP |
| 5913346 | Apr 2016 | JP |
| 2016528942 | Sep 2016 | JP |
| 2017522911 | Aug 2017 | JP |
| 6191929 | Sep 2017 | JP |
| 6216100 | Oct 2017 | JP |
| 6237000 | Nov 2017 | JP |
| 2017532825 | Nov 2017 | JP |
| 6248227 | Dec 2017 | JP |
| 100630762 | Sep 2006 | KR |
| WO-2008044569 | Apr 2008 | WO |
| WO-2014106041 | Jul 2014 | WO |
| WO-2018213727 | Nov 2018 | WO |
| Entry |
|---|
| Laerhoven et al., Fair Dice A Tilt and Motion-Aware Cube with a Conscience (Year: 2006). |
| Schweiger et al., Throwing Event Detection using Acceleration Magnitude collected with Wrist-Worn Sensors (Year: 2020). |
| Yatani et al. , Information Transfer Techniques for Mobile Devices y Toss & Swing Actions (Year: 2004). |
| U.S. Appl. No. 16/738,906, filed Jan. 9, 2020, Patrick John Goergen. |
| U.S. Appl. No. 16/738,917, filed Jan. 9, 2020, Douglas Evan Goodner. |
| U.S. Appl. No. 16/738,788, filed Jan. 9, 2020, Andrew Brian Raij. |
| PCT/US2020/013163 International Search Report and Written Opinion dated Apr. 17, 2020. |
| Number | Date | Country | |
|---|---|---|---|
| 20200225715 A1 | Jul 2020 | US |
| Number | Date | Country | |
|---|---|---|---|
| 62791735 | Jan 2019 | US |
