report

report

report

edit – maybe not is on my xp hdd

edit 2 – nope works fine

report

report

report

Scandalon, you are basically right in all your statements. Proceduralism is not any holly grail, it’s not a magic technology and it’s also in no way tight to the gpu (most visual effects see in movies are procedural shaders!). However as you point out, as gpus grow so fast in computing power while their memory keeps evolving very very slowly i capacity and speed, replacing texturemaps with computations makes more and more sense. Sure one cannot always “compute” the desired texture (or yes??), but there a few which are easily computable (like terrain textures, clouds, grass, etc), so it makes sense to start replacing those textures which were traditionally texturemaps with procedural textures. So yes, I agree with everything you say.

report

I have that exact same chipset – 1950XTX.

Elevated isnt dx10 is it?

report

report

It’s not that impressive when you realise how little is done by the app and how much is done by the directX libraries.

In fact, nothing is done by the dx libraries, other than the compilation of the shader. The rest is don all in-demo. Of course basics things like handling the keyboard, writing to video memory, initializing the sound device and so on are done will win32 api calls, we made a 4k demo, not a 4k operative system and gpu driver.

Also the music and light show suggests they are from Northern Europe. No-on else could be so straight-facedly cheesy, surely?

Actually I’m spanish, altough the musician and the other coder are danish. I created all the images just by visually remembering the spanish mountains, which are right now full of snow and I miss a lot.

Antivir finds a virus in every exe.

Don’t worry, no viruses, I promise. It’s just that the compression technique we used (Crinkler) is confusing the antiviruses.

report

Cedge/Jetsetlemming: (IANAGraphicsProgrammer, but I have a basic/vague comprehension of what was listed in the readme)

I understand the need to temper the “OMG, this is teh WIN!1! – Fallout 4 will b 4w3s0m3!” reaction, I think you’re shortselling the potential and muddying the waters a bit, esp. as it seems “procedurally generated” is kind of a fuzzy term to begin with. Procedural Content is not the be-all, end-all magic silver bullet, but one more, new(ish) tool.

“Procedurally generated” doesn’t have to mean “random”, but it can – perhaps “procedurally created” would be more precise for that definition. Some games you wouldn’t want any random world geometry, others, you’d want all random, and most “open world” type games you’d want a mix. (See the developer diaries for Subversion)

This demo shows very well some of the possibilities of doing much/most of the geometry work on the videocard, which often goes hand-in-hand (erroneously) with what people mean when they start talking about “Procedural Content” – but using the card is one method of doing PCG, not the method itself. (The light-rays in tune to the music was nifty – sure you could do that with most traditional engines, but I have a feeling this implementation was…more elegant.)

As for the “small but slow” argument – everything’s a tradeoff, but in this case, if I understand the readme, the rules for coloring a pixel are running directly against the mesh, they’re not even generating a texturemap, per se, procedurally. If I’m wrong about that, or for others that *do* first create a standard texturemap…why is that bad? If you can shave a few gigs off my steam download (or whatever) and then generate a texture cache on first launch of the starting area(s), and then generate the textures in the background, do it! (Preferably give me a “small, medium, large” disk space usage option.) Also, don’t forget moore’s law has a way of making previously unthinkably slow things possible.

report

Not frozen, just… nada.

report