So "it's not a bug it's a feature" ? To my mind:
- - Standing on a node, and then tracking it and having it say it's 71m away is not "working perfectly".
- - Having tracking say ya within 2m and then not being able to pop the node anywhere within 250m is not "working perfectly".
Yes, workarounds to the deficiencies in the tracking system have been known for 8 years, and it's been more of a chuckle than a real frustration....at least for masters with 360 degree and 100m prospect capability. That doesn't mean it's "working perfectly". And for those w/o those abilities, it is a real frustartion.
Moreover, post merge, things have changed. Tracking functions outside of PR still work ... most of the time,... but I do run into instances, post merge, where quite simply "It doesn't". Sometimes it works one day and another day it doesn't. Never ran into this problem in the 8 years pre-merge.
How have you confirmed that it is "working perfectly" for every material in every region and in every place ?
- - Standing on a node, and then tracking it and having it say it's 71m away is not "working perfectly".
- - Having tracking say ya within 2m and then not being able to pop the node anywhere within 250m is not "working perfectly".
Yes, workarounds to the deficiencies in the tracking system have been known for 8 years, and it's been more of a chuckle than a real frustration....at least for masters with 360 degree and 100m prospect capability. That doesn't mean it's "working perfectly". And for those w/o those abilities, it is a real frustartion.
Moreover, post merge, things have changed. Tracking functions outside of PR still work ... most of the time,... but I do run into instances, post merge, where quite simply "It doesn't". Sometimes it works one day and another day it doesn't. Never ran into this problem in the 8 years pre-merge.
How have you confirmed that it is "working perfectly" for every material in every region and in every place ?
---