7 replies to this topic

[Mitchfork]

I have encountered a rare but repeatable collision bug while testing.  
 
If the Quest Script Rule "Sprite Coordinates are Float" is enabled, and Link is 8.5 pixels north of a solid combo, Link can walk right through it right-to-left or left-to-right.  See the picture below for this in action:
 

 
Due to certain actions that cause the coordinates to round off (e.g. colliding with a solid wall will cause the engine to snap Link to the nearest whole pixel) this can sometimes be very hard to trigger, or very easy - but if you play around with it while constantly tracing Link's Y coordinate, it seems really consistent.  There may be additional pixel values that can cause collision to fail, but 8.5 north is for sure an issue.

EDIT: The applicable rules are:

• ON - Diagonal Movement
• OFF - Large Hitbox
• ON- New Hero Movement
• ON - Disable 4-Way Movement's Gridlock

Edited by Mitchfork, 02 December 2020 - 07:31 PM.

[Emily]

Do you have the rule "New Hero Movement" enabled? If not, enable it.

[Mitchfork]

I'm 99.9% sure that it's enabled - I should have listed all of those rule settings though. Can't check the file right now, but I'll update the post info when I can.

[Mitchfork]

Updated the post with the quest rules settings that I am using.

[Emily]

Can you replicate this with `New Hero Movement` off?

[Mitchfork]

Can you replicate this with `New Hero Movement` off?

 

No - with New Hero Movement off, Link's coordinates are always whole pixels.  At -8 and -9 pixels, there's no collision problem.

[Emily]

Good, that helps narrow this down. I'll try to look into this once finals are done.

[Timelord]

<Grumble, grumble...>