Lighting Dynamics Demo

[spynaz]

Alright, thanks guys!

[xXxMoNkEyMaNxXx]

Here, I made a pixel effect version completely from scratch:

spynazPE.love

For those who can use canvases and pixel effects.

(815 Bytes) Downloaded 301 times

I couldn't bear your insisting to index tables with strings, why not just use Lua? Instead of

Code: Select all

table["index"]

simply do

Code: Select all

table.index

[Ref]

Ah!
Lumens doesn't seen to work as expected - just changes diameter of spotlight, not it's intensity (alpha), see demo.

[Davidobot]

I like the new version over the previous one.

[xXxMoNkEyMaNxXx]

It changes the intensity fine on my computer... you have to remember that it's a reciprocal function.

I like the new version over the previous one.

Me too, the trees look cool
If you were talking about Ref's vs mine.

I think that I might have messed up with the way I draw the effect, but I'm sure it can be fixed easily enough.

[Ref]

Sorry, couldn't resist!
Don't bother looking at demo if you don't have 72 seconds to waste.

[Jasoco]

I couldn't bear your insisting to index tables with strings, why not just use Lua? Instead of

Code: Select all

table["index"]

simply do

Code: Select all

table.index

Serious question, but is there a drawback to doing that? Is one slower or something or is it just a readability thing?

I use that first method when needed. Like if I need to refer to a table entry through the use of a string variable. For instance:

Code: Select all

table = {
  entry1 = "Hello!",
  entry2 = "Nope!"
}

num = 1
var = "entry"..num

print(table[var])

> Hello!

[bartbes]

They are equal, but it is way more readable. Consider writing _G["myImage"] = _G["love"]["graphics"]["newImage"]("some/image.png").

And yes, for indexing with variables that is the only way, the 'dot-syntax' only works for names that are also valid identifiers (roughly equatable to potential variable names), but keep in mind that that's a different operation altogether, anyway.

[miko]

Sorry, couldn't resist!
Don't bother looking at demo if you don't have 72 seconds to waste.

Its 72 seconds of processor time (because of os.clock()), so if on my laptop it runs at 60fps with 0.20 load, then it takes 360 seconds (6 min) to complete. For wall-clock time, you need os.time().

[Ref]

Thanks!
Didn't appreciate the difference!
Docs say:
"os.clock() Return CPU time since Lua started in seconds."
Thought seconds were seconds - that CPU seconds were then same as Universal seconds.
Good catch!
Really appreciate input.
Edit:
Turns out on my computer that the os.clock() and os.time() happen to give the same elapsed time for this demo.
Demo actually is terminated by bee.buzz:isStopped( ) - when music is over.