[Equest-users] Equest-users Digest, Vol 74, Issue 17
ncaton at smithboucher.com
Mon May 19 11:35:18 PDT 2014
It has been some time since I last attempted Revit -> eQuest/DOE2, so there is probably more recent experience on these lists to pool from, but eQuest can import any properly formatted .inp without conflicting names or similar issues via the import function (post-wizards, in detailed mode, under the "File" dropdown).
I would suggest setting up a very simple dummy model with an offset shell (away from 0,0,0), and importing the .inp file as a test to see what you're working with, before trying it out with any developed model. You may find you only want to bring in limited parts of whatever Revit is exporting these days, in which case you might then decide to manually copy/paste some elements or otherwise trim the .inp you're starting with so only select stuff gets pulled into your "actual" model.
Best of luck!
NICK CATON, P.E.
Smith & Boucher Engineers
25501 west valley parkway, suite 200
olathe, ks 66061
From: Equest-users [mailto:equest-users-bounces at lists.onebuilding.org] On Behalf Of Jacob Goodman
Sent: Monday, May 19, 2014 1:15 PM
To: equest-users at lists.onebuilding.org
Subject: Re: [Equest-users] Equest-users Digest, Vol 74, Issue 17
I recently recieved a .inp file for DOE2 that was exported from a REVIT model. My hope was that I could get a head start on the building geometry and cut modeling time. However, REVIT does not (to my
knowledge) create a .PD2 file for eQuest to open. Does anyone have experience with this method of workflow? How do I create a PD2 file for eQuest to use?
Thanks and best wishes,
Equest-users mailing list
To unsubscribe from this mailing list send a blank message to EQUEST-USERS-UNSUBSCRIBE at ONEBUILDING.ORG
More information about the Equest-users