islandmon

Try>Excel>parse data @10,000 point intervals>copy>export to tab>import VW1... then repeat for VW2.... Finally, use WGR to compile the data into a master.

did you try > database>column>SUM

on the website side-bar > a 'mouse-over' hi-lite for those links is required

Try: Use_underscores_instead_of_spaces_in_file_names and avoid filenames which start with numerics like ' 0 '

IMHO : The VW Parent File A declares the Drawing Origin ( default = 0,0 ) for all subsequent Container insertions. If you desire a different Origin then create a Parent File B with Origin offset and it will be the overriding structure for all embedded child-Containers relative to it. Each file will display data based on the relation to the ParentOrigin. That being said VW allows for User declaration of unlimited Child-PageContainer Origins via "Set Origin ", but these supplemental Origins are always relative to the Parent File Origin. Therefore, since referenced files may be of kind Parent and/or Child, they import into the Parent File C with their Origin information relative to the existing Parent C Origin. However, this rule does not apply to DWG/DXF imports which may override the VW File Origin in order to rectify the translation ( thereby creating endless hassle for VW Users, et al. ) .

Actually VW pages-out/writes-out a very detailed description of the working environment associated with a complex User defined database structure ( assuming that said User will want to return to that environment sometime in the future ). Whereas, it's possible to just punch-out the object math & text ( thereby eliminating all the User variables ) via exports to obtain significantly smaller ( resolution dependent ) file sizes.

Blender 2.49a Release examples

A "right answer" is only right ... if & when it is determined to be "right" by someone with sufficient knowledge to make an informed judgement. Add a fourth factor to the analysis list: Comparison of the results with an independent Project or experience with similar characteristics. and then a fifth factor: Use common sense. and a sixth factor: Don't shoot the messenger !

Check the PIO > Data settings.. that "flange-thing" sure looks like a Jamb on steroids...

If they tell you ... then they would have to kill you ... and that would be one less User !

Think about each activity as involving Containers. With each Container having pre-sets & Over-rides depending on the nesting sequence. It all comes down to the complexities of ye olde Set Theory http://en.wikipedia.org/wiki/Set_Theory The easiest solution is to just maintain a common default Origin ( 000 ), then use Loci with coordinate offsets for everything, as req'd.

Historically, the easiest way to identify & prevent the migration of the Origin is to place a locked Locus at the Origin 000 of each DLayer. Imported Layers from DWG/DXF usually have the Origin at the lower left. Reversing those page coordinates is the offset distance to the default VW Origin (page center ).

Here'a an example of a model steel stair with ExtudeAlongPath railing: http://www.fractalnet.org/gallery2/v/CAD/StructSteel/CAD_ExtrudeAlongpath_Stair.JPG.html

Christiaan , is that a rhetorical question ? Gotta luv this IFC2x4 statement : my eye-balls are spinning around with the new control entity for proximity (relative distance between objects), for the capturing requirement (related constraint) or the actual situation (as designed or built). However, my brain is still using the same external reference mechanism as the other resource objects. Thanx for the heads-up ... : )

Window PIO >Data>Net Glazed

select > object > command-6

I'm not an expert on any of this .. but it seems that Set Theory would be invaluable. Thus avoiding the inherent recursion problem: { Criteria Set Procedure } { If > Criteria > Then > Set If > Set > Then > Procedure If > Procedure > Then > Set }

This 8x8 GlassBlock texture was provided by a Forum User.

We all must be careful about generating procedural command 'loops' . In the olde days this was not so much of an issue but now with speedier inputs >processor cycles it is common to stack multiple commands without knowing it. Some Users have a bad habit of clicking all over the place .. not realizing the implications. This holds true for every application not just VW. When things go wrong .. patience is often the best option. You can use Activity Monitor to watch the ebb & flow of the processor(s) as you work. Noting your RAM specs ... adding 2Gb more RAM will provide significant VW performance improvements.

It would appear that there's insufficient RAM

A wall is meant to be something other than a tree... when you want it to ascend don't expect it to make a bend ...

What kind of router ? What are the protocols & virtual services ? Are you using static addressing ?

There 2 basic considerations along with the page size & dpi: vector & raster. Vector is best for line work , but will create huge files for complex renderings. Raster sucks for the 2d work but really shines when there are various images and renderings involved, because of the downsampling to jpeg. The trick is to find a 'happy medium' between the two based on what you desire to provide the client. If file size is not an issue, then go for broke. Acrobat Professional has an option to 'reduce file size ' which analyzes the page and uses various settings to combine vectors & rasters in the most efficient manner. But the results can sometimes be weird especially with OpenGL Renderings. Export to PDF is usually the best option over all. But sometimes Print To PDF works better because it use the printers PPD description. This is most likely where you're experiencing the conversion slow down. The Printer is set to print/plot from an image not vectors. Therefore, the Print To PDF uses the Printer Driver to convert the vectorized VW page to an image ( printer dpi =500+ ) raster prior to saving to the print spool. Does your printer driver have a setting for switching between vector <> raster printing ?

Check out the >Console>Crashlog>VW... Are you using WGR ? Tried Purging unused objects... ? and , of course, do a Safe-Boot> Restart ( holding down shift key ) then check the permissions using Disk Utility or other maintenance utility. Then restart normally.

PDF Distiller conversion offers a vector > raster image conversion which is used to reduce the file size of various rendering modes like Final Shaded Polygon. This may be what "Flattening x% " is referring to.