the road paint is main characteristic thing of the whole minigame-project, will be not changed definitely.
If I had interest to do it differently, I would do it long time ago.

ah ok... sorry then...

Nice houses, your game is coming together.

dangerous racing, those old f1 cars...
a hard accident, pilot injured.

I like your enthusiasm in all the projects presented latest days here at forum

to the F1LR next downloadable release:
I  try to optimize the actual project with point to the decent game performance at standard pc computers.
the racing mini-thingy must have some reserve to add more cars in future (up to 6), so now I reworked the tree imposters visibility again to max 400 objects on the scene (heh, well, again, but new repositioned :-)). they actually, can say, copy the sides of racing track only now. also the house objects can be few collidable stuff near the track now only, the rest can be pure skinmesh  behind the invisible rigidbody tree "walls" .

would be very great add sort of boundary stones as collidable trackside objects, but linking it all as rb objects with 6.50 rad must be pain.
yes, there is more simplest way, which was done for many racing games - instead of linking all separate objects together  just make a simple invisible corridor wall around the whole road. this would save a lot of work and increased performance, but it is not a way, what I wann to go. too easy.

7.22 car and pcar settings was for me about more angry then fun, what I did with 6.50 quickly, I was not able to do with with 7.22 for days similar. see also this jestermons post 
making 3drad f1 car is special "fun", coz for high speed car object is there creepy shaking of wheel with high speed. 6.50 or 7.22, the ingame speed km/h indicator value must be a bit faked :-) this maybe you can not see with a bus car 

and here is my latest 400 tree terrain with buildings :-) runs good now.

That's why I now use ODE car object in 7.22

I thought, the basic formula is: 3drad 6.x use ODE (Open Dynamics Engine), 3drad 7.x use PhysX engine? isnt?

I thought, the PCar is just improved PhysX version of Car object, but if you use 7.22, both objects runs on PhysX. that is, why the car 6.50 project loaded in 7.22 is totally different handling. that is why I am not able with same/simular object properities make the car same/similar drivable to ODE version. that is why the car / pcar object can not collide the wheels (very important for open wheel car).

I don't have speed indicator shaking with a bus car.

I mean the car wheels are shaking and dancing around axis with high speed. I wanted to have a race car speed up to 300km/h, but the "real" game editor engine speed limit, when is the wheel shaking not visible yet, is far far away below this number. so to have a car able to indicate on the game screen 300 km/h needs multiply the valueprint (linked to the car object) source number, or the script rotation value linked to a needled sprite, if you use the graphical indicator

BEAST!