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.

[Roland's 2nd]

Originally posted by cooper:

(also we're 3 days out and no fixes or updates to the game yet, I'm screeching rn)

Yea i doubt they did much work over the weekend, but I did see someone say that the community manager said int he Discord that they acknowledged the crashing thing and identified the issue and were working on a patch, so hopefully that patch includes some of these other issues as well.

[Skye]

Originally posted by Roland:

Originally posted by Anankninan Skylkwaker:

Unknown Error Code 220.

Every possble suggested fix online hasn't worked. Patch it.

So from what little I can find, several people have said that they had site blockers setup to limit what servers they connect to for other games, and disabling those did the trick. Do you have anything like that in place?
Also possibly changing your DNS to something like 8.8.8.8 might help. Lemme know

I have this problem but I don't have any site blocker and I've also changed dns, I've disabled firewall, nothing fixes it :/

[DugiHowser]

Is there a fix for the Out of Video Memory error? I have a 4090 there should be enough.

[Roland's 2nd]

Originally posted by Skye:

Originally posted by Roland:

So from what little I can find, several people have said that they had site blockers setup to limit what servers they connect to for other games, and disabling those did the trick. Do you have anything like that in place?
Also possibly changing your DNS to something like 8.8.8.8 might help. Lemme know

I have this problem but I don't have any site blocker and I've also changed dns, I've disabled firewall, nothing fixes it :/

I do not recommend this long term, but as a test could you try going into your router settings and placing your machine in a DMZ?
Definitely do not leave it like this, but it would be a quick and dirty way to test to see if your router security is the issue.

Also I presume you've already checked your Windows Firewall settings and made sure the game was allowed?
If not do that first. Just type Firewall into the Start menu and select Firewall & Network protection and then click Allow app through the firewall.

Also also another thing to check would be what type of Network you are set to, as sometimes Public Network breaks games and apps. (it's rare but it happens)
To check this go to Settings in the Start menu, then Network & Internet. At the top of that Window click Properties and you should see the option to select Public or Private; you'll want it set to Private for your home network.

Try the second and third thing before you try the DMZ stuff; lemme know what's up.

Originally posted by DugiHowser:

Is there a fix for the Out of Video Memory error? I have a 4090 there should be enough.

Nothing definitive but i have some ideas.
If you're able to launch the game and reach the menu, try lowering resolution and settings.

If you can't make it to the settings menu we can try editing the settings file manually.
To find it open file explorer and put the following in the address bar:

%localappdata%\Marvel\Saved\Config\Windows

you should see a file called GameUserSettings.ini
In that file you will want to locate

ResolutionSizeX=
ResolutionSizeY=

You can try changing those to 1920 for X and 1080 for Y and see if that works.
Also you can try lowering the options under

 [ScalabilityGroups]

to 1 or 0 as this would set the settings to Medium or Low

Let me know if any of this stuff works and if not we will go from there

[I, Omor]

turned off control flow guard, still having horrible stutters any time a particle is loaded for the first time.

[Roland's 2nd]

Originally posted by I, Omor:

turned off control flow guard, still having horrible stutters any time a particle is loaded for the first time.

Check the stuff I listed under the Strange fix.

The very very first time you might get a stutter, or even right after a driver update, but once the shader cache is fully built, they should disappear.

I'm guessing you tried the obvious thing of turning effects down?

[I, Omor]

brought everything down to low, still stuttering for upwards of five seconds every time i start a match or select a new character.

[Roland's 2nd]

Originally posted by I, Omor:

brought everything down to low, still stuttering for upwards of five seconds every time i start a match or select a new character.

Well Characters specifically would be Models and Textures. Personally I have models on High and no issues on a 2060 Super with 16GB RAM

You have the game on an SSD right?
If so is it NVME or SATA?

And you have DLSS/FSR off?

And really, if you can list your entire system specs that might save some time here.

Edit:
Also some are reporting that simply clicking Optimize fixed things for them. Personally I'm skeptical as the "optimal settings" rarely get you the best fps, but I have seen a few games in the past where that is true.

[I, Omor]

models on high or low don't change anything, my SSD is a SATA, i have DLSS off, and optimal settings didn't change anything.

AMD Ryzen 7 5700X, 16 gigs of ram, RTX 3060, i'm above the minimum requirements and i've got better specs than some friends who i know have not had this issue.

[Roland's 2nd]

Originally posted by I, Omor:

models on high or low don't change anything, my SSD is a SATA, i have DLSS off, and optimal settings didn't change anything.

AMD Ryzen 7 5700X, 16 gigs of ram, RTX 3060, i'm above the minimum requirements and i've got better specs than some friends who i know have not had this issue.

Yea I mean you're not wrong, while the 3060 is weaker than the 2060 Super, you are well above a 1060 which is the minimum.

I'm wondering if the SATA SSD is to blame. Because some of what you describe sounds like my tests of running the game on a HDD except you didn't mention egregiously long loading times, and all of that stuff went away when I moved the game to my NVME SSD.

Do you happen to know the speeds of your drive?
And I'm guessing you don't have an NVME to try the game on?

[I, Omor]

checked the write time through command prompt, shows as 344 MB/s. and no, i do not have another SSD.

[Roland's 2nd]

Originally posted by I, Omor:

checked the write time through command prompt, shows as 344 MB/s. and no, i do not have another SSD.

uhh... which number is that?

You should have random read, sequential read, and sequential write.

To give you an idea of my numbers:

> Disk  Random 16.0 Read                       100.90 MB/s          7.1
> Disk  Sequential 64.0 Read                   2509.67 MB/s          9.1
> Disk  Sequential 64.0 Write                  3449.60 MB/s          9.3
> Average Read Time with Sequential Writes     0.025 ms          8.9
> Latency: 95th Percentile                     0.038 ms          8.9
> Latency: Maximum                             0.460 ms          8.9
> Average Read Time with Random Writes         0.025 ms          8.9

That's after running

 winsat disk -drive c

in a Powershell window Ran As Admin.

[I, Omor]

did that, here's what it gave

> Disk Random 16.0 Read 235.35 MB/s 7.9
> Disk Sequential 64.0 Read 433.98 MB/s 8.0
> Disk Sequential 64.0 Write 467.13 MB/s 8.1
> Average Read Time with Sequential Writes 0.169 ms 8.7
> Latency: 95th Percentile 0.669 ms 8.6
> Latency: Maximum 2.140 ms 8.8
> Average Read Time with Random Writes 0.179 ms 8.9

[Roland's 2nd]

Originally posted by I, Omor:

did that, here's what it gave

> Disk Random 16.0 Read 235.35 MB/s 7.9
> Disk Sequential 64.0 Read 433.98 MB/s 8.0
> Disk Sequential 64.0 Write 467.13 MB/s 8.1
> Average Read Time with Sequential Writes 0.169 ms 8.7
> Latency: 95th Percentile 0.669 ms 8.6
> Latency: Maximum 2.140 ms 8.8
> Average Read Time with Random Writes 0.179 ms 8.9

Well as I would have expected your drive is significantly slower than mine except for your Random Read

Unfortunately at this time I don't have other numbers to contrast it against. I'll keep an eye out and maybe do some digging later. In the meantime you could start a thread asking people what speeds they get when they run the command, especially if it won't load for them. (Note: if powershell isn't run as admin the results window insta closes)

I have a feeling the sequential read speed might be the key but we need more info

[I, Omor]

regardless, thanks for your help. hopefully i can get it working.