MEGATHREAD: A Collection of fixes for various issues.

[Roland]

Stuttering fix:

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

Publicado originalmente por 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/

Publicado originalmente por 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:

Publicado originalmente por 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/

Publicado originalmente por 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

Publicado originalmente por 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/

Publicado originalmente por 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.

Publicado originalmente por 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]

[PixelCorvid]

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)
Hopefully people see these threads. I'd hate to imagine not knowing and being frustrated and unable to play the game entirely.

[Roland]

Publicado originalmente por 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)
Hopefully people see these threads. I'd hate to imagine not knowing and being frustrated and unable to play the game entirely. :meadowfrog: :meadowfrog:

Oh yea! I forgot to include that, thank you , I'll add it to OP. My bad homie

[Орущий Снайпер]

is there a fix to freezing in loading screen on 0% and the music turn off and pc barely operates?

[A man with alot of air]

Unknown Error. Error code 220

[Plagues]

My only issue is that I had 120+ fps on thurs/Fri.... All high, dlss off, no frame Gen.... And since yesterday it's stuck at like 50gps without dlss/frame Gen.. And even thoughts it's over 100.it feels like ♥♥♥♥

[Anankninan Skylkwaker]

Unknown Error Code 220.

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

[Roland]

Publicado originalmente por Орущий Снайпер:

is there a fix to freezing in loading screen on 0% and the music turn off and pc barely operates?

I would need a lot more information to start with, such as your system specs, including what version of Windows you are on.

Publicado originalmente por Big Begger:

Unknown Error. Error code 220

Well that's a new one... When are you seeing this error?
I've seen no mention of this anywhere so far but I can see what I can find

Publicado originalmente por Plagues:

My only issue is that I had 120+ fps on thurs/Fri.... All high, dlss off, no frame Gen.... And since yesterday it's stuck at like 50gps without dlss/frame Gen.. And even thoughts it's over 100.it feels like ♥♥♥♥

You can try the SSGI and Post Processing stuff.

Post Processing is usually things like motion blur, depth of field, lens flares, stuff like that. Often in games if those options don't have their own setting you can get they are controlled by the Post Processing setting; not every time mind you, but often.

Eventually I'm going to do side by side comparisons of the global illumination because I suspect the differences aren't worth the performance impact, especially with the art style of the game, but for the time being I will continue to recommend slapping that ♥♥♥♥♥ on Low for the performance gains

[Roland]

Publicado originalmente por 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

[CaptainBasculin]

Linux specific fix:

If you see black screens for cutscenes while using Proton, use ProtonGE latest version

[Roland]

Publicado originalmente por CaptainBasculin:

Linux specific fix:

If you see black screens for cutscenes while using Proton, use ProtonGE latest version

Would you mind adding a step-by-step for that so I can add it to the post?
(I don't have Linux or a Steam deck to test it on)

[Well Butter my Biscuit]

What about being stuck at 99% on the loading screen and getting a punishment for leaving match?

[YeehawSpice]

Publicado originalmente por Well Butter my Biscuit:

What about being stuck at 99% on the loading screen and getting a punishment for leaving match?

The CM James on the Rivals Discord popped into one of the threads and said the dev team is aware of the bug.

"Hey guys! Just wanted to let you know that the team is aware of the issue and has found the bug that's causing it. We're working on a solution and making sure thing gets patched up properly. Thanks for your patience while we sort this out! Hotfixes will be coming your way very soon. We're on it!"

Hopefully we'll get a hotfix this week.

[Roland's 2nd]

Notice:

My main account got banned for telling users how to report content that was not appropriate for children.

"This post contains content used to insult, harass, or abuse other Steam users. This type of content is not allowed on the Steam Community."

Presumably the user who posted the content reported me for harassment.

Because of this I won't be able to update the main post for possibly 3 days, maybe up to 9 weeks. I've reached out to support to take a closer look at the situation and requested they remove the ban, because I was simply explaining how to report and not encouraging harassment.

In the meantime I will do the best I can to continue to help those of you that I can, and any new fixes reported or suggested will be added to the main post once this ban mess is over.

Sorry for any inconvenience

[PixelCorvid]

Publicado originalmente por Roland's 2nd:

Notice:

My main account got banned for telling users how to report content that was not appropriate for children.

Dude what. That's so dumb.
Hopefully it's resolved soon!
(also we're 3 days out and no fixes or updates to the game yet, I'm screeching rn)