Fine collision on Fusion 2.5+ Bugged (android)

[diefox]

Hi, I just purchased Fusion 2.5+ and im pretty sure that it messed up with Fine Collisions on android (it works fine on Pc runtime)

I hade a slope detection system in my custom movement that just do not work at all now on my android, but it worked absolutely fine prior to installing fusion 2.5+

Is it a known bug? Did I miss something in 2.5+?


ps.: The forum suggested that I post this on the BugTracker... but it seems to be offline =(

[diefox]

hi again, ive been trying and trying and i just dont know how to fix it, fine collision just seemed to stopped working on all objects, could you try opening my mfa and see if that happens on your end too?

ps.: it will work on pc, working on android is the problem im having

mfa and apk on the folder below.
https://www.dropbox.com/sh/avmco54cj...riRqPiz2a?dl=0

[Fernando]

can you narrow where to look

seems fine here

Capture.PNG

Capture.PNG

[diefox]

is it running on android? try going right where there is some kinda of slope and tell me if it goes up properly

bcause even though fine collisions are on it seems to be colliding with the whole box now.

press J to jump

[Fernando]

yes i tested also that but not sure how the collision is set for all block

please notice that in windows and android have different collisions methods


windows

fne x fine = fine
fine x box = fine
box x fine = fine
box x box = box

on others runtime

fine x fine = fine

fine x box = box
box x fine = box
box x box = box


in your slope

Capture.PNG

yellow remark is done by me just to make you see that the collision is set as box in the cyan block downgrading the collision to box, I will check in more deep later.

===============================
Added an example collisions seems fine, if you need for me to see this problem I will need from you a simple mfa for me to see your implementation

[diefox]

Fernando, thank you VERY VERY MUCH!!! I didnt know about this fine and box collision order, it helped me a lot!

heres what i did wrong in case someone happen to have the same problem:

When I got CF2.5+ I noticed via profiling that the player slope detection was taking too much time to process (it was ok on windows, but it was laggy on android) so I unchecked fine detection on all the colliders and thats when it all went wrong. In the end it was the amount of tiles (active objects) with "inactive outside frame" set to No that was making the app laggy =)

In case you still want the mfa to see how I implemented it im happy to give you!

[Fernando]

Glad everything is working now, please always keep in mind this rules for collisions, there is no need for your mfa.

[fnkycoldmadeanr]

This is very useful information thanks Fernando

[wpd]

why is it that windows and other runtime
Have different collision approach?

Is it gonna be the same in the future update?
Like multitouch obj, it was recently patched to be the same on windows and android right

[Fernando]

think on speed.

android is not as fast a PC, hope in the future the collisions can behave like windows runtime.

i will not expect this in near future, but could be after 2021