Hi Megaemce, I attempted to fix this as my first contribution to Chart.js and found the issue in the file src/scales/scale.radialLinear.js. The code skips ticks[0] at lines 581 and 648, which appears to always be the lowest value tick. They have included this to skip the 0th tick of auto generated ticks in radial graphs to not have a label at the center of the graph. I've made a fix for it in my own forked repo, but find it unlikely that they will merge the pull request because it may break other people's projects. You can check out my fix at https://github.com/finnegantdewitt/Chart.js. A work around I'd recommend is including another if in the callback for the lowest value. That should stop it generating all those extra lines that the return without an if makes.

Hi Megaemce, I attempted to fix this as my first contribution to Chart.js and found the issue in the file src/scales/scale.radialLinear.js. The code skips ticks[0] at lines 581 and 648, which appears to always be the lowest value tick.

Thank you for you support @finnegantdewitt. There should be a logic here that if the min is set below 0 then this tick should be displayed. I am not so sure about using tickOpts.autoSkip. Something like this:

if (index !== 0 || (index === 0 && this.min < 0)) {
     offset = this.getDistanceFromCenterForValue(tick.value);
     const context = this.getContext(index);
     const optsAtIndex = grid.setContext(context);
     const optsAtIndexBorder = border.setContext(context);

     drawRadiusLine(this, optsAtIndex, offset, labelCount, optsAtIndexBorder);

Can you give it a try and see if there is no errors (for example from this.getDistanceFromCenterForValue(tick.value))?

I've made a fix for it in my own forked repo, but find it unlikely that they will merge the pull request because it may break other people's projects.

That is why we use github and versioning bro!
Don't be shy and create a merge request (just test it correctly and give my version a try).

Maybe it would be best to not display based off the this.getDistanceFromCenterForValue(tick.value) because the if is supposed to prevent the center of the graph from having a value. What do you think?

Maybe it would be best to not display based off the this.getDistanceFromCenterForValue(tick.value) because the if is supposed to prevent the center of the graph from having a value. What do you think?

I just mentioned getDistance... as a reference to thorough code review before creating a merge request. The getDistance actually should make no harm here.

I just briefly checked getContex(index) and setContext and in my undestand this should make no issues at all.

Just try out my solution on your own device and if it works - make a merge request

@finnegantdewitt you were right. I changed both lines and did pull request (#11682) which should fix this issue.