Try doing this at the top of your main.lua, because sometimes writes to console get buffered and it might not print in time or some sillyness like that:

io:setvbuf("no")

I think yes but for a commercial one where this me to risky(but im just beginner coder) eventually some other's here will answer aswell ? and i personally would eventually recommend opengl or c++ + opengl or lua + opengl and write your engine from scratch not with a already somewhat overblown and p...

You can also smartly combine these to create a system where you can tell whether a key is in a specific state out of 4: - pressed this frame, - held this frame (press happened earlier), - released this frame, - not being held Also, probably better to use the scancode parameters and love.keyboard.isS...

Hi,

First of all, stop using rar, and compress your project with regular zip instead, that's the only format supported in most places.

Second, dll and other libraries that aren't lua files won't ever work from compressed archives, you'd need to copy them out to the save folder for them to work.

What do you mean exactly by generating graphics and sounds? Procedural stuff? Sure, you can programmatically make both graphics and sounds with ImageData and SoundData objects, for starters.

Why do you want to move it into main.lua? Just leave it in conf.lua... also, it does not "belong to function love.load()" whatever that means. If you want to defer creation of the window, you still need a conf.lua file where you do... in your case, app.window = false, then in love.load, yo...

Looks really interesting; always good to have fellow generative audio / audio synthesis afficionados who want to use löve for these kinds of stuff!

It seems like i did speak a bit soon, since after i wrote that post, Sasha did push a change to the repository called "Workaround for Windows 7 runtime compatibility", so maybe it might still be able to work.

Hi; I remember this issue being posted about on the discord; this wasn't a conscious decision on löve's part as far as i know, it's just that PhysFS, what löve uses for love.filesystem stuff, has some things hardcoded at compile time that stopped working when 11.5 had a new version of that included ...

you should not use löve's event mechanics like that; yes, you should implement your own.