top of page

A plugin that enables remote execution of the RIGDOCKS API over a network.

  • Version information: RADNODZ_ver2.0.0

  • Available OS: Windows 10 or later / macOS 12 or later

  • Available engine: Unreal Engine 5

-　API　-
03_GOLD.png

The operating platform has been migrated to RIGDOCKS Bridge, and APIs other than those that control Reaper can now be executed even when Reaper is not running.

RADNODZ_ver2.0.0

-　API Detail-

■Migrating the operating platform to RIGDOCKS Bridge

  1. Resident implementation: Changed the configuration so that the main API processing runs on RIDOCKS Bridge (a resident application).

  2. Installation: Changed to installation via package from RIGDOCKS Bridge.

  3. Settings: Go to the RIGDOCKS Bridge Plugin Settings screen to access settings and third-party display.

  4. Signature Verification: The code signature is now verified before loading modules, and modules that fail verification are not loaded.

  5. Terms of Use: RIGDOCKS Bridge has been modified so that you cannot execute the API until you agree to the Terms of Use.

  6. ■ Supports operation from the command line program "rigcmd"

■ Changes to server functions

  1. Unified listening: The RIGDOCKS system now handles TCP listening (accepting connections, TLS, and destination distribution). There is now a single port for the entire RIGDOCKS system, and the listening address and port are managed by the RIGDOCKS Bridge.

  2. Default Port: The default port for new installations has been changed from `12345` to `23760`. Environments with saved settings will retain the previous value. Default Listening Address: The listening address for new installations is `127.0.0.1` (PC only), and the server is turned OFF. Users can choose whether to expose it to the outside world using RIGDOCKS Bridge.

  3. Settings screen: Server startup/shutdown is now controlled by a toggle in the RIGDOCKS Bridge [Plugin Settings screen]. Third-party displays can also be accessed from the same screen.

  4. TLS: Changed to accept only TLS 1.3 (only AEAD cipher suite and ephemeral key exchange are accepted). Clients using TLS 1.2 or earlier cannot connect.

  5. Authentication Information: Key and authorized client information moved to a common RIGDOCKS storage location. Added a method to accept key requests from clients and approve them via RIGDOCKS Bridge.

  6. Connection Limitations: Added limits on the number of simultaneous connections, the number of simultaneous connections before authentication, the message size before authentication, and the time limit until authentication. Version Check: Changed the client compatibility check from matching version IDs to checking the range of communication specification (ABI) versions. For updates where the communication specification does not change, connections can be made without replacing the client. Unsupported versions will be rejected with `NotSupportedAbiVersion`.

  7. Logging: Connection start, end, and source are recorded in product-specific logs. Client-specific communication logs (default is OFF) can be enabled from the server tab in RIGDOCKS Bridge.

bottom of page