topic Re: AC16 and trace reference view maps in Documentation

AC16 and trace reference view maps

Anonymous — Fri, 26 May 2023 14:38:02 GMT

Hi

Just upgraded to AC16 today and have opened an old AC15 model and all runs well until I try to trace reference a view map. It then decides to drag/ no respond and occasionally crash.

Incidentally it doesn't do it when trace reference stories, layouts, sections etc. and the 'bug' happens in both layout and model space.

Any ideas? I have re-saved the file as a new name in AC16 but no change. Am loathed to transfer to a new a brand new file as it has tonnes of view maps etc. which will likely to get lost.

Re: AC16 and trace reference view maps

Katalin Takacs — Wed, 11 Jul 2012 09:08:36 GMT

Dear tlodge,

When ArchiCAD crashes, please submit the crash report and contact your local ArchiCAD reseller with the Bug ID to investigate the issue.
If you have already processed the crash but do not remember on the Bug ID, you can find in the CrashSubmissionLog.txt file. See detailed: http://archicadwiki.com/CrashSubmissionLog

Thanks,

Re: AC16 and trace reference view maps

Anonymous — Tue, 18 Dec 2012 10:49:50 GMT

Hi, I have the same problem, with a completly new file too. If I place a view under a view as a trace reference it freezes. But I don´t get bug report. What can I do?

Re: AC16 and trace reference view maps

Katalin Takacs — Tue, 18 Dec 2012 11:04:51 GMT

Hi Eszter,

probably your issue is the same as it is detailed here: http://archicadwiki.com/Troubleshooting/SlowTraceReference
This article describes the possible workarounds as well.

Please let me know if I you have further questions.
Best regards,

Re: AC16 and trace reference view maps

Anonymous — Tue, 18 Dec 2012 11:11:50 GMT

Than You for the fast reply. I foun this workaround "•Use a Reference file from the Project Map instead of the View Map. " But it would be better to use the view as trace reference.

Re: AC16 and trace reference view maps

Katalin Takacs — Tue, 18 Dec 2012 11:16:14 GMT

I agree. We schedule to fix this issue as soon as possible, in the next ArchiCAD 16 Hotfix.
Sorry for the inconvenience.