#CUBE 2 SAUERBRATEN OCTREE HOW TO#
#CUBE 2 SAUERBRATEN OCTREE UPDATE#
#CUBE 2 SAUERBRATEN OCTREE CODE#

After all, the formula's practically the same- and it really appears that there's something fundamentally wrong, that won't get fixed like magic by just sending it to a shader. Make it easier to arrive at a very fast shader-based approach as a future game option.

Speed up map rendering dramatically, immediately.ī. It is my (no-doubt somewhat ill-informed) opinion that addressing these issues could:Ī. Yeah, I know, it's not quite as smooth or pretty, but meh, it'd be a lot faster.

#CUBE 2 SAUERBRATEN OCTREE UPDATE#

It's simply not necessary, to update the mesh every frame- show the ugly version, if the camera jumps, then clean it up a half-second later at most. I'd have to vote that, unless there's a real need (explosion, Lua event), then it should wait no less than a SlowUpdate (although I'd offset it one frame, since it's a big CPU hit and there's so much going on then). Currently it appears to operate once a frame. The other thing that could (and IMO at least, should) get changed is the update frequency for re-tessellating the mesh. In fact, I have a sneaking suspicion that if that part of Spring was fixed up, SM3 might start looking. It's not the SMF format that's the problem, it's the fundamental drawing code. CPU hits for the map and wiremap on hit anywhere from 10% up to 20% in short bursts.įor a static, absolutely flat heightmap that will not be changing, that's ridiculous, imo. without any objects in the scene, at game start. I'm guessing that there are real fundamental issues here, and that we should see this area as a serious optimization area worth some time spent.

#CUBE 2 SAUERBRATEN OCTREE CODE#

I saw various notes in the ground-drawing code that said that some of SJ's hackish stuff was still in there, and presumably hasn't been fixed. I wish I could, frankly, it's a pretty messed-up area, and I know jK and Kloot are both busy on things that are more important atm.

#CUBE 2 SAUERBRATEN OCTREE HOW TO#

I'll be the first to say, I don't know how to address this, or even have a (crappy) clue as to where to go- this is way outside my comfort zone with rendering systems. for something that should be a quad, on a flat map, then tessellated only enough for the quite-large texels of the shadowmap. We're talking loads of tens of thousands of triangles. Repeated tests have revealed that the CPU hit is not trivial, when you add in groundscars, because they're being inefficiently tessellated, CPU-side, then are being tessellated again by the vertex and fragment programs.

I dunno what the circle is, anybody have any idea what we're seeing there?ģ. See the density of triangles near the bottom? I think it gets even smaller nearer and nearer the bottom, we just can't see them- my guess is that eventually the sub-divided squares are one texel in size. When the camera is near the center of the world, you see this, with wiremap on: It's almost like the renderer is treating heightmap squares in isolation, instead of the entire heightmap that's within the view frustrum. Instead, wide flat areas should always be very efficiently tesselated to a very low triangle count. According to what I read about how that algorithm I talked about last week is supposed to work. and found that flat maps offer practically no real performance advantages over hilly ones. I tested this because I'm trying to figure out how to wring enough performance from Spring to get really complex visuals on people's screens. I'm seeing hundreds to thousands of triangles where I should see a few dozen at most, on tests with perfectly flat surfaces. I've seen a number of other disturbing things:ġ. This is a perfectly-flat heightmap with ground deformation OFF, btw. It's a little hard to see, but the weird 'fuzziness' on those dots (which are caused by whatever bugs are present in the shadowmap code atm). Check this little enlargement of a screenshot I made today: This is in addition to the problems with shadows, which appears to a totally separate problem. They're tessellating far more than they need to.

Cube 2 sauerbraten octree