peetj
Member
Hi,
I am currently setting up 25 students in a Bitbucket workspace so that we can develop in teams. We are using the SCM in GMS2. In my testing I have found that if person A pushes a commit and person B pulls it, the Asset Browser is not refreshing. I know the change has been pulled by viewing the History. The only way I can see the change is by restarting GMS2 - not ideal. Closing and re-opening the A.Browser does not do the trick.
Is there a way of refreshing the Asset Browser without a restart?
Many thanks
Pete...
I am currently setting up 25 students in a Bitbucket workspace so that we can develop in teams. We are using the SCM in GMS2. In my testing I have found that if person A pushes a commit and person B pulls it, the Asset Browser is not refreshing. I know the change has been pulled by viewing the History. The only way I can see the change is by restarting GMS2 - not ideal. Closing and re-opening the A.Browser does not do the trick.
Is there a way of refreshing the Asset Browser without a restart?
Many thanks
Pete...