I've done a few laps using the only RAC race setup from Setup Field. Managing stable low 2:01.xx and trying to tweak the setup, which usually turns out bad (I make them worse)
I had practiced for this event so was more confident, and happy with qualifying 2nd.
However the start of the first race was terrible for me, my PC was jerky until the field spread out and I was way too nervous. A mistake let eraser past during the shocking early laps. I then settled down and caught eraser up again, was some good racing but followed him home into 3rd.
Second race and it was my turn to apply some pressure to eraser for the early laps, but he held it together. I then made an unforced error in touching the grass which relegated me to 6th right behind the three FZ50's of lococost, DaveWS and wimpie. These were fighting amongst themselves and I couldn't find a way past. I was thinking I would just have to wait for one of them to make a mistake... like what I do! Near the end wimpie and DaveWS collided during a fish tailing exercise so I got a lucky 4th place finish. Was enjoyable racing though
Looks like we'll be using X10 version this Thursday, since X30 was not converted to full blown patch Y over the weekend and if it was released over the next few days it wouldn't give us enough time to practice with the new physics/feel of the cars.
I'm sure we'll be using patch Y for the race after: AS3R
I had a similar problem with the latest driver just after getting my G25. I reverted back to the previous 5.0 driver, but that happened without a hitch. Sorry don't know what to advise apart from things worked OK when I reverted back.
Try installing the lastest version and then uninstalling again, in case something was missed?
Upon installing and starting I found no steering. Looking at the options>controllers screen I can see 3 devices detected which is correct and all the axis were listed.
Moving any axis on my wheel did nothing to the axis previews on the right, same for my joystick.
However, if I woke my wireless gamepad up (press a button) and moved one of it's axis, this was detected and shown in the axis previews. From that point all the other axis on the other controllers worked without having to reassign the axis to functions.
The wheel would work for the whole of a race. Upon starting another race, or visiting pits etc. the wheel would stop working again since the gamepad had gone into hibernation. Wake it up, move an axis and wheel axis resumed.
The fact I've got a gamepad and some have a similar problem with their posh keyboards sounds like the same fault.
I have
Logitech Cordless RumblePad2
Logitech Wingman Strike Force 3D
Logitech G25
I found that if I woke the rumblepad up (it hibernates when not used) and used one of it's axis, it enabled all other axis to work including G25.
This is a little awkward since this sequence is necessary every time I leave the pits, change car etc.
Sounds to me like we have a common problem that another devise is set as default controller
The rule says don't join again after pitting, there is no mention of Shift+S.
Driving into a pit box is still a pit stop
So I think it's down to you assuming the rule means telepitting.
Don't confuse the US straight 110V with the UK Site Safety Supply 110V (yellow boxes) since the second type has the centre tap connected to earth (55V-0V-55V). Using equipment designed for one system on the other system may result in damage to the transformer and/or equipment. ...transformers are my day job
The way I understand it; as long as the track is clear then you can cross the yellow line with caution.
If an incident occurs from crossing the line, then it is soley the fault of the driver leaving the pits.
Scripts are the way to go
I didn't want to be tied to one method for a car, so I programmed a button to swap mode (even during a race)
Here's my script to disect ( I have 3 controllers, hence high numbered buttons)