COBRA Feature Requests

Requesting a belt-pack or another holder for the 6M other than the mounting bracket for more comfortable wear on the body for SPFX applications.

Allow two 18R2 remotes to act as clones and communicate with the same firing modules.

Requesting decals with support information on them that could be applied to module cases for on-the-spot help. This can include a QR code for certain manuals, common error codes, or support contact information.

If a customer batch uploads a bunch of fireworks with a CSV, but they have incorrect information, there's no way to update them all with the CSV. Instead customers need to add them all as new fireworks, thus creating duplicates. If they have to do this multiple times there will be multiples of the same firework in their Archive, making it difficult to identify the valid firework easily

Feature request to add Compound Cake type to "My Fireworks"

Due to browser limitations it would be nice if there was the ability to create a show through the IGNITE App.

It would be great to have a dedicated DMX module without cues, at a fraction of the cost of a module. To use a 36M or 72M JUST to support some DMX fixtures, without needing cues, is an expensive "waste" of an amazing module! There are plenty of locations where I want to use a DMX fixture that are nowhere near racks. I understand that R&D might be high, but it's a dream. LOL

It would be nice to be able to use the Command Center to check e-match resistance on modules.

For those in the UK or Europe, when creating custom label templates, it is an extra step to have the dimensions you want for a label in mm, and then have to convert that to inches so that you can create or edit the label in Show Creator. I would like to have the option to choose the unit of measurement to use.

Currently using the touchpad and command pro software is the only way to quickly stop a script in order to select another. In the event of a command pro or touchpad issue where you would need to run multiscripts without the touchpad, the only way to stop a script and select a new one is by changing the modules to test and re-arming. This is a time consuming process that does not work in a fast moving multiscript production.