LÖVEly!

Just for the sake of reference and completeness, issue what I created in 3DreamEngine for this topic https://github.com/3dreamengine/3DreamEngine/issues/67 (in case anyone else tumbles over this same topic).

I simply used git submodules to insert some external libs. Sue that approach is not everyone but worked for me

Hopefully LÖVE 11.5 will be released soon, i.e. due to nasty bug appearently in 11.4 within luajit, which caused rather nasty havoc for me running in circles to understand why impossible things where happening in app.

Just pretty please (sure I can cover my case by compiling binary myself, but...)

ok, I've had my app running for 20+min now in bacjground, and it's still working fine. With LÖVE 11.4, couldn't run it this long without hitting strange issues (like all objects disappering, random "table" becomes nil/number and such). Thus with pretty good confidence I state that LÖVE 11....

Compiled LÖVE 11.5 from the HEAD of main, doing trials to see if it fixes oddities I've encountered.

LÖVEly, learned importanat didbit on how Lua and "pairs" actually works in iteration

I presume you meant something like this, function for_in_pairs(t, fn) local k, v = next(t) while k do fn(k, v) k, v = next(t, k) end end foo = { c = 'this', d = 'that' } for_in_pairs(foo, function(k, v) print(k, v) end) However, 300+ "for pairs" calls is pita to convert Q: any ideas when n...

Try replacing any and all pairs loops with calls to next; luaJIT has/had a bug with pairs

Marvellous! I will try that, you may have saved my sanity, Sanity-San

*BUT* this drives me nuts, [START: addObject-3] ----------1/3 (addObject-3)-------------------- ... meshes: Cube: Cube (36 vertices) ... ----------2/3 (addObject-3)-------------------- -1.1102230246252e-16 ----------3/3 (addObject-3)-------------------- nil ------------------------------ stack trace...