KLam
Member
After the release of v12 of FSD, I read a lot of evaluations of v12 to be better and a lot of evaluations of v12 to be bad. I was puzzled a bit, for my experiences have been better (I have only tested v12 on my neighborhood local city streets).
Then I realized that I have not evaluated v12 on two lane curvy Highways with turn in, turn out, occasionally signals, etc. like part of Route 152).
The path of v11 FSDb development is different from v12 FSDS.
For v11, it was a merge of the FSD v11 City and FSD v11 Highway codes. FSD v11 Highway was a re-code of the Old original Divided Highway code (AP, TACC, NOA etc) using the FSD v11 City code method. v11 City code always have problems with unmarked roads, narrow streets, speed control on local roads etc. but was pretty good on two lane curvy Highways (part of Route 152 using the v11 City code).
Now, that v12 coding method have resulted in pretty good City street driving, but have problems with two lane curvy Highways. (I have not tested to see if its worst then the v11 City code).
Then I realized that I have not evaluated v12 on two lane curvy Highways with turn in, turn out, occasionally signals, etc. like part of Route 152).
The path of v11 FSDb development is different from v12 FSDS.
For v11, it was a merge of the FSD v11 City and FSD v11 Highway codes. FSD v11 Highway was a re-code of the Old original Divided Highway code (AP, TACC, NOA etc) using the FSD v11 City code method. v11 City code always have problems with unmarked roads, narrow streets, speed control on local roads etc. but was pretty good on two lane curvy Highways (part of Route 152 using the v11 City code).
Now, that v12 coding method have resulted in pretty good City street driving, but have problems with two lane curvy Highways. (I have not tested to see if its worst then the v11 City code).