Download the latest RypelCam Ut2004 version from here: |
|---|
We do NOT support RypelCam downloaded from any other source. |
In order to emphasize very important information italics has been used, for RypelCam specific terminology underlining has been used. Highlighting is used to identify the exact representation of what you should be typing into the console or the Key you should be looking at. It has three values; Black/Orange is for Console commands. Blue/White is for keyboard keys. Green/Yellow represents 'buttons' on the Rcam GUI menu. |
|---|
Let’s start with a clientside recorded demo. The very first thing you need to do after the demo has loaded is hit Esc two (2) times. It has to be 2 times because once brings up the Demo Control bar. You need to hit Esc again to remove the bar, so hit it 2 times right away. You can NOT key bind this, you have to physically hit the Esc key on your keyboard 2 times for Rc to activate, it will not work any other way. |
With this action you activate RypelCam (Rc) |
To make things easier, understand that everything below this sentence in this tutorial can not function without Rcam been activated by pressing the Esc key at least once after you have started your demo playback. |
|
|
|
Pressing each key again removes what it brought on screen. Take the time to read them and familiarize yourself with each feature, experiment with the settings until you get used to what each command does. Before we move onto understanding how you move around the map with Rc. Let's go throught the functions available on the main menu bar that appears when you press the 'Esc' key once. |
![]() |
| As you can see by the picture the main functions on the menu are the ability to change demo speed, Seek to specific point in the demo, the main Rcam configuration, display properties and the demo file properties. We will deal with each one of these as we need them the rest will be detail in the ' Menus' Section of this Tutorial, but now let's see how Rcam let's us move around a demo. |
|
The text tells you the current spectatorspeed which you can change with Numpad 1 and Numpad 2. And you can get the position coordinates like in the picture by pressing '.' To move use your mouse, use your wasd keys and space / shift for up/down. |
Notice that you can move around the map, even though the demo is paused. If you try to move around in a circle, something stops you from doing a full circle. This happens when the white mouse cursor reaches the end of the screen. To go on with your turn you have to move the cursor into the middle of the screen. You can position it with your mouse when your not moving. So let go of the wasd keys and move your mouse cursor to the middle of the screen. |
So the mouse only changes the spectatorview direction when you hold down a movementkey. If you want to stand still and look around you can do this by first setting the spectatorspeed to 0. You should use the '1' key for that and use keys '2' - '9' to get speed back quickly. With Numpad 1 and Numpad 2 you can change the speed "softly". |
[x2 = Hit That Key Two (2) Times] |
|
|
|
A CamPoint not only represents a marker as in a physical location marker it is also a time signature and a photographic positioning. Which means it can only happen there at that point & time and the camera can only be looking exactly there when recording. So the actual shape of the CamPoint identifies direction and photographic placement / framing of the camera, internally it marks the point in both time and space at which this event will occur. The time part is only relevant if the timedpath command is activated. |
|
Four (4) CamPoints is the minimum for a Rc sequence. When you have 4 CamPoints a line of white dots automatically draws itself onscreen connecting the CamPoints. That tells you the CamPath is now ready to be saved and it also indicates the path the Rc will take between the CamPoints. |
You save your CamPath from the main menu item 'Open Rcam Configuration' found under the D button and you reload it using the same menu. Hit Esc and from the menu hit D, the following dialog box opens up; |
![]() |
The following dialog box let's you choose a name for your path so type it in and save you work. As you can see it will also list all your previous CamPaths saves. |
![]() |
| If you try to save a CamPath before you have 4 CamPoints then the following message will appear when you try to save your CamPath. |
![]() |
From the D menu you can also load your previous saved paths. Hit ESC followed by D |
![]() |
Now select 'Open Rcam Configuration' and the following dialog box appears; |
![]() |
From there you can now choose wich ever saved Rcam path you need. If you want to dumpframe your CamPath only reload a timedpath after restarting the demo or the game. It is saved in UT2004/saves/RCam_Package.uvx (or whatever name you gave it.) |
|
You don’t have to use these keys to adjust the speed during recording. That can be controlled by Rc while recording. We will discuss this a bit later. |
|
|
|
However if you just want to reposition a CamPoint you don’t have to erase it. First use Numpad '+' and Numpad 1 to select the CamPoint you want to reposition. This also lets you see what the CamPoint sees. You see a counter that can help you determine what CamPoint you currently have selected. |
|
|
|
|
Timedpaths |
As mentioned before it is possible to have Rc control the speed at which it moves through a scene when it is recording. We call this a 'timedpath' it has two values, '0' for off and '1' for on. With correct placement it allows you to synchronize your camera movement throughout a scene to specific action happening within that scene. Let's have at look at how it works. |
| To get a understanding of how timing works in RypelCam you should practice by making a CamPath that flies near a player for some time and distance. |
|
|
Then place your CamPoints at the places AND the exact times at which you want them to be reached. One way of doing this and most accurate way is by pausing the demo/game were ever you need to place a CamPoint and as many times as needed. For Example; |
|
|
This procedure allows you to very tightly integrate the Rc movement throughout the scene to the action within that scene. Keep in mind that even thou Rc has a set limit of 150 CamPoints per CamPath, you should never really need to go past the more stable 50 threshold. (To view how many CamPoints you have currently laid in your CamPath press H. Press H again to hide that menu). |
To help you lay a smoother CamPath, there is a built in "Distance Meter" that tells you how far you have traveled in a straight line from you last CamPoint. Hit the '.' on your keyboard to bring this display up, it also shows pitch, yawn, and x, y, z information. Hit '.' again to close it. |
After you placed all your CamPoints and you are happy with your CamPath, save your work one last time. Before you can DumpFrame (record your CamPath) you have to remove the drawpath (The dotted white line between your CamPoints) from the screen. This will also visually remove all of the CamPoints. |
Removing the drawmode path: |
|
Demo will automatically pause at the start of the timedpath. Switching Rc viewpoint to that of the first CamPoint. |
|
Your Rc is now recording in sync with your CamPath, so exactly how you placed it and what you saw/framed when placing it, is exactly what is going to be recorded. You can also fast forward your demo to a point close to were the CamPath starts, by using the right arrow key on your keyboard or by using the S Button on the Esc menu. But make sure that you stop fast forwarding before the start time is reached! If you fast forward for too long the system will miss you're Rc start time. |
Some users have experienced problems with fast forwarding, which is most likely due to the Unreal Engine itself. It's entirely up to you the way you choose to reach your Rc start point, if you experience problems fast forwarding, then slow down the speed to x2 instead of x4. Or better yet, let it play normal speed until Rc pauses in sync. the max fast forward speed also seems to be demo dependent. Sometimes high fast forward speeds make a demo lagg or sometimes the screen freezes during fast forward even at low fast forward speeds. But often it works fine. |
There will be more specific tutorials covering the various menus and advanced features of Rc. We will provide them as we write them. For now this introduction will get you started on your first TimedPaths and basic features of Rc. Please use the coments form on the last page of this article. Let me know how this was or was not helpful to you. We can not improve it without feedback. Thanks. |
http://rypelcam.net/rcf/index.php?automodule=downloads&showcat=4





Print Article
Send to a friend
Save as PDF