Troubleshooting: Strikepack Horizon
Expand for Strikepack PS5®/PC Troubleshooting...
🟠 When connected to your PS5® console, the Strikepack LEDs are stuck on Orange.
This LED behavior will be:
Orange on firmware version 1.2.3.
Likely accompanied by the controller not automatically powering on (the base of the Touchpad not lighting up on its own) after you plug the cable into your Strikepack-enabled controller.
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 be able to connect wirelessly instead of through the Strikepack, meaning No Functional Mapping or M.O.D.s.
Try the following:
✅ Firmware Update to 1.2.3.
✅ 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.
If your included cable is shaped like this, you have our latest 100W cable:
Alternatively, you can use a USB-A to USB-C: 15W cable.
Avoid hubs, extenders, and cables over 10 ft (3 m), as they can introduce bad connections and power drop out.
✅ Make sure your controller is updated.
✅ Make sure the Strikepack is fully attached to your controller, and you aren't obstructing it in some way (e.g. controller skins).
There should be no visible gap between the Strikepack's USB-C connector and your controller's USB-C port. If there is,
press it down onto your controller from the top.The four pins on the Strikepack's hinge clip must be
pressed into the bottom four holes on your controller's speaker grill to confirm a secure attachment.
✅ Fully charge your controller before attaching the Strikepack.
(Your controller will not charge while the Strikepack is attached, and a controller battery that is critically low may cause issues).
✅ Try using a different controller to rule out a faulty USB-C port. This is a common and often overlooked cause.
(USB data and power lines are separate — a controller may still charge and work wirelessly, but fail to work with the Strikepack, which requires a stable wired connection).
✅ Restart/power cycle your PS5® console.
(Rest Mode can potentially cause USB issues).
✅ If you’re certain you’ve tried all of the above and have ruled out both the cable and controller, the issue may be with the Strikepack’s USB-C female port or male connector. Check if the controller automatically powers on (lights up) when the cable is plugged in through your Strikepack-enabled controller. If it doesn’t, do not disassemble your Strikepack, as this will void your warranty. Contact our Support Team for assistance.
If you are playing on PC, it is normal for Strikepack to display Orange.
⚪ 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:
Hold the unlabeled Restart button on the right-side for roughly a second, then release it. Alternatively, you can 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:
- Hold the unlabeled Restart button on the right-side for roughly a second, then release it. Alternatively, you can 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.3.
Restart/power cycle your PS5® console.
If no luck, reach out to our Support Team for other solutions.
🎧 Audio Loss:
If you experience missing controller audio or microphone issues.
✅ Try the following:
Firmware 1.2.3.
Adjust system volume control.
Try a different headset if you can.
Check both your headset cable and your Strikepack’s USB cable for any damage — especially if you have pets. PS5® audio can be affected by even minor damage, and sometimes this damage isn’t visible to the eye.
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 together along with the unlabeled Restart button above them, plug your Strikepack—enabled controller into your PS5® console. After roughly a second, release the 3 buttons.
Reset Setup confirmed by
Strikepack LEDs.
🧼 Memory Clear.
Worth trying for issues with the app/M.O.D.s. While holding both unlabeled buttons (Function + Restart buttons) together, plug your Strikepack—enabled controller into your PS5® console. After roughly a second, release the 2 buttons.
Memory Clear confirmed by
Strikepack LEDs.Memory Clear should be attempted after a firmware update, not before.
🔴 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 the latest firmware 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:
Human agents do not operate on weekends or statutory holidays.
Human agent responses for our live chat are usually Mon-Fri, 9:30 AM-11:30 AM, then 12:30 PM-4:45 PM PT (Pacific Time). Gearhead, our AI agent will attempt to help you out of hours. Please be patience with him, as he is still learning.
Gearhead AI can help you to change shipping addresses and cancel orders prior to the point of shipping, and he can provide some basic knowledge.
📬 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 videos + photos. (Overly short, blurry, or poorly lit videos and photos are not helpful, and will delay our troubleshooting process).
Clear photo of the LOT number, found on the label on the underside of the Strikepack.
⚠️ 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 message may have been misplaced or not received. (e.g. no subject line or vague information may get filtered to spam).
Our Support Team will not be demanded, threatened, or abused into offering a quick solution, should we feel more troubleshooting is warranted. Please show patience with us in finding you a solution.
Issue: My Strikepack is becoming excessively warm and uncomfortable to touch.
Cause: It is normal for the Strikepack to become noticeably warm but not hot. Excessively high temperatures may indicate a defective device, especially if it this not resolved by a firmware update.
Solution: Do not dispose of the Strikepack, as this will void your warranty, and we may require the device back for analysis. Instead, stop using it immediately, note down the Lot Number on the underside label of the device, and contact our Support Team with that information for further instructions at support@collectiveminds.ca
Issue: My Strikepack is disconnecting from my controller during use.
Cause: This is usually caused by a loose or failing data connection, typically due to either a faulty cable or a problem with your controller's port. It can also be caused by improperly setting up the PS5® Strikepack. In rare cases, it may be the Strikepack itself, or for the Xbox® Strike Pack, an issue with the USB adapter.
Solution: If you have another controller try that first (controller port issues are not that uncommon), then try another cable if you have one that is data capable. If you're using the PS5® Strikepack, redo its setup process. If the issue persists or if you are within warranty and need a new cable, 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 Strikepack device.
Solution: Wait for your controller to turn on by itself when you connect the cable. If this doesn't happen, try with just the controller and cable (no Strikepack). If it still doesn't happen, either your controller's port or your cable is defective and needs replacing.
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. If you don't want to delete and reinstall the app, look for the permissions you denied in your smart device's settings. Allow all 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: Strikepack requires the latest Firmware Update to get started. You can use 1 of 2 methods to update it. 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 the Strikepack 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
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.
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: Make sure any "Match In-game" Settings if present, are matched to your in-game settings. Some settings are expandable so be thorough. 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 Recoil Assist is way off in specific game.
Cause: You have probably missed our known Known Requirements listings, which are now typically listed in the Gamepack Settings. Because these settings requirements often change throughout a game's lifecycle, it is important to check back often.
It may also be a recoil-affecting Weapon Attachment, or a special variant of a weapon that has different recoil.
You should also ensure that you have not randomly adjusted the Recoil Assist 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, we will likely have it fixed soon.
Solution: See the Known Requirements in the Gamepack Settings. Please note that if you do not want to follow these requirements, you will probably have to do some fairly heavy adjustments to Recoil Assist.
The point of Optimized Recoil Assist 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.
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: The Gamepack will typically include a Controller Shortcut to Block M.O.D.s; otherwise you can use the 
Block M.O.D.s feature on the app, or 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: By design, and so it can be used for Controller Shortcuts, this button 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, try replacing it with the Alt Activator Paddle Button M.O.D., which is available in most Gamepacks.
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 or Activator..." means that you should be holding it ahead of pressing the other button. This can be a miniscule amount of time but the Activator must always be held first.
Memory Clear
Issue: After a recent firmware update, I am experiencing issues.
Cause: The Strikepack 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 serial; accessible from the top-right gear while on the "Select Your Gamepack" screen, or send a Support Email through there which will typically provide the data we need to diagnose the issue.
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 disconnect from the app and was it stuck on connecting? Was you using a particular M.O.D. at the time? More detail is better.
Macro/Combo Record & Playback
Issue: Unable to record an additional macro/combo after recording a combo.
Cause: All recording space for this Gamepack Profile has 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 space. This is more of an issue with the Action Gamepack, as its successor, the Macro Gamepack has an enormous amount more recording space to play with.
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: We are unable to implement precise stick recordings, but because your sticks are downgraded during recording, your limited movements can be planned throughout. Minimize stick direction changes to conserve recording space.
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 space for this Gamepack Profile has been used up. Even a wait time that exceeds roughly 5 seconds, will use up a recording space.
Solution: Most Action-style Gamepacks are optimized for short combos. While you can create a new Gamepack Profile for a fresh set of recording space, you may still lack the required space for complex and extended sequences.
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 Macro/Combo, and the Block Controller Rumble features combined, you may attempt to create a generator. Macro Gamepack's export/import 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 Macro/Combo, as with the other 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 Macro/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. Please be careful with generators that have been shared online by others to import into Macro.
Last updated