I have just updated AGS to the latest version. I opened one of my game made in an earlier version and then the script for one of the rooms stopped to work.
I have a room with just a message that should be shown for a short while and it should then move on to the next room. I use the following code in Players enter screen (after fadein):
Wait(100);
NewRoomEx(1, 160, 203);
This worked in version 2.56 (I at least think that was the version I had) but now it just doesn't change room and because of that the game freezes since there is no other way to move on from this "message room".
Strange, should work. Are there anything in the "player enters screen (before fadein)", "player enters screen (for the first time)" or "repeatedly execute" events?
Nope! That's all the code there is for that room!
Can you upload the room file in question for us to investigate the problem?
I guess I could but I don't see how that would help since I already posted all the code that exists for that room. As I said it worked just fine in the earlier version of AGS but in the latest version it just doesn't change room.
Where can I upload the file?
If you don't have webspace yourself, you may try zipping the crm file and use this:
http://www.2dadventure.com/ags/upload/upload.html
(but don't abuse the use of the uploader)
Try bringing up the debug console immediately after entering the room, and see if it attempts to change the room.
I was wrong, the code in Players enter screen (after fadein) are as follows:
Wait(100);
FaceLocation(EGO, player.x, 0);
NewRoomEx(1, 160, 203);
When I press Alt+X to terminate the program it says that it was aborted on the line with the FaceLocation call. The player is hidden in this room so that might be the reason (I just wanted him to be turned in the correct position before changing room) however this worked just fine in the earlier version of AGS.
If you have "Characters turn to face location" switched on, yet the character is hidden when you call FaceLocation, it will hang v2.61.
This has been fixed in the latest beta (actually, now the Final) for 2.62, so try upgrading to that and see if it fixes the problem.
Thanks CJ, but where can I find v2.62?
the first post of this very topic
Oh... You mean the first thread of this forum... Thanks!
youre right, im sorry, i thought this was within the 2.62 release thread, not the bug report thread. i should have just posted a link.
No worries! I downloaded v2.62 and the problem is solved. Thanks again!