If you use Intel HD integrated graphics, you may have noticed a couple things:
1. The terrain generates with chunks missing, and the sea filled with bands of terrain
2. You're below minimum requirements, so there's not an official fix on the horizon (that we know of)
For reference, the issue looks like this:
This is an issue where the game will place chunks in the wrong place. I don't know the exact mechanics behind why it's broken, but I do know it's reading the indirection heightmap wrong, and I've been messing around with the heightmap files to try to get it fixed.
Currently, I've managed to figure out a quick fix for sea zones (just use the same sea chunk for all of the oceans on the map) and I'm working on figuring out coasts, and then inland areas.
If any of ya'll have suggestions for how to go about continuing progress on this, or have any insights into what the root cause might be (and how to patch it), or if you just want to help document where the terrain is missing, and where those chunks ended up, so, if all else fails, it can be bruteforced into the right place, it's all appreciated.
If you just want a temporary fix right now, you can either disable the heightmap.heightmap file in steamapps\common\Crusader Kings III\game\map_data by renaming it to something like heightmap.heightmap.disabled, or edit it, and change tile size to 0. Keep in mind both of those changes will modify your checksum, and you should back up the file before messing with it. They also don't really fix the heightmap, they just disable it in different ways. Removing the file preserves oceans and borders, whereas tile size preserves land and borders, but not oceans.
1. The terrain generates with chunks missing, and the sea filled with bands of terrain
2. You're below minimum requirements, so there's not an official fix on the horizon (that we know of)
For reference, the issue looks like this:
This is an issue where the game will place chunks in the wrong place. I don't know the exact mechanics behind why it's broken, but I do know it's reading the indirection heightmap wrong, and I've been messing around with the heightmap files to try to get it fixed.
Currently, I've managed to figure out a quick fix for sea zones (just use the same sea chunk for all of the oceans on the map) and I'm working on figuring out coasts, and then inland areas.
If any of ya'll have suggestions for how to go about continuing progress on this, or have any insights into what the root cause might be (and how to patch it), or if you just want to help document where the terrain is missing, and where those chunks ended up, so, if all else fails, it can be bruteforced into the right place, it's all appreciated.
If you just want a temporary fix right now, you can either disable the heightmap.heightmap file in steamapps\common\Crusader Kings III\game\map_data by renaming it to something like heightmap.heightmap.disabled, or edit it, and change tile size to 0. Keep in mind both of those changes will modify your checksum, and you should back up the file before messing with it. They also don't really fix the heightmap, they just disable it in different ways. Removing the file preserves oceans and borders, whereas tile size preserves land and borders, but not oceans.