- CryENGINE 3 Cookbook
- CryENGINE 3 Cookbook
- Credits
- About the Authors
- www.PacktPub.com
- Support files, eBooks, discount offers and more
- Support files, eBooks, discount offers and more
- Support files, eBooks, discount offers and more
- Why subscribe?
- Free access for Packt account holders
- Preface
- 1. CryENGINE 3: Getting Started
- 2. Sandbox Basics
- Introduction
- Creating a new level
- Generating a procedural terrain
- Terrain sculpting
- Setting up the terrain texture
- Placing the objects in the world
- Refining the object placement
- Utilizing the layers for multiple developer collaboration
- Switching to game mode
- Saving your level
- Exporting to an engine
- Essential game objects
- Running a map from the Launcher
- 3. Basic Level Layout
- 4. Environment Creation
- Introduction
- Creating your first time of day using the basic parameters
- Adjusting the terrain lighting
- Using the real-time Global Illumination
- Editing HDR lighting and the effects for flares
- Creating a global volumetric fog
- Creating a night scene with time of day parameters
- Color grading your level
- Creating a photo realistic ocean
- Improving your sky with clouds
- Making it rain in your level
- 5. Basic Artificial Intelligence
- 6. Asset Creation
- Introduction
- Installing the CryENGINE 3 plugin for 3D Studio Max
- Creating textures using CryTIF
- Setting up units to match CryENGINE in 3ds
- Basic material setup in 3ds
- Creating and exporting static objects
- Creating and exporting destroyable objects
- Using advanced material editor parameters to create animation
- Creating new material effects
- Creating image-based lighting
- 7. Characters and Animation
- 8. Creating Vehicles
- 9. Game Logic
- Introduction
- How to beam the player to a tag point from a trigger
- Making the AI go to a location when the player enters a proximity trigger
- Debugging the Flow Graph
- Creating a kill counter
- Rewarding the player for reaching a kill goal
- Displaying the player's health through a Flow Graph
- Changing the player camera through key input
- Creating a countdown timer
- 10. Track View and Cut-Scenes
- 11. Fun Physics
- 12. Profiling and Improving Performance
- Support files, eBooks, discount offers and more
- Support files, eBooks, discount offers and more
- Support files, eBooks, discount offers and more
In this recipe, we will look at one of the many methods to make a quick kill counter for the player based on the HitInfo taken from raycasted weapons (melee, bullets, and so on) and also using the Grunt entity types as the targets.
- Begin by placing an AreaTrigger entity onto the map to use as the container for the Flow Graph.
- In the RollupBar, click on the Entities button.
- Under the Triggers section, select AreaTrigger.
- Right-click the newly placed AreaTrigger and create a new Flow Graph. Name the Flow Graph as
KillCounter. - With the Flow Graph open and the new AreaTrigger selected, add in the following nodes:
- 2x Game:LocalPlayer
- Crysis:HitInfo
- Math:Counter
- HUD:DisplayDebugMessage
- Set Crysis:HitInfo Enable to true (1).
- You will also need to place down at least one Grunt within the level. Then with the Grunt selected, go back into the AreaTrigger Flow Graph and right-click Add Selected Entity.
- Link the Flow Graph together as follows:
- Game:LocalPlayer entityId out to Crysis:HitInfo ShooterId in.
- Crysis:HitInfo TargetId out to entity:Grunt Grunt # in. (This will change to<Input Entity> as these nodes take the entity IDs.)
- entity:Grunt Dead out to Math:Counter in in.
- Math:Counter count out to HUD:DisplayDebugMessage Show in AND message in.
- Second Game:LocalPlayer entityId out to HUD:DisplayDebugMessage Choose Entity in.
- The resulting Flow Graph should look like the following:
Using the Crysis:HitInfo node within the Flow Graph checks to see what the player is hitting with any Raycasting weapons such as bullets or melee for example. Each time the player lands a hit on an entity, the TargetId is then triggered in this node. As we are comparing against Grunt type entities, it checks to see if that TargetId died. If the Grunt has died from this event, it forwards a true value in the Boolean only once, which gets counted by the Math:Counter. The total value of the Math Counter is then displayed back to the player showing how many times the player has killed the Grunts.
The number displayed will appear in the upper-left corner of the screen after the successful kills have been made:
-
No Comment