Modular amusement park system and method

Abstract

The present disclosure relates to the field of amusement parks.SOLUTION: The system of the present embodiment includes an amusement park system having one or more hardware components and a controller. The controller includes a memory device storing a game layer and a software layer. The game layer includes game logic, and the software layer includes a game API communicatively coupled to the game layer, a wrapper API communicatively coupled to the game API, and a plurality of wrappers communicatively coupled to the wrapper API. The controller further includes a processor configured to execute instructions that cause the processor to receive a signal indicative of a modification of the hardware component, and based on the signal indicative of the modification of the hardware component, communicate with the hardware component via the wrapper to receive an input from the hardware component or cause an operation of the hardware component.SELECTED DRAWING: Figure 2

Description

[Technical Field]

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS This application claims priority to U.S. Provisional Patent Application No. 62 / 672,918, filed May 17, 2018, entitled "MODULAR AMUSEMENT PARK SYSTEMS AND METHODS," which is incorporated herein by reference in its entirety for all purposes.

[0002] The present disclosure relates generally to the field of amusement parks. Specifically, embodiments of the present disclosure generally relate to technological refreshes and updates in amusement parks. [Background technology]

[0003] The popularity of amusement parks (or theme parks) has grown significantly since the early 20th century. Amusement parks are likely to undergo constant construction and maintenance as new attractions are implemented and existing attractions are updated to accommodate the increased popularity. As modern attractions become more sophisticated and complex, and expectations among amusement park patrons correspondingly increase, improved systems and methods for accommodating technological refreshes and / or updates are required, which can result in increased attraction downtime. Summary of the Invention [Means for solving the problem]

[0004]

[0013] The following summarizes certain embodiments commensurate with the subject matter of the original claims. These embodiments are not intended to limit the scope of the present disclosure, but rather to provide a brief summary of some disclosed embodiments. Indeed, the present disclosure may include a variety of forms that may be similar to or different from the embodiments set forth below.

[0005] According to one embodiment, a system includes an amusement park system having one or more hardware components and a controller. The controller includes a memory device storing a game layer and a software layer. The game layer includes game logic, and the software layer includes a game application programming interface (API) communicatively coupled to the game layer, a wrapper API communicatively coupled to the game API, and a plurality of wrappers communicatively coupled to the wrapper API. The controller further includes a processor configured to execute instructions stored on the memory device. The instructions are configured to cause the processor to receive a signal indicative of a change in one or more hardware components of the amusement park system and, based on the signal indicative of the change in the hardware components, communicate with the one or more hardware components via one of the plurality of wrappers to receive input from or cause operation of the one or more hardware components.

[0006] In another embodiment, an amusement park configured to host a plurality of users includes a plurality of attractions, each attraction of the plurality of attractions including a plurality of interactive components configured to interact with the plurality of users. The amusement park further includes a controller having a memory device and a processor configured to execute instructions stored on the memory device. The instructions are configured to receive a signal indicating implementation of a new interactive component in one of the plurality of attractions and to cause the processor to register the new interactive component upon receipt of the signal. Upon registering the new interactive component, the processor is configured to process input signals received from the new interactive component, drive operation of the new interactive component, or a combination thereof.

[0007] In another embodiment, a method includes removing a first component from at least one connection of the amusement park. The first component is associated with a first set of functions. The method further includes implementing a second component of the amusement park utilizing the at least one connection. The second component is associated with a second set of functions, the first set of functions being different from the second set of functions. The method also includes registering the second component with an amusement park system of the amusement park such that the second set of functions of the second component is configured to be selectively triggered according to one or more input signals from a controller of the amusement park.

[0008] These and other features, aspects, and advantages of the present disclosure will be better understood from the following detailed description when read in conjunction with the accompanying drawings, in which like parts are designated by like numerals throughout. [Brief explanation of the drawings]

[0009] [Figure 1] FIG. 1 is a schematic diagram of an amusement park having a modular architecture, according to an embodiment of the present disclosure. [Figure 2] FIG. 2 is a block diagram of a controller for the amusement park of FIG. 1 in accordance with an embodiment of the present disclosure. [Figure 3] 2 is a flowchart of a process for implementing new components in the amusement park of FIG. 1 according to an embodiment of the present disclosure. [Figure 4] 2 is a schematic diagram of an amusement park attraction at the amusement park of FIG. 1 in accordance with an embodiment of the present disclosure. DETAILED DESCRIPTION OF THE INVENTION

[0010] The present disclosure provides systems and methods for quickly updating (e.g., refreshing) attractions and other entertainment features at amusement parks by promoting modularity and separability of hardware components. Provided herein is a system architecture that supports such modularity and promotes interoperability between hardware components that perform different functions within an attraction but are operationally related to one another. In some embodiments, an amusement park system architecture can include a game layer, a software architecture (e.g., “software”) layer, and a hardware architecture (e.g., “hardware”) layer. The game layer communicates the logic of a particular game and / or ride attraction to the software layer, which can further communicate this game logic to the hardware layer to implement the game logic via one or more hardware devices. That is, the software layer can effectively communicate the game logic to hardware drivers in the hardware layer using application programming interfaces (APIs) and wrapper-style protocols. This separation of at least the game layer, software layer, and hardware layer allows an amusement park to update various portions of its architecture (e.g., hardware and / or software components) with minimal impact to the overall amusement park system.

[0011] To illustrate, a new hardware component can be implemented (e.g., plugged in) within an attraction at an amusement park. The hardware component can be an input device and / or an output peripheral device. Once implemented within the attraction, the hardware component can be automatically registered with the system so that it can generate and / or receive events (e.g., communicate with other components at the amusement park). Indeed, the implementation of the hardware component can be seamless, without requiring a substantial overhaul of the existing attraction and / or further system reconfiguration by a technician. Once implemented and registered, the hardware component can be configured to respond to various stimulus messages that can originate from game logic in the game layer. Thus, an attraction can utilize existing hardware while also implementing new game logic and / or new software components. For example, a particular attraction can implement a first game using a game surface and multiple other hardware devices, such as ride vehicles and virtual reality headsets. Once the new game logic and / or new software components are implemented, the particular attraction can implement a second game using the existing game surface and multiple other hardware devices.

[0012] In one embodiment, some hardware components may allow guest input to further affect the operation of other hardware elements within the attraction to trigger a particular output (e.g., input from a guest weapon may cause a fixed target to light up or otherwise indicate a hit). As technology improves or the story of an attraction becomes more complex, the attraction may be updated with new hardware components, such as new weapon hardware, thereby enticing guests to return to the attraction. However, replacing fixed elements, such as fixed targets, may be more costly, especially if such targets include moving components. Thus, some hardware components (e.g., fixed targets) may continue to be used even when other hardware components (e.g., weapons) are replaced. Thus, the present technology, by way of example, in one embodiment, provides a system architecture that includes hardware wrappers or other communication protocols that enable new hardware components to communicate with existing hardware components without adjusting the protocols and / or existing hardware components in place. In this manner, hardware components, such as weapon hardware, may be replaced. New weapons may be introduced to the system and communicate with existing fixed targets without updating or modifying the existing system architecture and / or communication protocols.

[0013] The disclosed attraction systems and methods can be implemented in amusement park attractions, including shows, rides, promotions, etc. Using a modular architecture within an amusement park attraction allows the attraction to be easily updated and refreshed whenever new technology emerges. Thus, attractions are frequently changed and updated, encouraging guests to visit the park and further enjoying the thematic experiences the park offers.

[0014] With this in mind, FIG. 1 illustrates an embodiment of an amusement park 10 that can include one or more attractions 12. Each attraction 12 can accommodate multiple users 14 (e.g., guests, patrons). As described herein, the amusement park 10 can utilize a multi-layer system infrastructure to accommodate technology refreshes, updates, and the like, while minimizing downtime and impacts to the overall aesthetics and operations of the amusement park 10. In particular, the modularity of the multi-layer system infrastructure can enable changes (e.g., updates, replacements, additions, and / or removals) to one or more hardware or software components without substantially impacting other elements of the system (e.g., other hardware or software components).

[0015] To illustrate, in some embodiments, the amusement park 10 may include a first attraction 16, a second attraction 18, and a third attraction 20. However, it should be understood that the amusement park 10 may include any suitable number of attractions 12. As described in further detail herein, each attraction 12 may include any suitable number of hardware components 22, such as physical components, that may interact (e.g., communicate) with software components 24 stored in memory devices 26 of one or more controllers 28 and that may perform tasks related to the particular attraction 12. Indeed, there may be any suitable number of controllers 28. In some embodiments, each attraction 12 may be associated with a respective controller 28. The amusement park 10 may further include one or more hardware components 22 within an environment 29 (e.g., a queue) of the amusement park 10 that may also be communicatively coupled to the one or more controllers 28. In some embodiments, the environment 29 may include the attractions 12.

[0016] Controller 28 may employ processor 30, which may represent one or more processors, such as an application-specific processor. Controller 28 may also include a memory device 26 that stores instructions executable by processor 30 to perform the methods and control operations of amusement park 10 as described herein. Processor 30 may include one or more processing units, and memory 26 may include one or more tangible, non-transitory machine-readable media. By way of example, such machine-readable media may include RAM, ROM, EPROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to hold or store desired program code in the form of machine-executable instructions or data structures and that can be accessed by processor 30, or any general-purpose or special-purpose computer or other machine that includes a processor.

[0017] The controller 28 may be communicatively coupled to elements of the amusement park 10 through a communication system 32. In some embodiments, the communication system 32 may communicate through a wireless network, such as a wireless local area network (WLAN), a wireless wide area network (WWAN), near field communication (NFC), or Bluetooth. In some embodiments, the communication system 32 may communicate through a wired network, such as a local area network (LAN) or a wide area network (WAN). In some embodiments, the communication system 32 may communicate through light / laser, sound, quantum mechanical, or other environmental stimuli.

[0018] Each hardware component 22 (e.g., a peripheral device) can be categorized as an input device and / or an output device peripheral device. That is, each hardware component 22 can be an input device, an output device, or an input / output device. An input device can receive input, such as from one of multiple users 14, and send an input signal indicative of the received input to the controller 28. The hardware component 22 can include an interaction component, and the input can be received via one or more user input devices (e.g., buttons, knobs, touch screens, joysticks, actuatable elements, steering controls, triggers, etc.) of the interaction component. Correspondingly, the output device can receive an input signal from the controller 28 as a result of the input signal and / or directly from the input device. For example, the controller 28 can then further send one or more signals to one or more locations, such as output devices, within the amusement park 10 to provide an appropriate response according to the received input. In response, the output device can react to the signal, such as by operating a device or displaying images / information via a display device. For example, with respect to the hardware components 22 of the first attraction 16, the input devices may include VR devices such as VR tools and VR goggles, and the output devices may include VR goggles, since images are displayed through the VR goggles. With respect to the hardware components 22 of the second attraction 18, the input devices may include ride devices (e.g., tools) with which the user 14 can interact during the ride cycle, and the output devices may include animatronic show pieces and ride vehicles. With respect to the hardware components 22 of the third attraction 20, the input devices may include steering wheels, and the output devices may include a scoreboard and game floor displays. However, it should be understood that the amusement park 10 may include any suitable number of attractions 12 having any suitable number and types of hardware components 22.Additionally, the VR device may act as an input / output device, facilitating user interaction with the attraction 12 to generate input and cause another hardware element to output a response. The response may also trigger an output change on the VR device's display. As used herein, VR may refer to augmented reality, virtual reality, mixed reality, or a combination thereof.

[0019] Each of the hardware components 22 and software components 24 may be replaced or updated based on a variety of factors. For example, motivations for changing hardware components 22 and / or software components 24 of the amusement park 10 may include the release of new technology, movie or other media releases, seasonal changes, time of day, scheduled maintenance, or any combination thereof. When a component (e.g., a hardware component 22 or a software component 24) is installed, updated, or otherwise modified within the amusement park 10, the component may be registered with the amusement park 10 so that it can interact (e.g., communicate) with other components of the amusement park 10. That is, as described in further detail with reference to FIG. 2 , one or more controllers 28 may include various protocols for sending and receiving information to and from components of the amusement park 10.

[0020] 2 is a block diagram of the system architecture of an amusement park system 50 of the amusement park 10. The amusement park system 50 may be separated into a game layer 52, a software layer 54 (e.g., a software architecture layer), and a hardware layer 56 (e.g., a hardware architecture layer). The game layer 52 and the software layer 54 may each be stored in the memory 26 of the controller 28. The game layer 52 and the software layer 54 may be communicatively coupled to the hardware layer 56 via the communication system 32. The game layer 52 may include game logic 58 that determines the logic for when the attraction 12 interacts with, modifies, and / or manipulates elements of the attraction 12 (e.g., hardware components 22 and / or software components 24). That is, the game layer 52 may operate and execute the game logic 58.

[0021] The software layer 54 may include one or more game application programming interfaces (APIs) 60, one or more wrapper APIs 62, and multiple wrappers 64. The game APIs 60 may define a set of interface languages ​​that any game implementation (e.g., the game logic 58 of a particular attraction 12) can use to communicate with the software layer 54 and the hardware layer 56. For example, the game logic 58 may communicate with the game APIs 60 to trigger various environmental stimuli within the amusement park 10 (e.g., reactions that occur through the hardware components 22).

[0022] The wrapper API 62 can send messages from the game API 60 to the wrappers 64. The wrappers 64 are software elements that adapt, extend, and / or implement standard interface classes and are configured to register with the wrapper API 62 to receive messages related to environmental stimuli. The wrappers 64 can communicate with drivers associated with particular hardware components 22 so that the hardware components 22 can receive messages related to environmental stimuli. In some embodiments, each hardware component 22 can be associated with one or more respective wrappers 64. The wrappers 64 can act as a buffer between the hardware components 22 in the hardware layer 56 and the software components 24 in the software layer 54. For example, if a hardware component 22 is updated or modified, the operation, logic, and / or build of the software component 24 is not affected by the change or update. Conversely, when a software component 24 is updated, the wrappers 64 can reduce and / or avoid the need to update the hardware component 22 to match the latest software component 24. In some embodiments, additional hardware components 22 or functionality can be added. In such an embodiment, one or more wrappers 64 associated with the newly added hardware components may also be added to software layer 54. These newly added wrappers 64 may then be registered with wrapper API 62 to receive stimulus signals (e.g., messages, events).

[0023] The hardware layer 56 may include hardware components 22 configured for easy replacement and / or update as described herein. That is, the hardware components 22 may utilize a modular design (e.g., constructed of standardized units), standard (e.g., generic) attachment points, and dynamic internal configuration to facilitate the implementation of new hardware components 22 and the updating of existing hardware components 22. For example, the hardware components 22 may communicate with components in the software layer 54 and other hardware components 22 in the hardware layer 56 using a general-purpose interface bus (GPIB) 70 (e.g., a general-purpose interface (GPI)), which may be part of the communication system 32. Indeed, in some embodiments, the hardware components may utilize a wired communication network. In another example, the hardware components 22 may utilize a wireless communication network as described herein. In some embodiments, the hardware components 22 may communicate without the use of a network, such as by direct communication or broadcast communication via wired and / or wireless means. As a further example, hardware components 22 may utilize and / or be line replaceable units (LRUs) 72 that are easily replaceable modular components. Among other things, LRUs 72 may enable quick replacement at attraction 12 (e.g., “on-line”), thereby reducing downtime of attraction 12. Indeed, hardware components 22 within hardware layer 16 may utilize, for example, a limited number (e.g., one) of power supply types, a limited number (e.g., one) of input and output module types, and a limited number of other components. In this manner, even if some (or all) of hardware components 22 are to be added or modified, this portion can be easily implemented due, at least in part, to standard (e.g., common, generic, modular) components.The modular design of hardware component 22 can ensure correct implementation based on standards, guidelines, and best practices. In some embodiments, hardware component 22 can perform self-testing, i.e., hardware component 22 can determine whether it is suitable for continued operation. For example, hardware component 22 can include one or more sensors 73 configured to monitor inputs and outputs of hardware component 22 to determine the operational status of hardware component 22, such as whether hardware component 22 is operating as intended, and / or whether parts within hardware component 22 should be replaced / updated, such as whether hardware component 22 is nearing the end of its product life.

[0024] As an example, the hardware element 22 may be a weapon element of an attraction 12 in the amusement park 10. One or more of the hardware element's sensors 73 may detect a user input that activates a trigger to fire the weapon at a target. Other hardware components 22, such as targets, may detect a hit or miss based on the firing. Input signals caused by the firing of the weapon and hitting any target may be communicated to the game layer 52 via the software layer 54 to associate the hit with a particular user, and output signals may be sent back through the software architecture layer 54 to the hardware layer 56, for example, to illuminate or activate the target. That is, a user's input of activating the weapon may trigger an output of activating the target. Some attraction runs may include an enhanced weapon with new capabilities, and the game logic may receive an activation signal through an appropriate wrapper 64 to activate the target. If the upgraded weapon has explosive or other enhanced capabilities, the game logic 58 may unlock a new type of hardware component 22, which is typically fixed, or trigger a new target operation scenario. However, the absence of such enhanced functionality during normal game execution does not impede the ability to operate attractions 12. Furthermore, system 50 is able to quickly adapt to the incorporation of new hardware components 22 to execute special attractions and smoothly return to normal operation. Software layer 54 facilitates communication between hardware components 22 so that game logic 58 receives input signals in a plug-and-play manner.

[0025] 3 is a flowchart of a component implementation process 90 that may occur within amusement park 10. In some embodiments, the implementation of new components may be triggered, at least in part, by one or more variables. As described herein, motivations for park personnel to change attractions 12 may include new technology releases / updates, specific times of year, movie / video game releases, and maintenance. For example, a change of season, such as from fall to winter, may motivate a change from a Halloween-themed attraction 12 to a snow-themed attraction 12.

[0026] In some embodiments, the component implementation process 90 may begin with the removal of an existing (e.g., already installed) component (block 92). For example, if the new component being implemented is an animatronic show element, the existing (e.g., already installed) animatronic show element may be removed first. Once the existing component is removed, the amusement park system 50 may receive a signal indicating this removal (or may update the system to indicate the removal based on the absence of a signal from the element). Explaining, before block 92 occurs (e.g., before the existing animatronic show element is removed), the show clock of the attraction 12 associated with the animatronic show element may be configured to schedule a ride vehicle stop adjacent to the animatronic show element to allow viewing of the animatronic show element and / or passenger interaction with the animatronic show element. However, once the animatronic show element is removed, the system may receive an input indicating this removal and update the show clock to cancel the scheduled stop of the ride vehicle adjacent to the previous animatronic show element's location. In this manner, the interoperability of various hardware components can be dynamically updated based on changes in vehicle configuration.

[0027] At block 94, the new component may be installed (e.g., placed, connected, uploaded). As described herein, in some embodiments, the component to be installed and the existing component may each utilize an LRU 72. In fact, the new component may be easily installed using the same connections as the existing components, thereby increasing the efficiency of the component installation process 90 and reducing downtime of the attraction 12 during which the component installation process 90 is occurring. Furthermore, in some embodiments, the component installation process 90 may begin with the introduction of the new component (block 94). That is, it should be understood that it is not necessary to remove a component before installing the new component. In fact, the new component may simply be added to the amusement park 10.

[0028] At block 96, the new component may be registered (e.g., automatically configured) with the amusement park system 50. When the new component is installed (e.g., connected), the system receives an indication that the new component has been installed so that it knows how to interact with the new component. That is, the new component and its associated functionality (e.g., movement functionality, display functionality, special effects functionality, etc.) may be registered with the system so that the amusement park system 50 can utilize the new component and its associated functionality. In some embodiments, the automatic configuration (e.g., registration) performed at block 96 may be performed without user interaction with the amusement park system 50. In practice, once the component is installed (block 94), if the component is a hardware component 22, the wrapper 64 may identify the hardware component 22 and its associated functionality and notify the amusement park system 50 that the hardware component 22 has been installed, thereby enabling the amusement park system 50 to utilize the hardware component 22 at this time (block 96). In some embodiments, once the functionality of a hardware component is registered (block 96), the component may correspondingly be registered as an input peripheral and / or an output peripheral. Similarly, if the component is a software component 24 (e.g., an operating system update), once installed, the software component 24 and associated functionality may be selectively utilized by the amusement park system 50.

[0029] Generally, once a new component is registered, it can generate and receive events (e.g., communication signals). In particular, the amusement park system 50 can communicate with the component to utilize the registration functionality of the new component (block 98). In some embodiments, an event router / manager can be utilized to register the new component. The event router / manager can receive events from the new component and send them to other parts of the amusement park system 50. Similarly, the event router / manager can receive events from multiple parts of the amusement park system 50 and communicate them to the new component. In some embodiments, events can be assigned (e.g., communicated) using a flag, which can be a predetermined bit or bit sequence that holds a binary value indicating the presence of an event. That is, one or more components of the amusement park system 50 can communicate with other components in the amusement park system 50 using the flag. In one embodiment, the new hardware or software component can be registered as a type of a group of existing components.

[0030] In one example, the new hardware component 22 can be a holiday present structure that lights up at a specific time of day to indicate the availability of merchandise. When the new component is registered as a present and the system communicates to all registered presents via the wrapper 64, all registered presents can light up. Presents can be distributed throughout the park 10, and the system can register new presents in a modular manner and communicate to all registered present components, regardless of their location within the park 10, to trigger a common operation, such as a lighting function. Additionally, the new hardware component can have additional functions, such as an animatronic opening feature. The system 50 sends an activation signal to all presents, and for presents with enhanced features, the activation signal can trigger both the animatronic opening feature and the lighting function. For presents without enhanced features, the activation signal only triggers the lighting function.

[0031] FIG. 4 is a schematic diagram of a group of components 100 that may be included in one or more of the attractions 12 of FIG. 1. In the illustrated embodiment, the group of components 100 may include various software components 24 and hardware components 22 that may be organized and communicatively coupled using the hierarchical system architecture of the amusement park system 50 described with reference to FIG. 2. In the illustrated embodiment, the group of components 100 may include a ride vehicle 102, a steering wheel 104, a game floor 106, a special effects system 110, animatronic show elements 112, a show clock 114, and other components. In some embodiments, each component of the attraction 12 may be associated with one or more software components 24 and one or more hardware components 22. As described herein, the components of the group of components 100 may be updated using the method described with reference to FIG. 3.

[0032] For example, the game floor 106 may be an interactive game floor (e.g., hardware components 22) that can provide (e.g., display) various games in response to one or more signals provided by one or more software components 24. In some embodiments, one or more software components 24 in the game layer 52 and / or software layer 54 may be updated to enable the game floor 106 to provide new games. When a software component 24 associated with a display on the game floor 106 is updated, the game floor 106 may automatically communicate (e.g., receive / send signals / events) with the new software component 24 and begin displaying the new game. In some embodiments, implementing changes to the software component 24 may include registering new executable code. Similarly, in some embodiments, the hardware components 22 of the game floor 106 may also be updated. For example, the game floor 106 may be updated to include new animatronic show elements 112 on the game floor 106. Due at least in part to the structure and modularity of the amusement park system 50, the animatronic show elements 112 can automatically begin generating and receiving signals once they are installed (e.g., connected) within the attraction 12.

[0033] As a further example, the steering wheel 104 may be an input device that can provide directional control for the ride vehicle 102. In some embodiments, the steering wheel 104 may send one or more signals to the controller 28 that indicate the direction to steer the ride vehicle 102. The controller 28 may implement various effects, such as turning the ride vehicle 102 and increasing or decreasing a score, based on the direction of the ride vehicle 102. In some embodiments, the steering wheel 104 may be updated to account for different types of games. For example, the game type may be updated from a simple driving game to a game that includes virtual tools that are available through interaction between the user 14 and input devices (e.g., buttons) located on the steering wheel 104. In such an embodiment, the original (e.g., old, existing) steering wheel 104 may be removed and replaced with an updated steering wheel 104 that includes the input devices. Once the new steering wheel 104 is implemented (e.g., connected), the new steering wheel 104 may be registered with the amusement park system 50 so that it can subsequently generate and / or receive events.

[0034] In practice, the events (e.g., signals) generated and / or received by the original steering wheel 104 may differ from the events (e.g., signals) generated and / or received by the new steering wheel 104. For example, the original steering wheel 104 may be configured to receive directional signals (e.g., through user input) that indicate the driving direction of the ride vehicle 102. Furthermore, the new steering wheel 104 may be configured to generate multiple types of signals based on activation of input devices (e.g., buttons, knobs, touch screen, etc.) included in the new steering wheel 104. For example, activation of the input devices of the new steering wheel may generate special effect signals that indicate one or more special effects of the special effects system 110 (e.g., light effects, vibration effects, mist effects, sound effects, etc.) in addition to directional control. When the new steering wheel 104 generates a signal to activate a special effect based on user input, the controller 28 may receive the signal and activate the respective special effect of the special effects system 110. Additionally, as used herein, input provided by user 14 to hardware components 22 (e.g., input peripherals) of amusement park system 50 may also include biometric input, which may include body / gesture tracking.

[0035] 4 may be a path-based ride attraction 12 that includes one or more animatronic show elements 112 configured to operate based on input (e.g., signals) provided by a show clock (e.g., software component 24) 114. That is, the show clock 114 may be configured to provide signals that activate the animatronic show elements 112 to operate or perform a function when one or more of the ride vehicles 102 are within a particular distance threshold from the animatronic show element 112. In other words, the show clock 114 may maintain one or more schedules according to which the animatronic show elements 112 are scheduled to operate when one of the ride vehicles 102 is within a particular range of the animatronic show element 112.

[0036] The show clock 114 may also maintain one or more schedules that activate one or more effects on the ride vehicle 102 when the ride vehicle 102 is within a particular distance threshold of the animatronic show elements 112. For example, the show clock 114 may be configured to cause the ride vehicle 102 to vibrate, stop moving, or cause another special effect of the special effects system 110 to occur when the ride vehicle 102 is within a particular distance threshold. In some embodiments, the show clock 114 may be updated based on one or more new components being installed and registered with the amusement park system 50. For example, in some embodiments, a particular animatronic show element 112 may be removed from the attraction 12. When a particular animatronic show element 112 is removed, the amusement park system 50 can determine that the particular animatronic show element 112 has been removed, and the controller 28 can send a signal to the show clock 114 to update the schedule of the show clock 114 so that the ride vehicle 102 does not stop, vibrate, or produce a special effect when the ride vehicle 102 is within a particular distance threshold of the former location of the particular animatronic show element 112.

[0037] Additionally, as described herein, if the attraction 12 is to be updated, components such as the animatronic show elements 112 may be replaced. Specifically, the original animatronic show elements 112 (e.g., hardware components 22) may be replaced with updated animatronic show elements 112. In such an embodiment, the original animatronic show elements 112 may be associated with a first set of functions and special effects, and the updated animatronic show elements 112 may be associated with a second set of functions and special effects. For example, the original animatronic show elements 12 may actuate one or more of multiple limbs and spray water, whereas the updated animatronic show elements 112 may actuate one or more of multiple limbs, emit a particular light effect, emit a particular sound effect, and spray steam. In some embodiments, when the updated animatronic show element 112 is implemented, the updated animatronic show element 112 may utilize the same connections as the original animatronic show element 112. That is, as described herein, both the original animatronic show element 112 and the updated animatronic show element 112 may utilize LRUs 72, standard attachment points, modular designs, and other features that increase the efficiency of replacing (e.g., upgrading) the original animatronic show element 112. When the updated animatronic show element 112 replaces the original animatronic show element 112, the new animatronic show element 112 may register with the amusement park system 50 so that the updated animatronic show element 112 can generate and receive events (e.g., signals) and communicate with the amusement park system 50. Once implemented and registered, the amusement park system 50 can be configured to receive notification of the available features of the updated animatronic show elements 112 and to activate the available features of the updated animatronic show elements 112 (e.g., by sending an event / signal via one or more of the wrappers 64).Additionally, in some embodiments, an original component (e.g., an original animatronic show element 112) may be updated by updating (e.g., replacing) only one or more portions of the original component.

[0038] It should be understood that while some examples used herein describe the use of specific hardware components 22 and software components 24, such as ride vehicles 102, steering wheels 104, game floor 106, special effects system 110, animatronic show elements 112, and show clock 114, the associated methods, such as component implementation process 90 (FIG. 3), for modifying or updating components may be applied to any other suitable components within amusement park 10. In general, modifications to components (e.g., hardware components 22 and / or software components 24) may register functions associated with the component modifications such that amusement park system 50 can selectively trigger the functions.

[0039] While only certain features of the present embodiments have been illustrated and described herein, many modifications and changes will occur to those skilled in the art. It is, therefore, to be understood that the appended claims are intended to cover all such modifications and changes as fall within the true spirit of the present disclosure. It is further to be understood that certain elements of the disclosed embodiments can be combined with or substituted for one another.

[0040] The technology shown and claimed herein refers to and applies to tangible objects and specific examples of a practical nature that will materially improve the art, and thus are not abstract, intangible, or purely theoretical. Furthermore, where any claim appended at the end of this specification contains one or more elements designated as "means for [performing] ... [function]" or "step for [performing] ... [function]," such elements are to be construed pursuant to 35 U.S.C. 112(f). Conversely, for any claim containing elements designated in any other manner, such elements are not to be construed pursuant to 35 U.S.C. 112(f). [Explanation of symbols]

[0041] 10: Amusement park 22: Hardware Components 24: Software Components 26: Memory device 28: Controller 30: Processor 32: Communication Systems 52: Game layer 54: Software Architecture Layer 56: Hardware Architecture Layer 58: Games 60: Game API 62: Wrapper API 64: Rapper 70: General Purpose Interface Bus (GPIB) 72: Line Replaceable Unit (LRU) 73: Sensor

Claims

1. 1. An amusement park system, comprising: one or more hardware components; A controller; wherein the controller a memory device storing a software layer including a game layer including game logic, a game application programming interface (API) communicatively coupled to the game layer, a wrapper API communicatively coupled to the game API, and a plurality of wrappers communicatively coupled to the wrapper API; a processor configured to execute instructions stored in the memory device; and the instructions comprising: receiving a signal indicative of a change to the one or more hardware components of the amusement park system; communicating with the one or more hardware components via one of the wrappers to receive input from or cause operation of the one or more hardware components based on the received signal; configured to cause the processor to: An amusement park system characterized by:

2. the modification of the one or more hardware components of the amusement park system includes adding a new hardware component to the one or more hardware components or updating an existing hardware component among the one or more hardware components; The amusement park system according to claim 1 .

3. the modification of the one or more hardware components includes implementing new functionality in the one or more hardware components; The amusement park system according to claim 1 .

4. the communication causes the one or more hardware components to activate the new functionality. The amusement park system according to claim 3 .

5. further comprising one or more software components, wherein the instructions are configured to cause the processor to receive a second signal indicating a second change in the one or more software components. The amusement park system according to claim 1 .

6. the second modification of the one or more software components includes implementing new functionality in the one or more software components, and the processor is configured to trigger the new functionality upon receiving the second signal. The amusement park system according to claim 5.

7. the one or more software components include a show clock, and the processor is configured, upon receiving the signal indicating the change in the one or more hardware components, to adjust operation of the show clock based at least in part on the change in the one or more hardware components. The amusement park system according to claim 5.

8. the one or more hardware components include a line replaceable unit (LRU); The amusement park system according to claim 1 .

9. the one or more hardware components include one or more general purpose interfaces (GPIBs); The amusement park system according to claim 1 .

10. the one or more hardware components are configured to perform a self-test to determine the operational status of the one or more hardware components; The amusement park system according to claim 1 .

11. 1. An amusement park configured to host a plurality of users, comprising: a plurality of attractions each including a plurality of interaction components configured to interact with the plurality of users; A controller; wherein the controller a memory device; a processor configured to execute instructions stored in the memory device; and the instructions comprising: receiving a signal indicating implementation of a new interaction component within an attraction of the plurality of attractions; registering the new interaction component upon receipt of the signal; and wherein the processor is configured, upon registration of the new interaction component, to process input signals received from the new interaction component, drive operation of the new interaction component, or a combination thereof. An amusement park characterized by

12. the implementation of the new interaction component automatically triggers the registration of the new interaction component; 12. The amusement park of claim 11.

13. said registering said new interaction component registers a set of functions of said new interaction component with said controller such that said controller is configured to selectively invoke said set of functions; 12. The amusement park of claim 11.

14. When the new interaction component is registered, the new interaction component is configured to receive input from one of the plurality of users and generate an input signal based on the received input from the user, and the controller is configured to trigger a function of a hardware component of the attraction of the plurality of attractions based on the generated input signal of the new interaction component.

12. The amusement park of claim 11.

15. a group of existing components associated with a component type, the new interacting component being associated with the component type, and registering the new interacting component registers the new interacting component as the component type; 12. The amusement park of claim 11.

16. the controller is configured to, upon registration of the new interacting component, cause an action associated with both the collection of existing components and the new interacting component.

16. The amusement park of claim 15.

17. removing a first component associated with a first set of functions from at least one connection of the amusement park; utilizing the at least one connection to implement a second component of the amusement park associated with a second set of functionality different from the first set of functionality; registering the second component with an amusement park system of the amusement park such that the second set of functions of the second component is configured to be selectively triggered in accordance with one or more input signals from a controller of the amusement park; A method comprising:

18. implementing the second component of the amusement park includes connecting the second component via the at least one connection.

18. The method of claim 17.

19. the first component includes a first input device configured to generate a first input signal that triggers a first event in the amusement park system, and the second component includes a second input device configured to generate a second input signal that triggers a second event different from the first event in the amusement park system.

18. The method of claim 17.

20. registering the removal of the first component such that the removal of the first component triggers a change in one or more software components; 18. The method of claim 17.

21. the one or more software components include a show clock, and the removal of the first component triggers an adjustment of a schedule of the show clock.

21. The method of claim 20.

Images