Collision Placement and Performance...

sdvermillion

I am having some issues with collision detection. It is inconsistent with detection (see code). I check for collision at two different places yet .collision() only detects a collision inside my keyTracker if statement such that "collided there" is printed to the console.

The filter is correct as collision is detected at at least one place but when I change it's location in the code, performance suffers. What am I missing here?

$.playground().registerCallback( function() { if( $( '#player' ).collision( '.' + $.gameQuery.tilemapCssClass + ', .solid' ).length > 0 ) { console.log("collided here"); } if( jQuery.gameQuery.keyTracker[65] ) { var nextpos = $( "#player" ).x() - 5; if( nextpos > 0 ){ $( '#player' ).x( nextpos ); if( $( '#player' ).collision( '.' + $.gameQuery.tilemapCssClass + ', .solid' ).length > 0 ) { console.log( "collided there" ).length); $( '#player' ).x( nextpos + 5 ); } } } //... }, 50);

selim

I'm sorry but I'm not sure I understand you exact problem, I'll ask you a few question to narrow down what's happening exactly:
- Is a collision detected by the two calls in your example or only one ? (only in the keyTracker for example...)
- Or is it that the collision detection only works when you print something to the console too ?
- Is the code slower when the collision detection occurs outside of the keytracker ?

sdvermillion

Sorry about being ambiguous in stating my problem. The problem is is that collision is only detected in the keyTracker and not in the call outside the keyTraker.

sdvermillion

I found the solution to my problem. When I detected a collision with a solid object, I push the player back such that the player is not colliding with it anymore... which is why there was no collision detected with the first call.