MEGATHREAD: A Collection of fixes for various issues.

[Roland]

Stuttering fix:

https://steamcommunity.com/app/2767030/discussions/0/596260472619016088/

Originally posted by MikeRocksTheBoat:

For Windows 10 (likely works the same with 11)
Type "Exploit Protection" in your search bar. Exploit Protection should show up at the top, so open that up.

Click on program settings.

Click the plus sign next to "add program to customize"
Select "choose exact file path"

This will open up a browser and you'll have to locate "Marvel-Win64-Shipping.exe"
It's usually in "steamapps\common\MarvelRivals\MarvelGame\Marvel\Binaries\Win64" unless you've moved your steam library around.

Double click on "Marvel-Win64-Shipping.exe"

A program settings window will pop up. Scroll down until you find "Control Flow Guard (CFG)"

Tick the box that says "Override system settings"

Click the toggle to "Off"

Hit apply and you're done!

Make sure to restart Marvel Rivals if it was open while you were doing this.

(edited to point to the correct exe file)

Stuttering Fix 2:

-Make sure D.O.C.P. (for AMD CPU users) or XMP (for Intel CPU users) is Enabled in your bios settings.

Unfortunately I cannot give detailed instructions on this as BIOS menus vary by manufacturer and model. Please refer to your Motherboard manual to find this setting.

Crashes eating up disk space:

https://steamcommunity.com/app/2767030/discussions/0/596260472619085940/

Originally posted by cooper:

It's important to know that as of right now (12/7/24) and until the next update (which I hope fixes this,) the game crashing dumps a huge file into your PC's appdata folder.
In my multiple crashes, this file ranged from 6GBs to up to 20GBs.

Another thing about the game crashing that I learned:
If the game freezes and you know it's not coming back (I say give it 10-20 seconds),
then immediately kill the game process with task manager.
What it's doing (I assume,) is reading the (now frozen) scene/engine data and compiling that "fulldump" in your appdata folder.

During this, the memory usage for the program skyrockets over time until you're out of memory, and the dump file will fill a huge chunk of your disk space.
If you're like me and have low disk space on your OS drive, this is really bad.

So, clean your crash log folder!

It's located at OS:\Users\(your username)\AppData\Local\Marvel\Saved\Crashes
You can also open your file explorer and type %localappdata% in the navigation bar to get there, then find the "Marvel" folder from there.

Go find specifically the "UEMinidump.full.dmp" file! The other .dmp file is fine to keep or send to the devs in bug reports. (or just delete these folders when you crash if you don't care to send reports.)

I assume this is some debugging development thing they just forgot to turn off because UE5 games don't output files this big, ever.

Script below I marked as an answer is a temporary solution to this.
It'll remove the contents of the Crashes folder for you.

Hope this helped!

and the script:

Originally posted by Roland:

Here's a batch script to empty the folder for you.

@echo off
setlocal
set "targetFolder=%LOCALAPPDATA%\Marvel\Saved\Crashes"

echo Deleting files in %targetFolder%
del /q "%targetFolder%\*"

echo Done!
endlocal
pause

Copy this into notepad and save it as whatever-you-want.bat and make sure you select the drop down at the bottom to change it from .txt to "All Files" when saving otherwise it may save it as .bat.txt

Change highlight save location:

https://steamcommunity.com/app/2767030/discussions/0/596260472619085940/

Originally posted by cooper:

In my thread as well I discovered how to change the highlight save location.
Go to %localappdata% and find Marvel > Saved > Config > Windows and find GameUserSettings.ini
The settings in there don't have descriptions, so modify them at your own risk.
General rule of thumb is settings that use numbers use 0 as lowest and 3 or 4 as highest.

At the bottom is where you input the path to change the highlight save location.
[CareerHighLight]
HighLightVideoSavedPath=
Any path here works as long as it's connected to your PC. You can use external drive letters, ect. (ex. F:\Videos\MarvelHighlights)

Note: this can be done in game, but if for some reason that is failing or you'd rather not do it that way, this will work too.

Dr Strange causing performance issues:

• Disable Control Flow Guard as described above.
  
• Set Global Illumination to SSGI Low
  
• Set Post Processing to Low.
  
• Set Anti Aliasing and Super Resolution Type to TAAU.(possibly optional, needs testing)

Global Illumination and Post Processing are going to be the hardest hitters to performance in a game like this. I'm on a 2060 Super and have everything else set to Medium and Models set to High and at 1080p I'm having no issues as a Strange main.

Disable UAC notifications for the Launcher:

https://steamcommunity.com/app/2767030/discussions/0/596260472619011433/?tscn=1733782521

Originally posted by VIANDE:

You can prevent the UAC from triggering for nothing as the launcher don't always need admin rights.
Open the registry editor (regedit)
Go to HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers
Add a new String Value
Value name: Your path to MarvelRivals_Launcher.exe for example C:\Program Files\steam\SteamApps\common\MarvelRivals\MarvelRivals_Launcher.exe
Value data: RunAsInvoker

OR
https://steamcommunity.com/app/2767030/discussions/0/596260472619011433/

Originally posted by Martok:

You can also skip the UAC prompt without editing the registry, by adding the following to the game's launch options in Steam:

cmd /min /C "set __COMPAT_LAYER=RUNASINVOKER && start "" %command%"

Black Screen On Cutscenes Fix for Linux/Steamdeck:

Use ProtonGE latest Version.

Originally posted by CaptainBasculin:

Native Installation works like this:

1. Download a release from the Releases[github.com] page.
   
2. Create a ~/.steam/root/compatibilitytools.d directory if it does not exist.
   
3. Extract the release tarball into ~/.steam/root/compatibilitytools.d/.
   

   tar -xf GE-ProtonVERSION.tar.gz -C ~/.steam/root/compatibilitytools.d/

4. Restart Steam.
   
5. Go into Marvel Rivals' Properties by right clicking to it.
   
6. In the Compatibility tab, select Force the use of a specific Steam Play compatibility tool
   
7. Select the ProtonGE version
   
8. Launch the game.

For more detailed installations (like asdf, flatpak or snap), refer to here[github.com]

Possible crash fix:

- Set Low Latency Mode to Off

This one will take a bunch of testing because I've made all of the changes listed under the Strange fix as well, but the crashes only stopped when I did this as well as those. So far it's been almost 4 days without any crashes when previously I was seeing about 5 a day.

---

If any of the ones with links were helpful for you, please visit the respective threads they came from and give them your Steam points, I do not need them. You can drop a comment below to bump the thread for visibility and that will be thanks enough for me.

I will be updating this thread as people submit stuff and/or I come across things.
We can hope this gets pinned but I doubt it will anytime soon.

[76561199027321472]

Originally posted by Pizza Roll:

Originally posted by Pizza Roll:

Idk if anyone here has a solution, but my older brother has been having a very specific issue of the game freezing and giving only a black screen right after launching. Something I noticed though is that it specifically freezes the moment you click into the game. If you have the game open in the background rather than the foreground it will load all the way up to the start menu, but the second you click into the window it'll completely freeze up only letting you close it through task manager (it's CPU usage also drops to 0% but idk if that's important or not). I've checked to make sure all of his drivers are up to date and tried various solutions I've tried to find but nothing's been working.

Okay so just in case anyone is struggling with this, we figured it out for our case 😭😭😭

For some reason any game that runs of unreal engine 5 will freak out and do thay if you have a controller plugged into the pc. That was literally it. The moment we unplugged the dualsense controller (idk if it applies specifically to a ps4 controller or not) the problem stopped on any game running off of unreal engine. Hopefully if anyone is running into this problem, this is the only reason why because literally wtf 😭

I have the same problem, but I don't have any controller plug into my PC. So I don't know how to solve it. Thank you in advance for your help.

[Roland]

Originally posted by xander !:

Originally posted by xander !:

i am having the same exact problem on the same exact maps!! i can also play royal palace but not the other one etc, this is the first time i have encountered somebody else having the same problem. i hope someone who was able to fix it comes across this

i'm not sure if you were also having this issue, but my game would crash entirely and it would be incredibly hard to actually kill the game and regain control of my pc since it was lagging so bad and would also force itself into focus. i would have to hit windows+tab to open up a new desktop and then open task manager from that desktop to kill the game and that would instantly clear up the lag and allow me to use my pc again. what fixed this issue for me entirely was running the game in borderless windowed instead of fullscreen.

after switching to borderless windowed, the game does not screw my entire pc up when it crashes. however, if i load into either of the two specific maps you listed, i crash with an unreal engine error that has a strange error.

what fixed this for me was clicking Clear Local Configuration Files in the launcher before starting my game. i have since then been able to load the two maps i was not previously able to load before

This is noteworthy

[Kalavinka]

I need help regarding black screen on every cinematics (startup before loading, homepage screen, after every match I got stuck - cinematics not skippable). Currently running on:
- widows 11 64 bit
- 11th Gen Intel Core processor i5-11400F
- 16 GB RAM
- NVIDIA GEFORCE GTX 1660 SUPER

Does anyone have solve this?

[Kalavinka]

Originally posted by Roland:

Originally posted by xander !:

what fixed this for me was clicking Clear Local Configuration Files in the launcher before starting my game. i have since then been able to load the two maps i was not previously able to load before

This is noteworthy

I need help regarding black screen on every cinematics (startup before loading, homepage screen, after every match I got stuck - cinematics not skippable). Currently running on:
- widows 11 64 bit
- 11th Gen Intel Core processor i5-11400F
- 16 GB RAM
- NVIDIA GEFORCE GTX 1660 SUPER

Does anyone have solve this?

[Roland]

Originally posted by Chaos:

Originally posted by Roland:

This is noteworthy

I need help regarding black screen on every cinematics (startup before loading, homepage screen, after every match I got stuck - cinematics not skippable). Currently running on:
- widows 11 64 bit
- 11th Gen Intel Core processor i5-11400F
- 16 GB RAM
- NVIDIA GEFORCE GTX 1660 SUPER

Does anyone have solve this?

Are your video drivers up-to-date?

[Kalavinka]

Originally posted by Roland:

Originally posted by Chaos:

I need help regarding black screen on every cinematics (startup before loading, homepage screen, after every match I got stuck - cinematics not skippable). Currently running on:
- widows 11 64 bit
- 11th Gen Intel Core processor i5-11400F
- 16 GB RAM
- NVIDIA GEFORCE GTX 1660 SUPER

Does anyone have solve this?

Are your video drivers up-to-date?

yes, mine are up-to-date. I'm hopeless at this point

[Roland]

Originally posted by Chaos:

Originally posted by Roland:

Are your video drivers up-to-date?

yes, mine are up-to-date. I'm hopeless at this point

Somewhere in a different thread someone mentions your issue and it reminded me of an old issue from back in the day where you'd sometimes be missing a needed video codec and have your issue. It's really unlikely these days, but not impossible.

To remedy this back then I would have downloaded Combined Community Codec Pack. It's been dead for like 9 years but it's still possible to find copies out there. I would do the "No Players" install.

The other person never responded on if they tried it or if it worked. I'm not holding my breath, but it's worth a shot; worst case, it doesn't work and you uninstall it.

[Roland]

Happy Christmas or whatever

[Roland]

Originally posted by Roland:

Originally posted by Chaos:

yes, mine are up-to-date. I'm hopeless at this point

Somewhere in a different thread someone mentions your issue and it reminded me of an old issue from back in the day where you'd sometimes be missing a needed video codec and have your issue. It's really unlikely these days, but not impossible.

To remedy this back then I would have downloaded Combined Community Codec Pack. It's been dead for like 9 years but it's still possible to find copies out there. I would do the "No Players" install.

The other person never responded on if they tried it or if it worked. I'm not holding my breath, but it's worth a shot; worst case, it doesn't work and you uninstall it.

Did you ever try this?

[Cyberion]

Disabling all overlays (Discord, Steam, Nvidia) seemed to fix the routine crashes for me (running on the Steam version of the game)

[Roland]

Originally posted by Cyberion:

Disabling all overlays (Discord, Steam, Nvidia) seemed to fix the routine crashes for me (running on the Steam version of the game)

Odd. Noted. If i get another report or two of this working for others, I'll add it to the main post

[Kenzaki]

Will these fix the issues of game lagging in spider islands map?

[Col. Hathi]

I tried a couple of different potential solutions, but undid them when they didn't appear to work in the slightest. I then tried disabling Low Latency Mode... and I hate to say that it seems to work. So far, at least.

[Roland]

Originally posted by Col. Hathi:

I tried a couple of different potential solutions, but undid them when they didn't appear to work in the slightest. I then tried disabling Low Latency Mode... and I hate to say that it seems to work. So far, at least.

You might be surprised how many people didn't wanna hear that

[A h o y_hoy]

Thank you for your work, Godspeed