Troubleshooting: STRIKEPACK HORIZON™
Expand for PS5®/PC Strikepack Troubleshooting...
🟠 When connected to your PS5® console, the Strikepack LEDs are stuck on Orange or Green.
This LED behavior will be:
Orange on firmware version 1.2.0.
Green on firmware version 1.1.24.
This indicates No USB Data Connection, due to either:
Incorrect PS5® console setting.
Physical wired connection issue.
With no USB data connection, your DualSense® controller will only connect wirelessly instead of through the Strikepack, meaning No Functional Mapping or M.O.D.s.
Try the following:
✅ Firmware Update to 1.2.0.
✅ PS5® Console Settings:
Bluetooth®: On.
Communication Method: Use USB Cable.
✅ Don’t touch any buttons during plug-in.
✅ Use a high-quality data cable:
USB-C to USB-C: 100W
USB-A to USB-C: 15W
Avoid hubs, extenders, and cables over 10 ft (3 m).
✅ Ensure your controller is updated.
✅ Try a different controller if you can.
✅ Restart/power cycle your PS5® console.
(Rest Mode can potentially cause USB issues)
⚪ When connected to your PS5® console, the Strikepack LEDs skip to White (No Red).
Normal LED behavior if setup was previously completed.
You should be good to plug and play.
🔴 When connected to your PS5® console, the Strikepack LEDs stay Red.
To complete setup:
Plug your Strikepack—enabled controller into your PS5® console.
Open the STRIKEPACK CENTRAL™ app on your phone or tablet.
Wait for the LEDs to go from Red → White (this can take up to 60+ seconds).
If the LEDs are still Red after several minutes.
In the app,
tap the 
Gear icon → tap Forget Device (if shown).Close the app.
On your phone/tablet:
✅ Bluetooth®, Location, and Internet: On.
✅ App and device software: Updated.
✅ App Permissions: All Allowed.
Try switching:
From Wi-Fi ➜ Mobile Data Only (Disable Wi-Fi).
Or Mobile Data ➜ Wi-Fi Only (Disable Mobile Data).
Restart:
Phone/tablet (full power off/on).
PS5® console (full power cycle).
Restart the Strikepack:
1.2.0 firmware:
Hold the pill-shaped Restart button on the right-side for roughly a second, then release it.Older 1.1.24 firmware: Unplug/replug the cable.
Open the app and wait to see if the Strikepack LEDs turn White this time.
⚠️ Only reinstall the app as a last resort. If you've been exporting your profiles in their Settings sections, you’ll be able to import each one afterwards. Otherwise, all settings will be lost.
🎮 Controller Unresponsive After Setup Complete.
This can happen if setup took too long to complete. If LEDs are White, setup is done. To regain control:
1.2.0 firmware:
Hold the pill-shaped Restart button on the right-side for roughly a second, then release it.Older 1.1.24 firmware: Unplug/replug the cable.
Either way, it’s now plug and play.
⏱️ "Disconnects" / Time Out.
If your controller freezes mid-game (e.g. stuck walking), that’s a timeout. When you experience this, your controller will stop responding until you use the Restart button or unplug and replug the cable.
⌛ Time out within 1 minute:
Setup was unsuccessful (even if the Strikepack LEDs indicate otherwise).
Re-do the PS5® Setup Guide steps.
⏲️ Time out after several minutes:
✅ Try the following:
Firmware 1.2.0.
Restart/power cycle your PS5® console.
If no luck, reach out to our Support Team for other solutions.
🎧 Audio Loss.
If you experience no controller audio or microphone issues.
✅ Try the following:
Firmware 1.2.0.
Adjust system volume control to see if it restores audio.
Restart/power cycle your PS5® console.
Use a different headset if you can.
If no luck, reach out to our Support Team for other solutions.
🔁 Reset Setup.
If all troubleshooting has failed, try starting fresh. On the right-hand side, while 
holding Paddle Buttons 4 & 2 along with the pill-shaped Restart button above them, plug your Strikepack—enabled controller into your PS5® console. After roughly a second, release the 3 buttons.
Firmware 1.2.0: Reset Setup confirmed by
Strikepack LEDs.
🧼 Memory Clear.
Worth trying for issues with the app/M.O.D.s. While holding both pill-shaped buttons (Function & Restart buttons) together, plug your Strikepack—enabled controller into your PS5® console. After roughly a second, release the 2 buttons.
Firmware 1.2.0: Memory Clear confirmed by
Strikepack LEDs.
🔴 Red Gearhead Eyes Only.
If just the Gearhead Eyes are Red, this indicates the Strikepack is currently not connected with the app or the app is closed. (Several Gamepack M.O.D.s use resource-intensive features that require the app to remain open).
💻 PC Gaming Mode Previous Issues in Older Firmwares:
Update to 1.2.0 to fix these issues:
🔁 Button repeating behavior on mapped Paddle Buttons.
🐢 Responsiveness (polling rate).
🔈 No audio until volume adjusted.
🆘 When Contacting our Support Team for Help:
Before reaching out:
We do not operate on weekends or statutory holidays.
Our live chat is usually open Mon - Fri 12:30 PM - 4:45 PM PST.
📬 When emailing us, ensure your email inbox isn’t full. (Unfortunately common with iCloud® accounts).
Include in your message:
🧾 Picture of order receipt.
(Purchases from our site include an order number starting with US, UK, or CA).
🕵️ Detailed description of issue. (In the email body, not the subject line).
📎 Attach photos + videos if possible.
⚠️ Your warranty will be void if you accidentally damage, attempt self-repair of, physically modify, or discard the product without permission from our Support Team.
We are a small but 💪 mighty in-house Support Team. We will try our best to get back to you in reasonable time. However, if you don't receive a reply in a week, please email us again, as your email may have been misplaced or not received.
(Emails with no subject or vague information may get filtered to spam).
Issue: My Strike Pack is becoming excessively warm and uncomfortable to touch.
Cause: It is normal for the Strike Pack to become noticeably warm but not hot. Excessively high temperatures may indicate a failing device.
Solution: Do not dispose of the Strike Pack, as this will void your warranty, and we may require the device back for analysis. Instead, stop using it immediately and contact our Support Team for further instructions at support@collectiveminds.ca
Issue: My Strike Pack is disconnecting from my controller during use.
Cause: This is most often caused by a loose data connection, typically due to a faulty cable or a problem with your controller's port. In rare cases, it may be due to a failing Strike Pack, especially if it is overheating, or, for the Xbox® Strike Pack, an issue with the USB adapter.
Solution: If you have another cable that fits the USB guide of the Strike Pack, try using it to see if the disconnection issue stops. USB-A to USB-C or USB-C to USB-C and 10ft (3m) or shorter will work. If possible, try using a different controller as well. If the issue persists, please contact our Support Team email at support@collectiveminds.ca
Issue: I just started using a GAMEPACK and some M.O.D.s are not working.
Cause: Most GAMEPACKs need you to match how your buttons are setup or M.O.D.s will activate on the wrong buttons.
Solution: The GAMEPACK settings section is accessed through the gear icon at the top-right of a GAMEPACK's Dashboard. Any settings that you need to match to your game will be surrounded by a grey border. If a game has custom button mapping, it will be reflected here. If you are using any customized buttons, you MUST keep Button Layout set to Custom, and you MUST match all buttons individually.
Issue: I have used my STRIKEPACK HORIZON™ with the STRIKEPACK CENTRAL™ app on two different smart devices. Now it fails to connect to one of them.
Cause: One of the devices is holding onto a connection (this mostly happens with iOS devices). You can only be connected to one device at once.
Solution: Open the app on the device that you suspect is holding onto the connection. Tap the gear icon in the GAMEPACK selection screen, and tell it to forget device. Restart the app on the other device and try to connect.
Issue: My controller is lighting up but the Paddle Buttons are NOT mapping and none of the M.O.D.s are working.
Cause: You have probably turned the controller on yourself, instead of waiting for it to light up on its own. The controller has connected wirelessly to the console, instead of connecting through the wired Strike Pack device.
Solution: Turn on your console exclusively with its actual power button. Wait for your controller to turn on by itself.
Issue: I cannot connect to the STRIKEPACK CENTRAL™ app. It says something along the lines of "user did not allow permissions".
Cause: You did not fully allow all requested permissions. These permissions will vary between Android & iOS but it is vital that you allow them through.
Solution: Ensure you turn on Internet, GPS Location Services, and Bluetooth® on your smartphone or smart device. Then allow all permissions when starting the app. You may have to delete and reinstall the app, as this might be easier than trying to figure out which permissions you denied in your smart device's settings. On start up of the app, allow all requested permissions.
Issue: I cannot connect to the STRIKEPACK CENTRAL™ app, even after allowing all permissions. It just sits on connecting (or alternatively it connects but the RGB LEDs are all wrong).
Cause: Your firmware is out-of-date. The app will actually warn you that this is the case now.
Solution: Strike Pack REQUIRES the latest FIRMWARE UPDATE to get started. You can use 1 of 3 methods to update it. With Method 1 & 2, you can use almost any device that supports Chrome (or Edge) web browser and wired USB connection, other than iOS devices.
Method 1 (Recommended):
Method 2:
If STRIKEPACK HORIZON™ is already attached to your controller via the USB Adapter, you have the option of HOLDING PADDLE BUTTONS 1 & 3 TOGETHER while connecting it to the device to enter "UPDATER MODE", then to perform the update, visit the "WEB UPDATER" at firmware.modcentral.ca
Method 3:
DO NOT plug in the USB Adapter and try the "WINDOWS UPDATER" or "MAC UPDATER" here.
Tips:
You may need to disable your Anti-Virus, Firewall, or Popup Blocker to avoid them getting in the way of the update process. Whenever possible, you should try to use a USB port in the back of your computer or at least a port that you know is reliable. You may experience issues with anything older than Windows 10. The Mac Updater is going to come up as unverified/unsigned, just like the Windows Updater. Ensure that you configure your Mac OSX to allow this kind of software through.
Issue: M.O.D.s are not working or they are all pressing buttons that they are not supposed to.
Cause: It is likely that you have not yet matched the GAMEPACK 
Settings to your in-game settings, or you did try to do this and missed something.
Solution: Ensure that any grey bordered Settings if present, are expanded and matched to your in-game settings. This is the first thing that you should check for with any new GAMEPACK profile. Also ensure that you are NOT doing additional remapping in your console's system settings that are outside of the in-game settings.
Issue: "Automatic", "Hybrid", "Cycle", "Select", or "Third" Switch Weapon button tracking loses sync with your in-game weapon.
Cause: Lost sync occurs when your Switch Weapon button is pressed in a different context, or when your game switches your weapon through other means.
Solution: Turn off any in-game settings that unnecessarily switch weapons and become familiar with points in your game that commonly cause a lost sync, which typically include spawning, accessing menus, and performing alternate gameplay activities.
To correct a lost sync, use the Controller Shortcuts or app to swap to the correct ACTIVE Weapon Slot. With "Select - D-Pad", you can just reselect your weapon with the D-Pad to sync it.
Issue: Optimized Anti-Recoil is way off in Apex Royale, COD, RB6 Siege, Rust, other games.
Cause: You have probably missed our known Game Requirements listings; some of which are NOT default in-game settings. Because these settings requirements often change throughout a game's lifecycle, some of them will be missing from videos, so it is important to find all updated information at Game Requirements.
For example, Apex Royale and RB6 Siege GAMEPACKs are optimized for maximum Field Of View (FOV), as it is assumed that most players will increase it to gain an advantage. Our team previously found FOV to not much affect recoil in Apex Royale but now it does, so this requirement came in after its GAMEPACK Setup video was made.
It may also be a recoil-affecting Weapon Attachment, or a special variant of a weapon that has different recoil; an issue that quite often crops up in COD games.
You should also ensure that you have NOT aimlessly adjusted the Anti-Recoil slider settings before you have even started.
It may also simply be an update to the game that has changed a weapon's recoil. In which case, our team will likely have it fixed soon.
Solution: See the Game Requirements section here. Please note that if you DO NOT want to follow these requirements, you will probably have to do some fairly heavy adjustments with Quick Edit.
The point of Optimized Anti-Recoil is to either get you there at the start or at least point you in the right direction. If you want to use different settings, you will need to adjust with Quick Edit. The same goes for certain recoil-affecting Weapon Attachments, such as scopes that are higher than 1x in Apex Royale. RB6 Siege actually requires certain Weapon Attachments for its Optimized Anti-Recoil to be effective. RB6 Siege and Rust require a specific sensitivity and other settings. Want to use something different? Quick Edit. Our team cannot optimize for everything and how much we can optimize for depends on the game, but we try to make Quick Edit as robust as possible.
When it comes to making adjustments to Optimized Anti-Recoil, while Directional Quick Edit tends to be easier to use, the best result is usually achievable via Pattern Strength Quick Edit, because quite often the strength of the recoil changes; NOT its basic shape.
Issue: M.O.D.s interfere with in-game menus or alternate gameplay activities.
⚠️ This is notoriously a problem for vehicles, where you may switch out of the driver seat, or fail to accelerate and brake.
Cause: Interference occurs because ACTIVE M.O.D.s are typically designed for "run & gun" or "boots on the ground" gameplay, but they will always affect your controls, regardless of which activities share those controls.
Solution: "Automatic" and "Manual" have dedicated M.O.D. blocking Controller Shortcuts. For other "Weapon Swap Modes", try assigning Block M.O.D.s to a Weapon Slot that DOES NOT have Switch Weapon button tracking. Alternatively, use the 
Block M.O.D.s feature on the app, or try the Toggle M.O.D.s Paddle Button M.O.D.
Issue: In-game menus pop up when using Controller Shortcuts, or the in-game response of the 
TOUCHPAD or 
VIEW button feels delayed.
Cause: The TOUCHPAD or VIEW ACTIVATOR only passes through its normal gameplay function when it is RELEASED QUICKLY or HELD LONG.
Solution: Quickly use Controller Shortcuts, before an in-game menu can pop up.
As for the delay, if it is bothersome, or if orACTIVATOR is simply a difficult reach for your thumb, try replacing it with the Alt Activator Paddle Button M.O.D., which is available in most GAMEPACKs; particularly shooters. Action-style GAMEPACKs DO NOT offer an Alt Activator Paddle Button M.O.D. but they pass through TOUCHPAD or VIEW much more quickly to your game than Shooter-style GAMEPACKs do.
Issue: Controller Shortcuts are NOT functioning or they are inconsistent.
Cause: Controller Shortcuts are likely being pressed in the wrong order.
Solution: The order in which Controller Shortcuts are pressed matters. "While HOLDING orACTIVATOR..." means that you should be holding it ahead of pressing the other button. This can be a miniscule amount of time but Activator must always be held first.
Memory Clear
Issue: After a recent firmware update, I am experiencing issues.
Cause: The STRIKEPACK HORIZON™ caches data on its device memory. Sometimes when we make a dramatic update to the product such as a major new feature, this data may no longer line up correctly with the changes.
Solution: Perform a Memory Clear after the update, as shown in the video below:
App Crashes
Issue: The app is crashing.
Cause: We may need to improve compatibility with your specific phone/tablet/smart device model.
Solution: As the app matures, it will become more stable. We want to resolve the issue that is affecting your experience as quickly as possible. If you are experiencing crashes and especially frequent ones; contact us at support@collectiveminds.ca with the heading "App Crash Report".
So that we can diagnose the crash on our end, please provide your exact phone/device model and as close as possible to the actual time (indicating your time zone) that your last crash occurred on the date that it occurred. If possible, provide your STRIKEPACK HORIZON™ serial; accessible from the top-right gear while on the "Select Your GAMEPACK" screen.
Describe where you was in the app and what you was doing when the crash occurred. Was there a black screen? Did the app crash and close out? Did the STRIKEPACK HORIZON™ disconnect from the app and was it stuck on connecting? Was you using a particular M.O.D. at the time?
Combo Record & Playback
Issue: Unable to record an additional combo after recording a combo.
Cause: All recording blocks for this GAMEPACK profile have been used up.
Solution: Either re-record your previous combo and be more efficient, or create another GAMEPACK profile for a new set of recording blocks.
Issue: Immediately recorded stick movement that I did not make.
Cause: Your controller may have stick drift.
Solution: You should be able to resolve this with the Calibrator.
Issue: Analog sticks feel weird during recording.
Cause: Normal space saving measure. Analog sticks are downgraded to 8-way digital inputs during recording.
Solution: Precise stick recordings are impossible, but because your sticks are downgraded during recording, your limited movements can be planned throughout. Minimize stick direction changes to conserve recording blocks.
Issue: Analog triggers feel like hair triggers during recording.
Cause: Normal space saving measure. Analog triggers are downgraded to digital inputs (pressed at 100%) during recording.
Solution: Because your triggers are downgraded during recording, plan around any trigger presses being 100% pressed.
Issue: Unable to record long enough to create desired macro or generator.
Cause: All recording blocks for this GAMEPACK profile have been used up. Even a wait time that exceeds roughly 5 seconds, will use up a recording block.
Solution: Most Action-style GAMEPACKs are optimized for short combos. While you can create a new GAMEPACK profile for a fresh set of recording blocks, you will probably still lack the amount of required blocks.
This is where Macro GAMEPACK shines as it is optimized for large macros and it has by far the best chance of being up to your task. With Macro, Loop Combo, and the Block Controller Rumble features combined, you may attempt to create a generator. Macro GAMEPACK's code sharing system even allows you to share your generator online.
Issue: Successfully created a macro or generator but in-game rumbles are hazardous to an unattended controller.
Cause: Loop Combo, as with the other Combo Modes, DOES NOT block in-game rumbles.
Solution: On the Bottom-Bar, in the 
Controller section, toggling ON Block Controller Rumble will allow you to safely place down your controller with Loop Combo.
Issue: Cannot operate controller during combo playback.
Cause: Default Controller Interrupt Behavior; Block Inputs.
Solution: See Settings for Controller Interrupt Behavior. Several options hand you back control during combo playback. If you just want to move around during combo playback, Pass-Through Inputs is a good option.
Generators
Issue: Generator is going to the wrong places or "breaking".
Cause: You have likely either missed a step in the instructions or requirements, or started the generator in the wrong in-game location.
Solution: Please follow the generator's instructions exactly. Generators can become dangerous if they are activated in the wrong location without the proper requirements, especially when games are filled with microtransaction buttons. If you are sure that you are doing everything correctly, the game's user interface or timing may have changed. Please contact support.
Trademark Note: STRIKEPACK™, STRIKEPACK HORIZON™, STRIKEPACK HORIZON VISTA™ are trademarks of Collective Minds Gaming Co. Ltd. All product names, logos, brands, and other trademarks, images, or videos mentioned in this manual or on the website are used solely for identification purposes and remain the property of their respective trademark holders. These trademark holders are NOT affiliated with Collective Minds™, and they DO NOT sponsor or endorse its products, services, or websites. The trademarks "Xbox®", "Xbox Series X|S®", "Xbox One®" are owned by Microsoft Corporation. The trademarks "PlayStation®", "PlayStation®5", "PS5®," "DualSense®" are owned by Sony Interactive Entertainment. The trademark "Bluetooth®" is owned by Bluetooth Special Interest Group (SIG).
Last updated