15 replies to this topic

[The Imp]

I just finished installing the "Standard" suite of BiG World Setup mods and tried to start BG2.

Did you customize the install at all ? Or did you try the Standard out of the box thinking the standard package is actually normal ?
And the ASSERTION FAILED! ... ChDimm.cpp Line: 834 sounds familiar ... but I'll leave the interpretation of the google's search links for you. Hmm, like say does your games directory you start the game from(via the BGMain.exe) contain the file baldur.ini that has this example structure: The example game is installed into: D:\Games\BGII - SoA\

[Alias]
HD0:=D:\Games\BGII - SoA\
CD1:=D:\Games\BGII - SoA\CD1\
CD2:=D:\Games\BGII - SoA\CD2\
CD3:=D:\Games\BGII - SoA\CD3\
CD4:=D:\Games\BGII - SoA\CD4\
CD5:=D:\Games\BGII - SoA\CD5\

You probably need to actually reinstall if the games start fail because of this because the BWS install will produce bunch of bad grapes to non intended location, and if the operation systems security is involves, the game will start as if it did have anything installed on the game. But you should have checked the game that it works before you go an install mods to it.

Edited by The Imp, 15 March 2014 - 01:05 AM.

[The Imp]

Did you customize the install at all ?

I did not customize the install, as there were no options to customize.

There is, right after selecting the Compilation option of Standard, you push the "..." button right next to it. It will open the interface to fully customize the m´mods and components.... in a very large window.

Edited by The Imp, 16 March 2014 - 02:05 AM.

[The Imp]

So I checked out the stuff behind the "..." button, but while I can select mods, I can't actually select components. They all say "BATCH: Components are not displayed while using batch-installations".

Either you aren't using the latest BWS... but like a 9 months old, or.actually you need to go back a step to the main window and select the "BWS: BiG World Project (detailed customization)" option instead of the "BiG World Install.bat(fixed and well-tried)" ... so this:

Edited by The Imp, 17 March 2014 - 02:59 PM.

[The Imp]

Why doesn't this program start up at the main window in the first place?

I suspect that the program saves the included info on every step and thus it starts in a different spot if you quit it there... it's actually good for it's usability in the long run, when you take it into account. Especially on my case, haven't made a full install say in two years, but made a few checks every now and then and so...

Yeah, that was the issue. Thanks for all the help.

Glad to be of service.

Edited by The Imp, 17 March 2014 - 03:50 PM.

[Ithildur]

And the ASSERTION FAILED! ... ChDimm.cpp Line: 834 sounds familiar

Yeah; as it turns out, somewhere between my installing BG2, verifying the installation (i.e. playing it), and installing BWP Standard via BWS, my baldur.ini got replaced with a default file. Adding in the CD location lines fixed the issue, and the game plays fine (or at least fine enough that I can't tell the difference).

 

 

This just happened to me as well; somewhere along the way baldur.ini got swapped out, causing the exact same assertion failed issue. Sounds like a known issue; is there a cure? It's a relatively easy fix for those in the know about multiple game directories/baldur.ini files, but for new folks I would recommend not using the BWS feature (a nice one at that) to clone the game directory, and instead install into the default SoA directory; I'd imagine for a newcomer it'd be a nightmarish frustrating experience to spend hours installing (even with BWS) only to run into this error.

[The Imp]

Well, if you can eliminate the human component of this error coming up, we'll be easily able to fix what ever makes the mistake, but we need to know what it actually is.
Yeah, the BWS messes up the install if you switch between the install methods. And don't restart the process. Aka the program, and reinsert the correct game path, as it might need to be changed.

Edited by The Imp, 14 January 2016 - 04:21 AM.

[agb1]

I think we can probably add a check in BWS for these lines in baldur.ini matching the game folder path used for the install.

[The Imp]

The thing is, the BWS also installs or installed this. I could see that as the cause of the error if it's installed to a messed BWS game location path, that doesn't hold true anymore after the install method was changed.

Or if the game is a manual copy in a random directory that's not the one in the baldur.ini . But that's not the method that is said in the FAQ, as I intentionally say that YOU HAVE GOT TO change the directory location.

Edited by The Imp, 14 January 2016 - 04:39 AM.

[agb1]

News to me. Will look into it - thanks.

[agb1]

The thing is, the BWS also installs or installed this. I could see that as the cause of the error if it's installed to a messed BWS game location path, that doesn't hold true anymore after the install method was changed.

Or if the game is a manual copy in a random directory that's not the one in the baldur.ini . But that's not the method that is said in the FAQ, as I intentionally say that YOU HAVE GOT TO change the directory location.

I did a global search in BWS for "infinitylauncher" (not case sensitive) and found no matches. Doesn't look like BWS currently installs that. I don't know if it did in the past.

[Crimpson]

most launch  problems come from when the directory changes. ie. backing up and the drive letter changes, or you move the main folder. check the directories in baulder.ini