There is a small bug in the version 0.2 of TV Director. I found this bug 2 or 3 weeks ago. Because I have devided the application into 2 parts, the TV director does not recognize changed camera paramters, if they were changed only in the GUI. So the changes are used but not written to the disk. And the next time they are lost.
Small workaround: after changing the cameras, go to LFS and add there a camera and then delete this camera, this will trigger saving the cam to the disk, when leaving the edit mode.
It will be fixed in the next release (and this is not too far away )
German translation:
Es ist noch ein kleiner Bug in der Version 0.2 des TV Director, den ich vor 2 bis 3 Wochen entdeckt hatte. Aufgrund der Trennung des Programms in 2 Programmbestandteile bekommt der TV Director nicht mit, wenn Kameras ausschliesslich in der GUI verändert wurden. Nach dem Verlassen des Editiermodus werden die Kameras zwar benutzt, aber nicht auf der Festplatte gespeichert. Damit sind die Änderungen beim nächsten Mal verloren.
Abhilfe: Nach den Änderungen in das LFS-Fenster gehen und dort eine Kamera hinzufügen und danach wieder entfernen. Dann bekommt der TV Director auch mit, dass die Datei geändert wurde und schreibt sie auf die Platte.
Beim nächsten Release wird der Bug natürlich behoben sein.
I downloaded this ages ago and got confused with it - but today I fired it up again and WOW, what an amazing piece of software!!! This is going to change the way I make my videos forever and I thank you for it. It really is brilliant.
one question:
Is there any way to avoid these black spaces? When I'm using TVDirector, sometimes it happenes that during the race, and I'm watching the race, the track doesn't appear in total, parts of it are just black.
it's a problem with the Shift+U function, not TV Director. if you go to edit a camera, move the camera a little with the right click button, you'll notice that the black areas go away.
Unfortunately there is nothing that I could do. I assume it is some kind of fps optimization in LFS. From a given position it is not necessary to draw a texture that is not visible from this position. This works well for the LFS TV cams, because all camera positions are known by LFS and so all visible parts/textures of the track from this camera are known. But in Shift-U mode this is not applicable. It seems that LFS uses this optimisation nonetheless, if Shift-U is controlled by an insim application (this is only a guess).
As stated one post above by burnsy1882 there is a workaround to trigger LFS to draw all textures. Switch into edit mode, move the camera a little and then just leave the edit mode. Then you can enjoy the rest of the race without the texture issues.
However, this workaround will be useless with the next release of the TV director, when the onboard cameras are introduced (incar, front, rear cams). Because everytime when the TV director switches to an onboard cam and then back to Shift-U, then the texture issue will arise again.
All I can recommend is to design your cam file carefully. Do not put the cameras too high and try to prevent the cameras looking over far distances. Test the cam files carefully, sometimes the issues do not appear during a short test. Restart LFS and test again. I hope these hints will help you a bit.
Now you may understand why I have not yet added cam files for all tracks
Made extended cams using the TV D. editor and tried to keep the cameras in lengthy viewable positions so there wouldn't be a lot of camera changing. Some tracks, such as FE, only use 4 cameras.
BL1
BL2 (rally)
FE1R
FE1
SO3R (short mid-course)
SO6 (chicane)
SO1
Hi there i've got a problem with running LFS Director(like most of others insim apps). I'm doing everything what is told in howto but simply nothing happens. TVDir is running in the background(with insim 32300), i'm going into LFS, typing /insim=32300 and no welcoming message appears. On the track, when watching replay. Nothing .