Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
attached-track
{
road0
{
track <kuid:506208:100093>
useadjoiningtracktype 0
vertices
{
0 "a.road0a_x"
1 "a.road0b_x"
2 "a.road0e_x"
3 "a.road0f_x"
}
}
road1
{
track <kuid:506208:100093>
useadjoiningtracktype 0
vertices
{
0 "a.road0f_x"
1 "a.road0d_x"
2 "a.road1b_x"
3 "a.road1a_x"
}
}
}
attached-track
{
road0
{
track <kuid2:506208:100093:1>
useadjoiningtracktype 0
vertices
{
0 "a.road0a_x"
1 "a.road0b_x"
2 "a.road0e_x"
3 "a.road0f_x"
}
}
road1
{
track <kuid2:506208:100093:1>
useadjoiningtracktype 0
vertices
{
0 "a.road0e_x"
1 "a.road0d_x"
2 "a.road1b_x"
3 "a.road1a_x"
}
}
}
The double spline points are actually separate attachment points and getting the road correctly connected can be frustrating.
That's why I gave up on those and started building my own intersections with road spline and invisible roads. It really doesn't take much longer than getting the pre-built correctly lined up and height-adjusted. The trick is finding the right invisible road with traffic speed to match the visible road's. I have a pick list for the signals, signs &c. I commonly use.
:B~)
No luck with this yet, i guess?
Sorry, May 30th was my last attemp to fix it. After everything I've tried, nada. I still believe it's just a matter of finding the correct attachment points. I play with the points and get all sorts of results. If I had the original mesh files, I could see where they all are.
I made one from another mesh but the road edges don't match, so still a WIP