It looks like you're new here. If you want to get involved, click one of these buttons!
I have a half dozen assembly files I've created over the past several years. They use XREF's. In each case, all the XREFS were in a subfolder of the network folder where the assembly file resided. Recently I had to make a minor edit to one of these assemblies. When I opened the file, I discovered that a few of the dozen or more XREF's were flagged as "not found", or their paths were no longer correct. I checked the original components. All were fine. I tried other assembly files stored in other network folders with their own XREF subfolders. Those too had incorrect paths.
I returned to the original assembly, opened the assembly browser, and corrected the paths. So far so good. I decided not to risk corruption of the component paths again. I applied the "Switch to Local" command to eliminate the use of XREF's. The command appeared to complete without a problem. There wer no error messages. I proceded to make the edit, and BricsCAD promptly froze. I had trouble getting to the Task Manager, but when I did, I found that BricsCAD was gobbling up enormous amounts of memory, and that memory usage was steadily rising. It approached 8 GB, and that crashed Windows. I had to do a hard restart to recover.
Now you'd think that since I never had the opportunity to SAVE, following the "Switch to Local", and edit (very minor), that the file would open as an XREF assembly. Boy was I surprised. On opening the assembly, it froze and crashed AGAIN! So apparently the "Switch to Local" alters the file structure outside of Windows normal file management system. I'm no programmer, but I think this is VERY bad.
I attempted to "Switch to Local" on several of my other assemblies. They too, froze and crashed. I had to get the IT manager to restore the assemblies from backups. . I tried the file repair option in BricsCAD. It didn't work. My machine kept freezing and crashing. I have V17.2.08 (platinum), and V18.2.14 (platinum) installed. Same result with both versions - a corrupted assembly file that eats massive amounts of memory.
I filed an SR. They told me the best way to transmit the restored assembly and XREF's subfolder was to perform an ETransmit. I did so. They claimed they performed the "Switch to Local". I did. They claimed the switch worked fine. I insisted on seeing the localized file. It crashes my machine......
Attached is the etransmit file I sent to support. It is an XREF assembly that opens just fine on my machine. If any of you are brave enough to open it and attempt the "Switch to Local" , I'd appreciate your findings... Be sure and make a couple edits after the switch, close the file and then re-open it. If you're really brave I have attached the "localized" file, the support group gave me. I can't open it without a crash.