Menger Sponge Explorer

[GijsB]

Edit : Pathtracer Added!

Edit : Movement and 'slider' controls are now scancodes and fractal iteration loop is unfolded.

Edit : Movement speed can be changend and camera is now proper thanks to raidho36.

Edit : Sun position editable.

Edit : Fixed for some users.

Edit : All controls scancodes.

Edit : Actual working scancodes.

Edit : Now user friendly with GUI's.

Edit : Right click slider for fine-tuning.

Edit : Realized Offsets of the same 'direction' create the same fractal but scaled differently, so it's normalized now.

Edit : Render Resolution can be changed

Oh and please share you discoveries by taking a screenshot with the information screen on!
(Screenshot folder is located in %appdata%/roaming/LOVE)

And don't forget to press 'j' for EXTREME PHOTOREALISTIC RENDERING WOOO

[Le_juiceBOX]

Lol laptop crashed.

[skyHights]

It's really cool, I have one problem though.

This is what I see when in normal render mode:

1483927839.png (932.78 KiB) Viewed 10283 times

This is what I see when in ULTIMATE RENDER MODE:

1483927834.png (1.71 MiB) Viewed 10283 times

[GijsB]

It's really cool, I have one problem though.

This is what I see when in normal render mode:
1483927839.png

This is what I see when in ULTIMATE RENDER MODE:
1483927834.png

Uhm yes that is not actually a bug! I implemented Depth of Field and your Focal Length and Aperture are wrong for this shot, literally a camera out of focus. Try to lower the aperture and make the important parts red by changing the focal length. (the red thingies in normal mode show focal length <=> red parts are sharp)

[zorg]

You mind using scancodes instead of keycodes?
Makes it more i18n user friendly that way.

Edit: Works for me otherwise btw, though interestingly the "EXTREME PHOTOREALISTIC RENDERING WOOO" mode lags my PC without me seeing just what is happening; löve reports no extreme CPU or GPU usage... so it's a bit weird...

[raidho36]

Crashed for me. The culprit is the sponge shader. Just having it loaded crashes the program shortly, without even using it to render anything - which crashes it instantly. Something must be terribly wrong with that shader. But also it crashes with a segfault without raising any errors, and that warrants LÖVE source code investigation.

[GijsB]

Crashed for me. The culprit is the sponge shader. Just having it loaded crashes the program shortly, without even using it to render anything - which crashes it instantly. Something must be terribly wrong with that shader. But also it crashes with a segfault without raising any errors, and that warrants LÖVE source code investigation.

Could be your graphics card actually. But yeah the shader is BIG.

You mind using scancodes instead of keycodes?
Makes it more i18n user friendly that way.

Edit: Works for me otherwise btw, though interestingly the "EXTREME PHOTOREALISTIC RENDERING WOOO" mode lags my PC without me seeing just what is happening; löve reports no extreme CPU or GPU usage... so it's a bit weird...

I didn't know keycodes aren't universal, expect scancodes tomorrow. Also that is kind of weird, GPU usage should be through the roof...

[raidho36]

No I in fact believe it's your graphics card - 5 bucks says it's Nvidia. There could be very serious problems with the shader, but your GPU will try munching through them instead of raising errors, obscuring the very existence of the very real issues from you. For this single reason, Nvidia GPUs are the worst choice for graphics code development. But I digress; I'm not the only person who has it crash on them, and the evidence (runs fine for most but not on ATI and probably Intel) suggests that there are problems with the shader that Nvidia obscures but that are apparent on other vendor graphics, being a very common problem for Nvidia owners who try developing graphics code.

[zorg]

Raidho36: If you mean me, then yeah, i have a combined nvidia gtx 960 and gtx 750 ti (with latest drivers that support the latter)
Maybe it reports gpu usage wrongly, idk.

[srcn]

demoscene is not dead