-
Notifications
You must be signed in to change notification settings - Fork 208
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Reenabled new pathcaluclation after one year. To be tested!
- Loading branch information
Showing
2 changed files
with
14 additions
and
10 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
25b4980
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Stephan-S Not a long time ago I tried to use this path calculation method because I liked its behaviour with blue lines, but I found that in big routes (ex. 4x map, 6 different routes inside each bunker silo to distribute discharge) it triggered the limit of >500000 calculations. Increasing this limit made calculations too laggy.
FS19_AutoDrive/FS19_AutoDrive/scripts/PathCalculation.lua
Line 128 in 25bbe18
Calculations were multiplied by 2 at every path bifurcation, and exponential calculations become too big. That's what made me try to improve DijkstraLive to calculate blue lines forward and backward instead.
Anyway, at least for me, it worked fine with smaller routes.
I hope this info can be useful for your testing ;)
25b4980
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hey @jala15 ,
thanks for the quick feedback.
Do you have a network with a problematic size for me to test this?
I can't seem to reproduce any errors with it. There is exactly one small lag the first time you start a driver because it prepares some tables. But I could just as well put that into the init code during map loading.
Otherwise the performance is better than the old Dijkstra implementation or at least the same.
It could have to do with that line:
25b4980#diff-5335b753e3c250d60b8a51be252cf70c981829f6fa4c032f3fbd71bef82a21b8L72
I honestly don't yet know why Axel put it in there and I haven't heard back yet, so I removed it for now.
25b4980
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have this config for the map Southwind Fields
AutoDrive_config.xml.txt
I remember my truck couldn't drive from "Sellpoint 150" to "F6 sw", but I guess it could drive from "Sellpoint 150" to "Fuel station" and from there to "F6 sw". I'm not sure of the last statement, but I guess the limit of driving/not driving was around "Fuel station".
25b4980
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, I checked it out and there was zero lag for me and 'Sellpoint 150" to "F6 sw" was no problem at all.
25b4980
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Wow I feel quite stupid now. So much time spent with dijkstraBlue instead of removing one line. I will give it a try in a few days, very busy at the time.
Thank you very much