Climbpro in a running

Do you never run on hills?

Mountain running is a thing. But to use ClumbPro you have to follow a course. Then it will be showing a progress against all the climbs and descents on that course. 

It's because you would get info about how big and long climbs there is, as you can't use PacePro when it's hilly. PacePro only works on mostly flat courses where there is no real hills as you can't adjust the PacePro pace enough to be good in hilly course eg. in trail running.

If PacePro would allow larger differences in the speed then you wouldn't so much need ClimbPro and could just use PacePro ;) 

Garmin might have different idea on this, but this is how it seems to go in normal reality. And no ability to make bigger adjustment to PacePro has been made, so they probably think it's working concept also. 

jmto said:

If PacePro would allow larger differences in the speed then you wouldn't so much need ClimbPro and could just use PacePro ;) 

I don't get this comment. To me these two functions are completely different. PacePro is supposed to keep me on pace, especially when racing. ClimbPro tells me how much longer until the top. Even if I stop for a lunch in the middle of a long climb, I still know how much of the climb is remaining. ClimbPro may be useful for pacing too, but it isn't its only purpose. 

You can create a pace pro plan with splits based on elevation change.  This means that when the route goes from uphill to steep uphill or easy downhill to steep downhill or uphill to downhill, the pace guidance changes.

You can't make the speed change to be enough for it to be useful. The slider should go to 11.