Weird backdrop collision issue...

[Konidias]

Okay so I've set up a custom movement system and I have the character being able to grab a wall or solid object that they are up against. The character can also get "pushed" if they walk up against the corner of a solid object or obstacle, like in Zelda A Link To The Past.

Now here's the weird issue... Both of my scripts for collision against an active and collision against a backdrop are identical (aside from swapping the active for backdrop, etc)

But I get these weird issues with the backdrop collision object. First, if I run my game level via the run frame button, my character can't grab the top of the backdrop obstacles but can grab the top of actives just fine. Also the corner sliding when the character presses down on a top corner works fine with an active but doesn't register with a backdrop obstacle, and instead lets the character slide from nearly anywhere on the top of the obstacle.

That's not the weirdest part...

Then I run the entire game from MMF and go to the same level. The grabbing of obstacles from the top now works. The sliding is fixed. But a new problem occurs where if my player is above an obstacle, turns to the side to not face the obstacle and then grabs, they still grab... the air. Which is weird.

Why am I getting two different problems/scenarios when running the frame separately and running the whole app?

I'm not setting anything differently when jumping to a frame from the main app. So I would think that at least I'd experience the same issues. But I get different results running the frame and running the app.

It's kind of hard to fix the problem when it isn't a problem half the time and is a totally different problem the other half...

Is there something wrong with the backdrop collision in MMF? Is there some way I can fix this? I can set up a test app and see if it occurs again there, if needed.

[uprize]

You really should upload an example.

[Crash86]

Yep would be easier to have a look.

[mobichan]

Is your app only one frame? If not, are you initializing some variables or data or something in the other frame?

[Konidias]

It's multiple frames. I'm loading data and such from other frames but the data wouldn't have anything to do with the movement or collision detection or controls. The conditions for the corner detection and grabbing of obstacles rely solely on the objects in that frame, and those objects aren't being altered by variables outside of the frame.

If nobody has any idea why this is happening, I'll make an example when I get home from work and if it's still breaking, I'll post it up in the archive. If it's not breaking, I'm going to be even more confused. :p

[Konidias]

Nevermind, I'm dumb. I seemed to have fixed it. Apparently it was some weird issue with the action point/hot spot on my overlap detectors. I've fixed it now, but it was still odd that it was doing different things via run frame and run app. Still can't figure that one out.