Hmm...
I have a Daily DB install & a DB Comics(&FCD) install as well.
No problems here.
Though it has to be said that they share the My Docs folder & (therefore) local .cdb, so you should start there Edited by Jesleyh on 24-01-2014 13:29
Jesleyh wrote:
Hmm...
I have a Daily DB install & a DB Comics(&FCD) install as well.
No problems here.
Though it has to be said that they share the My Docs folder & (therefore) local .cdb, so you should start there
I have only one db installed and the issue appeared anyway. It worked fine for a couple of months btw and then suddenly happened for a few races. It's a true pain in the a**, the only thing i can imagine is the local.cdb, which i edited once. Not sure though, if i did that before the issue appeared. I will try the way of creating a new race in dyn_race, using the same constant and name as for the race where the problem appeared.
@TMM
Try swapping the local.cdbs once. You probably have a DB Comics(= FCD) local still in use, instead of the PCMdaily.
Might cause the problems. PCMdaily one should be the backup one in My docs/PCM 2013.
The double installs were cross communicating with each other, via the shared My Documents folders. Basically they overwrote each other when making a problem with the local.cdb (two existing together, weird as fuck).
Anyway cleared that all up and created an extra separation between the two installs (one on C: and one on D: drive). So far i cannot create the startlist problem which gives me hope i've fully fixed the problem.
baseballlover312, 06-03-14 : "Nuke Moscow...Don't worry Russia, we've got plenty of love to go around your cities"
Sarah Palin, 08-03-14 (CPAC, on Russian aggression) : "The only thing that stops a bad guy with a nuke is a good guy with a nuke"
Big thanks to jdog for making this AMAZING userbar!
@Jesl - Not really sure... It wasn't a "~" variation. Just kind of strange. I think that one install would boot with a local.cdb as normal but that the local.cdb was not the right one. The other would also boot with a different local.cdb, or at least the fuck up broke the local.cdb in some way. I would say it was corrupted like a "~" variation, just without specifically saying so in the file name.
Found the Daily local.cdb on the site, gave it a quick dl and now things are running smoothly.
TheManxMissile wrote:
I would say it was corrupted like a "~" variation, just without specifically saying so in the file name.
A ".cdb~" isn't a corrupted file, just an automatic backup. Not sure if that's what you meant though
Anyway, this all seems really weird to me. The double installations can't be "communicating" at the same time, since the game only updates the My Docs folder when you run it (for example, if you delete the My Docs folder it'll only be recreated when you open the game again). So if you for example didn't open the Comics .exe for a week and only opened the Daily one, or vice-versa, there shouldn't be compatibility trouble in the Local.cdb. Likewise, I'm not sure again if this is what you meant, but I don't think any DB installation can make the game change the Local.cdb if it isn't the compatible one for that DB. All the game will do is check whether the Local.cdb is compatible with the current patch, and if it isn't it'll replace for the original Local. Since both DBs have Local.cdbs compatible to the latest patch I also don't think that would be the problem.
But well, whatever reason it is, it's good to know it's working, that's what matters after all
@lluuiiggii
Thought ~ meant corrupted based of past experiences.
Equally my explanation was crap cause i look at it and my mind melts. Something in the local.cdb was wrong and i don't know what caused it. My assumption is the double install where an FCD based db is against a Daily based DB incorrectly overwrites the local.cdb
But yes, and hopefully for more than a few months this time
