1) This is unrelated to what we are talking about.Yeah, the new update didn't come over clean. Even down to dynamicnames_england has a red mark.
2) Did you manually edit this file?
1) This is unrelated to what we are talking about.Yeah, the new update didn't come over clean. Even down to dynamicnames_england has a red mark.
Had a different idea that might work if you don't mind trying. What happens if you open the RFC_3000BC.txt file with Notepad++, use Edit -> EOL conversion -> Windows, and then try to load the 3000 BC scenario?That's no bueno either, with the MapParser.py change or not. Is the problem exclusive to the Steam version?
3000BC file was already in Windows format. I tried it for the 600AD one but it made no difference, still just closes the game.Had a different idea that might work if you don't mind trying. What happens if you open the RFC_3000BC.txt file with Notepad++, use Edit -> EOL conversion -> Windows, and then try to load the 3000 BC scenario?
I'm on Windows 11 and playing the Steam version of Civ4 (rolled back to a prior version which was recommended somewhere here on the DoC forums).
Me too.I did it by downloading as a zip
Yes, it seems that something goes wrong with the files when downloaded as a zip for one reason or another. It works after pulling with TortoiseGit.Interesting. I will see what happens when I do this on my end.
If you're open to it, you can try the git client. This one is pretty easy to install on windows: https://git-scm.com/download/win