MEGATHREAD: A Collection of fixes for various issues.

[Roland]

Stuttering fix:

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

Escrito 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/

Escrito 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:

Escrito 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/

Escrito 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

Escrito 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/

Escrito 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.

Escrito 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.

[GGhost]

if anyone still gets stuttering after all other steps try this ini: https://www.nexusmods.com/marvelrivals/mods/24. It's the only thing that worked for me

[Roland]

Escrito originalmente por GoroMajima:

how petty of you.

Quite.
Not really sure what their problem is, but there's nothing meaningful they can do. And I have lots of tricks up my sleeve to keep this thread on the front page often; if I wasn't otherwise occupied, it would never leave the first 50 results.

Escrito originalmente por Star-Platinum-I7:

When I turned off EMP, I got less stturing, I got 4080s and i7 14k

Dear sir and or madam,

Please keep Electromagnetic Pulses away from your Computer!



(seriously though, what are you talking about when you say EMP?)

Escrito originalmente por GGhost:

if anyone still gets stuttering after all other steps try this ini: https://www.nexusmods.com/marvelrivals/mods/24. It's the only thing that worked for me

I saw "mods" and was like "OH ♥♥♥♥ that's a bad idea with an anti cheat" but then I click on it and it's just a stupid ini edit.

I hate when people post ini edits to Nexus. It's very literally "this could have been an email" but instead of email it could have been a Steam guide and you can just copy and paste.

Like if it helped you, that's cool, I just hate the distribution method and don't really count them as mods, since all you're doing is changing options and settings, nothing is actually added.

[BADER-REDAB]

GPU Crash dump Triggered

Marvel_Win64_Shipping
Marvel_Win64_Shipping
Marvel_Win64_Shipping
Marvel_Win64_Shipping
Marvel_Win64_Shipping
Marvel_Win64_Shipping
Marvel_Win64_Shipping
Marvel_Win64_Shipping
kernel32
ntdll

please help me

[LemonOwl]

yoo i solved this issue for a friend last weekend

We did a multiple of things. you can try some or all of them if they work:

- Enabling game through firewall (both public or private)
- running sfc /scannow and Dism.exe /online /Cleanup-Image /Restorehealth
- Switching off any external antivirus
- Running the game in windows 8 compatibility mode, and disabling full screen optimisations (I think this was the one which solved it)

[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.

[Roland]

Escrito originalmente por LemonOwl:

- Running the game in windows 8 compatibility mode, and disabling full screen optimisations (I think this was the one which solved it)

It's wild how often that randomly solves things. It's a thing where it's not always the solution, but if nothing else is working, it just might do the trick

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

Have you guys tried the Disable Fullscreen Optimizations option?

The description of your issue is tickling something deep in the forgotten memories that I can't quite place, but I know I've seen it before... (I refuse to admit i'm getting old) It'll probably come to me in like 3 days when I roll over trying to go back to sleep; as these sorts of things do

[mna99]

Escrito originalmente por Roland:

So I can no longer say I haven't had crashes in over 5 days.
I was cycling different heroes to chase achievements, and Scarlet Witch has crashed 2 out of 2 matches on me... :sotsad:

I've started a thread to ask around if anyone else is noticing such a phenomena.

Can you link that thread? I get crashes when Thor is in my screen or if I play as Thor. Any of his hammer attacks/moves that feature electrical charge effects on the hammer can trigger it. Which is a lot of them. The easiest way to trigger the CTD is to use his shift (hammer flight).

If someone else is playing him, I can survive for a little while if I just avoid looking at him. Obviously that is not always a workable solution.

Captain America can crash me if he uses the Thor teamup ability and attacks with it. He gets the same lightning effects on his shield/body that Thor has on his hammer. That also causes CTD. Cap on his own will not crash me.

I've had a few crashes on Klyntar but I think all of those were caused by Thor.

I have not tried the control flow guard trick yet. Everything is updated, on a 3900X w/ 16gig RAM and Radeon VII.

Also as an aside, please use caution when recommending that people turn on XMP or DOCP.

[Roland]

Escrito originalmente por mna99:

Escrito originalmente por Roland:

So I can no longer say I haven't had crashes in over 5 days.
I was cycling different heroes to chase achievements, and Scarlet Witch has crashed 2 out of 2 matches on me...

I've started a thread to ask around if anyone else is noticing such a phenomena.

Can you link that thread? I get crashes when Thor is in my screen or if I play as Thor. Any of his hammer attacks/moves that feature electrical charge effects on the hammer can trigger it. Which is a lot of them. The easiest way to trigger the CTD is to use his shift (hammer flight).

If someone else is playing him, I can survive for a little while if I just avoid looking at him. Obviously that is not always a workable solution.

Captain America can crash me if he uses the Thor teamup ability and attacks with it. He gets the same lightning effects on his shield/body that Thor has on his hammer. That also causes CTD. Cap on his own will not crash me.

I've had a few crashes on Klyntar but I think all of those were caused by Thor.

I have not tried the control flow guard trick yet. Everything is updated, on a 3900X w/ 16gig RAM and Radeon VII.

Also as an aside, please use caution when recommending that people turn on XMP or DOCP.

No one ever replied to it. I solved the Scarlet Witch crash by changing from TAAU to DLSS Native. (this is also why I crossed at the TAAU suggestion in my Strange fixes)

As for XMP/DOCP, if they are using the Default Profile, aka Profile 1, that usually ships with the setting, it will be fine.

[mna99]

XMP and DOCP can sometimes enable unsafe voltage settings, depending on the board/CPU. Enabling DOCP on certain AM5 motherboards with EXPO RAM kits used to raise vSoC to unsafe levels on Zen4X3D CPUs.

Since I have an AMD card, I can't use DLSS, but I had more luck with TAUU enabled than FSR native. FSR native lead to all kinds of crashes. With the one patch they've released and by tweaking other settings, I've got it down to just crashing on Thor (and Cap/Thor teamup).

[Roland]

Escrito originalmente por mna99:

XMP and DOCP can sometimes enable unsafe voltage settings, depending on the board/CPU. Enabling DOCP on certain AM5 motherboards with EXPO RAM kits used to raise vSoC to unsafe levels on Zen4X3D CPUs.

Since I have an AMD card, I can't use DLSS, but I had more luck with TAUU enabled than FSR native. FSR native lead to all kinds of crashes. With the one patch they've released and by tweaking other settings, I've got it down to just crashing on Thor (and Cap/Thor teamup).

That figures that there would be an X3D issue with DOCP... I've noticed a lot of people that have issue have X3D cpus. I'll keep that in mind in the future, but i must ask, when you say "unsafe" are you just talking unstable or are we talking actual risk of component damage?

I'ma be real, at this time the DLSS Native was my hail mary. I avoid DLSS and even FSR I try to only use Native if I must, so if i'm resorting to it, you know I'm at the end of my rope

You could maybe check that "mod" ini file one person shared. I thought about comparing it to mine to see if they actually changed anything meaningful but I suspect it would be a waste of time; I know there's certain settings that you can try to change all you want and the engine will either change them back, or will ignore them entirely. But maybe it changes certain settings related to effects or particles that actually does something, idk.

[Pizza Roll]

Escrito originalmente por 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 😭

[mna99]

Escrito originalmente por Roland:

That figures that there would be an X3D issue with DOCP... I've noticed a lot of people that have issue have X3D cpus. I'll keep that in mind in the future, but i must ask, when you say "unsafe" are you just talking unstable or are we talking actual risk of component damage?

For a brief time, people were damaging their CPUs. AMD issued replacements and released microcode updates that mobo OEMs integrated into their UEFI updates to solve the problem. Actual damage doesn't occur anymore (thankfully), but it is a cautionary tale regarding people tweaking UEFI/BIOS settings without understanding everything that's going on under the hood.

I'ma be real, at this time the DLSS Native was my hail mary. I avoid DLSS and even FSR I try to only use Native if I must, so if i'm resorting to it, you know I'm at the end of my rope :p4g_sweat:

Same, I'm not a fan of upscalars.

You could maybe check that "mod" ini file one person shared. I thought about comparing it to mine to see if they actually changed anything meaningful but I suspect it would be a waste of time; I know there's certain settings that you can try to change all you want and the engine will either change them back, or will ignore them entirely. But maybe it changes certain settings related to effects or particles that actually does something, idk.

I'll have to look into it.

[roal]

Escrito originalmente por Roland:

Stuttering fix:

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

Escrito 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/

Escrito 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:

Escrito 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/

Escrito 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

Escrito 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/

Escrito 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.

Escrito 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.

What if I can't find the marvel folder in \appdata\local\. it just isn't there...

[xander !]

Escrito originalmente por gay and loud:

I'm literally crashing on 2 maps ALL the time, no matter the fixes
these are burning T'Challa and Yggsard (each of these maps has 2 variants, and one of them is fine but the other is not. i.e i can play royal palace for Yggsard but can't play the other version)

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.

[xander !]

Escrito originalmente por xander !:

Escrito originalmente por gay and loud:

I'm literally crashing on 2 maps ALL the time, no matter the fixes
these are burning T'Challa and Yggsard (each of these maps has 2 variants, and one of them is fine but the other is not. i.e i can play royal palace for Yggsard but can't play the other version)

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