* GetWalkableAreaAt I just migrated my test project from 3.4.1 to 3.5.0 and it was working on 3.4.1. Coordinates are player.x and player.y. I think they are room coordinates?
According to the manual, GetWalkableAreaAt requires screen coordinates, so in scrolling room it will require adjustment with GetViewportX()/Y().
I will test that myself soon though, I recall we had some problem with detecting walkable areas (although that could have been another version).
* I can explain it with an easy example :
if (cChar.Frame == 35) {
cChar.ChangeView(X);
}
In this simple code, the engine doesn't wait to change the view till the frame number 35. Instead, It changes the view immediately. Whatever the the actual frame number is, the engine thinks It's 35 and executes the command.
But that's technically impossible if only Character.Frame is not working, it's about how "==" operator is working then, because Character.Frame itself cannot know what number you are comparing to. Either things are completely messed up in the engine, or there is something else in the script that affects that.
Could you for example log the current frame value somewhere, like print on a GUI label and see how it changes?
EDIT: I did a very simple test, which looks like this:
function repeatedly_execute_always() {
lblScore.Text = String.Format("Frame: %d", player.Frame);
if (player.Frame == 6)
{
lblScore.Text = lblScore.Text.Append("+");
}
}
This prints character's frame value on label, and adds "+" only if it's particular frame.
Show Posts