Okay I took a quick look and got it working. The problem was that your shader handler (shader/init.lua) was written for an older löve version and could not work but because it catches basically any exception and prints strange error messages instead you did not notice. * it used love.graphics.drawq ...

I'd love to help but but your description seems a bit vague. Are you having trouble getting your code to run or don't you know where to start? Do you have any existing code that you want to add on to or are you starting from scratch? One: How do I use multidimensional arrays in the case of creating ...

If you ever get through your list, I'd love some more involved feedback on my ludum dare entry http://www.ludumdare.com/compo/ludum-dare-29/?action=preview&uid=28506 I'm currently in the process of creating a much improved post-ld version and would be especially interested on any gameplay relate...

Mhm today I went down from #55 to #70. Apparently there was a mistake in ranking calculations which has now been fixed?

My entry didn't fare too well, stats-wise: #1980 Coolness 22% and that's it. I didn't expect anything at all, since it's not even finished. But it's an improvement over my previous one, which was a total failure (I didn't have anything playable after two days). So I can't complain. Doesn't that jus...

Without your code and just your description I'd say that your problem is that you let your player move/fall anywhere and If you discover that he is on an invalid position you adjust his position. That's generally not what you want to do as judging how to fix an invalid position is not easy (as you j...

I just wanted to congratulate you on your rating! Of all games I played this ludum dare, Safety Blanket was my absolute favourite!

My game got a pretty satisfying rating: #53 Theme 3.97 #55 Overall 3.92 #96 Fun 3.72 #168 Mood 3.56 #187 Innovation 3.64 #197 Humor 3.13 #381 Audio 3.03 #626 Graphics 3.05 And it's very obvious what I need to do to get better the next time: Graphics and Audio! It's interesting to see that Overall i...

After sitting down with a pen and some paper I managed to figure out what I was doing wrong. When shearing for a value k into x and y direction at the same time, screen coordinates (xs,ys) for a point (x,y) are calculated like this: xs = x + y * k ys = y + x * k The reverse (what I was looking for) ...

First, let me thank you for taking the time to help me! However I think my post was unclear. I'm not shearing first into x and then into y direction, I'm shearing into both directions at the same time. I found the source of my conversion problem, though: If I use shear before drawing something like ...