Perhaps someone could actually explain some of these supposedly-real workarounds? Last time I asked about this, I had someone suggest (with no examples or clear explanations of how this is even possible, naturally) that I drop it down to just one render layer and use stencils to deal with various dr...

I was using canvases. The moment the source image climbed above about 512x512 pixels, everything slowed to a snail's pace, because the laptop this is running on has an Intel Graphics 520 on-board graphics chip. It's rendering somewhere around 20 layers at a time.

If you want an Image that you can change, a Canvas might be more useful. You can both draw onto a canvas, and draw the canvas onto the screen. I tried that. It didn't work, because I still could not find a way to not throw the entire massive original image at the system every time it needed an upda...

Fine, then let's try a different approach: how do I efficiently render an image that changes constantly to screen, without throwing the entire original massive image at the GPU every draw cycle?

That doesn't help me, at all. I'm not asking for a lesson on PC architecture here, I'm trying to figure out how the hell I update an Image with changed ImageData and not have it be crazy-slow. I'd even settle for a way to render ImageData that doesn't involve the absurdly limited Image object.

Well then how am I supposed to DO this? I do not understand. Declaring a new image every time I need to update the on-screen image is not acceptable, but you're telling me basically that this is the only way I can do what I'm trying to do. How am I supposed to render a changed image to screen withou...

I get that. That's not the problem. The problem (at least as best I can tell, it might be something with my code that's wrong) is that a declared Image does not update when the ImageData that it was declared with updates. Let's say we have this: fooimage = love.image.newImageData("foo.png"...

So here's the deal: I have an ImageData that takes a chunk of another ImageData that's exactly the size of the user's screen, because rendering everything offscreen as well as onscreen is for chumps. But I cannot for the life of me figure out how I can efficiently render this, because as best I can ...

So this is kind of awful. I've discovered that LOVE does not update love.mouse.isDown(), love.mousepressed, or love.mousereleased if any key on the keyboard is being held down when a mouse click is inputted. It only relents if 1. a new key is pressed or 2. the existing key is released. Is there any ...

480 draw calls eating 12% of the GPU power sounds about right, in by book that's pretty generous actually. Batching will reduce the amount of draw calls. If you were using version 11 or later there should be autobatching enabled; check the output of love.graphics.getStats. That's the thing, though:...