For the longest time, MM2CT has plagued me with broken intersections and sidewalks. It's getting old, so I decided to enlighten myself as to what makes a PSDL work. I downloaded PSDL Viewer and watched Fred's story unravel about how his program works, and read up on tutorials on how to make a working PSDL city.
Long story short, the reason why MM2CT is constantly breaking my sidewalks is because of the order of vertices. I have learned from all of this reading that the vertices need to go in a counter-clockwise motion. All of my original vertices are there, however MM2CT is not able to calculate the correct order of vertices. I'm assuming it uses a distance algorithm that calculates which vertex comes next for the order of vertices.
This is a failed sidewalk due to MM2CT not being able to calculate which vertex to use next:
But after moving the index's order around, I was able to fix my sidewalk and achieve this effect:
To make MM2 styled sidewalks, the same vertex needs to be referenced multiple times. MM2CT is not capable of doing this, and therefore messes up the operation. I'm curious as to whether or not MM2CT alters the vertices of a sidewalk if it's not built to proper specifications, but I should probably look into that a bit later.
The purpose of this topic is to basically prove that not all cities built with MM2CT are broken if you experience this issue. I know that this has saved me lots of stress and prevented me from cursing out MM2CT
UPDATE:
For crosswalks, apparently you need to fix their order too. It can cause the map to freeze...looking into it now.
UPDATE 2:
The crashes that are caused by going over a crosswalk with a broken sidewalk are perimeter errors. MM2CT assigns unnecessary vertices to a block, causing a crash. I understand how this works and now know what to do.
Would be curious know what Maxoff, the MM2 City Toolkit program author, may think about this research. He's no more in the MM2 scene, this his program would have got great improvements now.
