Blockland Forums > Modification Help
"Should never be considering a brick bigger than us here!" -Solved
Kalphiter:
Depends if it's read in as a string or not, considering the error, it probably does.
Jardev:
--- Quote from: Kalphiter on February 20, 2012, 11:01:17 PM ---Depends if it's read in as a string or not, considering the error, it probably does.
--- End quote ---
I clamped those z values to 4 decimal places, but to no avail. I'm now getting the error on the first try.
--- Code: ---brick4xCubeData TAB -23.5963 78.2299 0.0102 TAB 6
brick4xCubeData TAB -21.5963 78.2299 0.0102 TAB 6
brick4xCubeData TAB -19.5963 78.2299 0.0102 TAB 6
brick4xCubeData TAB -17.5963 78.2299 0.0102 TAB 6
brick4xCubeData TAB -15.5963 78.2299 0.0102 TAB 6
brick4xCubeData TAB -13.5963 78.2299 1.0102 TAB 6
brick4xCubeData TAB -11.5963 78.2299 0.0102 TAB 6
brick4xCubeData TAB -9.5963 78.2299 0.0102 TAB 6
brick4xCubeData TAB -7.5963 78.2299 2.0102 TAB 6
brick4xCubeData TAB -5.5963 78.2299 2.0102 TAB 6
brick4xCubeData TAB -3.5963 78.2299 1.0102 TAB 6
brick4xCubeData TAB -1.5963 78.2299 1.0102 TAB 6
brick4xCubeData TAB 0.4037 78.2299 2.0102 TAB 6
brick4xCubeData TAB 2.4037 78.2299 2.0102 TAB 6
brick4xCubeData TAB 4.4037 78.2299 1.0102 TAB 6
brick4xCubeData TAB 6.4037 78.2299 2.0102 TAB 6
brick4xCubeData TAB 8.4037 78.2299 2.0102 TAB 6
brick4xCubeData TAB 10.4037 78.2299 3.0102 TAB 6
brick4xCubeData TAB 12.4037 78.2299 1.0102 TAB 6
brick4xCubeData TAB 14.4037 78.2299 1.0102 TAB 6
brick4xCubeData TAB 16.4037 78.2299 3.0102 TAB 6
brick4xCubeData TAB 18.4037 78.2299 4.0102 TAB 6
brick4xCubeData TAB 20.4037 78.2299 2.0102 TAB 6
brick4xCubeData TAB 22.4037 78.2299 2.0102 TAB 6
brick4xCubeData TAB 24.4037 78.2299 5.0102 TAB 6
brick4xCubeData TAB 26.4037 78.2299 5.0102 TAB 6
brick4xCubeData TAB 28.4037 78.2299 3.0102 TAB 6
brick4xCubeData TAB 30.4037 78.2299 4.0102 TAB 6
--- End code ---
If the error is reading a string, how do I prevent that? Possibly break up the 3 word position into each word, then piece it back together for the field in the created brick?
Kalphiter:
Are those even valid positions?
Jardev:
--- Quote from: Kalphiter on February 20, 2012, 11:19:14 PM ---Are those even valid positions?
--- End quote ---
I'm currently under the impression that creating a brick at the position "-23.5963 78.2299 0.0102" would actually create it at something like (just an example): "-23.5 78 0". I could be totally wrong, but I thought that was how brick creation worked.
I'm not sure if this helps, but in the console, it gives the following before crashing:
--- Code: ---buildString called
octTree::insertBrick - maxed out re-rooting tree!
octTree::insertBrick - octTree is probably busted now!
octTree::insertBrick - this is really bad!
octTree::insertBrick - maxed out re-rooting tree!
octTree::insertBrick - octTree is probably busted now!
octTree::insertBrick - this is really bad!
octTree::insertBrick - maxed out re-rooting tree!
octTree::insertBrick - octTree is probably busted now!
octTree::insertBrick - this is really bad!
octTree::insertBrick - maxed out re-rooting tree!
octTree::insertBrick - octTree is probably busted now!
octTree::insertBrick - this is really bad!
octTree::insertBrick - maxed out re-rooting tree!
octTree::insertBrick - octTree is probably busted now!
octTree::insertBrick - this is really bad!
octTree::insertBrick - maxed out re-rooting tree!
octTree::insertBrick - octTree is probably busted now!
octTree::insertBrick - this is really bad!
Fatal-ISV: (/Users/erichartman/dev/Blockland/trunk/premake/BlocklandGame/../../engine/bricks/octNode.cpp @ 130) octNode::r_insertBrick - should never be considering a brick bigger than us here!
--- End code ---
(It crashes instantly, this is just pulled from console.log)
Greek2me:
Maybe you're simply creating bricks too quickly?