Rename your dds folder to dds2, create another dds folder and open LFS. Then start putting stuff related to the car back in the dds folder and reloading the textures using low -> high res textures until you find it.
I doubt it would affect races with safety cars, normally you just do /cars=GTR+FZ5+RB4 and obviously racers use the GTRs and admins the other ones when needed. And anyway, you'd need to develop/update insim applications to make use of it.
Will be useful if you do some stuff on a public server with all cars enabled, someone joins in a bad choice of car and you can spec them easier.
All the layouts are finalised so no testing help required, but you can see times others are doing in practice I suppose. The conflict with the other event is nothing to worry about, no one turned up to that one last time Only other conflict is the Indy 500, but that starts an hour before, and missing 10 minutes won't hurt.
6pm BST? The rally starts at that time, so you may as well not turn up if you need to leave straight away. We tried to schedule this away from any other events, what is this clashing with if you don't mind me asking?
Well, we have 27 signups. The super special is first, so there should be 2 people going off every 2 mins. In the rest of the stages, a car goes off every minute.
So for the first person, it'll be: total time to drive each stage (<10mins) + time moving between servers (<5mins). For each person after that, it'll be a case of adding the additional time waiting for the gap between each person. Say you're 10th in line, that'll be the 5th SS1 race, so a ~10 min wait. So basically, it depends on how many people turn up, but I wouldn't think it'd take more than a hour or so.
2. Entries close when the rally starts, as I need to get you the password and after that I won't really check the forum.
3. Whatever, only the username is required to track you in the rally
4. If you wish
You could always do the test rally in the LFS World Rally Challenge on Sunday evening Ok, you need to be on a server and it can't be done at your leisure, but we should be having a Fern Bay round in the actual season, and I'm sure we'll use some of the interesting places as shown in this layout
Quick thing, useful for the tracker to display the car numbers - if you can update your driver line-ups for round 2, or your line-ups for all rounds, to include the following:
username,full name,country (short or long),number,team
e.g.
SCA-F1,Simon Cattell,GBR,18,ineX Racing
that'd be lovely as it'll show numbers on the tracker.
Yes, if you delete the start point, then shift+p and rejoin you'll still appear at the start poiint. Once you /restart the race without the start point you'll appear back on the grid...
In all the time I've been creating layouts, and doing them recently on the open configs, I've never seen this. I just tested it as well - works how you describe.
I can only assume the CR boys made a mistake somewhere I'm sure a short mpr or video would be the best way to show the bug.
Agreed, no offence but you have to be mentally challenged to not ensure that you have all of the skins. It's pretty simple - download the skinpack for that round, set LFS not to download skins and see how many you don't have - then either download the rest in high res or rename some of the files if the names have changed. Christ we'd all help you with a skinpack if you posted a replay.
Pity that you didn't sync up the commentary for the Kyoto 500 - for those that saw the race it's a bit confusing as you showed the same corner a few times as the commentary was progressing round the track.
And a shame that you didn't include any of his DWC mentions from PSR TV - one of the most important things in iRacing for him but all we see is some text and a few cars going round a track.
Overall it's decent, but to me it seems to be quite drawn out with not enough footage, especially from the past, and a distinct lack of onboards - a camera looking at Nolan in car would be a good addition.
Pinging 127.0.0.1 with 32 bytes of data:
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Ping statistics for 127.0.0.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms