Rpg Vx Ace problem after Intro.

[cha0sw01f]

(Sorry if this isn't in the correct place)..

So today I decided to make a game and put in an intro. It basically freezes once I get transferred to the 2nd area.

here's the Event:

Spoiler

@>Fadein Screen
@>Set Weather Effects: Storm, @0, Wait
@>Text: -, -, Transparent, Top
: :Text here
@>Text: -, -, Transparent, Bottom
: : Text here
@>Text: -, -, Transparent, Middle
: : Text here
@>Text: -, -, Transparent, Top
: : Text here
@>Fadeout Screen
@>Transfer Player:[Town](025,0470, Up
@>Exit event Processing

And then it goes to my town and here's the script that run automatically after the player is transferred there:

Spoiler

@>Set Weather Effects: None, @0, Wait
@>FadeinScreen
@>Change Party MemberL Add [Natalie]@>Exit Event Processing

And it's frozen and I can't move...

 

[Alexander Amnell]

Change your second 'exit event processing' events to 'erase event' instead. Exit event processing doesn't do what you think it does, it actually only stops anything underneath it from running, it doesn't stop a parallel or autorun event from triggering again. (and erase event will only erase it until you return to the map, so it will successfully fix your weather effects and such.) For the first event, you will want to turn on a self switch at the end and create a blank page with that self switch as a condition so that the text doesn't appear every time you enter the first map (unless it is a scene only map and you cannot access it later.)

 

[Andar]

And then it goes to my town and here's the script that run automatically after the player is transferred there:

Spoiler

@>Set Weather Effects: None, @0, Wait
@>FadeinScreen


@>Change Party MemberL Add [Natalie]


@>Exit Event Processing

And it's frozen and I can't move...

No, that is not the entire event - and most likely the problem is in that part of the event that you refused to display above ;-)
Autorun-Events automatically loop once per frame, which means that "exit event processing" only aborts the current loop, having it restarted the next frame.


You need to switch off any autorun or parallel process event if you want them to stop - make a second evend page, condition that second page to a self-switch, do not change anything else on that second page (leave it empty and on action button), and then replace the "exit event processing"-command with a "control self-switch ON".


If that is not your mistake (or next time when you have an event problem), please post screenshots of the entire event - an event is more than only the content area, and very often the bug is in the settings outside the content area - like it was probably here.


EDIT: Or use the erase event like said above if you want to restart the event whenever you enter that map - as said we can only guess what you've planned to do because you didn't show us the entire event.

 

[cha0sw01f]

No, that is not the entire event - and most likely the problem is in that part of the event that you refused to display above ;-)

Autorun-Events automatically loop once per frame, which means that "exit event processing" only aborts the current loop, having it restarted the next frame.

You need to switch off any autorun or parallel process event if you want them to stop - make a second evend page, condition that second page to a self-switch, do not change anything else on that second page (leave it empty and on action button), and then replace the "exit event processing"-command with a "control self-switch ON".

If that is not your mistake (or next time when you have an event problem), please post screenshots of the entire event - an event is more than only the content area, and very often the bug is in the settings outside the content area - like it was probably here.

EDIT: Or use the erase event like said above if you want to restart the event whenever you enter that map - as said we can only guess what you've planned to do because you didn't show us the entire event.

Yeah.. I'm new to the way to put out this stuff sorry I'll try harder next time...

 

[Shaz]

Show the WHOLE event, not just the commands. The problem with stuff like this is usually in areas OTHER than the list of commands.