Author Topic: Deception!  (Read 6678 times)


I was talking to Dread, saying I'm sory because I didn't see his builds.
I saw what you can do.

What you guys write is not correct.
Badspot wrote himself that it is possible to increase the limit: http://forum.blockland.us/index.php?topic=15483.msg209596#msg209596

2. We build as much effective as possbile. But it seems you guys don't understand that.
3. No one tells you guys to join servers with a lot of bricks.


I hope there will be a change.
If you read closely, Badspot said he will eventually allow the limit to be changed again.

If you read closely, Badspot said he will eventually allow the limit to be changed again.
They don't teach sarcasm over there, do they General?
I don't see it. What has been shown so far is that Badspot is not at all interested.

Well since the memory allocator was fixed back in v13, maybe it is time to increase the brick limit.  I guess if I get any emails about people running out of ram or their video drivers crashing, I'll just forward them to you and you can tell them how the computers in germany have no such limitations.

Next time you have a suggestion or request, try phrasing it as such instead of burying it in this "I've been cheated, I'm going to sue" bullstuff.  It'll save you a lot of flames.  
This states effectively that Badspot doesn't give a stuff, and thought the OP was thinking of suing.
Rather than, you know, addressing the problem.

Why not release a 'Master Builder" patch which people could download optionally for those with superior computers? (If, as has been said, this simply consists of a change in one file.)

Quote from: Badspot
The ghostIDs are transmitted using 17bits.  2^17 = 131072 ghosted objects at a time.  Due to bugs in the ghosting code, if you have more objects than that, you may have problems like not seeing other people or not being able to respawn.  Even if it works perfectly, you won't be able to save everything at once from the client because not all of the server's objects will be represented on your client. 

I could up the ghost limit but there are problems with that.  Say I up it to 19 bits for 524288 ghosts max.  That would be an extra 2 bits for every single ghost update packet that is sent out to every client.  If you're on the DSL network setting, the maximum packet size is 400 bits and the maximum packet rate is 20.  So for a scene with 128k bricks, those extra 2 bits would take 640 packets which would take a minimum of 32 seconds to send out to you.  Realistically though, it would probably add over a minute to the brick loading time. 

Considering the framerate most people get in the city as it is now, I don't think adding more bricks is a prudent thing to do.
I think the patch idea works with this in mind. Then people who want to, may add time to their loading, and you don't have to mess with everyone else.

Sadly, the brick limit means nothing to me since I can't run well past 30k.  Thankfully, I get a laptop for college and may actually be able to run something since this dinosaur can't do stuff.