- changed status to open
Bad textures on segments with multiple lanes
Found on Darpa sample, as it has segments with multiple lanes. When we load the complete example we get one behavior and when loading only roads that have the problem we get something different.
Full sample:
Isolated sample:
Probably related to: #140
Comments (11)
-
reporter -
reporter - edited description
-
reporter The problem is the following. The driveable_bounds of each lane are the complete extent of asphalt that belongs to the segment, and the lane_bounds are the extents of the lane in that segment. So, we should define lane_bounds in terms of the width of the lane and the driveable_bounds in terms of all the lanes that belong to that segment. So we need to pre-compute the extents of the driveable_bounds when defining the lanes that belong to the segment.
-
reporter Partially solved, but got an issue in RNDF segments that have lanes that have different directions:
The RNDF segment that goes from the left side to the right side have two lanes that have different directions. Bug detected there. This makes the code explode since lane partitioning is based on the idea that lanes share the same direction.
-
reporter Got some improvements but there are still other child issues.
Now lanes that have different directions are swapped to match the direction:
-
reporter -
reporter - changed status to new
-
reporter - changed status to open
-
reporter -
reporter - changed status to closed
-
reporter - changed status to resolved
- Log in to comment