Confirm Menu Access
If the menu does not appear, start with Menu Not Opening. For Internal, the documented flow uses F2 in the lobby, a wait for injection and Insert for menu access.
Distinguish a missing software session from a single disabled visual, then review the display controls in your exact package.
If Marvel Rivals ESP is missing, first decide whether the menu is also missing or whether only the player visuals are absent. Those are different symptoms. Internal and Predator organize their visual settings differently, so the next checks should follow the selected product’s current menu.
If the menu does not appear, start with Menu Not Opening. For Internal, the documented flow uses F2 in the lobby, a wait for injection and Insert for menu access.
Internal lists boxes, skeletons, health, ultimate, names and distance. A missing single element is different from a completely missing player overlay.
Predator lists self, teammates and enemies as player groups. Confirm which group you are trying to display rather than assuming all players share one visible setting.
Predator lists Only Visible; Internal’s Chams & Glow lists Show Visible Only. These affect their relevant displays and should not be confused with aimbot visibility checks.
If every visual is absent, check menu access and the correct product session first. If boxes or names appear but the ultimate element does not, inspect the relevant element’s controls rather than repeating the entire launch flow immediately.
Glow and ordinary boxes are different features. A highlighting setting may explain missing model color even when box ESP is present. Keep the symptom specific.
Internal explicitly lists saved configs. Loading an older profile can restore older choices, so review the visual settings after using Load Config. The feature list does not establish identical configuration behavior in Predator.
The configuration guide explains the distinction between saved configs and hero profiles. A selected combat profile does not automatically prove every visual element is enabled.
If the menu is available and the relevant visuals still do not appear, provide support with the exact product, Windows build, launch step reached, which visual is missing and whether other overlay elements work. Include screenshots of the menu and scene where possible.
Check the current product status for compatibility updates. Requirements and the product comparison can help identify whether you are following the correct package instructions.
Use the arrows below the player to switch between the two product previews.
Browse the aiming controls, Magic Bullet settings, Triggerbot options, hero selector and keybinds. Use the arrows to switch screenshots, or click the current image for a larger view.
Compare the aiming menu with an in-game visual preview. Each image can be opened at full size.
Start with menu access because the software session may not have reached the documented stage.
Model highlighting and overlay boxes are separate listed visuals.
No shared behavior is established. Inspect the relevant visual category’s own settings.
Identify the product, launch stage, exact missing visual and whether the menu and other visuals work.
Explore individual features, compare the packages, or find setup and troubleshooting help.
View the current features, requirements and purchase options for your chosen package.