This track is going to be ridiculous popular. Think of all the posibilites within league racing and huge grid!
Yes that will be great but at the moment i think the rf2 servers can't handle more than about 40 clients with regard to stable connections/server. I read something like that here in the forum. It is a shame that the rF2 servers still can't handle more than the rF1 servers
In my league (http://www.gtitalia.org/index.php?wsp=hp&Source=1), with rf1, at least one race per month takes place in the Nordschleife.
Hmm... I'm getting a weird glitch when racing the new Vette here. The AI in front of me have a really weird flickering going on, when they're a certain distance away from me. Please excuse the AWFUL video quality... ShadowPlay at play, at it's very best...... If you switch to 1080 you should be able to see the problem.
Can confirm this bug and it is even worse with the new version (GP track included). There is a lot of z-fighting going on and it seems (in my opinion) the reason for this are the huge dimensions of the track. DJC had (and has) a lot of flickering problems with the GP track since he added the track to the Tourist layout. Every track has an "origin point" (0,0,0 coordinates) and in case of the Nordschleife this point lies somewhere in the centre of the Tourist layout, 600 meters below the race surface. I believe the further away an object is from the 0,0,0 point the more inaccuracy you see. I can reduce this flickering for the most TV cams by adjusting the front clip plane to a much higher value (2 - 10 meters), but this is impossible for in car cams, because the cockpit and the environment around it would disappear.
Thanks for explaining Tosch! It's tuned to my liking, and everything is placed where it should be. Otherwise I wouldn't use it. Also I don't race with it enabled all the time. I hit control-space when I need some info, and then disable it after getting that info.
It would be great if ISI could chime-in on this issue. Even many smaller third-party tracks have problems with this, so it's clearly a common, but difficult technical issue to resolve.
I would think that ISI should be thinking that this track would be advantageous to rF2... wouldn't you think?
