Game Processing Order: Difference between revisions
Jump to navigation
Jump to search
(Created page with "left|caption == Game processing order == Here is an overview to show the order in which things get done during an average frame of playing MTA. Th...") |
(Add onClientPedsProcessed) |
||
| Line 1: | Line 1: | ||
[[File: | [[File:Game_process_order.png|left|caption]] | ||
== Game processing order == | == Game processing order == | ||
Here is an overview to show the order in which things get done during an average frame of playing MTA. | Here is an overview to show the order in which things get done during an average frame of playing MTA. | ||
| Line 6: | Line 6: | ||
The [[onClientHUDRender]] event is triggered before GTA renders the in-game HUD, so it the best place to apply any full screen effects that you want 'behind' the HUD. | The [[onClientHUDRender]] event is triggered before GTA renders the in-game HUD, so it the best place to apply any full screen effects that you want 'behind' the HUD. | ||
The [[onClientPedsProcessed]] event is triggered after GTA updates bone transformations for all peds. This event can be used for updating bones. | |||
Revision as of 01:20, 24 November 2020
Game processing order
Here is an overview to show the order in which things get done during an average frame of playing MTA.
The onClientPreRender event is triggered after GTA updates the world, and is the ideal place to do dxDraws that are in some way attached to world elements.
The onClientHUDRender event is triggered before GTA renders the in-game HUD, so it the best place to apply any full screen effects that you want 'behind' the HUD.
The onClientPedsProcessed event is triggered after GTA updates bone transformations for all peds. This event can be used for updating bones.