Blockland Forums > Suggestions & Requests
Higher Brickcount
Derroith:
Bumping due to being gone for about a week, hoping for an answer from Badspot when I'm back. :panda:
beachbum111111:
--- Quote from: Derroith on August 11, 2013, 02:46:55 AM ---Bumping due to being gone for about a week, hoping for an answer from Badspot when I'm back. :panda:
--- End quote ---
I doubt he will see this topic unless you PM him.
Monkeyboy:
in all honesty there are a few build ideas that ive never bothered starting because i know i will hit the limit before finishing..
is there a reason not to raise the limit other than it being a pain to do?
Kalphiter²:
--- Quote from: Zeblote on August 10, 2013, 04:31:06 AM ---In that post badspot explains that it was capped at 128000 so it fits in 17 bits, it was then raised to 256000, so I guess it now has 18 bits, he could easily add another one
In his post he says that the only effect is that the ghosting time would be a minute longer, oh my god, who cares
--- End quote ---
The real solution is to totally rewrite the inadequate method of data transfer that Torque uses.
262144 is the limit of server objects ("ghosts") and datablocks combined, not just bricks. The brick limit has consistently been lower than the object limit because there needs to be extra room for non-brick objects.
262144 max ghosts - (4096 max datablocks + 256000 max bricks) = 2048 non-brick, non-datablock "ghosts"
Zeblote:
--- Quote from: Kalphiter² on August 11, 2013, 04:52:35 PM ---The real solution is to totally rewrite the inadequate method of data transfer that Torque uses.
262144 is the limit of server objects ("ghosts") and datablocks combined, not just bricks. The brick limit has consistently been lower than the object limit because there needs to be extra room for non-brick objects.
262144 max ghosts - (4096 max datablocks + 256000 max bricks) = 2048 non-brick, non-datablock "ghosts"
--- End quote ---
oh that makes sense