I imagine/hope it will be altered at a later date after testing, so as to work out how best to get the geography right?
Wouldn't bet the house on it.
I imagine/hope it will be altered at a later date after testing, so as to work out how best to get the geography right?
I imagine/hope it will be altered at a later date after testing, so as to work out how best to get the geography right?
Because it changes the Max RGO size, reducing the productive value of these provinces.
cant you model the map with mountains but not define the region as mountanous?
Part of the issue here is of course province size. Unlike in HoI3 where the sheer number of provinces makes it much easier to model differing geographies in a region, the much larger provinces of Victoria make it difficult to capture things like flat valley land right around Aosta or Grenoble (surrounded by mountains to be sure, but the cities themselves are not mountainous) or the division of Turin between mountainous regions west of the city and the flat plains of the Po Valley heading eastward towards Lombardy.
Just as an example, in Clio for Victoria (which is what the V2 map is based on) Aosta is a single province, but in the HoI3 Clio's Iron Heart, the same area is occupied by IIRC three provinces. Since Clausewitz IIRC can only assign one terrain to a province for purposes of determining things such as battle bonuses/maluses (and as King said, impact on RGO production in V2), you thus get stuck in a conundrum as what is the best terrain to represent an entire region at the scale of Victoria's provinces. In those cases, sometimes it is necessary to look at what is best for gameplay when making those decisions.
And of course those who disagree with Paradox' decision on how to model this region or any other region of the world can simply tweak the appropriate map files to better reflect how they see the geography should be. Unlike V1 and other older games, map modding in the Clausewitz engine is a much easier process that anyone with a basic knowledge of graphical editors (Paint, Photoshop etc) can do.
Part of the issue here is of course province size. Unlike in HoI3 where the sheer number of provinces makes it much easier to model differing geographies in a region...
Given that V2 also uses Clausewitz, surely the obvious solution is to add more provinces to the region?Just as an example, in Clio for Victoria (which is what the V2 map is based on) Aosta is a single province, but in the HoI3 Clio's Iron Heart, the same area is occupied by IIRC three provinces. Since Clausewitz IIRC can only assign one terrain to a province for purposes of determining things such as battle bonuses/maluses (and as King said, impact on RGO production in V2), you thus get stuck in a conundrum as what is the best terrain to represent an entire region at the scale of Victoria's provinces. In those cases, sometimes it is necessary to look at what is best for gameplay when making those decisions
I'm sure its very easy to mod this game but I think its safe to say that most people would prefer to see an error like this fixed before releaseAnd of course those who disagree with Paradox' decision on how to model this region or any other region of the world can simply tweak the appropriate map files to better reflect how they see the geography should be. Unlike V1 and other older games, map modding in the Clausewitz engine is a much easier process that anyone with a basic knowledge of graphical editors (Paint, Photoshop etc) can do.
Just as an example, in Clio for Victoria (which is what the V2 map is based on) Aosta is a single province, but in the HoI3 Clio's Iron Heart, the same area is occupied by IIRC three provinces. Since Clausewitz IIRC can only assign one terrain to a province for purposes of determining things such as battle bonuses/maluses (and as King said, impact on RGO production in V2), you thus get stuck in a conundrum as what is the best terrain to represent an entire region at the scale of Victoria's provinces. In those cases, sometimes it is necessary to look at what is best for gameplay when making those decisions.
I'm sure its very easy to mod this game but I think its safe to say that most people would prefer to see an error like this fixed before release
cant you model the map with mountains but not define the region as mountanous?
Now THAT would be confusing.
@King:
OK, I can understand that. For me it is still one more reason to make the map as acurate as possible from the very beginning, but I never made any games.
True 'dat. Paradox don't make mistakes, just design decisionsExcept that it is not an error, it is a delibrate design intent for balancing purposes.