create fly-through (Help)

[Anonymous]

Hi
I am trying to create a fly through of a ArchiCad Group project and the error message is "No free disk space" and it is unable to render.

I am using ArchiCad 9 Student Version.
OS Windows XP SP2

===========================
Hardware is pretty new
Intel Core 2 Duo E6400 2.4 GHZ
Corsair VS Ram 2 GB DDR2 533 MHZ Ram
Free Space on C Drive 45 GB
Graphics Gigabyte GV-NX76T256D-RH 256MB DDR3 ram
(256MB GDDR3 memory and 128-bit memory interface )
===========================

PC does not have any memory issues etc. Runs fine and does not crash etc.
The project i am trying to render has 505 frames.
Please suggest what to do.

Any help is greatly appreciated.

I am able to create fly throughs for small projects.

[Djordje]

LightWorks rendering engine?

[TomWaltz]

Is your disk actually full?

[Anonymous]

1. No the disk is not full. It is a 320GB HDD. The primary OS partition is 100GB. It has more than 45 Gb of free space.

2. I have tried with the lightworks rendering engine as well. Still comes up as "No free disk space" and it is unable to render.

3. I have 2GB DDR2 Ram. Even with ArchiCad running I have more than 1.3GB of free (physical) ram.

Are their any settings that i need to fine tune?

Thanks for your help.

[Anonymous]

hi,

My problem is solved.
the only thing that was required was to change the no of key frames.

Thanks

[Anonymous]

Hi
The error message is back and it says

Disk is full or not enough memory to create 3D data structure. (error code:22)

Free Space on C Drive 45 GB
Free memory at the time of this error message was around 650MB.
ArchiCad 9 was using around 850MB Ram.

Please suggest what i need to do.

==============================================
Error message is

Disk is full or not enough memory to create 3D data structure. (error code:22)

Options are

Stop Continue



Projection : Custom axonometry
Camera azimuth : 37.4502
Start time : 1/13/2007 11:26:21 AM
End time : 1/13/2007 11:26:21 AM
Elapsed time : 0 seconds
----------------------------------------------------------------------
Duplicated database name "AC_9_INT"
at line 1 of file MASTER_GDLAC_9_INT.gdl.
Duplicated database name "RoofMaker 2.1"
at line 1 of file MASTER_GDLRoofMaker 2.1.gdl.
----------------------------------------------------------------------
Document name : Group2_Master.ppe
Processed : 237 walls 201 objects 76 columns 0 ncBeams
81 slabs 0 meshes 0 pitch roofs
Start time : 1/13/2007 11:26:56 AM
End time : 1/13/2007 11:26:58 AM
Elapsed time : 2 seconds
----------------------------------------------------------------------
Projection : Custom axonometry
Camera azimuth : 33.0216
Start time : 1/13/2007 11:26:58 AM
End time : 1/13/2007 11:26:58 AM
Elapsed time : 0 seconds
----------------------------------------------------------------------
----------------------------------------------------------------------
Document name : Group2_Master.ppe
Processed : 0 walls 0 objects 0 columns 0 ncBeams
Start time : 1/13/2007 11:28:00 AM
End time : 1/13/2007 11:28:00 AM
Elapsed time : 0 seconds
----------------------------------------------------------------------
Projection : Custom axonometry
Camera azimuth : 33.0216
Start time : 1/13/2007 11:28:00 AM
End time : 1/13/2007 11:28:00 AM
Elapsed time : 0 seconds
----------------------------------------------------------------------
Internal Rendering Engine
Image size : 992 x 648 (2511 K)
----------------------------------------------------------------------
PhotoRendering :
Start time : 1/13/2007 11:28:02 AM
Shadow body generation time : 0 seconds
Model info : 19116 K ( = 13128 K + 367 K shadow bodies + 5621 K projected)
: 88416 polygons, max. 5642 in one scan-line
End time : 1/13/2007 11:29:03 AM
Elapsed time : 1 minutes 1 seconds
----------------------------------------------------------------------
----------------------------------------------------------------------
Document name : Group2_Master.ppe
Processed : 0 walls 14 objects 0 columns 0 ncBeams
Start time : 1/13/2007 11:30:19 AM
End time : 1/13/2007 11:30:19 AM
Elapsed time : 0 seconds
----------------------------------------------------------------------
Projection : Custom axonometry
Camera azimuth : 33.0216
Start time : 1/13/2007 11:30:19 AM
End time : 1/13/2007 11:30:19 AM
Elapsed time : 0 seconds
----------------------------------------------------------------------
Internal Rendering Engine
Image size : 992 x 648 (2511 K)
----------------------------------------------------------------------
PhotoRendering :
Start time : 1/13/2007 11:30:20 AM
Shadow body generation time : 0 seconds
Model info : 2804 K ( = 1990 K + 61 K shadow bodies + 754 K projected)
: 11117 polygons, max. 992 in one scan-line
End time : 1/13/2007 11:30:55 AM
Elapsed time : 35 seconds
----------------------------------------------------------------------
----------------------------------------------------------------------
Document name : Group2_Master.ppe
Processed : 2 walls 1435 objects 0 columns 0 ncBeams
Start time : 1/13/2007 11:33:09 AM
End time : 1/13/2007 11:33:13 AM
Elapsed time : 4 seconds
----------------------------------------------------------------------
Projection : Custom axonometry
Camera azimuth : 33.0216
Start time : 1/13/2007 11:33:14 AM
End time : 1/13/2007 11:33:14 AM
Elapsed time : 0 seconds
----------------------------------------------------------------------
Projection : Custom axonometry
Camera azimuth : 33.0216
Start time : 1/13/2007 11:34:03 AM
End time : 1/13/2007 11:34:04 AM
Elapsed time : 1 seconds
----------------------------------------------------------------------
Internal Rendering Engine
Image size : 992 x 648 (2511 K)
----------------------------------------------------------------------
Disk is full or not enough memory to create 3D data structure. (error code: 22)
Disk is full or not enough memory to create 3D data structure. (error code: 22)
Projection : Custom axonometry
Camera azimuth : 33.0216
Start time : 1/13/2007 11:50:40 AM
*** User Break ***
End time : 1/13/2007 11:50:44 AM
Elapsed time : 4 seconds
----------------------------------------------------------------------

[Dwight]

You will execute a Problem Isolation Exercise to locate the corrupted element that is causing the wacky 3D file.

This problem is most likely an irrational slab or a library part.
To loacte the bad element, turn off 1/2 of the layers and see if the problem persists. If not, then you know it is in the other 1/2 of the layers.
Show 1/2 of them. If not, etc... Through this process of elimination, you can find the layer where the bad part is.

Take this element out and beat it until it behaves.

[Anonymous]

Thanks Dwight i will try this and let you know.