I'm working on a project that was created using the gbxml -> GBS -> doe2
methodology. I've had zero problems working with the file in detailed
edit mode and running normal simulations. However, when I switch the
file into Title 24 2008 compliance analysis, it loads the compliance
rule list fine, but any subsequent modification to any compliance OR
non-compliance fields causes eQUEST (and my computer) to lock up. I
thought at first it was just taking a while to make the change in this
large file, but even minor changes don't work. I've tried changing wall
construction names, space names, air-side system type and some other
modifications - all to the same effect.
Has anybody had similar issues and hopefully solutions? I appreciate
any feedback that can be provided.
Greg Collins
Consider trying to adjust the camera range in the .PD2 file. Josh
shared this about a year ago.
[Equest-users] Lost 3-D Geometry Model
Josh Greenfield JGreenfield at primerachicago.com
64225D88886F22C0114C30B%40pelexch1.primerachicago.com%3E>
Sun Jan 17 10:17:46 PST 2010
* Previous message: [Equest-users] Lost 3-D Geometry Model
* Next message: [Equest-users] Throttling Range
* Messages sorted by: [ date ]
________________________________
If "Reset Camera" AND closing/re-opening doesn't work...close
eQuest...open your .PD2 file in Notepad and look at lines 13
(ClippingRange), 14 (FocalPoint) and 15 (Position)...
Proj "Peck_Baseline"
ProgramVersion = "eQUEST 3.63.6510"
BDBaseVersion = 24
ProductCode = "eQUEST"
WeatherFile = "TMY2\CHICAGIL.bin"
CreateDate = 1255555885
ModDate = 1262904952
RunDate = 1262903881
LibraryFile = "eQ_Lib.dat"
ActiveMode = 0
InputModule = 1
UseCameraData = 1
ClippingRange = ( 400.541, 1731.6 )
FocalPoint = ( -89.875, 25.375, 18.0293 )
Position = ( -807.176, 648.915, 295.315 )
If any of the values in there are HUGE (probably with exponents) then
just change them to zero...save...re-open eQuest. These values are just
used by the eQuest camera so you're not changing any shell positions or
anything.