|
#1
|
|||
|
|||
This was indeed due to a bug in the Perforce action, occurring when processing a large number of files. Attached is an update that should resolve the issue (extract to your VisBuildPro install path).
|
|
|