Author Topic: What exactly holds back the bricklimit?  (Read 1621 times)

To my understanding it seems the only reason as to why the brick limit is, give or take, 260k bricks is because the player/game wouldn't be able to "Handel" it. Which is damn high, but I on a few occasions have hit the limit.

And yeah, yeah, servers probably wouldn't be able to support insane brick amounts for obvious reasons.
But single player? Maybe.

Also for the lag issue that comes with insane amounts of bricks in a small localized area, who's to say they ain't spread out far past view distance. Like you wouldn't be ghosting everything all at once.

I know I sound sort of "all over the place," but I think what I'm getting at is:
What's stopping Blockland from raising the brick limit?

« Last Edit: August 24, 2012, 04:31:19 AM by Hectic II »

Networking speeds and memory usage.

Networking speeds and memory usage.
Forgive me if I sound idiotic, not the most computer savvy, but would network speed matter if in singleplayer?

Forgive me if I sound idiotic, not the most computer savvy, but would network speed matter if in singleplayer?

You're still using network power

Forgive me if I sound idiotic, not the most computer savvy, but would network speed matter if in singleplayer?

It wouldn't.

you can go over the brick limit, its just once you get like ~400k bricks stop rendering.

And if I ain't wrong after 256k bricks they won't even save/load anymore.

Technically I guess you could go to millions but the performance would be terrible. Optimizing hundreds of thousands of objects is difficult.

And if I ain't wrong after 256k bricks they won't even save/load anymore.

Not exactly, see below.

you can go over the brick limit, its just once you get like ~400k bricks stop rendering.

Currently the game simply cannot ghost more than 256000 objects at a time. This is a hard limit defined in code.

I always thought it was around 320k.
Perhaps because the scenarios I'm thinking of have bricks spread further apart, your client never hits the cap/drops bricks further away once it does.

I stopped Seattle project cause i reached 262k (absolute limit, my computer isnt very Powerfull but i didnt lag at all. Im Kinda pissed. (it was défault bricks)

The evil kingdom of lord tony

Does the limit have to do with the age of engine or the type? (by type I mean how there are some companies that have better engines)

Would the server be able to render if I had 256000 bricks here, and more 256000 bricks out of vision range (ie very far away)?

The highest amount of bricks I've gotten to on a server is a good 10k, so I'll never have to worry about reaching over 200,000 bricks. o_o

Also, I don't like the duplicator limit, 5000. Is there a way to change that?