Personally, I'd make these scripts: viewBoundsLeft = GetViewBoundsLeft(x), viewBoundsTop = GetViewBoundsTop(y). Then use them as playerBoundsLeft = GetviewBoundsLeft(player.x) and similarly for playerBoundsTop. Then I'd put the polling code within the camera object. Are the border sizes always the same? I assume they are since they're always right outside of the player view. If they are always the same, you can simplify some of your camera code. When the player view bounds changes from the actual view bounds, you can just lerp from the old view bounds to the new one. The lerping can be done in the camera object, independent of the player code. So basically, when you detect the new view bounds, you begin these separate (as in the code isn't mixed together) but related processes: camera movement, player movement and animation, doors, game freezing.

I don't know how am I going to post this, but.. I was about to stop doing "Raccoon's Way" because of the situation, and was bound to tell you to do it for me. But since I'm an experienced coder (not exactly an expert, but getting into it) and it's my game, I have to [b]TRY[/b]. So in other case, I'm still trying to figure out what you're saying as it's called a "solution". If you can try to make it at least for sensible for me to put out, then I'll gladly do so. If not, that's OK since I'll continue to figure it out. [size=50]And I'm sorry for not posting this earlier.[/size]

Old Drawing Banners

Things I support/others

My favorite theme:

Where do you need help with understanding?