Update and troubleshoot 360 Hextile CAM

Manual updates, rollback, and what to do when 360 Hextile CAM refuses a request.

Last updated: 2026-11-01

Updating 360 Hextile CAM is a manual folder replacement. From 0.1.2, the download contains one HextileCam plugin folder. Versions 0.1.0 and 0.1.1 contain two folders. There is no automatic installer or updater.

Update to 0.1.2 or later

Select the exact Unreal Engine patch and BuildId from Downloads. The steps below target 0.1.2 or later. If installing a historical 0.1.0/0.1.1 package instead, install both plugin folders and keep or restore their corresponding project plugin references; do not apply the companion-removal step.

  1. Close Unreal Editor and back up your project, including its .uproject.
  2. Keep the old plugin ZIP or folders for rollback. Move the installed HextileCam and, if present, HextileCamMoviePipeline folders outside all Unreal plugin discovery paths. A backup still inside Plugins may be detected. If using development junctions, move the junction itself; do not delete its target.
  3. Copy the new package's Plugins/HextileCam folder into your project's Plugins folder. Never merge new files over an older installation.
  4. When upgrading from 0.1.0/0.1.1, remove any HextileCamMoviePipeline entry from the Plugins list in your .uproject. Keep HextileCam. The separate plugin is gone; the identically named module is now inside HextileCam.
  5. Open the project and follow Check the installation. Check saved cameras, Blueprint children, material overrides and saved Movie Pipeline configurations, then render a still to a fresh output folder.

Leaving the old companion folder can cause duplicate modules. Leaving its enabled project plugin reference can cause a missing-plugin error. Module names and saved class paths are unchanged; actual saved-workflow qualification is separate from that source compatibility. No update modifies project files automatically.

Roll back

Close Unreal, move the new plugin outside discovery, then restore your backed-up project descriptor and the complete old plugin folder(s). A 0.1.0/0.1.1 rollback needs both old folders and its corresponding project plugin references. Keep your level and sequence backups; backward compatibility of newly saved assets is not promised. Never remove old render output as part of an update.

Troubleshooting

Start with the exact error text. 360 Hextile CAM reports a technical reason when it refuses a request, and repeating an unchanged request will not change the result.

What you see What it means What to try
Missing-module prompt, or a plugin will not load The package does not match your engine build Install the package for your exact engine version and BuildId.
Output already exists (DestinationExists) The camera never overwrites a file Use a fresh folder or a different Name.
Invalid Settings, including an invalid exposure A setting is outside its allowed range Fix the setting named in the message and retry.
Capacity Exceeded or Bloom Work Limit Not enough GPU or memory headroom for this request Lower the final dimensions or the source face size, or turn off supersampling.
Missing Asset Or Shader A required shader was not available yet Wait for first-use shader preparation, then retry.
Unsupported Recipe or Unavailable World The combination or world is outside what is supported Use an Editor level with the camera-driven render launcher. Packaged games, remote executors and -game rendering are not supported. An out-of-scope world can currently show a camera-association error instead of an unsupported-context message.
Busy Another capture or render owns the camera Wait, or cancel the running still or render.
Lumen looks wrong or is not applied Lumen needs project settings that the plugin does not change Set them yourself; Lumen is Off by default.
Cancel is slow Cancelling waits for shader preparation, the capture in progress and the GPU Wait. There is no fixed cancellation time.
A cancelled render left files Cancelled renders keep partial output and metadata Render again into a fresh folder.

Other refusals you may see are Invalid Camera Association, Ambiguous Camera, Incompatible Target, Target Owned By Another Camera, Stale Generation, Invalid Pixels, GPU Or Readback Failure, Delivery Failure and Unknown Or Expired Request.

Information to keep when something fails

Keep and share:

  • the exact error text;
  • your Unreal Engine version and BuildId;
  • the package's PackageManifest.json;
  • the camera and render settings that were used (the evaluated recipe);
  • the output metadata/ files, which are written alongside images.

Say whether you think the cause is an unsupported context, an invalid setting, an output collision, or a real shortage of memory. A refusal is a technical statement about the request, not a licensing or upgrade prompt.

Provenance of this guide

Written for the first 360 Hextile CAM download (plugin version 0.1.0, source revision 710c698283df1508bbe9a8ce89c35f0875855cb7) and checked on Unreal Engine 5.8.4, Windows, D3D12 SM6, on an NVIDIA GPU. This page is for that release and does not describe other hardware.

Esc
Searching...
No results found.
Type to search the documentation
↑↓ Navigate ↵ Select Esc Close

We use cookies for analytics to understand how visitors use our site. Privacy Policy