noobTV Camera Guide |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
IntroductionThis guide will walk through all the options one can set for the custom cameras. First they are listed in a table, and then they are explained more extensively. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Property table
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Property explanation |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
How to make a camera? |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Before you can start writing down all the camera's in the camera file, you should first find some nice spots to place a camera. Start LFS and get into shift+U mode, and just fly around for a little while. Play around with the FOV value or the height. Just fiddle around for a little while. Also decide if you want to create a set of camera's that are TV-like, or are ment to make even the slowest hotlap look like a thrilling ride. In the first case, try to find some places that give a good overview on the track and involve less cameramovement to achieve a smooth and pleasant view. In the second case you might want to put the cameras closer to the track, with a higher FOV setting to increase the sense of speed. After you have found some nice spots, start TVcameratool and go ingame. If you get into shift+u mode, you will see that the X, Y, Z, heading, pitch, roll and FOV values are updated every second or so. You fly to the position where you want to place a camera, wait for the values to come to rest, and write them down. You can use the buttons at the top of the TVcameratool window to get higher then 2.6 meter. NOTE: TVcameratool will only work in multiplayer mode! If you want the camera to focus on a car automatically, you can choose to make the fields heading, pitch, roll and/or FOV free. If a certain field is free, noobTV will calculate the best value for that field, to make sure that the car is in the center of the screen. Each field can be set separately, so you can have a camera that has a free heading and FOV, but a fixed pitch. Keep in mind that the roll value is not supposed to work for trackside camera's. Camera's on a line are not so different from pointcamera's, except that they can also make a translational motion. They will do that between the startpoint and the endpoint of the line. Look in the table above for a detailled explanation of the linePositioning property. Now you have to define the area for which the camera will work. For a basic trackside-camera, nodes are a good way to define the area. For special camera's, such as pitcams, use the area function. Nodes: Get out of shift-u mode, and drive your car to the startingpoint. Wait for the values to come to rest, and write down the node value. Then drive to the endpoint and write down the node value. Also see picture 2. Area: Defining an area can be a little bit tricky. You find a cornerpoint by taking the (x,y) coordinates of the car, after you have driven the car to the correct position. The z-coordinate is not necessary. The order of the cornerpoints is important to get right, observe picture 1 closely. If you draw a line connecting the points A to B, B to C, C to D and from D back to A, the lines should not intersect each other. The area can have any shape, as indicated in picture 3. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
![]() |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
![]() |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
After you have collected all the values for a camera you make a new .txt file using Notepad (or any other text editor you like). A typical cameradefinition looks like this: startCam name=Turn One track=BL1R type=point x=1844207 y=-12453335 z=76252 heading=free pitch=free roll=free fov=free areaDef=node startNode=23 stopNode=66 stopCam It might be a wise idea to start making a few pointcameras that are defined using the startNode and stopNode properties, so you get used to the TVcameratool program and the way the .txt files work. You can add as many camera's to a certain file as you like, but from a managing point of view, it might be wise to split your camera-definitions into a few smaller files. Defining camera's in different files does not influence the functioning of a camera at all. Save your camera files to a particular folder, this will be your camera set. If you make your camera definitions available for other people, they can put all your files in a certain folder, to keep the cameradefinitions separate. |