Keyboard ghosting, perhaps?
The article explains what might be the problem, be sure to check out the keyboard application at the top of the page! For example, press 'A', 'Z' and then 'X'. Now, press 'Z', 'X' and then 'A'.

Hi, spectralcanine (nice username) You’re pretty much right. Parsing the skeletal data should be pretty straight forward, as you mentioned, rotation and translation matrices should do the trick. Obtaining the actual animation data is the tricky part, because of that, I thought of using blender for a...

I can't run the love file, there appears to be something faulty in main.lua, line 18. This should be fixed now. When importing FBX all skeletal information is discarded. I only care for polygon data and object transformations. A well-adapted custom blender exporter would be ideal! Has anybody of yo...

This is really interesting, I've been toying with the idea of a 2D skeletal system for real-time animation in löve for a while, I'm highly interested on this, mainly because I'm also using blender. I am just starting to learn blender with the intent to use character animations in 2D-games. FBX impor...

Ah! thanks for your clarification, slime! I have yet to play with löve's thread implementation, I'm a little bit stuck in C at the time, but it's super helpful to know that löve's implementation is a little bit more benevolent.

Hi, I haven’t used löve’s implementation of threads, but I have experience with C threading, so I’d be able to give a basic idea of what this is all about. First, I’d suggest to be cautious about threading, depending on what you are doing, their implementation and debugging could be somewhat difficu...

Interesting, I'll make sure to check this out, thanks for sharing!

This is very nice, micha, excellent work!
I did a quick test and didn't get any weird rope behaviour while swinging with the left and right keys.

The overall effect it is pretty cool, nice rope physics.

Keep it up!

Hi Jasoco,
I haven't carried out any formal test, but according to this (test 4). math.min/max are somewhat slower than the pure comparison approach.

Sounds like you're removing an element from a table using a “normal” loop instead of a “reverse loop”. If you remove an element while looping from the first to the last element, the table reshaping could be skipping an element, take a look at this example: local someTable = { "apple", &quo...