A game's framerate (FPS) is determined by whichever of three threads takes the longest: the game thr...

[github-actions]

A game's framerate (FPS) is determined by whichever of three threads takes the longest: the game thread, the rendering thread, and the graphics. In almost all Core games, the rendering thread is slowest, and responsible for taking game data and sending it to the graphics processor.

---

platform-documentation/src/references/merged_models.md

Lines 22 to 25 in dce2d44

	<!-- TODO: A game's framerate (FPS) is determined by whichever of three threads takes the longest: the game thread, the rendering thread, and the graphics. In almost all Core games, the **rendering thread** is slowest, and responsible for taking game data and sending it to the graphics processor. -->
	Merged models allow Core to run a process when your game first loads to simplify a Merged Model into just the sides that a player might collide with and sends that data to the server.

---

This issue was generated by todo-issue based on a TODO comment in dce2d44. It's been assigned to @StanzillaManticore because they committed the code.

[github-actions]

A game's framerate (FPS) is determined by whichever of three threads takes the longest: the game thr...

A game's framerate (FPS) is determined by whichever of three threads takes the longest: the game thread, the rendering thread, and the graphics. In almost all Core games, the rendering thread is slowest, and responsible for taking game data and sending it to the graphics processor.

---

platform-documentation/src/references/merged_models.md

Lines 22 to 25 in 1cf20e5

	<!-- TODO: A game's framerate (FPS) is determined by whichever of three threads takes the longest: the game thread, the rendering thread, and the graphics. In almost all Core games, the **rendering thread** is slowest, and responsible for taking game data and sending it to the graphics processor. -->
	Merged models allow Core to run a process when your game first loads to simplify a Merged Model into just the sides that a player might collide with and sends that data to the server.

---

This comment was generated by todo-issue based on a TODO comment in 1cf20e5. It's been assigned to @StanzillaManticore because they committed the code.

[github-actions]

A game's framerate (FPS) is determined by whichever of three threads takes the longest: the game thr...

A game's framerate (FPS) is determined by whichever of three threads takes the longest: the game thread, the rendering thread, and the graphics. In almost all Core games, the rendering thread is slowest, and responsible for taking game data and sending it to the graphics processor.

---

platform-documentation/src/references/merged_models.md

Lines 22 to 27 in c43b1b1

	<!-- TODO: A game's framerate (FPS) is determined by whichever of three threads takes the longest: the game thread, the rendering thread, and the graphics. In almost all Core games, the **rendering thread** is slowest, and responsible for taking game data and sending it to the graphics processor. -->
	Merged models allow Core to run a process when your game first loads to simplify a Merged Model into just the sides that a player might collide with and sends that data to the server.
	The graphics processor then visually renders the Merged Model entirely, instead of waiting on calculations for each object on whether or not they are close enough to a player to be rendered.

---

This comment was generated by todo-issue based on a TODO comment in c43b1b1. It's been assigned to @StanzillaManticore because they committed the code.

[github-actions]

A game's framerate (FPS) is determined by whichever of three threads takes the longest: the game thr...

A game's framerate (FPS) is determined by whichever of three threads takes the longest: the game thread, the rendering thread, and the graphics. In almost all Core games, the rendering thread is slowest, and responsible for taking game data and sending it to the graphics processor.

---

platform-documentation/src/references/merged_models.md

Lines 22 to 27 in 5b834cf

	<!-- TODO: A game's framerate (FPS) is determined by whichever of three threads takes the longest: the game thread, the rendering thread, and the graphics. In almost all Core games, the **rendering thread** is slowest, and responsible for taking game data and sending it to the graphics processor. -->
	Merged models allow Core to run a process when your game first loads to simplify a Merged Model into just the sides that a player might collide with and sends that data to the server.
	The graphics processor then visually renders the Merged Model entirely, instead of waiting on calculations for each object on whether or not they are close enough to a player to be rendered.

---

This comment was generated by todo-issue based on a TODO comment in 5b834cf. It's been assigned to @StanzillaManticore because they committed the code.

[github-actions]

A game's framerate (FPS) is determined by whichever of three threads takes the longest: the game thr...

A game's framerate (FPS) is determined by whichever of three threads takes the longest: the game thread, the rendering thread, and the graphics. In almost all Core games, the rendering thread is slowest, and responsible for taking game data and sending it to the graphics processor.

---

platform-documentation/src/references/merged_models.md

Lines 22 to 27 in 339a538

	<!-- TODO: A game's framerate (FPS) is determined by whichever of three threads takes the longest: the game thread, the rendering thread, and the graphics. In almost all Core games, the **rendering thread** is slowest, and responsible for taking game data and sending it to the graphics processor. -->
	Merged models allow Core to run a process when your game first loads to simplify a Merged Model into just the sides that a player might collide with and sends that data to the server.
	The graphics processor then visually renders the Merged Model entirely, instead of waiting on calculations for each object on whether or not they are close enough to a player to be rendered.

---

This comment was generated by todo-issue based on a TODO comment in 339a538. It's been assigned to @StanzillaManticore because they committed the code.