I am unable to replicate this on 2016.3-2017.1. I am also not seeing any currently logged defects surrounding this. However, perhaps a little more discovery is needed.
What exactly is your calculation doing and why? What type of calculation is it? And, can you share the calc with us?
Is there also a dynamic window calculation at play, showing/hiding fields in this scenario?
Can you try temporarily removing the calculations you have in place to rule them out as a cause?
Thanks for your post.
There was another calculations using this fields which make it show and not hidden .