in, missed previous one 
A small update which will be released any time soon now (in March). The CameraPath timeline was made for a replay speed of 1x, but the cameras would be out of sync when movie makers are recording at 0.250 or 0.500.
Some of you may know, but the next release will have a big surprise for viewing races and broadcasting
Some of you may know, but the next release will have a big surprise for viewing races and broadcasting
Good commentary although removing the HUD completely would suit the video better. Also onboard cameras would be even nicer to see the close battles, nevertheless good job 
although removing the HUD completely would suit the video better. Also onboard cameras would be even nicer to see the close battles, nevertheless good job In, unless its a Thursday
Aaah 
I rewrote the camerpath a while ago, (the timeline interface) and because of that the load/save didnt work anymore. The buttons you see in the manual are hidden, thats why 
Although the timeline is a bit user friendlier (removing is now possible). I'll fix the load and save methods for the camerapath in the next version
I rewrote the camerpath a while ago, (the timeline interface) and because of that the load/save didnt work anymore. The buttons you see in the manual are hidden, thats why Although the timeline is a bit user friendlier (removing is now possible). I'll fix the load and save methods for the camerapath in the next version Slipstream was nice
It wasn't safe to try to pass the other aswell If you enabled the Shift U Focus Feature (the 1st one), then you can use the scrollbar to to change the FOV and height of the camera. Even better is to click on the scrollbar and you can use your mousewheel to increase/decrease the value.
Yeah ok, so it would be easier to record it in 1 go, but for now you can use the Shift U Focus feature right? Record each movie segment and edit it together later?
No sorry, not atm. I can look for some modifications so it might work. 
Why would you use this feature on AU layouts?
Why would you use this feature on AU layouts?
I guess your using the TV director feature? If so, yeah that doesnt work because it needs info from the pth files. And there are no pth files of AU.
The Follow Focus tab is something else (future stuff), didn't remove it before releasing v2.6.
See the manual for the 2nd car follow mode:
Note!, don't focus to the same racer which you placed the camera at! LFS can do some strange things
What version of LFS are you using? Are you sure its mine app that's causing it, and not another app?
Thanks, Good to hear that the app is useful for a few people
I was going to clean-up the first post so it would be more clear what this application can do, with each feature/movie.
LFS CarFocus v2.6
Can't see what a pass has todo with it. What have tried sofar ?
Enabled insim? you get the list with racers? which feature did you wanna test? ect, you gotta give some more info
Another preview movie: http://vimeo.com/2863153 (The chat will be removed ofcourse as is just debug info) (FOV and height can be changed during the algorithm)
This focus algorithm can be used in 2 ways.
- The choice to use another car as camera location and another car as focus point. (this makes the focus sometimes not right because of the predicting of the car locations)
- A position behind the following focused car.
Version 2.6 is out
(See first post for the attachment, or click here)- Couple of fixes like Shift U now possible on AU layouts.
- Tweaked the prediction algorithm.
- Added the beta CameraPath timeline, and better implementation of Follow Cam from a 'camera car' seen here: http://vimeo.com/2938286
Have fun
Manual: http://lfs.finalgear.com/carfocus/
Yeah, its possible to watch a race although its not the program its main purpose.
There are features that will interest movie makers like automatic focus in Shift U mode or you can preset some camera locations and follow a racer around the track.
v2.6 is finalizing: Fix fro AU layouts, included a better camera path GUI and a few new ways to focus at drivers while following the car.
this is mine cfg thingy:
I change some values few years ago, so i'm not sure what every stuff means. it works anyway
Read the whole thread and you see:
http://www.lfsforum.net/showthread.php?p=1046518#post1046518
that you don't need to edit the cfg. Have you tried my approach and see what it does?
I change some values few years ago, so i'm not sure what every stuff means. it works anyway
Read the whole thread and you see:
http://www.lfsforum.net/showthread.php?p=1046518#post1046518
that you don't need to edit the cfg. Have you tried my approach and see what it does?
Last edited by FireFox86, .
enable insim typing this in lfs. Press T first,
Then right click in the app, togo to the connection screen. Click on OK, and you should see this in LFS:
And your ready togo
Then right click in the app, togo to the connection screen. Click on OK, and you should see this in LFS:
And your ready togo
Are you loading a replay which runs AU1, AU2, AU3 or AU4? Then its a known bug and I will try to fix it as soon as possible.
CarFocus; Camera Timeline activation
I'm creating a CarFocus tool that helps moviemakers shooting their scene. It works quit well but i'm having trouble with the following idea:
I've created a 'CameraPath' where camera setting/locations are sent to LFS after some time. This works really nice if you want to move the camera around a car. The same technique Victor used in the promotion video.: 0.15 till 0.45 seconds. http://www.youtube.com/watch?v=rsYGl5fK93Q
Atm, you just have to press 'Play' and the program will move the cameras for you. (Time isnt a factor here) See: http://vimeo.com/2509710
However, when you want to shoot a battle (where time is a factor) you gotta start the sequence at the right time.
If you start too early or too late with the activation, all the camera won't focus at the right spot, because the cars are already gone. I think an accuracy of 0.1 second should be enough and doable.
- Request LFS for the race time and use it for a trigger. (this means i have to request the racetime packet every 0.1 second, and then compute all the camera stuff)
- To give the moviemaker more time to activate the timeline is by slowing the replay down to 0.5x or 0.25x. (Maybe as last resort, because I don't wanna force the moviemakers to shoot their scene in slomo)
- Use a LFSdata as trigger, given a sector time in a lap as activation. So if a driver crosses a split, the timeline will be activated. (The moviemaker has to calculate the time between the split and the time of the 'movie scene'.
Any ideas how to solve this 'problem'?
Screenshot of the CarFocus Timeline: (The length of the button corresponds with the time it takes to switch to the next camera location.)
I've created a 'CameraPath' where camera setting/locations are sent to LFS after some time. This works really nice if you want to move the camera around a car. The same technique Victor used in the promotion video.: 0.15 till 0.45 seconds. http://www.youtube.com/watch?v=rsYGl5fK93Q
Atm, you just have to press 'Play' and the program will move the cameras for you. (Time isnt a factor here) See: http://vimeo.com/2509710
However, when you want to shoot a battle (where time is a factor) you gotta start the sequence at the right time.
If you start too early or too late with the activation, all the camera won't focus at the right spot, because the cars are already gone. I think an accuracy of 0.1 second should be enough and doable.
- Request LFS for the race time and use it for a trigger. (this means i have to request the racetime packet every 0.1 second, and then compute all the camera stuff)
- To give the moviemaker more time to activate the timeline is by slowing the replay down to 0.5x or 0.25x. (Maybe as last resort, because I don't wanna force the moviemakers to shoot their scene in slomo)
- Use a LFSdata as trigger, given a sector time in a lap as activation. So if a driver crosses a split, the timeline will be activated. (The moviemaker has to calculate the time between the split and the time of the 'movie scene'.
Any ideas how to solve this 'problem'?
Screenshot of the CarFocus Timeline: (The length of the button corresponds with the time it takes to switch to the next camera location.)
Last edited by FireFox86, .
I think I'll remove the auto connect feature, because its not really usefull imo and the AU cameras will be fixed in the next release.
I did some other work on the camera path feature. I used the idea of a 'flash timeline' to control the camera locations/configurations. Adding and removing camera and changing the length of a camera transition is now easier to edit
This system works quite well if you shoot at a standing still car. The same technique Victor used in the promotion video http://www.youtube.com/watch?v=rsYGl5fK93Q at 0.15 - 0.45 seconds.
Atm, the timeline feature is a pain in the ass to use for a replay battle, because you have to start the timeline at the right moment. If you don't all the camera will have the wrong focus.
I did some other work on the camera path feature. I used the idea of a 'flash timeline' to control the camera locations/configurations. Adding and removing camera and changing the length of a camera transition is now easier to edit
This system works quite well if you shoot at a standing still car. The same technique Victor used in the promotion video http://www.youtube.com/watch?v=rsYGl5fK93Q at 0.15 - 0.45 seconds.
Atm, the timeline feature is a pain in the ass to use for a replay battle, because you have to start the timeline at the right moment. If you don't all the camera will have the wrong focus.
I think you forgot to enable the insim connection. press T in LFS and type: /insim=63392
For the camera path feature gotta do it like this: Position the camera.(it will record the camera setting, location, fov, shift u mode ect)
Give the camera a name (usefull for later reference) before you click on 'record' give the amount of seconds in ms to go to the next camera. I've put the default on 1 second, but for a long camera path (T1 and last corner of Westhill) you wanna make a nice smooth movement of 10 seconds.)
Then click on 'Record' Redo this several times with different camera positions and then click "play camera path"
I've noticed with the latest version that it tries to load the Autcross PTH file. Because there isnt any AU1.pth the application disconnect again. That will be fixed in the next version.
For the camera path feature gotta do it like this: Position the camera.(it will record the camera setting, location, fov, shift u mode ect)
Give the camera a name (usefull for later reference) before you click on 'record' give the amount of seconds in ms to go to the next camera. I've put the default on 1 second, but for a long camera path (T1 and last corner of Westhill) you wanna make a nice smooth movement of 10 seconds.)
Then click on 'Record' Redo this several times with different camera positions and then click "play camera path"
I've noticed with the latest version that it tries to load the Autcross PTH file. Because there isnt any AU1.pth the application disconnect again. That will be fixed in the next version.
FGED GREDG RDFGDR GSFDG