Carmack On 'Infinite Detail,' Integrated GPUs, and Future Gaming Tech

Vigile writes "John Carmack sat down for an interview during Quakecon 2011 to talk about the future of technology for gaming. He shared his thoughts on the GPU hardware race (hardware doesn't matter but drivers are really important), integrated graphics solutions on Sandy Bridge and Llano (with a future of shared address spaces they may outperform discrete GPUs) and of course some thoughts on 'infinite detail' engines (uninspired content viewed at the molecular level is still uninspired content). Carmack does mention a new-found interest in ray tracing, and how it will 'eventually win' the battle for rendering in the long run."

Comments

Does carmack still check slashdot?

[walshy007]

Years ago he posted here on occasion and I even remember seeing small active discussions on rendering technique technical points etc.

It has been ages since I've last seen this, which makes me ponder if he even reads slashdot these days when topics related to him are posted.

Re:Does carmack still check slashdot?

[Stradenko]

Yeah, anyone still around here is obviously a real loser.

Re:Does carmack still check slashdot?

[elsurexiste]

It's hard sometimes to wade through hordes of trolls and misinformed people, I guess...

Re:Does carmack still check slashdot?

[Baloroth]

It's hard sometimes to wade through hordes of trolls and misinformed people, I guess...

Well then, it's a good thing he works in the video game industry, which is troll and misinformation free!

Re:Does carmack still check slashdot?

[drsquare]

Doubt he'd bother coming, Slashdot barely has a games section anymore. Unless you want to read about Apple and Google over and over again, every day, there's not much point in visiting.

Re:Does carmack still check slashdot?

[sortius_nod]

Congratulations on demonstrating GP's point expertly. You earn +10 slashdot troll points to spent in the store.

Ray Tracing != Ray Casting

[Suiggy]

It should be noted that John Carmack believes that Ray Casting, not Ray Tracing, will win out in the long term.

Unfortunately, many people outside of the graphics field confuse the two. Ray Casting is a subset of Ray Tracing in which only a single sample is taken per pixel, or in other words, in which a single ray is cast per pixel into the scene and a single intersection is taken with the geometry data set (or in the case of a translucent surface, the ray my be propagated in the same direction a finite number of times until an opaque surface is found). No recursive bouncing of rays is done. Lighting is handled through another means, such as with traditional forward shading against a dataset of light sources, or using a separate deferred shading pass to un-hinge the combinatorial explosion of overhead caused by scaling up the number of lights in a scene.

John Carmack has been quoted on saying that full-blown ray-tracing just isn't feasible for real-time graphics due to the poor memory access patterns involved, as casting multiple rays per pixel, with multiple recursive steps ends up touching a lot of memory in your geometry data set, which just thrashes the cache on CPU and modern/future GPU hardware alike.

When people talk about real-time ray-tracing, they almost always invariably are referring to real-time ray-casting.

Re:Ray Tracing != Ray Casting

[Vigile]

I think he has come full circle on that though and thinks ray TRACING will win. Did you listen to the full interview?

Re:Ray Tracing != Ray Casting

[AvitarX]

Does that mean you miss out on the reflectivity though?

Because I thought that was one of the main benefits to ray tracing.

Re:Ray Tracing != Ray Casting

[QuasiSteve]

When people talk about real-time ray-tracing, they almost always invariably are referring to real-time ray-casting.

Developers of dozens of realtime raytracers are lining up to disagree with you.
e.g. VRay RT, Octane, etc.
http://www.youtube.com/watch?v=6QNyI_ZMZjI

Raytracing is extremely straight-forward and parallel. The only thing you have to do to make it feasible for use in games is either A. throw more power at it, B. cheat where you can, C. combination of A&B.

Not to mention companies that make dedicated hardware, almost invariably treating raytracing less as a raycasting problem and more as data access problem.

Re:Ray Tracing != Ray Casting

[AvitarX]

It looks like even basic movement causes trouble.

Re:Ray Tracing != Ray Casting

[Suiggy]

Yes, you do lose out on reflectivity, so you have to handle reflections through other means. If you use deferred shading, you can handle it in a separate reflective lighting pass in combination with something like cube-mapping. Even though you do a second pass to handle it, it'll still end up being faster than had you tried to implement fully recursive ray-tracing.

Ray-casting would still have the benefit in providing better scalability than polygonal rasterization as there is a fixed cost per pixel, whereas with polygon rasterization, as you scale up the complexity of the geometry, you increase the computational cost. And that's why Carmack thinks it will eventually win out against rasterization: ray-casting becomes a better use of the available computational resources you have at your disposal once you get past a certain level of detail in your scenes.

Re:Ray Tracing != Ray Casting

[Suiggy]

The video you posted is not real-time frame rates, it's interactive frame rates. It takes a few seconds to fully recompute the scene once you stop moving the camera. And note how there's only a single car model. imagine scaling up the amount of geometry to a full world. With ray-tracing, as you scale up the complexity of the geometry, you end up scaling up the required computational complexity as well due to radiosity computations. Full real-time ray-tracing on huge worlds in real-time is a pipe-dream. What you will be able to do with ray-casting or rasterization with deferred shading composition to simulate things like reflections or radiosity will always be more than what you can do with ray-tracing, and so games developers will always choose the former.

Re:Ray Tracing != Ray Casting

[Suiggy]

I also forgot to mention that conventional rasterization and ray-casting is also just as parallel in nature as ray-tracing. In fact, more so because it has much better memory access patterns as I mentioned in a previous post. Memory-access is the biggest limiting factor in building scalable, parallel systems. If you don't have good memory-access patterns, you might as well being doing sequential work, because it's getting serialized by the hardware memory controller anyway.

And this situation isn't improving, it's actually getting worse on each subsequent hardware generation... memory access is increasingly becoming a bigger and bigger bottleneck. I suggest you educate yourself on how memory works on modern cache-coherent hardware.

https://lwn.net/Articles/250967/

Re:Ray Tracing != Ray Casting

[Rockoon]

Unfortunately, many non-programmers such as yourself dont understand algorithmic complexity and as such fail to realize that O(P log N) will eventually beat O(PN) once N is large enough, even though the constants in the first are much larger than the constants in the second.

Carmack knows that raytracing will eventually be superior in performance to rasterization because it is inevitable.

The thing is that when the critical N is reached, O(P log N) isnt just going to be slightly better, its going to be enormously better from then on out. It is similar to how for small N that Bubble Sort beats Quick Sort but once the critical N is reached, Bubble Sort is left in the dust with absolutely no hope of beating the better-scaling algorithms.

Re:Ray Tracing != Ray Casting

[loufoque]

John Carmack has been quoted on saying that full-blown ray-tracing just isn't feasible for real-time graphics due to the poor memory access patterns involved, as casting multiple rays per pixel, with multiple recursive steps ends up touching a lot of memory in your geometry data set, which just thrashes the cache on CPU and modern/future GPU hardware alike.

It's not good for a vector processor, but it's still pretty good for a many-core processor.

Re:Ray Tracing != Ray Casting

[Suiggy]

I can't tell if you're trolling or you just wrote up a reply without fully reading my post. I never said rasterization is better. I alluded to the fact that ray-casting will win out over rasterization, and in the very near future. What I said was the ray-casting will win out over ray-tracing. The algorithmic complexity of ray-casting + deferred-shading is better than recursive ray-tracing.

Re:Ray Tracing != Ray Casting

[Pinky's Brain]

The data access problem of backward rendering is unsolvable ... it will always access data without regard to object coherency. For primary and shadow rays forward renderers will always be able to be more efficient when efficient occlusion culling is possible and subsampling isn't needed.

The video you linked has a realtime preview ... in 1/60th second it probably doesn't get that much further than the raycasting solution (primary rays).

Re:Ray Tracing != Ray Casting

[Sycraft-fu]

I think part of the problem is that you get a bunch of CS types who learned how to make a ray tracer in a class (because it is pretty easy and pretty cool) and also learn it is "O(log n)" but don't really understand what that means or what it applies to.

Yes in theory, a ray tracing engine scales logarithmically with number of polygons. That means that past a point you can do more and more complex geometry without a lot of additional cost. However that forgets a big problem in the real world: Memory access. Memory access isn't free and it turns out to be a big issue for complex scenes in a ray tracer. You have to understand that algorithm speeds can't be taken out of context of a real system. You have to account for system overhead. Sometimes it can me a theoretically less optimal algorithm is better.

Then there's the problem of shadowing/shading you pointed out. In a pure ray tracer, everything has that unnatural shiny/bright look. This is because you trace rays from the screen back to the light source. Works fine for direct illumination but the real world has lots of indirect illumination that gives the richness of shadows we see. For that you need something else like radiosity or photon mapping, and that has different costs.

Finally there's the big issue of resolution that ray tracing types like to ignore. Ray tracing doesn't scale well with resolution. It scales O(n) in terms of pixels, and of course pixels grow in a power of two fashion since you increase horizontal and vertical resolution when you get higher PPI. Then if you want anti-aliasing, you have to do multiple rays per pixel. This is why when you see ray tracing demos they love to have all kinds of smooth spheres, but yet run at a low resolution. They can handle the polygons, but ask them to do 1920x1080 with 4xAA and they are fucked.

Now none of this is to say that ray tracing will be something we never want to use. But it has some real issues that people seem to like to gloss over, issues that are the reason it isn't being used for realtime engines.

Re:Ray Tracing != Ray Casting

[Pinky's Brain]

Real time in it's common technical meaning is mostly nonsensical when talking about rendering, it would mean you could guarantee a maximum delivery time ... real time rendering most often used as synonymous to interactive rendering (with interactive being a fuzzy concept, but lets say >10 fps in honor of Carmack's famous turtle in Quake).

Re:Ray Tracing != Ray Casting

[Suiggy]

I admit, I made my post before watching the video. Now that I've watched it, I think my position still holds. He talked a lot about using ray-tracing in content preproduction and preprocessing tools during development, and he talked about building ray-tracing engines in the past to experiment with the performance characteristics. This is the same research he did where he came to the conclusion that ray-casting will be better than ray-tracing. Where his position has changed is in that he used to think it would only be feasible using voxel as your input data set, but he's starting to come around on ray-casting against analytical surfaces... polygonal meshes, curved surfaces, etc. in real time.

Re:Ray Tracing != Ray Casting

[NoSig]

Everything you wrote is mathematically accurate, yet the actually interesting thing is exactly how big N has to get. The mathematics of big-O notation tells you nothing about that, yet that is the crux of the matter. For example, if N has to be bigger than 10^123478234897298, the apparent better asymptotic complexity has no impact on the real world. The point is that if I tell you that one algorithm is O(1) and the other is O(2^n), you haven't actually learned anything useful about which algorithm you should use for your program - you also need to know the point at which one becomes better than the other. But if you know that, you don't have to know the complexity to choose which algorithm will work better for you! So you see, big-O notation can be useful for understanding how your program behaves. It is never by itself (!) useful for deciding between two algorithms at any size of input - it doesn't give you enough information. So don't just tell me the complexities, tell me that one method is better than another at X multiple of current performance.

Re:Ray Tracing != Ray Casting

[billcopc]

The only thing that makes it "realtime" is that it has a relatively high redraw rate (for a raytracer). That's why there is a lot of fuzz when the camera pans around. It might render only a few thousand rays between redraws, which does give fast feedback but also slows down the rendering process overall. Most raytracers will churn 100k rays before updating the preview.

This is analogous to progressive jpeg decoding, where you start with a very chunky low-res preview and gradually work your way up to the full detail image. I don't see how this could be usable in games, unless you're specifically going for that TV-static effect :P

Re:Ray Tracing != Ray Casting

[Suiggy]

You still run into the same problems regardless of whether you're using a vector processor with no branch-prediction and no cache, to if you're using a bunch of in-order cores with cache coherency, or full-blown out-of-order cores with cache coherency. You end up pulling in a combinatorial explosion (ie. exponential number) of cache lines or memory accesses per recursive ray tied to the complexity of your scene.

People like to talk about how you can just throw more cores and distributed computing architectures to increase the performance of ray-tracing graphics. Yes, it works, but only up to a point. You can cut the number of days or weeks or months off of fully rendering a CG movie by building out a distributed render farm, but it's not going to hold for when you get single shared-memory machines with enough cores and you expect it to be able to do it all in real time.

It'll still be a much better use of those hardware resources if you go with algorithms which are much more orthogonal in nature when it comes to memory access patterns. Ray-casting + deferred shading should scale better than fully recursive ray-tracing, even on many-core shared-memory CPU architectures.

Re:Ray Tracing != Ray Casting

[Suiggy]

Yeah, not to mention that with full ray-tracing, as you add more lights to a scene, it increases the overall complexity per pixel per ray bounce linearly as well. That's why doing deferred shading is so nice because it unbuckles the lighting from the rasterization or ray-casting/tracing step and lets you scale up the number of lightings independently with a fixed amount of overhead and linear cost per light for the entire scene, instead of per pixel or per ray or per polygon.

Going with pure ray-tracing doesn't let you take advantage of that.

Re:Ray Tracing != Ray Casting

[Suiggy]

And if you include lighting into the equation, with N = L lights + S geometric surfaces, he's advocating for O(c * 2^backtraces * N) over O([c1 * S] + [c2 * L]) that you would get with ray-casting + deferred shading&lighting, where it could be proven that c2 c1 c, seeing as how you also have to cast multiple rays per recursive back-trace to get a decent approximation of lighting in your scene, where you only need to perform a single sample per pixel with what I'm advocating for.

Re:Ray Tracing != Ray Casting

[Suiggy]

That should read c2 < c1 < c.

Re:Ray Tracing != Ray Casting

[Rockoon]

Everything you wrote is mathematically accurate, yet the actually interesting thing is exactly how big N has to get.

You know that this very question has been researched, right? I am amazed that you are intent to discuss this issue without having actually done any research in this matter.

You might want to start with this 2005 paper from Intel where they do some performance comparison for both hardware rasterization and software raytracing for various scene complexities.

That paper in particular illustrates how close we are. We are approaching the crossover point with the number of on-screen primitives right now. GPU's have done a lot to decrease the need for more primitives since then (hacks like parallax mapping and so forth,) but they are doing those things precisely because the demand for more scene detail is outpacing the ability to deliver higher primitive counts on GPU's. Piling on shaders (stream processors these days) only goes so far in delivering higher primitive counts, because their real choice is latency or bandwidth.. pick only one, even though you need both.

Re:Ray Tracing != Ray Casting

[Suiggy]

Actually, now that I think of it, that should be O(c * 2^backtraces * log N) vs O([c1 * log S] + [c2 * L]) given that you would normally use spatial data structure such as an octree with logarithmic look-up times.

Re:Ray Tracing != Ray Casting

[NoSig]

Everything you wrote is mathematically accurate, yet the actually interesting thing is exactly how big N has to get.

You know that this very question has been researched, right? I am amazed that you are intent to discuss this issue without having actually done any research in this matter.

What I'm discussing is what can and cannot be concluded from big-O asymptotic complexity. You were drawing a mathematically correct conclusion that "for big enough N, raytraycing is better." You then made an incorrect further conclusion that "eventually, raytraycing is better." Big-O notation never guarantees that you'll ever be able to solve an input so big that the complexity estimate becomes accurate as to which algorithm is better. You then chose to heed my advice and present data on what actually matters - which algorithm is better in practice for which inputs. Good on you, even if the quote above is a very dickish way to accept advice.

Re:Ray Tracing != Ray Casting

[Rockoon]

Yeah, not to mention that with full ray-tracing, as you add more lights to a scene, it increases the overall complexity per pixel per ray bounce linearly as well. That's why doing deferred shading is so nice because it unbuckles the lighting from the rasterization or ray-casting/tracing step and lets you scale up the number of lightings independently with a fixed amount of overhead and linear cost per light for the entire scene, instead of per pixel or per ray or per polygon.

I highlighted the key thing that you overlooked. They are both linear to the number of lights.

Re:Ray Tracing != Ray Casting

[ShakaUVM]

It gets even worse when you realize you have to do subsurface scattering to get realistic looks for a lot of surfaces (like, oh, skin). Then you no longer can terminate a photon when you reach most surfaces, but then have to further reflect and refract photons from that point.

It does make for nice looking materials, though... without it, you get those iconic hard and shiny surfaces in ray traced images, like the famous metal balls.

(http://en.wikipedia.org/wiki/Subsurface_scattering)

Re:Ray Tracing != Ray Casting

[loufoque]

You still run into the same problems regardless of whether you're using a vector processor with no branch-prediction and no cache, to if you're using a bunch of in-order cores with cache coherency, or full-blown out-of-order cores with cache coherency. You end up pulling in a combinatorial explosion (ie. exponential number) of cache lines or memory accesses per recursive ray tied to the complexity of your scene.

GPUs have no cache.
(Fermi has one, but it doesn't really work, so we might as well not count it)

Re:Ray Tracing != Ray Casting

[Suiggy]

Again, your ability to comprehend fails to you. Scaling linearly per ray cast (and you doing multiple ray casts per pixel with ray-tracing) and scaling linearly with respect to the entire frame buffer are entirely different.

Ray-tracing: O(2^b * L * log N)
Ray-casting + deferred shading: O(log N) + O(L)

Re:Ray Tracing != Ray Casting

[Suiggy]

GPUs eventually will get working caches. AMD's next-generation GPUs are shipping with stuff comparable or better than Fermi, and nVidia's Kepler is getting something better than Fermi.

Furthermore, Intel's Larrabee, Knight's Ferry, and Knight's Corner HPC compute products have cache, yet feature just a bunch of simple in-order, non-speculative x86 cores.

There's a wide spectrum of what's out there, and yes, you can have vector processors with cache, there's nothing saying that you can't do that.

Re:Ray Tracing != Ray Casting

[Suiggy]

Ahh, okay, gotcha, now what you original said makes sense. There's more than one way to scale it. Generally, on a given project you have fixed budgets for pixels and polygons, but over the years as you target each subsequent generation you get to scale up both categories--however, scaling up the number of pixels beyond 1920x1080 or 1920x1200 doesn't really make as much as much sense as say continuing to scale up the complexity of your geometry, so I guess my brain assumed that's what you'd want to scale up rather than the output resolution.

Re:Ray Tracing != Ray Casting

[loufoque]

Anyway, the point is that of course ray casting is better suited to that hardware, but a lot of raytracing applications, like in medical or semiconductor imaging, already benefit from GPUs greatly.
And those things actually run in real (or interactive) time.

Re:Ray Tracing != Ray Casting

[QuasiSteve]

I won't go into what constitutes realtime vs interactive, as I can make even the fastest game engine out there 'interactive' as long as I run it on low enough hardware with all the features enabled and running it across multiple HD screens.

But the converse is also exactly my point - raytracing is something that scales very well, you just throw more computational power at it.

I did also mention 'cheats'; in that a game engine doesn't necessarily rely on any one single technology to begin with. We've now got on-hardware tessellation and mesh displacement - but that doesn't stop most games from still using bump maps, normal maps, parallax maps, etc. for the vast majority of surfaces (having to support older hardware factors in to it as well, of course).

Re:Ray Tracing != Ray Casting

[Creepy]

I'd hope he is talking about ray tracing - I'm basically doing ray tracing inside of polygons in shaders today, and I'm sure he has, too. I really don't think ray casting has enough advantages over polygons that would make it worth it, and has significant disadvantages that would need to be worked around (no reflections, shadows, etc). Back in the 1980/1990s, programmers used the painter's algorithm instead of zbuffer because it was significantly slower to use zbuffer up to a certain number of polygons, and right as zbuffer was becoming practical consumer hardware became available that used it, killing the painter's algorithm. Ray tracing actually falls into a similar category - as the number of objects in a scene grows, it scales linearly, so at some point it will be cheaper or as cheap to use ray tracing as it is to use polygons. If monitors had stuck with 640x480, we'd easily be there today.

Not that ray tracing doesn't have issues - it needs access to the entire scene in memory (GPU memory optimally - GPU parallel processing is ideal), creates hard shadows only (without photon mapping or similar - I'd say Radiosity, but I doubt we'll see that full scene in realtime anytime soon - O(n^5) I believe), requires a lot more processing power for larger monitors (640x480 is 307200 rays, 1920x1200 is 2304000 rays or 7.5x more expensive - in contrast, polygons don't increase in cost by monitor size), and displays reflective lighting far better than diffuse.

All of the problems above are solvable by lots of GPU horsepower and memory - we're not there yet, but in 10 years, who knows?

Re:Ray Tracing != Ray Casting

[NoSig]

You don't like it when you make mistakes, do you?

Re:Ray Tracing != Ray Casting

[Rockoon]

Amazingly, you think that lighting can be handled without respect to scene geometry.

You do realize that the deferred lighting passes must deal with the actual scene geometry, and not just the frame buffer, right?

Re:Ray Tracing != Ray Casting

[Rockoon]

My conclusion was not incorrect as you claimed, and in fact I gave a citation to prove otherwise, and after reading that proof you decided my conclusion was incorrect on "general theoretical grounds" even though the paper proves it "in actual practice."

The mistake is clearly yours in thinking that the metrics involved havent been well researched. You go on about the theoretical.. I'm sure that will impress some other guy that doesnt actually do shit.

10^123478234897298 indeed.... right out of your ass.

Re:Ray Tracing != Ray Casting

[Daniel Phillips]

The thing is that when the critical N is reached, O(P log N) isnt just going to be slightly better, its going to be enormously better from then on out

Obviously, but many commenters seem to gloss over the fact that polygon rendering can also be reduced to O(N log N) by multi-resolution rendering.techniques.

Re:Ray Tracing != Ray Casting

[Suiggy]

Wrong again.

With deferred shading, lighting is done in a second pass (or multiple passes for different types of lights) directly against the g-buffer. The g-buffer contains a surface normal, depth value, and lighting & material coefficients for each pixel and is populated by rasterizing or ray-casting/tracing your scene geometry into it. With rasterization, each of your polygonal meshes are rendered into the g-buffer once without regard for lighting, during the lighting stage, each light is applied to the g-buffer without regard to the different primitives that were used to create the initial g-buffer. Thus you can scale up the number of lights independently from the scene geometry.

I'm really starting to think you're a troll looking for a quick fix.

Re:Ray Tracing != Ray Casting

[DrKnark]

Then there's the problem of shadowing/shading you pointed out. In a pure ray tracer, everything has that unnatural shiny/bright look. This is because you trace rays from the screen back to the light source. Works fine for direct illumination but the real world has lots of indirect illumination that gives the richness of shadows we see. For that you need something else like radiosity or photon mapping, and that has different costs.

Forgive my ignorance, but I don't quite understand why ray tracing can't handle indirect illumination. Wouldn't the traced ray modify the intensity and color of the (eventually found) light source with each bounce? Or is the problem that when you cast one ray per pixel you only get the contribution from a single light source in the end?

Re:Ray Tracing != Ray Casting

[Sycraft-fu]

You basically have it right. You trace a ray for each pixel, starting at the monitor, and it bounces back to the light source. To deal properly with indirect illumination and thus get good shadows and so on, you'd have to do it the other way, you'd have to trace rays from the light source, bounce them off materials, and see where they end up. That, of course, gets real CPu intensive since you can be tracing rays that never intersect with the display.

That strategy is more or less what radiosity is. It simulates indirect lighting to a certain number of bounces (the more the better it looks). The Wikipedia article on it is decent and the picture is good. Compare their little room that is direct and radiosity illuminated. Notice not only the soft shadows, but the way the red carpet colours the walls.

At any rate there's all sorts of various solutions out there, the problem is they just take a lot of power. Using something like photon mapping along with ray tracing gets you a very realistic setup with good caustics, indirect illumination, subsurface scattering, and so on. However it takes some serious computation to do right.

Re:Ray Tracing != Ray Casting

[smallfries]

At 13:30 he seems to be talking about path-tracing. That accumulation step that he describes with an arbitrary cut-off to make the frame deadline and the random jitter makes it quite certain. The random jitter in time reusing previous pixel results somes like a very bizarre and trippy form of "motion" blur - it would look similar but blurring would be proportional to path length casting from that pixel. I might have to hack that up and try it...

Re:Ray Tracing != Ray Casting

[kvezach]

It's possible to make a low-res realtime version of photon mapping. See https://www.youtube.com/watch?v=GckOkpeJ3BY for an example. It isn't as good as proper photon mapping, but it *does* give indirect lighting.

Re:Ray Tracing != Ray Casting

[smallfries]

Raytracing is extremely straight-forward and parallel.

If only.... In the real world that would be an exclusive or, so pick one of the two. On small uncomplicated scenes it is straight-forward to make the tracing of each ray happen in parallel. As you add more geometry though it begins to behave differently. You will need a giant cache of rays to handle all of the bounces otherwise all of the recomputation will kill your performance. This was well known in the graphics community prior to GPUs and the same scaling issues were seen on clusters used in rendering. Working out how to implement that cache so that it scales nicely with the number of nodes is a really difficult data-structures problem.

Say that you avoid this problem (for now) by only looking at a low number of bounces per ray, and you favour performance over fidelity by only casting a few (or just one) ray per pixel. You certainly don't want an O(n) intersection test with your geometry, and to hit some kind of O(log n) you will need a spatial subdivision tree of some kind. The problem that you will now face is that every ray traverses the tree in a slightly different order. This means that memory locality amongst your cores is a absolute bitch.

Either replicate *all* of your geometry into huge local memories for each thread (not feasible). Or try and cover the latency with throughput. Of course high-throughput on a GPU depends entirely on memory coalescing (not possible because the access patterns diverge in each thread) and a high arithmetic to access ratio (not really going to happen during tree traversal). Then you have the smaller issues like the SIMD restrictions that mean every thread in a workgroup must execute the same trace, so both sides of branches are run and recursive traversal functions are pig-slow.

There is some really, really nice work out there. But it is hideously inefficient because the problem does not map onto the architecture. The Sparse Efficient Volumetric work from (siggraph 2 years ago?) shoots about 140Mray/s on a GTX-580. It looks pretty gorgeous, but it expands out all of the geometry into 2.7GB on the card to make the approach a little bit closer to brute-force and spend less time on processing acceleration structures. But that card can hit 800Gflop/s so each ray is still costing 6000 arithmetic instructions (or more likely their equivalent as they are memory bound). They are not computing hundreds of bounces per ray on average, that huge cost is because their arithmetic to access ratio is so bad, and that is a direct result of it being so difficult to parallelise the ray processing.

Of course dynamic scenes are much, much harder than these minor problems that you get for static scenes...

Re:Ray Tracing != Ray Casting

[smallfries]

What do you think memory access coalescing is, and why do you think it needs to be on aligned boundaries? Exploiting spatial locality of reference is still a cache, even it only has a single line. Given the huge impact of non-aligned access within a warp it seems silly to pretend that a GPU is not a cached architecture.

Re:Ray Tracing != Ray Casting

[MBraynard]

In the long term, it is not Ray Casting or Ray tracing that will win out, but Ray Charles because you got the right one baby!

Re:Ray Tracing != Ray Casting

[NoSig]

That is a misunderstanding - the objection is not that the conclusion is wrong, it's that your argument for it was wrong. Your original argument is not helped by coming up with a different argument that shows the same thing. I told you to use practical evidence instead of incorrectly applying theory, and then when you did that, you think that that shows that what I said was wrong.

You can have both rasterization and ray-casting.

[Suiggy]

The Euclideon infinite detail technology was exposed in a recent interview to be efficient sparse voxel octree ray-casting with contours (instead of axis-aligned cubes), which was previously investigated by nVidia researchers and others.

http://www.tml.tkk.fi/~samuli/publications/laine2010tr1_paper.pdf

It's still not quite competitive enough with conventional rasterization techniques if you also try to do decent lighting with it along with all of the other stuff that goes into developing a game. Maybe in couple of more GPU generations. And in the Euclideon demos, you can see they're only getting 15-25 frames per second, and yet they're using a simplistic lighting model with a single global light.

Also, you can merge polygon rasterization and voxel ray-casting under the same rendering architecture if you employ deferred shading and composition. That way you can have your static models as a voxel-octree that you ray-cast into your geometry-buffer, rasterize your dynamic polygonal models in a second pass into the same geometry-buffer, and then perform your lighting passes with the geometry-buffer as input, and then your final scene composition and post-processing passes. In fact, I bet you that in 5-6 years time, this will become a standard practice among PC game developers. Unfortunately, I think the upcoming next console generation, with hardware from Sony and MS due out next year, will miss out on being able to handle this.

Hey!

[toby]

Speak for yourself! ;-)

Re:Hey!

[davester666]

You must be new here...

Re:Does anyone actually listen to him

[discord5]

Why after all this time do people still hang on to his every word? Its just some dude, not Jesus.

By all means, feel free to do something more noteworthy and become the new authority on the subject at hand. Until then, I think I'll continue feeding my Savior Reincarnate shrine its daily snackrifices.

Re:Does anyone actually listen to him

[TehNoobTrumpet]

To be fair, Jesus was also just some dude. Possibly.

Best Yet

[Kid Zero]

(uninspired content viewed at the molecular level is still uninspired content)

Best quote I've seen yet about this.

Re:Why can't we have both.

[Skarecrow77]

I know, right!

Next, he'll be asking for real time mpeg encoding.

Too much dependence on drivers

[loufoque]

They rely too much on drivers, they should just attack the hardware and make their own renderer rather than relying on crappy OpenGL and DirectX...
But of course, they don't really want to invest in R&D. Game development is more of a "do something dirty quickly and then throw it again" kind of thing.

Re:Too much dependence on drivers

[hedwards]

That would be a tremendous step backwards. You can get away with doing that if you're programming for a console, in fact that's how it used to be done. The problem is that as soon as you've got any variation at all in the hardware you very quickly start to have to code for every individual unit that you're going to support.

Need multiple resolutions? Well, you're going to have to make sure you code for them rather than handing them off to a 3rd party library. Unit have extra RAM? Well, you're going to have to adjust the code to deal with that as well.

Sure, it is much faster to run code like that, but it's also not portable really at all and you don't get any of the benefits that come from using a library.

Re:Too much dependence on drivers

[NoSig]

That is the bad old days of computer graphics and sound - if a given game wasn't written for your particular hardware, too bad. It's hard to write to the hardware when there is a proliferation of distinct graphics cards out in the world and many more are added every year. On top of that, the way to talk to a given graphics card is often secret. There's a reason that people use OpenGL and DirectX.

Re:Too much dependence on drivers

[SuiteSisterMary]

Even a few years ago, hell, probably still, for all I know, there was the DX8 path, the DX9 path, the openGL-nvidia path, the openGL-ATI path, and so on.

Or fifteen years ago, when part of the setup was picking exactly the correct video mode (hope your monitor and card support VESA 2.0 modes) and sound card, down to IRQ and DMA settings....

Re:Too much dependence on drivers

[LWATCDR]

Let me make a guess. You don't program do you?
1. AAA games already cost a lot to make. You want to spend $200 for a game?
2. Hardware is changing fast. If you write for the hardware what hardware do you write for? Which card? All of them? What about the cards that come out while you are spending the three years developing the game?

Now you may be confusing drivers with game engines but even then you would be wrong just not insane.

Re:Too much dependence on drivers

[loufoque]

The problem is that as soon as you've got any variation at all in the hardware you very quickly start to have to code for every individual unit that you're going to support.

If your software is of good quality, it is generic and easily retargetable.

Also, if you just consider GPUs, the interfaces to program them (CUDA in particular) has been there for quite a few generations and probably will stay for a long time still.
And all NVIDIA (and probably also AMD) drivers use the same code, with relatively few low-level details that change depending on model.

Re:Too much dependence on drivers

[loufoque]

Let me make a guess. You don't program do you?

I write software tools for high-performance computing that work on a variety of hardware, including all variations of x86, POWER, PowerPC and Cell, ARM, GPUs, multi-core, clusters... and other more confidential architectures (many-core, VLIW, FPGA, ASICs...)
Supporting a lot of different hardware is not an insurmountable problem if you have a good design (and a good test farm).

Now you may be confusing drivers with game engines but even then you would be wrong just not insane.

What we call graphics drivers nowadays is not just the code that allows to interact with the hardware. It's an OpenGL and DirectX implementation.
With the advent of programmable GPUs, this abstraction has become much too high-level. A C compiler is quite a better one.

Re:Too much dependence on drivers

[loufoque]

You say this as if the market wasn't essentially restricted to two vendors, with one clearly preferred by gamers.

Re:Too much dependence on drivers

[0123456]

You say this as if the market wasn't essentially restricted to two vendors, with one clearly preferred by gamers.

But a game written for OpenGL or Direct3D in 2001 still runs on modern hardware. A game written to write directly to 2001 hardware does not.

Writing directly to hardware without a standardised API is retarded and pretty much guarantees that in ten years time the software won't work or performance will be lousy if it does.

Re:Too much dependence on drivers

[NoSig]

They make more than 1 graphics card each. Btw Intel sells more graphics cards than anyone else. You've probably got one integrated on your computer without knowing about it. There are also many flavors of each graphics card that the big companies come out with.

Re:Too much dependence on drivers

[RyuuzakiTetsuya]

At first i thought you were insane because writing for individual vendors was kind of crazy. However, between Intel, nVidia and ATI, you've cast a pretty wide net.

Then I realized it's even crazier wanting nVidia, ATi and Intel to all make their hardware communicate the same way through out the generations.

Re:Too much dependence on drivers

[loufoque]

But a game written for OpenGL or Direct3D in 2001 still runs on modern hardware. A game written to write directly to 2001 hardware does not.

This is irrelevant, since the industry does not try to make money out of old games. What they want is to make money at launch, then milk the cash cow for some time with a couple of people working on DLCs, then move on.

Also notice how your old Playstation games don't work without a Playstation (short of using an emulator). This is not a serious issue. Games are not meant to yield profits for life, so if they're limited to the lifetime of the platform it's fine.

Writing directly to hardware without a standardised API is retarded and pretty much guarantees that in ten years time the software won't work or performance will be lousy if it does.

What matters is that the game is groundbreaking and people want to buy it when it goes out.

Back when the Cell was released, it was a very powerful (it still is, but to a lesser extent). Game developers could have used it instead of the graphics card to do very innovative things (and Sony actually supported this idea). They didn't, even though it was available in many homes.
Game developers just can't handle doing serious R&D in graphics. They need hardware manufacturers or middleware people to do it for them. I know for a fact there are only a couple of Cell experts in the whole of Ubisoft.

Re:Too much dependence on drivers

[loufoque]

All flavours of NVIDIA cards run the same base OpenGL implementation, likewise for ATI/AMD.
Intel GMA cannot even start most recent games.

Re:Too much dependence on drivers

[loufoque]

CUDA and OpenCL should be all you need.

Re:Too much dependence on drivers

[NoSig]

If you listen to the interview, you'll hear John Carmack saying that built-in cards might out-perform dedicated cards for some things in future if they grant better memory access by virtue if using system memory directly. How do you know that the hardware interface between graphics cards never change? That doesn't sound right to me, but if you have an inside source, feel free to enlighten us.

Re:Too much dependence on drivers

[RyuuzakiTetsuya]

I wonder how much of a bitch a pure CUDA port of Quake would be.

Re:Too much dependence on drivers

[hedwards]

I spent a very small amount of time playing around with hamlib for the GBA and that's how things were done on it. If you wanted to draw something on screen, there'd be a particular set of registers to write to, same for most other things that you might want to do. All in all it was a pretty nice set up.

Re:Too much dependence on drivers

[LWATCDR]

CUDA and OpenCL are driver dependent. That is still not writing to the hardware.

Re:Too much dependence on drivers

[chammy]

All flavours of NVIDIA cards run the same base OpenGL implementation

Nope, sorry. There is a reason why there exists a "legacy" Nvidia driver.

Re:Too much dependence on drivers

[edxwelch]

Actually, he's only concerned about the overhead of texture upload, not the entire driver. Surely, that would be easy to fix with an OpenGL extension or something?

Re:Too much dependence on drivers

[gl4ss]

Cell was seriously over hyped as platform for generic computing - as was ps3, which is seriously short on memory. dreamcast would make a fine example of using shitty general sdk(the wince based one) vs. doing native, because on it

now, there's a difference between game engine developers and content-jockeys. content jockeys just create content on autodesk tools, totally dependent on old school artistic plot writing and art creation - thus, their games very rarely manage to amaze people on the virtual world side of things(elite 2 frontier first encounters is the direct opposite of this, for example, while a game like mass effect 1/2 is just that, a game where nothing amazes on how it was possible to execute because you know the game could have been created using original unreals udk - or even with halo's engine, except it would then have had better car physics).

thing is, those content jockeys are a dime a dozen, because that's the sort of thing you can teach at courses and the things they create they can see as they create.

however, just targeting modern cards with pure self-boot code would usually mean that your stuff wouldn't work even 2 months from release if it worked at even the release, now if gpu development stalled for a few years AND the gpu interface specs were available, we would start seeing those again, selfboot dvd titles(they would actually put a little dent on piracy, but just a little, interestingly the original pc pirates! was a self boot title, at least the version I had).

also for reasons of not having to care that much of developer access enabling pirating of native titles these interpreted virtual machine environments are really tempting for hw manufacturers, since then they can just give the sdk to just about anyone(xbox live etc) so we're mostly seeing a move away from bare to metal development, making things go backward or rather seem like game complexity is stalled at the moment - it seems though that the actual problems lie along project management approaches to game development, since when did you last time see a virtual world that was as complete as ultima 6 had?

Re:Too much dependence on drivers

[tempest69]

I'm going to agree, at least partially. I think we do rely too much on drivers to overcome the problem of a very diverse video card system.

This bugs me.
I see no compelling reason for the video manufacturers to postpone a more modern standard for video cards. Video cards have simple compatibility at a ~20 year old standard. It is really depressing to see that when I install an OS, the video is set to some horrible resolution. When I go to download the driver it's a mess, because the site is nearly unusable at the ancient resolution. Creating a card that could have limited functionality (up to 2560X2048 video DX 6/ OpenGL 1.0 capable) with the new equivalent of a "vga" driver seems like a reasonable possibility.

I understand that it would add some minor cost to each video card, but it would make life so much easier.

DirectX and OpenGL are really quite nice, and getting someone who has the skill/sanity to rebuild the graphics is not going to be cheap, and the results will probably look amateureish.

Re:Does anyone actually listen to him

[darkwing_bmf]

To be fair, Jesus was also just some dude. Possibly.

No, Jesus wasn't the dude. He was the dude's bowling rival.

Re:Does anyone actually listen to him

[ddt]

There are a lot of reasons people still follow him closely.

He's really smart, hard-working, and open with his opinions. If something blows, he doesn't sugar coat it out of fear for his relationship with the company whose product he's bagging on.

He's also fiercely empirical. Moreso than a lot of his competitors, he doesn't buy into his own bullshit. If he has an idea, he makes an experiment to test it, and if it doesn't cut the mustard, he adjusts his view on the subject. He reverses his opinions over time and points out when he's been wrong. You'd think that trait would be common amoungst coders, what being lovers of science and engineering in general, and you'd be wrong.

He's also open with his source code, and a lot of coders have actually learned how to write games by reading his source for Doom & Quake. In addition to being a fast coder, he writes very clean code with a very crisp style, and that code has been a really positive influence on the next generation of game programmers.

But if you're looking for Jesus, you need look no further. I was one of the first coders John hired, and if you recall, Jesus is the *son* of God, and like Jesus, I was cast out from Heaven to muck about with mortals and spread the good word. Also, unlike John but more like Jesus, I believe my own bullshit without the need to test it. Crucially, if you look up "gamer" under Google images, I'm on the first page, and you'll see conclusively that I can rock the long Jesus hair. I am also skinny, emaciated, and have been repeatedly crucified. If you choose to become a disciple, I will welcome you with open arms. I just won't respect you.

Re:Does anyone actually listen to him

[Grizzley9]

Id rater listen to him than jesus, what does that tell you?

That idiots post as anonymous cowards on Slashdot.

Re:Does anyone actually listen to him

[XanC]

So how many games will the 'Horns win this year?

Re:Does anyone actually listen to him

[h4rr4r]

Yeah, it is real person not some quite likely fictional historic figure. What exactly is your point?

Re:Does anyone actually listen to him

[MattSausage]

Have you not read this?

That's a pretty good reason to take him seriously.

id dosen't want R&D?

[SanityInAnarchy]

Really?

I mean, the main criticism for id games has been that they are less games and more tech demos. Practically every game engine id ever sold has been used for much more interesting games by other people, but id still gets license fees.

If they don't invest in R&D, why are they doing their own engine design at all, and more importantly, just what are they investing in?

And even if you're right about OpenGL and DirectX being "crappy", which I highly doubt, the fact is that they are at least somewhat portable across hardware. Suppose he's right, and Intel integrated graphics suddenly win. If they went directly to the hardware, as you suggest, they'd need to port their game to Intel cards, or that game wouldn't work with those cards. We'd be back to the bad old days when you actually had to check the system requirements for your sound card and video card manufacturer.

Re:id dosen't want R&D?

[loufoque]

It wasn't a commented directed at Id in particular, but at the game developer industry in general.

We'd be back to the bad old days when you actually had to check the system requirements for your sound card and video card manufacturer.

Don't you have to do this anyway?
It's true consoles have stopped PC games from requiring new hardware, but a few years ago, you needed to replace your graphics card every other year to play new games.

Re:id dosen't want R&D?

[Desler]

Don't you have to do this anyway?

No. Gone are the days were you have to make sure you have a Sound Blaster 16 vs some other card because the game was only written to that specific sound card. Games usually give what generation versions of a video card you would need if running on various manufacturers but with probably almost no exceptions are games written to a specific manufacturer's audio or sound card.

Re:id dosen't want R&D?

[Truekaiser]

Directx is only 'cross platform' if you count different video cards and the xbox360 as different platforms.
Opengl 'is' cross platform, you can run it on your pc, it's used on mac's, it's used in linux, it's used in most cellphones, it's used in most consoles(sans xbox and xbox360).

Re:id dosen't want R&D?

[loufoque]

As I said in another subthread, it doesn't matter if you have choice since there are only two manufacturers anyway (with Nvidia being better supported by games in general).
Games usually can't even run on Intel GMA even on the lowest settings.

And if you need to replace your graphics card every two years to run new games, it's no different than buying a Sound Blaster 16 or whatever other fancy hardware a game at the time required.

Re:id dosen't want R&D?

[Lunix Nutcase]

Except that for unlike what you are talking about that I don't need to always keep around the Sound Blaster 16 to play that old game. Written to a portable API means I can use that same game on an old Sound Blaster or my new integrated sound card. This is what you seem to be missing.

Re:id dosen't want R&D?

[Lunix Nutcase]

Directx is only 'cross platform' if you count different video cards and the xbox360 as different platforms.

I'm pretty sure that an Xbox 360 and a PC are different platforms. "Cross-platform" only means "runs on different platforms" it does not imply some minimum number of platforms. If I write something that works on both OS X and Windows it is "cross platform" even if it won't run on Linux or a cellphone.

Re:id dosen't want R&D?

[loufoque]

This is irrelevant, game developers don't care about whether you can play old games on new hardware. That's not their business model.
Again, I've already addressed this in another subthread. Go read it for more details.

Re:id dosen't want R&D?

[Lunix Nutcase]

Sorry, it's not irrelevant despite what you continue to claim. Your idea leads to more code needing to be written, far more testing is needed and programs are far more likely to break and have issues than what is written now. Basically your idea is fucking stupid on pretty much all counts.

Re:id dosen't want R&D?

[Truekaiser]

It's not cross platform because xbox360 runs on windows built for the ppc chip inside. cross platform would be directx being able to run on mac os x.

Re:id dosen't want R&D?

[loufoque]

The idea is to ditch that model of "write once then throw away" and replace it with "write a good engine and reuse it throughout all your projects".
That's what the big game development companies are moving towards. The ones that can't do their own or can't license that of a third party will have to fall back to casual games that don't require much processing power.

Re:id dosen't want R&D?

[SanityInAnarchy]

I didn't say "corss-platform", you did. I said "somewhat portable across hardware," which is true -- you can develop a game for nVidia, ATI, and yes, even Intel, and if you stick to the API, you don't need code specific to any of those cards.

Re:id dosen't want R&D?

[SanityInAnarchy]

a few years ago, you needed to replace your graphics card every other year to play new games.

This is both irrelevant and untrue.

Untrue, because any decent game at that point would be able to turn the settings down to where you could play on older hardware. You still had a quicker upgrade cycle, but it wasn't that bad, especially if you stay just behind the curve -- you could often buy at least a new video card for under $100, and when the PS3 came out, it was possible to build a new gaming PC for less.

Irrelevant, because there were at least 5 or 6 different sound card manufacturers when we had to check for that. There seem to be even more now, but I'm not sure, because it doesn't matter -- sound has "just worked" for awhile, because we use higher-level abstractions like DirectSound and OpenAL, so your game can just play sound and it just works.

So, even if I needed a new video card every few years, I can still play the original Half-Life with the same shiny new video card I used to play Portal 2.

Re:id dosen't want R&D?

[SanityInAnarchy]

game developers don't care about whether you can play old games on new hardware.

Yet I can, whether they care about it or not. I'd like to be able to keep doing that, so...

That's not their business model.

...I don't plan to be buying games which target a specific piece of hardware if I can avoid it.

ARM cores?

[SanityInAnarchy]

Did anyone else catch that?

That's probably the most interesting thing he said all day. Throw an ARM core on the GPU, provide some sort of standard API for using it, and you eliminate all those pesky latency issues. Modern GPUs have enough RAM that one could potentially push the entire renderer onto the GPU, with the CPU and main memory only being responsible for game logic.

Of course, he also seems to be implying that this might go the other way, with integrated graphics winning out...

Re:ARM cores?

[Rockoon]

I thought it was interesting that he said hes spent the last 1.5 years working on raytracers. Carmack is very much a research guy now, not a developer. He pays others to develop.

Re:ARM cores?

[gl4ss]

pyramid3d.

shit idea, computer on a board. yo dawg..

anyhow, graphics AND game logic(game physics) are very closely connected. when they're not, you end up with stuff like nwn-engine derived shit(where the game is like a game from 386 era, but with plastered on super fancy graphics, while the game still just runs basically in a 2d field, or when a game is full of let's say grass thats shaded, but while that grass has no meaning to gameplay or even ai's field of view).

Re:ARM cores?

[mikael]

That was done 20 years ago with TIGA graphics boards. There was a simple BSP tree demo (flysim) which downloaded the scenery database and renderer into the cards memory. All the host PC did was to convert keyboard events into camera motion commands.

Re:ARM cores?

[SanityInAnarchy]

shit idea, computer on a board. yo dawg..

Too late. My current video card has many times more RAM than my first computer. It also has two GPUs, which can perform certain tasks ridiculously faster than my CPU despite "only" operating at a few hundred megahertz. Tons of stuff can be trivially offloaded to the point where the CPU is just coordinating things, and we hardly even need such a low-latency connection, at least for non-game-related task.

ARM chips are so small, cool, cheap, such a small power draw that they're insignificant next to everything else on that board, but there are still things that even a modest ARM chip could do much better than a GPU. Still, it's not a replacement for a good CPU -- it's more a console on a card, and still not really, you still almost certainly want a decent CPU doing some of it.

anyhow, graphics AND game logic(game physics) are very closely connected.

I didn't say physics, I said logic. Physics is traditionally part of it, but it's getting to the point where it could be as external as graphics. There's a lot of stuff which doesn't need to impact gameplay, and would be problematic if it did. For example:

...a game is full of let's say grass thats shaded, but while that grass has no meaning to gameplay or even ai's field of view).

Suppose the grass were treated as solid, so that it was difficult to walk through -- the player could easily be "stuck" between blades of grass. Obviously, you want to move past that to even more realistic physics, where the player simply tramples the grass. Still, as a player, I'm not in complete control of my avatar, so for a lot of situations, it makes sense to give me a relatively simple environment. Probably the cleanest solution is to treat the field of grass as a single surface with the special property of "has grass", so if we want it to have gameplay effects, do it from that perspective.

Affecting AI FOV is similar -- tricky to do right, probably much easier to just say "Hey, there's grass there," and treat it as a solid block with a fixed value of translucency, so you're less likely to be noticed/shot if you're hiding behind it.

Do that, and you avoid a bunch of hard problems, you hopefully avoid the NWN issue, but you can also have tons of individual blades of grass, so vivid you could smell them, waving in the wind. That's the kind of thing I would think you could do without the CPU, both to improve the eye candy and free the CPU up for more interesting things -- AI, maybe.

Re:Does anyone actually listen to him

[Anonymous Coward]

Shut the fuck up Donny, you're out of your element.

Re:Does anyone actually listen to him

[Desler]

Great, but John Carmack admitted he didn't write the code and the derivation of the magic constant goes back many years prior to stuff SGI did.

Re:Does anyone actually listen to him

[Stormwatch]

Crucially, if you look up "gamer" under Google images, I'm on the first page

Lemme check... holy crap, is that really you? Man, you were awesome in '300'.

Re:Does anyone actually listen to him

[Daniel Phillips]

Judging from the Rage trailers it is safe to say that JC has set the bar higher once again. It still looks like Quake with cars so I'm not much interested in actually playing it, but interestingly you can see some intrusions from the Bethesda culture in the form of ambient banter and quests. It seems like a no brainer that John has already turned to the truly open world problem so Bethesda can realistically use his next engine for a proper walk-around.

Re:Does anyone actually listen to him

[mikael]

Still fascinating though.

It's always amazing how there is a faster way of doing calculations in using a few simple instructions rather than one complex instruction. Swapping registers using XOR instructions, using SUB to clear registers, and using integer arithmetic to manipulate floating point data were the ones I heard about.

Automata Engine 1.0

[SICKECHO]

The Automata Engine 1.0 looks to be a step in the right direction, some of it's features:


* multilayer 3D canvas, composed of pseudo-voxels
* voxel-based sprites, composited via ink effects
* 3D sprite-based lighting
* cellular automata rule engine
* multiple rendering paths for optimization
* multithreading
* audio engine, configurable via externally defined "rules."
* time-sliced stats module -- allows sound to be tied to the number of voxels, for instance
* game levels and level transitions
* movers, colliders, streakers (objects that add cells into the environment)
* two camera impementations: simple and "follow"
* XBox, Windows, and soon Windows Mobile 7


Relevant links:
http://www.newlifeinteractive.com/main/
http://www.youtube.com/watch?v=mOu9QhWGla0

Re:Does anyone actually listen to him

[ifrag]

At the time, it probably was faster, which is good because Quake III ran on some really old hardware. Unfortunately on the CPUs of today it's actually slower, at least with the 20k or so operations I benched with.