Editor Todo

[MSchmoecker]

I really like this project and here is a list of things I want to make for the current system. If I find some time of course :)

Todo

• Snap tools
• Intersection editing
  • directly edit the size of boxcollider/remove it and make a custom system
  • better tools for stop signs and traffic lights?
  • Linking segments together
• Waypoints
  • add points in between of existing ones
  • option to add a new point as the last point
• Code Cleanup
  • Move Gizmos to own class
  • Move Inspector drawing to own class
• Gizmos
  • Segment label not clear at the moment (if two are close together)
  • equal hight of strokes (currently some are at y=0, and some on y = 1)

Done

• Easy moving of waypoints
• Undo in the Editor
• Arrows for strokes

And here are some thoughts I have to left

• Waypoints for curves? This would make sense with a better CarAI
• Waypoint system + NavMesh doesn't really fit, it seems doubled. I completely understand why the NavMes is used, but from my point of view it can be removed in the future and use a more customized system (together with a new CarAI)
• The component initialisation is confusing/forbids prefabs (like Trafic System doesn't work on Prefab Objects #6)
• in my workflow I have tiles of roads, so linking Waypoints to prefabs and then joining them/let them automatically join with rule patters
• Maybe some sort of vocabulary/keyword collection. I often struggle with certain words like what to call the lines between waypoints

I am open for any discussion^^

[mchrbn]

@MSchmoecker thanks for your help and updates :) - I had too much work in past months and couldn't focus on this project. However I'm planning to work on it again in one month or so. Most of your points are right and if we can improve these we could have a more solid package.

I agree that it needs a better CarAI, that's one of the most important thing actually as it makes now the whole output a bit clunky as the cars don't behave so well. Do you have some ideas/suggestions on which way to go?

[MSchmoecker]

For a better carAI it makes sense to rework a lot of stuff. So I think the main goal is to not overshoot it with new features, at least for now (for example overtaking another car).
The cars should be aware of the next points, but if this would be hard-coded it will not work right. This could be solved with a curve path out of the existing points. Also, all of the points don't have to be GameObjects anymore and use of the Unity pathfinding is unnecessary. This would allow a much light-weighter package.

My main intention of contributing to the project was to make it easier to use inside the Unity Engine, but I can help here as well if you like.