Home Trending Latest threads New posts Developer diaries

1861 scenario problem

Jump to latest Follow Reply
  • We have updated our Community Code of Conduct. Please read through the new rules for the forum that are an integral part of Paradox Interactive’s User Agreement.
U

unmerged(33958)

Sergeant
Sep 4, 2004
97
0
For some reason I cant get V:R to run the 1961 scenario so I can play the CSA.

All these errors pop up. I hit ignore on them. Then it lets me do all the set up on the csa, but when I un pause it, the game quits out.

Was there something I missed in the patch or something?

I could play the CSA in 1.04
 
Upvote 0
To play the 1861 scenario you should either install the Victoria 1.04 patch before Revolutions or rename the file scenarios\1861\France_Rhône_Alpes.csv to France_Rhone_Alpes.csv. If you have more errors than that one showing up when starting then you should reinstall.
 
Atilla1 said:
I repurchased the game from where you get the Revolutions.

I reinstalled, but I am getting the same errors again.

This is only for the 1861 scenario.
Click to expand...
Can you list the exact errors you are getting (at least the first few)?
 
I had this problem also. I think the reason was because I had not updated victoria to 1.04 before installing revolutions. I removed Victoria and Revolutions, reinstalled Victoria, updated to 1.04, installed Revolutions. Working fine now, but I have not yet installed the Revolutions patch.
 
I had this problem recently I installed revolutions on my laptop (it works fine on my regular computer) and the 1861 scenario kept getting that France_rhone error. I changed the Rhone like they said above and it works fine now. This should be addressed in a patch.
 
ComteDeMeighan said:
I had this problem recently I installed revolutions on my laptop (it works fine on my regular computer) and the 1861 scenario kept getting that France_rhone error. I changed the Rhone like they said above and it works fine now. This should be addressed in a patch.
Click to expand...
I'm sure it will be fixed in the next patch (and maybe even in OHGamer's hotfixes since it's not a .exe change).
 
You must log in or register to reply here.
Top Bottom
Back