|QUOTE (Aschratt @ Thursday, Oct 6 2011, 20:15)|
|Just in case anyone is interested.|
I have updated the first post which is now linking to the new download. I have re-released the tool, because many people asked me to do so. Anyway I will discontinue support for it. I have also updated the readme file - you will find information about the development of the tool in the last years there.
I have also changed the license to an more open simplified BSD agreement. This makes it easier for you to share the tool.
Also I have merged APE with my Paths Viewer. You can find it inside the "tools/" directory of the download package.
For more information about the re-release please read the readme file.
@Luten/CrazyRussian: This problem somehow is related into the thread apartments of the user interface. For some reason APE uses multithreaded apartments which are incompatible with the native windows file dialogs in versions after Windows XP SP2 (?) and on x64 systems. This problem might disappear if you are using an outdated machine to modify your paths. Also it does not appear very often. However I am unable to change this at the moment. Please remember how much time has passed between the initial release of APE 1.1 (2004) and today. Changing one line of will definitely lead to problems somewhere else with newer technology. I am sorry for this.
nice to have your good work
I worked this year very intensive with APE 1.1, now i have a nice pathviewer
At the end i ignored your tutorial and the connect-function and edit the dnf file with texteditor
and this is the report from my work in practice:
APE 1.1 makes very stable paths as long as you only edit the flags
unless the start and end point must have 987137
Best is to record the path with APE, then save it as dnf and edit then with texteditor or sannybuilder
It needs then edit the flags to give the pathpoints a behavior
Open the *.dnf file with texteditor or sannybuilder
There are flags for carnodes and flags for navinodes
FLAGS OF CARNODES (carnodes are pathpoints of your recording)
987137 = Start/End
987138 = normal
991234 = fast highway cars
3088386 = Driver exit vehicle
987426 = no traffic
FLAGS OF NAVINODES (navinodes are calculated navipoints between the pathpoints of your recording)
2304 = 2 lane, forward and backward traffic
2048 = 1 lane right forward
256 = 1 lane left backward
2344 = wide street
4608 = 4 lanes
4688 = 4 lanes wide street
9376 = 4 lanes, a little bit wider street
traffic lights in direction north/south:
397,2844|-745,9026|28|0|-42|-85|67840 <--- traffic light at your right side by recording
408,4861|-722,9667|28|2|-47|-93|84224 <--- traffic light for oncoming traffic
traffic lights in direction east/west:
461,4669|-365,2333|28|12|99|-23|133456 <--- traffic light at your right side by recording
442,7587|-360,548|28|14|92|-22|149760 <--- traffic light for oncoming traffic
Aschratt, please correct me if i'm wrong:
A path, done with APE1.1, have allways a start and a end node where the cars are turning back
if the cars can't turn back they rotate around end or start point
It's not possible to connect 2 paths