#REPLAY PLAYER ONE HOW TO#
#REPLAY PLAYER ONE CODE#

In the level's 'World Outliner', select all of the EditorCubeXX-actors and set their property 'Static Mesh Replicate Movement' to true. You can safely skip to the next section if your project is already set up for multiplayer games. The engine treats the replay recorder like a networked client, even in a single player game, so that replicated data is automatically recorded. In order to let the engine record gameplay, you need to make sure that our actors are properly replicated. This step will enable and load the DemoNetDriver for you, which is the actual recorder. +NetDriverDefinitions=(DefName='DemoNetDriver',DriverClassName='/Script/Engine.DemoNetDriver',DriverClassNameFallback='/Script/Engine.DemoNetDriver') After the project is created, open the project folder on your hard drive and navigate to ReplayTutorial/Config/DefaultEngine.ini, open it, and add the following statement at the end of this file: You can also include this tutorial in your own project, but for the sake of simplicity I will display it for a clean one. I chose the 'First Person Example' as a base, however any Example should do. To begin with, create a project of your liking.

Finally, there is still bug that needs to be fixed, this is described in 'Conclusion, Bugs'.

The last section 'Adding the ReplaySpectator Controller' introduces a PlayerController to handle a Replay Playback and a Widget to interface between User and PlayBack.

The section 'Testing it' is a good spot to make a break from this tutorial and an invitation to play around.

#REPLAY PLAYER ONE HOW TO#

In 'MainMenuUI' I show you how to make a simple Replay Browser to manipulate previous records.

In 'Blueprint (UI) Implementation you will find a minimalistic Set-Up to start/stop Recording from Blueprints.

In 'Adding our C++ code' I introduce some functions to a new GameInstance class that will start/stop recording and Find, Rename, Watch and Delete Replays from Hard Disk.The section 'Replication' sets up the First Person Example to replicate its Projectiles, Cube Meshes and to let Clients call Server_Fire.In the Initial Setup I'll show you how a new project is initially configured to be able to deal with Replays.(NOTE: Replays can't be recorded or played back in PIE mode. While the tutorial does include some c++ code, I will show you how to expose the necessary methods, so that they can be called from blueprints. My method might not be the optimal one, but it works and I'd like to share it with those who want to work with replays as well.

#REPLAY PLAYER ONE CODE#

I spent quite some time reading through the engine code to be able to implement this in my own projects and was surprised that no one covered it in a tutorial yet, so here goes. This tutorial is intended to show you how to easily create a basic replay system, enabling you to record game data to a hard drive and play it back at a later time.

8 Adding the ReplaySpectator Controller.

Replay System Tutorial - Epic Wiki # Replay System Tutorial

Replay player one