Perforce 2005 and the 2006 Beta will both hang BC with 100% CPU usage when you try to use BC's version control integration with them. Something has changed in Perforce to cause this and as far as I can tell there isn't anything we can do in BC to correct the issue.
I contacted Perforce's technical support about this and they've opened an enhancement request to support BC, which means they'll consider officially supporting BC in a future release. If you want to use newer releases of Perforce with Beyond Compare contact Perforce's technical support at [email protected] and tell them that you want p4scc.dll to officially support Beyond Compare. The more customers that contact them the more likely it is the issue will be fixed.
In the meantime, you can use the integration dll from Perforce 2004.2, which will work with newer Perforce servers. To do that download ftp://ftp.perforce.com/perforce/r04....6/perforce.exe, do a custom install, and install ONLY the P4SCC DLL option.
I contacted Perforce's technical support about this and they've opened an enhancement request to support BC, which means they'll consider officially supporting BC in a future release. If you want to use newer releases of Perforce with Beyond Compare contact Perforce's technical support at [email protected] and tell them that you want p4scc.dll to officially support Beyond Compare. The more customers that contact them the more likely it is the issue will be fixed.
In the meantime, you can use the integration dll from Perforce 2004.2, which will work with newer Perforce servers. To do that download ftp://ftp.perforce.com/perforce/r04....6/perforce.exe, do a custom install, and install ONLY the P4SCC DLL option.
Comment