You g27 wheel somehow looks broken! Time to upgrade
Did you post your monitor settings somewhere?
Those photos are made from multiple photos stitched together, so it makes the wheel look funny. But I assure you it's just fine.
It took forever to get the monitor settings correct, they behave very strangely and much like the course maker if you make an adjustment to one it can have a strange effect on the others.
My bezel width is 3%
Screen curvature is 0
Screen angle is 100
I have my front monitor overlapping the inner bezel of the side monitors so I have a very small bezel, .5", but I think that screws with the other settings. It puts the monitor at a slightly unnatural angle and I think that's partly why it took so long to get dialed in and why my settings are so strange. I think it was worth it to have the tiny bezel width though. My monitors ended up at a wider angle than I anticipated but they look great and I can see beside me which is just fantastic!
Here's a longer video showing the final setup from the cockpit of a Cappy.
When you gonna be done showing off?????
Sorry, won't speak of it again.
There's a good article on all the online racing problems on the
GTPlanet news page.
This brings up the dreaded topic of the bug. I've been following all of this very closely and with GTP officially reporting on it I think we can be pretty confident this thing really exists and is pretty bad for online racing. If you don't know much about it you can read all about it
HERE. Testing shows that 10 people and under in a race is perfectly fine but once you get over 10 things get progressively worse. With 11 and 12 people the effects are "tolerable" and relatively small but they are still there without fail. Above 12 people and the room quickly starts to implode with some people seeing lap times 5-10 seconds slower than normal or than what the game clock shows as well as massive changes in handling and graphics quality.
This puts us in a pretty tough situation. In past seasons it might not have been a big deal to limit rooms to 10 people but with our large increase in participants it is a problem. We're already having to ask people to sit a race out if we get more than 12 in a room which I really hate having to do and I don't feel like it's fair to have people sign up for a league only to be asked to sit out a race. I know people are doing it voluntarily so far (which I greatly appreciate) but I still don't like it. Even though the effects are smaller with 11 or 12 people they still persist and can cause drivers to be 1-2 seconds per lap slower than pre-race conditions. I also don't feel this is fair, someone can lose a race or positions due to no fault of their own. Conversely, someone can also win a race due to problems suffered by others.
The specifics of the bug are thought to be related to workload on the console. The more going on, the more resources are demanded and the harder it has to work. It seems to be considerably worse when you are around other cars, especially multiple cars. Disabling mics seems to be one of the biggest things we can do to improve the condition, tests show a rather large improvement in network quality when mics have been turned off. Basically any USB or Bluetooth accessory can amplify the problem. Also, turning off some of the game options such as visual/mechanical damage and fuel/tire wear can minimize the effects of the bug. The less data to be processed, the better the room quality is.
So, I've been mulling it over this weekend and I've decided that we will continue with Round 3 at la Sarthe but we will be doing so with mics disabled. Not just mics turned off, the chat settings for the lounge will be disabled so nobody will be able to use mics. I really enjoy chatting with you guys on the mics but for now we just have to do without. We already run with visual damage "off" so that should help but we might want to consider running with mechanical damage "off" as well. I like the added "realism" of mechanical damage but if it will improve our room quality by any margin I think it might be worth running with it off at least for now. Beyond those changes I don't think there's much we can do short of limiting the room to 10 but with our high interest I don't think that's feasible or desirable.
Some quick notes about the race at la Sarthe. First, there will be a practice session tonight starting around 7pm EST (approx). We will be running the time change version of 2009 la Sarthe with Chicanes. The time will change during the race so that we start in the afternoon light, gradually change to darkness and then finish in the morning sunshine.
I tinkered with the time progression settings and found a nice balance that has the first third of the race in light, second third in darkness and the final third in light. The starting time of the map will be 15:00 with a progression of 23, I found this gave the best blend from light/dark/light without any abnormally quick changes (some settings saw the light-to-dark transition happen in a matter of seconds, these settings should see that transition take approx. half a lap).
There will be one mandatory pitstop during the race that can be taken on any lap except your final lap. Technically a pitstop may not be
needed in the sense that your tires probably won't get too bad during 5-8 laps and we surely won't need fuel. The mandatory pitstop is just to add a bit of strategy and realism to the event since we are trying to semi-replicate a smaller version of a 24 hour endurance race. We did this last season and personally I found it to be quite enjoyable and a nice change from the short, double-header races we normally do.
Please let me know your opinions on the above changes and on the "bug" itself. I highly doubt the impending update will have any major change on this bug and I expect it to be something we have to deal with for the whole season. Right now I'm in "wait and see" mode, we'll do this week with the proposed changes, run the special WRS vs. ORCA event next week and then decide how to proceed from there. Many other leagues are postponing their seasons due to this bug, I hope we don't have to do that but it's a very real possibility right now.