Camera 101
Posted: 27 Dec 2006, 23:13
Hi all, it was suggest that these information maybe usefull to be share.
I spent few hours on how camera works. It is complicated and easy at same time. Up to now, it took me 4 hours to understand this.
I took SteveB Sylverstone track. 1 deleted all info in cam file to keep only 1 camera. Then with that single camera, the POS value works with 3 value the X Y Z
With 1 camera : put the POS at 0.000000, -10.000000, 0.000000 and look down were you are on track. This position on Sylverstone is in middle of grid stat/finish line.
I will use cardianal points to help you figure how (North, South, Est and West)
POS 1st value : is the X distance (from 0 value, the plus value (+) will be the 'south' and minus (-) will be the 'north' position from the 0)
POS 2nd value : is the Z distance (from ground to sky) Plus value (+) is under the ground and the (-) value is getting you close to the sky. A -8.000000 is and excellent position close to a Camera post on top of a pole at +/- 75feets height. A -5.000000 is a cam set close to a barrier height and Zero is flat to ground. Watch out, some track have denivelation that may change the height of cam from ground.
POS 3rd value : is the Y distance (from 0 value, the plus value (+) will be the 'West' and minus (-) will be the 'East' position from the 0)
Exemple, Sylverstone (refer to map curve name to see where it is)
Grid is at 0.000000, -10.000000, 0.000000
Copse curve is around -350.000000, -10.000000, 0.000000
Stowe curve is around 0.000000, -10.000000, 1700.000000
Then you have the FOV value. That one im still not shure. The distance of the previous value is the position (POS) of the cam. If you choose a cam around the track, that you can move the view with your mouse, that is exacly were the cam is located. Thos same cam are the same one that when you look at replay, and they folow a specific car. This is the main problem of few track that we race last year (2006). That is the distance that the cam will be zooming to follow a car. Theyrs 2 value, and im still trying to figure what 1 value do, and what the second do. BUt FOR SHURE a good value is in a range of 10-60. But this depend on how close the cam is from the car. A 10 on 1 cam maybe too close, and too far on another cam. Try this on your test cam and see the difference.
Up to now i only done those test and that is what i understand after 4 hours. This is only what is taken to fix any cam on steveB track of 06 season. Other value may be usefull, but i dont know how the value change will react. I can speculate on them by logic, but not mucth more.
Here the info you need to play with to keep it simple (Position and Fov that i explain up) :
TrackingCam=TrackingCam013 //Last Sector
{
Position=(248.000000, -19.000000, 12.000000)
Orientation=(0.000000, -3.100000, 0.000000)
Fov=(10.200000, 10.000000)
Clear=TRUE
Color=(0, 0, 0)
ClipPlanes=(1.000000, 1500.000000)
LODMultiplier=(45.000000)
Size=(1.000000, 1.000000)
Center=(0.500000, 0.500000)
Flags1=(0)
Flags2=(0)
ActivationLocation=(212.000000, -5.000000, 284.000000)
ActivationRadius=(131.000000)
TrackingRate=(6.000000)
MovementRate=(0.000000)
If any expirement more or just know more, let us know. Hope i was able to help any of you a little.
I spent few hours on how camera works. It is complicated and easy at same time. Up to now, it took me 4 hours to understand this.
I took SteveB Sylverstone track. 1 deleted all info in cam file to keep only 1 camera. Then with that single camera, the POS value works with 3 value the X Y Z
With 1 camera : put the POS at 0.000000, -10.000000, 0.000000 and look down were you are on track. This position on Sylverstone is in middle of grid stat/finish line.
I will use cardianal points to help you figure how (North, South, Est and West)
POS 1st value : is the X distance (from 0 value, the plus value (+) will be the 'south' and minus (-) will be the 'north' position from the 0)
POS 2nd value : is the Z distance (from ground to sky) Plus value (+) is under the ground and the (-) value is getting you close to the sky. A -8.000000 is and excellent position close to a Camera post on top of a pole at +/- 75feets height. A -5.000000 is a cam set close to a barrier height and Zero is flat to ground. Watch out, some track have denivelation that may change the height of cam from ground.
POS 3rd value : is the Y distance (from 0 value, the plus value (+) will be the 'West' and minus (-) will be the 'East' position from the 0)
Exemple, Sylverstone (refer to map curve name to see where it is)
Grid is at 0.000000, -10.000000, 0.000000
Copse curve is around -350.000000, -10.000000, 0.000000
Stowe curve is around 0.000000, -10.000000, 1700.000000
Then you have the FOV value. That one im still not shure. The distance of the previous value is the position (POS) of the cam. If you choose a cam around the track, that you can move the view with your mouse, that is exacly were the cam is located. Thos same cam are the same one that when you look at replay, and they folow a specific car. This is the main problem of few track that we race last year (2006). That is the distance that the cam will be zooming to follow a car. Theyrs 2 value, and im still trying to figure what 1 value do, and what the second do. BUt FOR SHURE a good value is in a range of 10-60. But this depend on how close the cam is from the car. A 10 on 1 cam maybe too close, and too far on another cam. Try this on your test cam and see the difference.
Up to now i only done those test and that is what i understand after 4 hours. This is only what is taken to fix any cam on steveB track of 06 season. Other value may be usefull, but i dont know how the value change will react. I can speculate on them by logic, but not mucth more.
Here the info you need to play with to keep it simple (Position and Fov that i explain up) :
TrackingCam=TrackingCam013 //Last Sector
{
Position=(248.000000, -19.000000, 12.000000)
Orientation=(0.000000, -3.100000, 0.000000)
Fov=(10.200000, 10.000000)
Clear=TRUE
Color=(0, 0, 0)
ClipPlanes=(1.000000, 1500.000000)
LODMultiplier=(45.000000)
Size=(1.000000, 1.000000)
Center=(0.500000, 0.500000)
Flags1=(0)
Flags2=(0)
ActivationLocation=(212.000000, -5.000000, 284.000000)
ActivationRadius=(131.000000)
TrackingRate=(6.000000)
MovementRate=(0.000000)
If any expirement more or just know more, let us know. Hope i was able to help any of you a little.