Bug Reports and Technical Issues

If you check the tile, it's not actually coast or ocean, but one of the mod's special terrain types. I can't remember off the top of my head, but it'll be a lagoon or atoll or something. Venice and New Orleans are on similar tiles.
 
This isn't the first time I've seen this but finally got to including a save. One of the French TC Conq stacks spawns in Korea/Manchuria (139/59). Intended target was Kanchipuram. Note: if anything looks odd or surprising this game was experimental so lots of WB stunts occurred.
The units are already there, so not much of a chance to find out what put them there.
 
The units are already there, so not much of a chance to find out what put them there.
Isn't that a consequence of the TC stacks spawning in a location that isn't accessable from lack of access from No Open borders or war status. I've had more than one Indian TC fail when stacks teleport to the hinterland of TIbet.
 
Caravels *seem* to lock onto a path that follows Antarctica after passing Cape Horn, at least until reaching Australia/New Zealand. The Spanish caravel now located in the Moluccas was the first to do this. Squadron of Carracks hugging South America also conspicuous. Conclusions are to be treated as provisional until more samples are collected of course.
1737251608123.jpeg


EDIT: Few turns later.
1737251763672.jpeg
 

Attachments

Last edited:
Isn't that a consequence of the TC stacks spawning in a location that isn't accessable from lack of access from No Open borders or war status. I've had more than one Indian TC fail when stacks teleport to the hinterland of TIbet.
That's good to know, but I would still like to have a save before the conquerors are triggered so I can debug the spawn instead of just guessing the reason.
 
Fresh install of the dev branch is throwing python exceptions anytime I attempt to launch a map. Tried spawning in as Harappans in 3000 BC and ended up on a map that was definitely not the DoC map with 1 turn research and build times, plus more error codes than I could count. Similar happened when spawning as China on 600 AD. Trying to spawn as any post-start civ causes a CTD.

Potentially relevant: I'm running the GoG version on Linux. I've had more or less perfect stability with Civ4, including the 1.17 release of DoC, up to this point.

Edit:
1. Noticed that all the vanilla map types appear in the play menu, not just DoC. I haven't tried launching any of them but I don't remember those being in 1.17 so it's possible that's indicative of whatever issue I'm facing.
2. Grabbed a screenshot, this is from attempting a 3000 BC start as Egypt
 

Attachments

  • Screenshot from 2025-01-19 13-50-00.png
    Screenshot from 2025-01-19 13-50-00.png
    2.9 MB · Views: 775
Last edited:
I never tested file path resolution in Linux, that might be the issue.
 
I never have gotten Civ4 running on Linux, so I have no way of testing it. The relevant code should be in Files.csv, I would guess it is either in os.cwd() or the path concatenation. In case you want to try your hand at a fix.
 
In a very unexpected turn of events, I have found a fix. I changed the name of the mod folder to "RFC Dawn of Civilization" from simply "Dawn of Civilization" which I had before. My map has loaded normally and everything appears to be functioning. I'm not sure if this is just a noob mistake that I forgot I could make or if this is an OS specific issue.
 
Oh, yes. That is definitely needed, the installation guide mentions it. Actually, I am surprised that it got as far as it did.
 
It's not the first time as India that I see the game crash when I load a save. Here two exemples.
Which version / commit of the game were these saves created with?
 
Which version / commit of the game were these saves created with?
The update from saturday. One more thing is that initially it didn’t crash because of loading the save but simply because I clicked on something at the begining of a turn (a unit, a new tech to research, a city…) and then when I wanted to reload a save corresponding to this turn or a turn just before, it automatically crash.
 
Interesting. Do you have an earlier save that you are able to load?
 
Interesting. Do you have an earlier save that you are able to load?
Yes. If I reload 2 turns before the problem it works perfectly fine and the crash doesn't happen anymore even when I reach the initial problematic situation. Here the save in 220 which works fine.

Currently I'm in 1000 AD and I didn't get the problem more since 240 AD.
 

Attachments

Back
Top Bottom