I'd like to point out that the ability to get to the 128k limit without running out of ram is a relatively recent development. How quickly such things are taken for granted.
Do bricks that aren't rendered really cause stress?I turn down my draw distance to a bare minimum and I run fine even at very high brick counts.
128k is enough bricks for 1 or 2 large builds together.but if i want those on a massive built landscape im screwed.hell i would landscape up 128k land, then begin building a 100k castle on it.then another 100k town for it.
pictures of you unfinnishd 20k brick build
Maybe later.
when you've made one, rite?
I know that you don't want to change in the engine, but I think there is a way of fixing this. As default, if you're too far away from a brick, it wont ghost nor render. I suggest you do an opposite thing that removes bricks to render if you're too far away and removes them from the client. Or at least find a way to store it temporarily on the HDD on both the server and the client. Saves RAM and could still be accessed if required.The only problem here is that most people put all their bricks on a group which will crash the client if it tries to look at it. That could also be fixed by limiting areas for a brick limit.Just an idea.
Or at least find a way to store it temporarily on the HDD on both the server and the client. Saves RAM and could still be accessed if required.The only problem here is that most people put all their bricks on a group which will crash the client if it tries to look at it. That could also be fixed by limiting areas for a brick limit.Just an idea.
It still completely lacks any kind of interior or exterior..