+1 for me too - more tracks always good
Hotkey for Time/FPS switch.
I like having the FPS on screen, but, it would also be handy to have the time every now and then. How about a button which you can press whilst racing to switch them over?
Couldn't get the Http address to work, but the MMS one did.
Quality is bit poor, lots of buffering, but the FPS when it is going is very smooth.
is the 5 connections limit due to peercast or another factor?
I hadn't managed to get peercast to work yet, think it's a port forwarding problem
Hi... it said Channel not found on Peercast.
I'm interested as I have been looking at Peercast myself recently.
I'm interested as I have been looking at Peercast myself recently.
Can I tell you exactly.... well no as to be honest, I spent a whole night fiddling to get it working, it's not an exact science. Luckily Fireball had previously setup the VPS using SSH already, I have only just started using SSH today.
But I can tell you roughly.
Two pc's
SvideoTV Out
TV card svideo in
NSVtools (mainly NSVcap)
VP6 plugins
shoutcast VPS server
But I can tell you roughly.
Two pc's
SvideoTV Out
TV card svideo in
NSVtools (mainly NSVcap)
VP6 plugins
shoutcast VPS server
Sorry for the delay.
I wanted to say thanks to Sören again for letting me use the director tool for OLFSLtv. I must report that it was great, and feedback was fantastic.
The only complaint, was that the onscreen display, car position etc, doesn't change along with the camera, e.g. switching to the director tool whilst looking at position 3, for the whole race, you only see the split times and position for whoever is in 3rd place at the time. but apart from that, everyone loved it.
6 hours of streaming with no problems.
I wanted to say thanks to Sören again for letting me use the director tool for OLFSLtv. I must report that it was great, and feedback was fantastic.
The only complaint, was that the onscreen display, car position etc, doesn't change along with the camera, e.g. switching to the director tool whilst looking at position 3, for the whole race, you only see the split times and position for whoever is in 3rd place at the time. but apart from that, everyone loved it.
6 hours of streaming with no problems.
I dont intend for this topic to continue, but I was asked if I was sure disabling Vsync lowered FPS. I tested again. Yes it does cause a huge drop, but only if Adaptive Anti Aisling is enabled. Great work, downloading V6 now.
I think I am using Temporal AA as well.... I read it was meant to be better, I'll have to switch it off and try again.
Yup switching TAA off worked a treat. Great work on the patch.
Last edited by russraine, .
I tested out Vsync and this is what I got.
LFS in Window mode 77 fps with Vysnc enabled.
LFS in window mode 76 fps with Vsync disabled.
LFS Full Screen mode 41 fps with Vsync enabled.
LFS Full Screen mode 20 fps with Vsync disabled.
(very big and unplayable drop, interesting).
AMD 64 3700+, Radeon 9550pro, 1.5 gig ram. 2xAA enabled. 1440x900 resolution, Acer 19" widescreen monitor.
LFS in Window mode 77 fps with Vysnc enabled.
LFS in window mode 76 fps with Vsync disabled.
LFS Full Screen mode 41 fps with Vsync enabled.
LFS Full Screen mode 20 fps with Vsync disabled.
(very big and unplayable drop, interesting).
AMD 64 3700+, Radeon 9550pro, 1.5 gig ram. 2xAA enabled. 1440x900 resolution, Acer 19" widescreen monitor.
Thanks for listing the stream recordings. Video and sound quality a fair bit lower than the stream though.
Sorry about NSV.... as soon as something better is available, we'll try it.
Sorry about NSV.... as soon as something better is available, we'll try it.
Well done Mooney!
Yah.... it was amazing watching those last 3 laps with Mooney and Ruditurbo. Mooney picked his moment perfectly, bad luck for Rudi who managed to hold off Mooney for the whole race.
Feedback from me...
Very pleased with the streaming today, no problems whatsoever (on the technical side).
Having a pc capture 25fps for nearly 6 hours without stopping is pretty tough!
Lots of feedback about the volume being too loud. I turned the volume down quite a fair bit, so, I'm a bit puzzled as to why, this was the case. I can only think:
A) the sound is being normalized on the server.
B) that maybe the clients software (winamp/vlc) is doing it.
I'll try turning the sound right down next time, but it is very odd as to why it would need to be near silent for capture?
I do agree about the too many camera complaint, it was the first time I had set cameras in this new tool before, and did not have an oppurtunity to test it in race conditions, be better next time, I promise.
The one downside to this program, is, as many have noticed, the postion marker and split times not correct. There maybe something I can do about that, I'm not sure, I will investigate.
About the commentary, sorry there was none today, now the hardware and software is working properly, I can look into reinstating the commentary as, I have not quite worked out how to capture from the microphone, without using a cpu intensive program in the background to LFS. Any suggestions, please let me know.
Now I have a fully stable setup, I can actually get around to improving the service, all ideas to boost it were on hold, until the bugs were removed, and thanks to Nassa Osoi (and Nassa Ant for pointing me his way) they are.
For interested parties, the mp3 encoder was crashing, the reason, when input and resampling audio rates were not exactly the same.
(thanks to Soeren Scharf for letting me use his new director tool as well)
Very pleased with the streaming today, no problems whatsoever (on the technical side).
Having a pc capture 25fps for nearly 6 hours without stopping is pretty tough!
Lots of feedback about the volume being too loud. I turned the volume down quite a fair bit, so, I'm a bit puzzled as to why, this was the case. I can only think:
A) the sound is being normalized on the server.
B) that maybe the clients software (winamp/vlc) is doing it.
I'll try turning the sound right down next time, but it is very odd as to why it would need to be near silent for capture?
I do agree about the too many camera complaint, it was the first time I had set cameras in this new tool before, and did not have an oppurtunity to test it in race conditions, be better next time, I promise.
The one downside to this program, is, as many have noticed, the postion marker and split times not correct. There maybe something I can do about that, I'm not sure, I will investigate.
About the commentary, sorry there was none today, now the hardware and software is working properly, I can look into reinstating the commentary as, I have not quite worked out how to capture from the microphone, without using a cpu intensive program in the background to LFS. Any suggestions, please let me know.
Now I have a fully stable setup, I can actually get around to improving the service, all ideas to boost it were on hold, until the bugs were removed, and thanks to Nassa Osoi (and Nassa Ant for pointing me his way) they are.
For interested parties, the mp3 encoder was crashing, the reason, when input and resampling audio rates were not exactly the same.
(thanks to Soeren Scharf for letting me use his new director tool as well)
Hmmm...... I can't see how the drag effect can be disproven. I think maybe it's not as bad as made out originally perhaps?
I haven't managed to catch Fiendi about this yet, but either there are super serious problems, or as I suspect he is upgrading the whole site.
The third option, which, there is a small possibility, involves FienDi, Vodka and the recent full moon, but I can't say anymore about that, it is a secret.
The third option, which, there is a small possibility, involves FienDi, Vodka and the recent full moon, but I can't say anymore about that, it is a secret.
Well I thought I got it to work okay, you load cam hack, then the tv director tool, you then go into the Shift U mode, and press Crtl Z or X to use cam hack. When you set a camera, the height is saved by the director tool. Obviously if next time cam hack isn't enabled when you try to use it and load the settings it wont work, as the director wont be able to achieve the heights.
Just out of interest Solar, do you keep track of the other things which can affect the fuel efficiency, such as, tyre pressure, windows open/closed, air intake/conditioning etc. From what I've read, over a month of use, they can change figures quite a deal.
This is a tougher combo than I thought, even setting a hotlap has been tough going, with nearly a 3 minute lap, it's a long time to be driving without touching the grass or the evil walls.
don't forget about that other app - camhack, it overrides LFS set camera height, I tested and it does work with TV director.
looking forward to the next big update to LFS myself, most console games don't really ever get an update, not to the same extent as LFS anyway, you get more value for money from LFS, that's for sure, and no online subscribtion to play it either.
Hot damn this is good, in five minutes I had got some cams setup and it worked.....! Amazing!
Do you have any problems with me trying it on OLFSLtv (www.lfs-league.com)? Happy to add a link back here, or whatever.
Do you have any problems with me trying it on OLFSLtv (www.lfs-league.com)? Happy to add a link back here, or whatever.
Last edited by russraine, .
I am not having any real problems with the site, other than since this morning, the frame is now too big for my screen, and since I'm using a widescreen this is very odd.
Well this is a bit of a pickle isn't it? Not heard back from Solar yet, but I know he is busy this week, so that's ok, we have time to decide about this.
@Mooney. I don't think it was specfically my HD that caused it, just an indication of something on my system, at that time. But if you say he is having other lagouts, this could just be an awful coicidence, or, pherhaps his lagout caused something with the replay saving, which got my HD going at that exact point (but I guess everyone else would have the same, although, if they were racing, may not have noticed it is my guess).
I must ask for you not too speculate and think about rule changes, the question here is if I was right in my snap judgement, whether as a host who believed his computer caused a lagout was right to let someone who he thought suffered do to his system, rejoin. There is nothing wrong with OLFSL rules, and no change is necessary, any real suggestions can be put on the suggestions board.
Please do not think, that although the decision was quick, that it was easy, I knew exactly that I would be under scrutiny post race, and that it might cause a fuss, but I had to make a choice at that moment, right or wrong.
I also know that, allowing a driver back onto track was dangerous, again in my judgemnet I was confident that a pool one driver is sensible enough to be careful when rejoining the race, and again, any recordings of the stream will show me watching his progress out of the pits.
It is now up to Solar to decide, as I entrust his decision to either let the result stand, or for Pirriste to be excluded from results.
@Mooney. I don't think it was specfically my HD that caused it, just an indication of something on my system, at that time. But if you say he is having other lagouts, this could just be an awful coicidence, or, pherhaps his lagout caused something with the replay saving, which got my HD going at that exact point (but I guess everyone else would have the same, although, if they were racing, may not have noticed it is my guess).
I must ask for you not too speculate and think about rule changes, the question here is if I was right in my snap judgement, whether as a host who believed his computer caused a lagout was right to let someone who he thought suffered do to his system, rejoin. There is nothing wrong with OLFSL rules, and no change is necessary, any real suggestions can be put on the suggestions board.
Please do not think, that although the decision was quick, that it was easy, I knew exactly that I would be under scrutiny post race, and that it might cause a fuss, but I had to make a choice at that moment, right or wrong.
I also know that, allowing a driver back onto track was dangerous, again in my judgemnet I was confident that a pool one driver is sensible enough to be careful when rejoining the race, and again, any recordings of the stream will show me watching his progress out of the pits.
It is now up to Solar to decide, as I entrust his decision to either let the result stand, or for Pirriste to be excluded from results.
Hi there!
I was waiting for this to come up, heheh.
Yup I was hosting pool one, and did allow Piiriste to rejoin. The reason being I suspected it was a moments lag on my computers part which may have trigged his lagout, a big churn on my harddrive did happen at that point (which may be viewable on the stream if someone recorded it), and so as host, I made an instant decision to allow him back.
There are a number of other factors to take into account.
1) The official stance is to change the server password just after the race starts, to stop latecomers joining the race. Not all hosts do this; I usually do, but forgot on this occasion.
2) As host it is my responsibility to keep the race flowing, if, as I suspected, the lag was at my fault at that moment, it is not the fault of any racers on track, so for someone to be penalised is unfair. If the lag is caused by racers, the effect is shared by everyone, in my belief.
3) I kept a VERY close eye on Piiriste throughout the race, and did advise him on regaining positions, it was shown he was under blue flags, but was considerably faster than all he was driving around, if I felt he was hindering people, I would have acted. Trying to regain positions safely is allowed under our rules.
4) This also happened very early on in lap one, there would never be any chance for restarts of any kind, after lap one.
5) Basically, I made the decision on the spur of the moment, we do have rules, and yes, by the book, Piiriste should not have rejoined, but as hosts we do have room to manoeuvre for 'the good of the sport', if everything was done without any leeway, I think a lot of you would be complaining about that. As I recall, the majority of OLFSL members voted to keep assistance from the pool manager, if you were unable to race in a set pool, being able to race in a later pool would be possible. Many people have been spared DNSH's if they have a fair excuse, again, a lot might argue, until it happens to them that this is against the rules, but as soon as you ever have a problem, you would wish for flexibility and compassion every now and then.
We can either be 100% militarian, or have leeway, you can't have both.
No one is more equal than others, I don't recall ever speaking or racing with Piiriste (I’m one of the slow guys remember!) so I have no personal kinship with him/her. It could have been any pool or any racer, someone in 1st place or last place.
I can't say any more than that, I made the decision, it is not a fault with anyone else at OLFSL HQ - if you are not happy with my on the spur decision, then please feel free to write to Solar Hydro, he as appeals arbiter has power to overturn my decision and take any points Piiriste earned away, if he too thinks I was wrong at this point.
I emailed all fellow staff about this, straight after the event, so it has not been a secret. I'm sure, if another host believed they caused a lagout, or say, accidentally kicked the wrong driver, they would try to reconcile they error, or maybe not, I don't know, let's see what Solar thinks :-)
I was waiting for this to come up, heheh.
Yup I was hosting pool one, and did allow Piiriste to rejoin. The reason being I suspected it was a moments lag on my computers part which may have trigged his lagout, a big churn on my harddrive did happen at that point (which may be viewable on the stream if someone recorded it), and so as host, I made an instant decision to allow him back.
There are a number of other factors to take into account.
1) The official stance is to change the server password just after the race starts, to stop latecomers joining the race. Not all hosts do this; I usually do, but forgot on this occasion.
2) As host it is my responsibility to keep the race flowing, if, as I suspected, the lag was at my fault at that moment, it is not the fault of any racers on track, so for someone to be penalised is unfair. If the lag is caused by racers, the effect is shared by everyone, in my belief.
3) I kept a VERY close eye on Piiriste throughout the race, and did advise him on regaining positions, it was shown he was under blue flags, but was considerably faster than all he was driving around, if I felt he was hindering people, I would have acted. Trying to regain positions safely is allowed under our rules.
4) This also happened very early on in lap one, there would never be any chance for restarts of any kind, after lap one.
5) Basically, I made the decision on the spur of the moment, we do have rules, and yes, by the book, Piiriste should not have rejoined, but as hosts we do have room to manoeuvre for 'the good of the sport', if everything was done without any leeway, I think a lot of you would be complaining about that. As I recall, the majority of OLFSL members voted to keep assistance from the pool manager, if you were unable to race in a set pool, being able to race in a later pool would be possible. Many people have been spared DNSH's if they have a fair excuse, again, a lot might argue, until it happens to them that this is against the rules, but as soon as you ever have a problem, you would wish for flexibility and compassion every now and then.
We can either be 100% militarian, or have leeway, you can't have both.
No one is more equal than others, I don't recall ever speaking or racing with Piiriste (I’m one of the slow guys remember!) so I have no personal kinship with him/her. It could have been any pool or any racer, someone in 1st place or last place.
I can't say any more than that, I made the decision, it is not a fault with anyone else at OLFSL HQ - if you are not happy with my on the spur decision, then please feel free to write to Solar Hydro, he as appeals arbiter has power to overturn my decision and take any points Piiriste earned away, if he too thinks I was wrong at this point.
I emailed all fellow staff about this, straight after the event, so it has not been a secret. I'm sure, if another host believed they caused a lagout, or say, accidentally kicked the wrong driver, they would try to reconcile they error, or maybe not, I don't know, let's see what Solar thinks :-)
FGED GREDG RDFGDR GSFDG