No it's not a spelling mistake. I did mean math. :)
I began to wonder, why the evaluate method keeps checking, if the time step is already small enough, when subdividing the track? Couldn't it just calculate how many subdivisions are needed and then do that many?
I thought that the key would be somewhere in logarithms. The formula would look like this:
numOfSubdivs = ceil(log(thisSegTime/maxSegTime) / log(2.0));
But I checked something in the code and it turned out, I did not think it all the way through. It would be possible to work on that principle, but it would not be fool proof as such.
Sorry for the false alarm. :)
Log in to post a comment.
Sign up for the SourceForge newsletter:
You seem to have CSS turned off.
Please don't fill out this field.