Menu
Rising Storm 2: Vietnam
  • Action
  • Massively Multiplayer
  • Simulation
  • Strategy

Game

Rising Storm 2: Vietnam

Rising Storm 2: Vietnam is a sequel to the stand-alone expansion pack to Rising Storm and focuses on the Vietnam War.

Red Orchestra Series' take on Vietnam: 64-player MP matches; 20+ maps; US Army & Marines, PAVN/NVA, NLF/VC; Australians and ARVN forces; 50+ weapons; 4 flyable helicopters; mines, traps and tunnels; Brutal. Authentic. Gritty. Character customization. And napalm in the morning.

Rising Storm 2: Vietnam screenshot 1 of 81 / 8

About Rising Storm 2: Vietnam

Released
May 2017
Developers
Antimatter Games, Tripwire Interactive
Engine
Unreal Engine 3
Platforms
PC (Microsoft Windows)

Where to get it

Release, studio and platform data from IGDB. Store links go to the sellers, not to us. We do not sell games and we do not host files.

Browse everything

Sorted, filterable and paged. Every link goes to the author’s own download.

From the developers

Official announcements, newest first. Posted on Steam.

Mods indexed
440
Versions
0
Newest tracked
none yet
Most disruptive update
No breakage data for this game

Most downloaded

Measured from the source's own counts, summed across every release.

Browse all 440 Rising Storm 2: Vietnam mods Sortable by downloads, rating and date.

More massively multiplayer games see all

Why Rising Storm 2: Vietnam mods break

A mod is compiled against one version of a game. When the game updates, anything that reached into the parts that moved stops working, and it usually stops working silently rather than with a message that explains itself.

That is what the table above counts. It is not a guess: each row is a mod the community has reported as broken by that specific release. The number is a fair measure of how disruptive an update was, and it is the reason people delay updating a game they have modded heavily.

Common questions

Does IndexGG host Rising Storm 2: Vietnam mods?

No, and it never will. Every download link points at the author's own page on Nexus, GitHub, CurseForge or wherever they published it. We index the ecosystem; the files stay with the people who made them.

Where does the compatibility data come from?

From the communities that maintain it in the open, not from guesswork. Each claim carries how it is known, so a reported breakage is never presented as though the author said it.

Why is a mod listed as broken when it works for me?

Compatibility depends on your exact game version and the rest of your load order. A mod marked as broken in one release may work fine on an older one, which is exactly why the version is recorded next to the claim rather than a bare yes or no.