Apparently, Apple is deprecated OpenGL to force developers to move towards Metal. How will that affect Love2d in the medium and long term? Medium-longish term, not at all. Apple formally deprecated legacy OpenGL on macOS like 5 years ago, but it still works. I expect Core Profile OpenGL will contin...

Automatically batched vertices are transformed on the CPU, so TransformMatrix doesn't include the current love.graphics transform in auto-batched draws.

Indeed, almost every love API that accepts a number stores the number in something less precise than a 64 bit float. That's a lot of APIs.

I don't see what else changed that could be causing it, so it'd be nice to be able to check. The internals of love.graphics have been substantially rewritten since 0.10. It takes advantage of more OpenGL 3+ features when available than before, which runs more risk of encountering bugs inside graphi...

raidho36 wrote: ↑

Wed Apr 18, 2018 6:09 am

With that in mind, I'm not even sure why it's there.

Mostly so people can (theoretically) still use raw OpenGL if they really really want to, and are really careful.

The love.graphics.flushBatch wiki page describes it.

Are you sure you downloaded the LÖVE 11.1 iOS source? It works for me, and has Metal.framework listed under the frameworks dropdown and set to weak-link: Screen Shot 2018-04-15 at 8.38.56 PM.png Also note that you'll need to change the code-signing and bundle identifier settings in the General tab o...

Your screenshot didn't get posted correctly, but if the errors are related to linking Metal functions, the iOS source code for LÖVE 11.1 – released today – resolved that (by weak-linking with Metal.framework).

Following on the heels of LÖVE 11.0 's release two weeks ago, version 11.1 is now out! 11.1 is a small – but important – bug fix release. It resolves a few issues introduced in 11.0 including love.graphics.setCanvas failing to work in many situations, stencils breaking on older phones, and t.console...