[Equest-users] DWG import prolems in 3.65

[Daniel Knapp]

Thank you for the update. I have to say that I’m tremendously grateful that this software continues to be so well supported and distributed free of charge.  

—
Daniel Knapp, PhD, P Phys, LEED® AP O+M
danielk at arborus.ca

Arborus Consulting
Energy Strategies for the Built Environment
www.arborus.ca
76 Chamberlain Avenue 
Ottawa, ON, K1S 1V9 
Phone: (613) 234-7178 ext. 113
Fax: (613) 234-0740




On Oct 31, 2013, at 5:18 PM, Jeff Hirsch <Jeff.Hirsch at DOE2.com> wrote:

> The eQUEST team apologizes for the DWG import problems. There were changes to both the DWG internals and the libraries we use to import DWG that interacted to cause the problem (and we are embarrassed to say we did not catch this). We are implementing a fix that also allows import of files from more recent DWG versions (such as 2011 to 2014, as our previous release only “officially” handled up to 2010 although files created with later versions often imported okay as well). We hope to complete testing and post that update early next week.
>  
> Jeff Hirsch
> James J. Hirsch & Associates
> _______________________________________________
> Equest-users mailing list
> http://lists.onebuilding.org/listinfo.cgi/equest-users-onebuilding.org
> To unsubscribe from this mailing list send  a blank message to EQUEST-USERS-UNSUBSCRIBE at ONEBUILDING.ORG