Red Orchestra 2: Heroes Of Stalingrad/LevelDesign/OptimizationGuide: Difference between revisions
(Created page with "=Optimization Guide= ==Introduction== The purpose of this document is to give information on the guidelines used to optimize the maps inside RO2. These guidelines worked for...") |
No edit summary |
||
Line 1: | Line 1: | ||
'''''Optimization Guide''''' | |||
=Introduction= | |||
The purpose of this document is to give information on the guidelines used to optimize the maps inside RO2. These guidelines worked for us. If you are a community level designer and/or artist you may find this document useful. This document will cover the various approaches and the reasoning behind decisions so that the reader may be able to avoid pitfalls when making levels for Red Orchestra 2. | The purpose of this document is to give information on the guidelines used to optimize the maps inside RO2. These guidelines worked for us. If you are a community level designer and/or artist you may find this document useful. This document will cover the various approaches and the reasoning behind decisions so that the reader may be able to avoid pitfalls when making levels for Red Orchestra 2. | ||
=Preliminary Work= | |||
There is a small amount of setup work that must be completed. | |||
==RODebugPosedPlayer== | |||
We have made a tool for level designers and artists that are used to gather statistical data about maps called Posed Players. The purpose of the Posed Player is to have a placeable actor to simulate a player in a scene. It has the capability to be used as a camera during profile stage. All of which I will go over now. | We have made a tool for level designers and artists that are used to gather statistical data about maps called Posed Players. The purpose of the Posed Player is to have a placeable actor to simulate a player in a scene. It has the capability to be used as a camera during profile stage. All of which I will go over now. | ||
===Actor In Tree=== | |||
[[File:RODebugPosedPlayerActorTree.jpg|RODebugPosedPlayer in Actor Tree]] | |||
The RODebugPosedPlayer actor is found at Actor -> RODebugPosedPlayer | |||
===Properties=== | |||
[[File:RODebugPosedPlayerProperties.jpg|Properties of RODebugPosedPlayer]] | |||
*Pose: The pose, or stance, the posed player will be in when spawned | |||
*Weapon: The weapon the posed player will be using when posed | |||
*Pawn Type: German or Russian | |||
*Can Possess: Allows the user to possess this posed player using the '''PossessPosedPlayer''' console command | |||
*Description: Small description on what this posed player is - OPTIONAL | |||
====Available Poses==== | |||
[[File:RODebugPosedPlayerProperties_Pose.jpg|Available Poses for RODebugPosedPlayer]] | |||
The pose will not make a difference in regards to performance and optimization. It was added so if you wanted to stage a scene for screen shots or something along those lines, this allows you to put the posed player into various positions. | |||
====Can Possess==== | |||
[[File:RODebugPosedPlayerProperties_CanPossess.jpg|Can Possess Changes Color of RODebugPosedPlayer to BLUE]] | |||
===Placing Actor in Map=== | |||
====Create a NEW sublevel==== | |||
[[FILE:LevelBrowser_CreateNEW.jpg|Create a new sub level]] | |||
====Posed Player Placement Guideline==== | |||
*Expected player count is 64 player which would be the worse case scenario in regards to performance | |||
*Use Can Possess on posed players that have vantage view on a particular high traffic area/areas of performance pits | |||
*Any particular player SHOULD NOT see 100% of the map nor players |
Revision as of 12:07, 6 July 2012
Optimization Guide
Introduction
The purpose of this document is to give information on the guidelines used to optimize the maps inside RO2. These guidelines worked for us. If you are a community level designer and/or artist you may find this document useful. This document will cover the various approaches and the reasoning behind decisions so that the reader may be able to avoid pitfalls when making levels for Red Orchestra 2.
Preliminary Work
There is a small amount of setup work that must be completed.
RODebugPosedPlayer
We have made a tool for level designers and artists that are used to gather statistical data about maps called Posed Players. The purpose of the Posed Player is to have a placeable actor to simulate a player in a scene. It has the capability to be used as a camera during profile stage. All of which I will go over now.
Actor In Tree
The RODebugPosedPlayer actor is found at Actor -> RODebugPosedPlayer
Properties
- Pose: The pose, or stance, the posed player will be in when spawned
- Weapon: The weapon the posed player will be using when posed
- Pawn Type: German or Russian
- Can Possess: Allows the user to possess this posed player using the PossessPosedPlayer console command
- Description: Small description on what this posed player is - OPTIONAL
Available Poses
The pose will not make a difference in regards to performance and optimization. It was added so if you wanted to stage a scene for screen shots or something along those lines, this allows you to put the posed player into various positions.
Can Possess
Placing Actor in Map
Create a NEW sublevel
Posed Player Placement Guideline
- Expected player count is 64 player which would be the worse case scenario in regards to performance
- Use Can Possess on posed players that have vantage view on a particular high traffic area/areas of performance pits
- Any particular player SHOULD NOT see 100% of the map nor players