Here's a build of LÖVE 11.2 you can try which should have this issue fixed. We're planning to do a full release of 11.2 including fixes for this issue soon. https://bitbucket.org/slime73/love_macb ... efault.zip

Here's a build you can try which should have this issue fixed. We're planning to do a full release of 11.2 including fixes for this issue soon. https://bitbucket.org/slime73/love_macb ... efault.zip

There's no easy complete fix, but a really simple workaround is to only call setMode in keyreleased instead of keypressed.

Sorry about that, I've updated the link with fixed download links. We're working on getting an official release out ASAP.

You can access custom vertex attributes you've set via mesh vertex formats, by declaring them with the same name as an attribute in the vertex shader code. e.g. in your shader code you'd do something like this, since you have the "VertexNormal" attribute as part of your mesh's vertex format: attribu...

It's not a mistake, it's just work that hasn't been done yet.

If the canvas is an array texture or cubemap or 3D texture, you need to give it a layer/cube index to render to as an argument in setCanvas.

It's not an implementation detail, it's consistency and extensibility. Previous love versions already had colors in the 0-1 range... but only in shaders, which is not consistent. love 11 also allows you to create and modify ImageData at different bit depths than 8 bits per color component (e.g. via ...

I think only the World:setCallbacks page should have it, since almost every love.physics object method that modifies the object can't be used (that's a lot of things to document), whereas World:setCallbacks is what affects those functions, so people who don't use that method won't care about those n...

EliterScripts wrote: ↑

Sat Oct 13, 2018 2:58 am

string.pack()

string.unpack()

I've got good news, those are already in love (in a different module, but the code for them is from Lua 5.3's source code.)

love.data.pack

love.data.unpack