Author Topic: Blockland keeps crashing when reaching the brick limit  (Read 2258 times)

I am not sure if this is just me but this is my second error I have encountered since V21 when trying to get to the brick limit, the first time I did it the game did not crash, however whenever I loaded the Pyramid build, instead of it only loading the bricks it can and give me the Brick Limit number it just crashed.



Can the brick limit be raised in the future? How does it work, is it a formula? Does Badspot just update memory usage or something??

With V21 this is a big issue, Badspot really needs to raise the limit.

With V21 this is a big issue, Badspot really needs to raise the limit.
Thats not really what I am concerned with, I am just concerned at the fact the game crashed on me twice just to reach the limit, I wanted to see how long it would take for all of the bricks to ghost at once but it keeps crashing

this is how I get it: (FACTS MAY OR MAY NOT BE TRUE IDK)
It's not about any of that junk, it's actually about the Octree. The octree is what makes the game run smooth, and it's max is probably 256,000. It's not about the graphics but how the bricks are stored. So unless you want to change the several thousand (100,000) lines of code just for the god damn Octree, I'd grow some balls and start being brick friendly. You can't have unlimited bricks you know.

Its an actual-sized recreation of the bedroom with default bricks.
theres no possible
brick friendly.
way to do that.

You can't have unlimited bricks you know.
isn't that kinda the appeal of building games like this

I remember some time ago badspot said it was imposable to raise the limit more than 256k

He's not asking for the limit to be raised, he wants Blockland to stop crashing when it's hit.

He's not asking for the limit to be raised, he wants Blockland to stop crashing when it's hit.
Yeah that's pretty much my main, if its going to be impossible to raise it more than 256k we should at least be able to hit correctly.
I am sort of wondering why/how the brick limit gets raised, if Badspot added 64bit or basically allow more memory usage or something could he raise the limit a bit, or had Badspot done this before?

Yeah that's pretty much my main, if its going to be impossible to raise it more than 256k we should at least be able to hit correctly.
I am sort of wondering why/how the brick limit gets raised, if Badspot added 64bit or basically allow more memory usage or something could he raise the limit a bit, or had Badspot done this before?

What if somebody using the 32-bit version joins a server that uses the 64-bit version which has more than 256k bricks?

had Badspot done this before?

The limit used to be 128k.

What if somebody using the 32-bit version joins a server that uses the 64-bit version which has more than 256k bricks?
Maybe it just wouldn't render the rest?

Maybe it just wouldn't render the rest?

Providing a different experience for different users really isn't acceptable. Some users not having shadows or the like is okay seeing as how it doesn't actually affect gameplay, but bricks appearing for some people and not for other people isn't a viable solution.

Providing a different experience for different users really isn't acceptable. Some users not having shadows or the like is okay seeing as how it doesn't actually affect gameplay, but bricks appearing for some people and not for other people isn't a viable solution.

Introduce a chunk system aha

Introduce a chunk system aha
That would actually be pretty good because Blockland seems to lag like a motherforgeter thanks to the shadows being rendered everywhere, even in places you aren't looking at. Also ghosting should be included in the loading screen so you don't have to wait trough a bunch of glitching players and shaky ground to start playing.

"Ghosting"
"Ghosting....."
   "shut up"
"Still ghosting"
"how long is this ghosting gonna take?"
    "how should I know?"
"Still ghosting"
"I still cant play because ghosting is taking forever"
"GGHHOOSSTTIINNGG....."
    "SHUT UP!!"