It's probably better if you follow Plu's advice and iterate over a line of values and add them to the table. Here's an example that works if you want to have a value on every line. I kind of hardcoded the 13 in there, so that's not the prettiest example. map = {} for line in love.filesystem.lines(&q...

What are you using that you need to enable that extension?

Another thing: The built-in function 'inverse' only comes with GLSL 1.4 and up. LÖVE targets 1.2 if you don't override it.

I think LÖVE 0.8.0 has some issues with properly allocating the texture units for the GLSL uniforms and it looks like you actually ran into this. I do not know a workaround for it. 0.9.0 had some changes in that area and should work better. Often, your only resort with them is rewriting the whole th...

This is an issue in LÖVE. You have to keep a reference to the Image around or the garbage collector will collect it and the shader is sad that his image disappeared. For example the line where you load the image. If you mark the sky variable as a local, then Lua doesn't need it anymore once main.lua...

Does the Console run as a separate process on Windows though like Terminal does on Unix? Yes and no. The consoles are handled by a Windows service and the processes just request their allocation or attachment. The console window itself is associated with the process that allocated it (Not that this...

love.window.setMode will be the function used in LÖVE 0.9.0 to set the window properties. In LÖVE 0.8.0 use love.graphics.setMode

That's right, their separate Lua environments and don't know of each other. The only way threads can communicate (in LÖVE 0.8.0) is through their message boxes that you access with the functions [wiki]Thread:set[/wiki], [wiki]Thread:get[/wiki], [wiki]Thread:peek[/wiki] and [wiki]Thread:demand[/wiki]...

The love.thread page mentions that the thread only loads love.thread. The require function will use love.filesystem function to find the Lua file and you need to load the module to make it succeed. Just put a require("love.filesystem") at the top of thread.lua.

The callbacks are not defined when LÖVE starts up. The code in love.run just checks if they exist and calls them if that's the case. There's no timing code in LÖVE to force some kind of rules upon love.update or love.draw when they get called. They always get called in the same order and it tries to...

Uhm. I still think the names you pass to newImage don't match the file names in the archive.

If you want us to have a look again, upload the new file.