{"author_name":"GFM","cat":"LD #26","comments":[],"epoch":1367592360,"likes":2,"metadata":{"p_key":"42776","p_author":"GFM","p_authorkey":"7375","p_urlkey":"78411","p_title":"Weird Bugs","p_cat":"LD #26","p_event":"LD26","p_time":"1367592360","p_likes":"2","p_comments":"0","p_status":"UPD5","us_key":"7375","us_name":"GFM","us_username":"\/author\/gfm\/","event_start":"1366934400","event_key":"16","event_name":"LD26"},"text":"

During the compo, I ran into a bug that made two pushable box (which should collide and stop) run over each other.\u00a0 I’ve been trying to fix that, but now nothing makes sense anymore… The gif bellow can better show it (and also show a new stage! :)).<\/p>\n

\"gfm_ld26_box_bug2\"<\/a><\/p>\n

As you can see, the first time it collides perfectly… but the second time (which should be the exact same situation), they overlap each other… One thing that I was able to notice (after dumping some frame-by-frame information to a .txt file… >_<)\u00a0 is that there may be a relation with their order in the object list (FlxGroup, if you’ve ever used Flixel).<\/p>\n

Ok, this gave me a (stupid) idea. I’ll check which is the left most one and pass that as the second object to the collision method (FlxObject.separate). I’ll post soon with results.<\/del> Obviously, it didn’t work. \u00ac\u00ac<\/p>\n \n

Tags: as3<\/a>, bug<\/a>, Flixel<\/a>, postcompo<\/a><\/p>","time":"May 3rd, 2013 9:46 am","title":"Weird Bugs"}