LÖVE 0.7.2 Released

[LuaWeaver]

Game fusion! Hello .exe!

[headchant]

Any chance for shaders in 0.80? Would be epic.

[BlackBulletIV]

Yeah, there's been a lot of talk about shaders. I'm hoping they'll come, because I'd love to be able to use some of the awesome things they have to offer.

[Jasoco]

It seems that 0.7.2 no longer loads a conf.lua file from a projects "Identity" folder. I loaded up my old Adventure Engine in preparation to start working with it again, dusted it off and loaded it up and it wasn't loading the conf.lua file that my game creates. Instead, since there is no conf.lua file in the actual project, it reverted to defaults. It took me a few minutes to figure out what was going on. The give away was when I noticed the titlebar said "Untitled" instead of the project name.

Is this by design or a bug?

Not that it's a problem. I won't be creating the configuration file from now on instead setting the settings after load. But I was curious. (I originally made it as a workaround for choosing game resolutions. It would create the conf file with the width and height hard coded in when you set it. Now I am just using the built-in resolution setting functions.)

[thelinx]

Yeah, I don't see a reason to generate a conf.lua.

If you want to set a resolution based on previously saved information, set t.screen to nil in your conf.lua, then launch a window manually in love.load.

[bartbes]

At the time conf.lua is loaded love hasn't decided where the save dir is at yet, so it can't load it from there.

[Jasoco]

Makes sense. It just took me off guard and made me realize I needed to redo the entire project anyway.

Older projects would just set their identity as a folder with the projects filename by default.

[bartbes]

They still do, unless the name is ".", but maybe that now happens later on.

[nonesuchplace]

By the by, I just tried out Love in OS X Lion, and it works.

[slime]

By the by, I just tried out Love in OS X Lion, and it works.

There's a known issue with fullscreen in Lion (caused by SDL), it will be fixed by the time 0.8.0 comes out I think.