- Joined
- Jul 22, 2014
- Messages
- 5,624
- Reaction score
- 5,104
- First Language
- English
- Primarily Uses
- RMVXA
In the past I've created several maps which had a few dozen parallel process events running a lot of different functions, and it's created moderate amounts of lag. No surprise there.
But yesterday I made a mostly empty map with about 200 Action Button/Event Touch events (6 pages each) grouped up in the same area (in order to create a randomized chessboard-style minigame), a couple of very light Parallel Processes, and nothing else... and it created significant amounts of lag (dropping the FPS on my middle-of-the-line desktop to about 20-40). When I only had about 30 of these events insead of 200, it was running smoothly at 59 FPS. I was really, really surprised at this, because (if I understand the processing correctly, at least) it doesn't need to actually process the event code for these events and yet the performance seems to be taking a hit.
So I'd like to ask if anyone who knows Ace really well can help me understand what about events requires a lot processing and what doesn't?
Do events themselves take up a lot of processing power? Does it matter whether they have a graphic or not? Does it matter whether they need to be animated? Does the number of pages matter, assuming none of the pages are Parallel Processes? Does any of the event code get evaluated (but not executed) if the event is never triggered? Is there any reason why it might be better to have a Parallel Process event and 200 "dummy" Action Button events rather than 200 Event Touch events with the same code? Is there anything else that might be helpful to know about economizing performance with Events?
But yesterday I made a mostly empty map with about 200 Action Button/Event Touch events (6 pages each) grouped up in the same area (in order to create a randomized chessboard-style minigame), a couple of very light Parallel Processes, and nothing else... and it created significant amounts of lag (dropping the FPS on my middle-of-the-line desktop to about 20-40). When I only had about 30 of these events insead of 200, it was running smoothly at 59 FPS. I was really, really surprised at this, because (if I understand the processing correctly, at least) it doesn't need to actually process the event code for these events and yet the performance seems to be taking a hit.
So I'd like to ask if anyone who knows Ace really well can help me understand what about events requires a lot processing and what doesn't?
Do events themselves take up a lot of processing power? Does it matter whether they have a graphic or not? Does it matter whether they need to be animated? Does the number of pages matter, assuming none of the pages are Parallel Processes? Does any of the event code get evaluated (but not executed) if the event is never triggered? Is there any reason why it might be better to have a Parallel Process event and 200 "dummy" Action Button events rather than 200 Event Touch events with the same code? Is there anything else that might be helpful to know about economizing performance with Events?

