Is it just me, or are three quarters of the pits at Westhill in a strange shadow when you select Cloudy Afternoon? Just tried it with 0.6E and 0.6F (and a 0.5Z28 copy I had lying around) and it is the same.
Tried it using 0.6E on my Acer laptop too, and its also the same.
Viewed from high up, I don't see what it could reasonably be the shadow from, so it looks like a bug.
Might be fixed in new Westhill, but I thought I'd raise it now.
Another year is upon us and, after a slower than usual start, we are back with a brand new season! This time we are taking you on a journey through the cars LFS offers, starting with the slowest and slowly working up to the big guns (although, not all the way). The name of the season is The Original LFS League - From Tortoise to Hare.
Join us for the ride of your life and have fun along the way.
The qualifying format will be identical to previous seasons but there is one important difference; the name of our servers have changed. Please note that they are now called:
The Original LFS League 1
The Original LFS League 2
The Original LFS League 3
The Original LFS League Qual
Please use these new server names for qualifying and racing. Also, don't forget to check out the rules and regulations even if you are an OLFSL veteran, just to make sure you have them firmly planted in your heads.
We hope you enjoy the season and can't wait to see you on track!
First of all, a big thank you for implementing the ISP_HLV packet - I have used it to good effect on our qualifying server so we no longer need to build layouts to stop corner cutting. Instead, all laps just have to be HLVC compliant and it is so easy because people can use hotlapping to perfect their lap before joining our quali server.
Anyway, I also just used it to watch for corner cutting during races (by analysing the replays with ISP_HLV turned on) and I found a strange thing. I am tracking all cars with the MCI packets, and I wanted to know which node the HLV violation was fired so I could trend it to see if they cut the same corner every lap.
The corner in question is node 445 on KY3 (which is the corner coming off the oval back on to the road track where there is a nice chicane (perfect for cutting)). On lap 5 and 6 of the replay for a particular car, the HLV packet fires before the car has actually reached the off track bit. When I get the HLV packet, the car is at node 443, which is actually the middle of the track on the line they have taken. It does then cut the corner at 445, where I would expect the HLV packet to be fired.
Is this something to do with lag? Is the HLV coming from the client and being saved in the replay (maybe?) instead of being generated again by the replay when it is running? If it is, I doubt there is an easy fix, but just wanted to understand the reason if nothing else.
On the whole, I like it, but there are some concerns for me.
The first one is that at the moment, the start of the race isn't set in stone exactly. We say, for example, 16:00GMT, but the race might actually start at a few minutes past while we wait for a few stragglers. Using this format, we would have to start the qualifying at a very specific point for it to last exactly five minutes and then the race to start. In one respect this would give more incentive to racers to show up on time, but I see more people saying "please wait for me" and it getting too difficult to suit everyone.
The second problem is that it adds a lot more pressure on us (well me) as the hosts to ensure everything goes well. To stop people pitting is possible with an update to the insim app which we currently use to start races but it is getting more complicated. Definitely possible, but quite hard to ensure every possibility is thought of and covered.
Having said all that, it is a good idea and something I will have a look into for next season as an option - no promises and it will have to be put past the rest of the staff for approval (if I can get it workable in the first place). You never know I might come up with something along these lines which is a compromise on some of the areas - once I start thinking and coding it, I will know more. I doubt it will be any time soon though.
Sorry, didn't notice this thread yesterday, if you post in the "Qualifying System Bugs/requests" thread I will get an email, so best to use that one. As it happens, I did notice and started it again. 500servers are upgrading their servers at the moment, but this will not affect the quali server until after the qualifying deadline.
Hmm, I had thought of these, and I could go mad on features. Ideally, I want the app as small and as single minded as possible. To this end, I don't really want to add this type of functionality in - KISS! (Keep It Simple, Stupid!) For example, I have started another app (in VB.NET 2010 Express) which tracks your time around a certain area of track (so you can practice a certain corner or series of corners and it can tell you if you were faster or slower than last time and help to improve a little section of track at a time). This will not be added into LFSQual, ever.
I said I take the point, I didn't say I agreed with it. We didn't just pick the combos off the top of our heqds randomly, there was thought about what we would like to see and like to race. The schedule is the outcome of this work. If we change it now someone else could say there is too many reverse events, for example and say they want that changing. Were do we stop? So, the schedule will not be amended.
If we had put together a schedule that everyone loved, we would have had a small miracle on our hands. As it is, I take the point about too much open wheel action. To be honest, I prefer open wheelers to the GTR classes, so (as I put the schedule together) it favours my choices. The RB4 and RAC are in there, and I really can't get along with either of them, so we all have to take the good with the bad.
Well an announcement would have saved me a lot of work searching frantically for another host in time for our next season, but I am genuinely glad you are OK and it wasn't (as I was fearing) something worse.
Our ticket has closed itself again so I will re-open it for visibility.
No it isn't normal, and I suspect something is either drastically not working which is stopping them seeing the support tickets or they are having personal issues which is taking them away from here. When I have had a problem previously it has always been sorted quickly and professionally, so this is clearly something more serious.
I am not going to get angry at Dean/Franky500, no matter what the reason. It is just fortunate that we are not in the position where we need the servers for our league just yet.
The news is that our personal lives have become more hectic recently and our ability to complete another season with the same quality has dropped a little.
The good news is that I am starting to kick the next OLFSL season into life, so there will either be some good news (ie a schedule and a start date) or some bad news (ie sorry, long delays) in the very near future.
I hope to have this news to you before Saturday 18/12/2010 is over.
Praise indeed, which is somewhat misplaced I am afraid. Whilst my coding is nowhere near "great" it is sufficient for our purposes. Having just spent a few minutes reminding myself of the contents of a small text file by the name of "insim.txt", I can tell you that my ability to code anything to fix sets is seriously lacking. LFS Insim has nothing in it which allows sets to be checked at any level. I am sure that a real coder/hacker could check memory locations and see what bits are set to understand the setup (much in the same way some of the LFS tweaks worked to increase car power etc) but I simply don't know how to do this.