Problem with clean install and build of latest CSK
by TheMartian · in Combat Starter Kit · 11/05/2008 (8:32 pm) · 5 replies
So I install and compile the latest drop of CSK (whatever is there as of today nov 5th 2008).
It compiles just fine but when you go to launch it into the test missions it stops on this assert
void TSIntegerSet::setAll(S32 upto)
{
AssertFatal(upto<=MAX_TS_SET_SIZE,"TSIntegerSet::setAll: out of range");
dMemset(bits,0xFFFFFFFF,(upto>>5)*4);
if (upto&31)
bits[upto>>5] |= SETUPTO(upto);
}
This is in the file tsIntegerSet.cc
MAX_TS_SET_SIZE is defined as
#if defined(TORQUE_LIB)
#define MAX_TS_SET_DWORDS 32
#else
#define MAX_TS_SET_DWORDS 6
#endif
#define MAX_TS_SET_SIZE (32*MAX_TS_SET_DWORDS)
This is taken from tsIntegerSet.h
setAll receives a value of 196 while loading what looks like a vehicle.
The exe that came with the installer appears to work and not have this problem only if you compile it yourself.
I am using the solution file from the VS2005 directory and this is a clean (its own directory) install from your provided CSK installer. No changes, no mods, no patches, just load up, compile, start with starter.combat and boom.
Only happens in debug builds most likely because the asset macro is removed in release builds.
It might not be significant, increasing the value from like 6 to 8 fixes it but im not sure what ramifications that might have just yet.
you guys have a reliable solution for this?
It compiles just fine but when you go to launch it into the test missions it stops on this assert
void TSIntegerSet::setAll(S32 upto)
{
AssertFatal(upto<=MAX_TS_SET_SIZE,"TSIntegerSet::setAll: out of range");
dMemset(bits,0xFFFFFFFF,(upto>>5)*4);
if (upto&31)
bits[upto>>5] |= SETUPTO(upto);
}
This is in the file tsIntegerSet.cc
MAX_TS_SET_SIZE is defined as
#if defined(TORQUE_LIB)
#define MAX_TS_SET_DWORDS 32
#else
#define MAX_TS_SET_DWORDS 6
#endif
#define MAX_TS_SET_SIZE (32*MAX_TS_SET_DWORDS)
This is taken from tsIntegerSet.h
setAll receives a value of 196 while loading what looks like a vehicle.
The exe that came with the installer appears to work and not have this problem only if you compile it yourself.
I am using the solution file from the VS2005 directory and this is a clean (its own directory) install from your provided CSK installer. No changes, no mods, no patches, just load up, compile, start with starter.combat and boom.
Only happens in debug builds most likely because the asset macro is removed in release builds.
It might not be significant, increasing the value from like 6 to 8 fixes it but im not sure what ramifications that might have just yet.
you guys have a reliable solution for this?
#2
12/03/2008 (8:38 am)
Hiya, I couldn't reproduce that error. I compiled CSK on both 2009 and 2005 right out of the box and run the misssions. Soon as I can find an answer I will be back with you.
#3
12/03/2008 (1:03 pm)
From my testing it only does in in debug builds since it is macro'd out in release builds. 
#4
12/03/2008 (1:36 pm)
I have also seen this happen in debug, it's something that just needs to be bumped up, some of the shapes are extremely complex (like the ground assault carrier). There isn't any other ramification outside of a warning however, for a ridiculously large (complexity-wise) shape that might otherwise slow things down and leave you scratching your head wondering why your framerates are low.
#5
http://www.garagegames.com/community/forums/viewthread/46941
Searching for MAX_TS_SET_DWORDS will reveal a few more results which you might find useful.
What concerns me more is that this came from a vanilla installation of the CSK and affects the Debug config. Breaking the build and that particular config is a BIG faux pas! I could speculate further on the exact source of the problem but that would probably make me seem like even more of a cranky axe-grinder... which I am in case you were wondering. :-)
01/15/2009 (3:08 pm)
I encountered the same bug and likewise bumped up MAX_TS_SET_DWORDS to 7 to work around the problem (with VS 2008). According to the forum post below the only consequence of making that change is increased memory consumption which isn't horrible unless you're working with a console.http://www.garagegames.com/community/forums/viewthread/46941
Searching for MAX_TS_SET_DWORDS will reveal a few more results which you might find useful.
What concerns me more is that this came from a vanilla installation of the CSK and affects the Debug config. Breaking the build and that particular config is a BIG faux pas! I could speculate further on the exact source of the problem but that would probably make me seem like even more of a cranky axe-grinder... which I am in case you were wondering. :-)
Torque Owner TheMartian
Conundrum Studios