1.1 : Put the RCam306.u into the MyGames/UnrealTournament 3/UTGame/Published/CookedPC folder.

1.2 : Now open the UTGame.ini in MyGames/UnrealTournament 3/UTGame/Config and replace the line DecalManagerClassPath=UTGame.UTDecalManager with DecalManagerClassPath=RCam306.RCamDecalManager
If you use the rk demowatcher (download) you need to do the same change in the UnrealTournament 3/UTGame/Config/DefaultGame.ini

1.3 : RypelCam will use a lot of keys on your keyboard by default(theres a keybind overview at the end of this tutorial), so it can happen that your current keybinds conflict with RypelCam. Cause of that it is recommended to make 2 inis. One for RypelCam and one for playing. RypelCam for example uses all the the Numpad keys together with some alphabetic and numerical keys. So you should remove your keybinds, if they onflict with the RypelCam binds. Though not removing them will not mean that RypelCam wont work. If you have a keybind, for example on the Numpad keys, and you hit that key when RypelCam is activated, both functions will be executed. The normal and the RypelCam one. So you will notice when one of your keybinds makes problems together with a RypelCam bind.
You should especially rebind the LeftArrow and RightArrow keys cause they will get annoying otherwise, since by default they make you look left and right, but i assigned them the same functions they have in UT04 where they are used for demospeed control.

1.4 : For recording you should set bSmoothFrameRate=True in the UTEngine.ini file. And should set MaxSmoothedFrameRate to a value that your PC can really handel. Especially when you record a demo with Fraps it produces a smoother vid if you set MaxSmoothedFrameRate to the same value you set in Fraps for recording. Be aware that recording smoothly with all details up requires a very good PC cause the engine doesent slow down when recording to match your PC. Teh moviemaking scene will experiment with different ways to record using either Fraps or dumpframe methods. RypelCam comes with a experimental dumpframes function. You can activate it with the 'F2' key.

You should also set 'NetServerMaxTickRate=60' and 'LanServerMaxTickRate=60' in the UTEngine.ini. That will tell the Game to record your Demos with a higher framerate. UT3 interpolates frames in demos so that you can get a high framerate anyway but when you set ServerMaxTickRate higher you should get more "real frames".

2.1 : If youve done the steps in Chapter 1 correctly RypelCam should automatically load at demostart.

2.2 : First you should get yourself familiar with the spectatorcam. To view it either hit the right mousebutton or the 'k' key. The difference is that the right mousebutton will teleport the speccam to your current location unlike the 'k' key, which will teleport you to the speccam instead(and the 'k' doesent work in some situations). Then you can fly around with it using your normal controls. But to move the speccam when the demo is paused you have to use the 'w,a,s,d,shift,leftalt' keys. You can pause the demo with the 'DownArrow' key (notice that 'spacebar' will unpause the demo. That was Epics idea and i couldnt deactivate that yet.).
You can change the speed of the speccam when the demo is paused to fixed speeds with the '1' to '9' number keys or you can change the speed smoothly with the 'Numpad1/Numpad2' keys.

2.3 : Basic Democontrols:
You can pause the demo with the 'DownArrow' or the 'Pause' key. You can slow it down using the 'LeftArrow' key and you can speed it up using the 'RightArrow' key. Hitting the 'UpArrow' switches the demo back to normal speed.
You can use the 'L' key to lock the rotation to the viewingdirection of the player your currently watching if youre in behindview mode (only in serverside demos)

2.4 : If you want to make Camerapaths you first need to know what a Campoint is. Campoints are RypelCams "keypoints" that you place in the map to define the way your Camera should take. The Cam will fly through all the Campoints and will compute a smooth path between them. A Campoint also saves "keytimes" and the Cam can compute its speed based on this times. However this is optional. You can also control the speed of the Cam by hitting the speedkeys, which are also used for the speccam('1-9' and/or 'Numpad1/2'). You can read more about timing in chapter 4.

2.5 : To make a Campath you have to create at least 4 Campoints. To create a Campoint fly with the speccam('k') to a point in the map where you want a Campoint and then hit 'Numpad5'. A Campoint will be created that saves location,direction(in which your looking) and the time of its creation.
This already completes a basic Campath.

2.6 : After you have placed at least 4 Campoints you can make the Cam fly through them by hitting the 'Numpad3' key. '1-9' and 'Numpad1/2' keys can be used to control its speed. You can make the Campath invisible for recording with the 'Numpad9' key. It will cycle through 3 different draw modes(everything invisible, everything visible, only Campoints but not the path between them visible).
To add more Campoints go back to the speccam view('k' key) and then you can go on placing Campoints. You can create up to 98 Campoints and you can preview your Campath anytime with 'Numpad3'(but remember the "at least 4 Campoints rule". With less then 3 Campoints you cant play your path). You can remove Campoints with 'Numpad4'.

2.7 : It can happen that RypelCam doesent allow you the creation of a new Campoint. You will get a message in the console when that happens. This happens when you try to create a Campoint that is too close or too far away from the previous Campoint. What "too close" or "too far away" means depends. It depends on the smallest distance between 2 Campoints in your path. The longest distance between 2 Campoints can not be greater then 15 times the smallest distance between 2 Campoints in your path. And the smallest distance is not allowed to be 15 times shorter then the longest distance. This is for performance and optimization reasons.

3.1 : You can save a Campath with 'F4'. And you can load a Campath with 'F5'. Campaths are saved in the UTRypelCam.ini, which can only store 1 Campath. If you want to store multiple Campaths or different versions of your Campaths you can make copys of the UTRypelCam.ini.

3.2 : In the UTRypelCam.ini you can also find some other RypelCam parameters that you can change to your needs if you like.
At the moment entrys that might be of interest to you are 'drawdetail',' 'speccamspeed','basic_speed2','PauseCamMouseSensitivity' and 'tpdelta'.
- drawdetail : Defines at what detail level (how many dots) the Campath is drawn.
- speccamspeed : Defines the default speed of the speccam(this will only affect the speccam when the demo is paused though).
- basic_speed2 : Defines the default playbackspeed for your Campaths when not in timed path mode(See 4.3 for timed path mode).
- PauseCamMouseSensitivity : Defines the Mouse Sensitivity when moving arround with the Speccam in Pause mode, cause your normal Mouse Sensitivity doesent apply to the Speccam in Pause mode.
- tpdelta : You can play arround with this value if timed paths doesent seem to work for you. See Chapter 4.3.

In the ini you can also see the saved values of a Campath(a Campoint is called Flag internally and in the ini) about location,rotation,fov,time. If you think you know what youre doing and if you want to make small adjustments you could do it right in the ini.
Notice that 'Z' indicates the number of saved Campoints in the ini, even if sometimes there seems to be more Campoints saved. If 'Z' is 4 for example and there are datasets for 6 Campoints, the last 2 Campoint datasets are datasets from an old path and you should ignore them just like they will be ignored when this ini is loaded. They are still there in the ini till they get overwritten, but they wont be loaded. Only as much Campath datasets as 'Z' indicates belong to the current path and will be loaded with it when you hit 'F5'. That also means if you might want to manually add Campoint datasets to the ini dont forget to increase the value for 'Z' too.

4.1 : To control the speed of the Cam is obviously a very important thing to do. To control the speed with RypelCam is not difficult but to make it look "good" and to make it flow nicely with the players/things you want to record, is kinda difficult and you will have to practise that.
You have two possibilities to control the Cams movement speed. Both have advantages and disadvantages.

4.2 : Controlling the Speed manually:
When you are activating your Cam with 'Numpad3' it will automatically put you in the Cam view and it will travel along the path automatically. Then you can use the keys '1-9' and/or 'Numpad1/Numpad2' to change the Cams speed, the same way you can change the speccam speed when you are in speccam(and if the demo is paused).
The advantage of this method is that you have full control over the speed and when to accellerate/deccellerate. The disadvantages are that you have to be fast in order to keep up with the gameplay and that it can look a bit more jerky then the automatic timing.

4.3 : Controlling the speed automatically:
When you place a Campoint it saves the time of its creation. The Cam can use this information to adjust its speed and to accellerate/decellerate smoothly on its own. Then it will automatically reach the times of the Campoints.

In order to do this you not only have to take care of "where" you place your Campoints but also you have to take care of "when" you create them. Its creation time is saved in each Campoint of the path.
So save a path with 'F4' and after you reloaded the demo and the path('F5'), hit 'J' to activate the automatic timing mode. Then the demo should pause at the right time(the time when you created your first Campoint) and as soon as you unpause('ArrowDown') the Cam should start moving on its own. You can fast forward the demo till the starttime for your timed path is reached but you should go back to normal speed at least shortly before the starttime is reached! Otherwise the propability that the demo wont pause at the moment of the starttime is very high.

Notice that when you created your Campoints when the demo was paused, the Campoints will all get the same time(since the demo is paused) and automatic timing wont work. So if you want to use/test automatic timed paths dont place your Campoints in pausemode. Also dont speed the demo up or down when you create your Campath otherwise your Campath will not work properly in timed path mode.

Sometimes it might happen that the Cam doesent start or starts too late. You can then edit the StartTimedPath_Later_seconds and StartTimedPath_Earlier_seconds in UTRypelCam.ini to modify the timedpath start, or try to set 'tpdelta' in the UTRypelCam.ini to a higher value. If you set it higher you also might loose some accuracy though thats why you should only set it as high as needed for the autopause to work.

6.1 : You can delete the last Campoint with 'Numpad4'. This way you can delete the whole Campath too, by just deleting the last Campoint iterative till all Campoints are deleted. This is also the only way(besides reloading a old path) to delete or to reset the whole Campath or parts of it.

Notice that when you delete so much Campoints that only 3 or less are left, the Campath disappears cause you need at least 4 Campoints in a Campath. So then you need to add Campoints again till yoreu back to at least 4 Campoints.

6.2 : You can change the position of a Campoint. To do this first select it with 'Numpad-/+', then switch back to the speccam and fly to a new location for that Campoint and hit the 'Z' key. This will move the Campoint to this new location. Only the position and not the time of a Campoint is changed with this.

7.1 : If you want to make your Cam a littlebit more unique and dynamic you can assign some Campoints different values for roll and fov. RypelCam will then compute smooth transitions between this settings as soon as the Cam is started.

7.2 : To do this first select a Campoint with'Numpad-/+' and then you can use 'Numpad7/8' to change roll or fov. "Roll" means making the Cam lean left or right. By default 'Numpad7/8' will change roll, but if you hit the 'O' key it will switch into a mode where 'Numpad7/8' changes the FOV value of the selected Campoint instead.
When you hit 'Numpad7/8', hold the key down. Only release the keys when a setting you like is reached.
(Once youve made this changes to one or more Campoints you can hit Numpad3 to start the Cam and to see the result of your changes.)

8.1 : Remember that when you place a minimum of 4 Campoints, RypelCam will compute a smooth Campath that connects these Campoints. In some situations you might want to change this path without changing the Campoint locations. For example if you placed the Campoints too close to a hill, the resulting Campath might cut through the hill what will not look so pretty.
With Pathedit Mode you can change the path so that it doesent cut through the hill anymore. Another example would be to change the shape of your Path for sharper or softer turns.

8.2 : First you have to hit 'F3' to enable this editing Mode. After enabling it you can use 'NumPad+'/ 'NumPad-' to select a Campoint. To change the path, use 'NumPad1' and/or 'NumPad2' and the path between the selected and the prior Campoint changes. You can switch back to the free camera to keep track of the path changes.

F4 - Saves current Cam

F5 - Loads a Campath from the RypelCam.ini

F3 - Goes into Pathedit Mode. See Chapter 8.

Numpad1/2 - Changes either Speccam speed or Camera speed. Or if you are in Pathedit Mode this keys can change the shape of the Campath. See 2.2, 4.2 and 8.

Numpad-/+ - Selects a Campoint so that you can roll it, replace it, or to change the path next to it. See 6.2, 7 and 8.

Numpad5 - Creates a new Campoint. See chapter 2.

Numpad3 - Puts you into Cam view and manually starts the Camera. See 2.6.

Numpad6 - Selects a Projectile(rockets etc.) as target. See chapter 5.

Numpad9 - Makes the Campath invisible. See 2.6.

Numpad7/8 - Used to change roll/fov for Campoints. See Chapter 7.

O - The 'O' key(not the zero key) is used to switch between rollmode and fovmode. See chapter 7.

1-9 - The Number keys on your keyboard can be used to change the speed of either the speccam(when demo is paused) or your camera quickly. See 2.2.

Numpad4 - Deletes the last Campoint. See 6.1.

Z - Assigns a Campoint a new location. See 6.2.

K - Switches to Speccam from the current location. See 2.2.

RightMouseButton - Switches to Speccam without teleporting the Speccam to your current location. See 2.2.

WASD,SHIFT,LEFTALT - used to move the speccam(at least in pause mode). See 2.2.

U - Lets the Speccam travel through walls/hills/anything. In other words the speccam will not collide with the world anymore.

P - If you hit this key and pause the demo while youre playing a Campath, the Cam will also stop moving. Otherwise it will continue moving(but only if it is not in timedpath/automatic mode. In timed path mode the Cam will not move when the demo is paused). See Chapter 4.

UpArrow - Sets Demospeed to normal. See 2.3.

DownArrow - Pauses the Demo. See 2.3.

PAUSE - Pauses the Demo. Does the same as DownArrow. See 2.3.

LeftArrow - Slows the Demospeed down. See 2.3.

RighArrow - Speeds the Demospeed up. See 2.3.

H - Switches HUD on/off if available.

M - shows RCam related additional info in the HUD.

L - Locks Rotation to Viewtarget. See Chapter 5.

J - Enables Auto Pause for Timed Paths. See 4.3.

I - Deactivates weapondisplay in 1st person view.

RightCtrl - Switches between 1st and 3rdperson mode(behindview command).

F2 - Activates experimental dumpframes command. This records bmp screenshots. You might want to edit the "ScreenShotPath=..\UTGame\ScreenShots" in the UTEngine.ini to specify where the screenshots are saved(they will take a lot of space).