Assemblage

Tried it..same result. No idea what's wrong...doesn't like PC's? Happy to send the little test files; there are 3 at 100K each.

It would be great if you could expand on this Jeffrey. I made the changes suggested, but still just get a column of "0"s. There are no spaces in the record or field names, but I tried all these anyway: =Room.Name, ='Room.Name', =(Room.Name), =('Room.Name')...and all return a "0" in every cell as before. The =AREA returns all the correct areas, and just the fact that sub-rows under the database header are being generated shows the worksheet is finding the objects without any problem. The worksheet is picking up the object attributes but not the data contained in the database record..I have no idea why. As I mentioned, if make identical worksheets in files A and B there is no problem, so I don't think I've made bad object records and fields. Clearly the aim however is to have the worksheet reside in the file with all the DVLPs (my file C), not the source files. The Help notes do not give any advice about retrieving record information when using DLVPs. I looked at the Ellicott worksheet record retrieval syntax and it appears to be the same as I have it. I've made a number of searches through the Community Board but can't find advice for this problem; apologies in advance if there is an actual discussion of this.

We're having issues with this, and reproduced the problem in a very simple test: There are 3 files: A and B are referenced into C using DLVPs, 'constructing' the drawing in C's design layer, as Jeffrey indicates. The aim is to make a simple room schedule in C, listing room name, number, and area. A and B's Record Format is simply "Room", with one field: "Number" (an integrer). The objects are named in the OIP. Problem 1: Using "=N" for the room name in the worksheet produces "NNA#2_Living" instead of just "Living". Problem 2: Using "=Room.Number" produces just a "0" in each cell. However the area works fine using "=AREA". Neither problem occurs if I create separate worksheets in A and then in B (but these are not very useful). I've a deadline looming...any help appreciated!!

Using 2009 (SP3), we are finding symbols are changing back to earlier versions of themselves found in other files in the project folder. In our current project for example, we find even after closing and reopening all VW programs in our project team (so all reference files should have resolved themselves), one can still open a file and find the old symbol showing. VW often does not find the updated symbol, and finds the old version in one or other of project files. In case it is related to the problem, we use referenced layers and not DLVPs, as we found the DLVPs increased files sizes by 10 times or more.

Simple one: Am in 3D 2009. Can snap points on 3D polygons, but not on extrudes or generic solids. I can select and go into them, but can't snap to any point. Layers and classes all set to 'Show/snap/modify', so shouldn't be that. I'm finding it is the same problem in any view, including 'Top/plan'. Any help appreciated.

Anyone? Has anyone experienced similar?

Just tried some experiments in new empty files - you're right, it does move as it should...thanks everyone. There must be a problem with the layer/class designations. I'll sort through and report back briefly to cap the query off. Many thanks,

VW is a fraction of the cost of Revit, which adds up fast with multiple users. It will only chip into the Autodesk markshare however if the functionality is really robust (eg database notes, sheets, no crashing, automatic updating viewports, etc, etc).

Yes, but what I meant was when stretching an area which includes groups in their entirety, the groups don't move. That is, we're not trying to stretch the group, just have it move along with the rest of the stretched objects.

In Microstation/AutoCAD et al, you draw a fence around nodes, and stretch them. Using '2D Reshape' in VW in the same way, it doesn't move anything Grouped, in a Symbol, etc. Are we missing something?

..it seems to be a problem with the sheet layer viewport being rotated 90deg, and only parts of the symbol rotate and others don't. We don't understand why some shapes rotate with the viewport correctly and others choose not to.

Hi all. We're having problems with parts of symbols rotating unexpectedly in sheet layer viewports. They look fine in the design layers. Anyone experiencing this?

Good to know change is on the way Jeffery. We get different bugs to the ones Will is getting, possibly due to our PC platform..? Problems we are experiencing include: - The most important functionality, to easily and automatically update instances of notes from a central database, is not easy and not automatic; - "Description" changes by itself, seemingly randomly; - Carriage returns are not saved, ie a note which has 5 short lines of text is converted by the database into a single long line of text, with small boxes where the carriage returns were. The user then has to go in and manually delete the boxes and reinstate each carriage return for every instance of the note. It's quite laborious. Peter

We recently looked hard at moving our whole office to Revit for it's BIM capability, but decided to stick with VW and upgrade to 2009. Like any company of architects, we work with literally thousands of callouts and need the database functionality as a basic feature. Jeffrey, are there any plans to fix this?

Further to this, are there any plans to have Notes update automatically from the database (without the need to 'reconcile')? P

Found it - many thanks. It was just not in the current Workspace, and needed adding in.

I'm on VW Fundamentals/Architect/Renderworks and wanting to create a section viewport, but it does not seem to be available in the View menu...is this functionality not available in Architect?

If it's any help, this is how we structure our files: we do all our drawings in one or more files we call "design files". We then have a series of files we call "sheet files", and we use the sheet layers in these files to carry all the viewports and text (eg notes, title blocks etc). Like Bob, we don't use design layer viewports yet; all our viewports are on the sheet layers of our "sheet files". Any ideas??

We still don't know what's causing it, but it seems that if all the workgroup reference files are set to scale 1:1, then they arrive in the right spot. If not, they arrive in shifted (usually by just a small amount (eg 1 or 2 cm in the sheet file). So, currently we're trying remember to always set files to 1:1 scale when closing them, so they go through to other files they're referenced into as 1:1. It's very odd. We don't see why the scale of the reference should affect a sheetfile viewport when all the drawing lines etc are drawn correctly in the right place across all the various files. PB

We still don't know what's causing it, but it seems that if all the workgroup reference files are set to scale 1:1, then they arrive in the right spot. If not, they arrive in shifted (usually by just a small amount (eg 1 or 2 cm in the sheet file). So, currently we're trying remember to always set files to 1:1 scale when closing them, so they go through to other files they're referenced into as 1:1. It's very odd. We don't see why the scale of the reference should affect a sheetfile viewport when all the drawing lines etc are drawn correctly in the right place across all the various files. PB

Workgroup references throughout our projects are moving around randomly in the viewports of the sheet files they're referenced in to. This is causing serious chaos in our company, and great loss of time and resources. It is also very basic functionality any company relying on drawings would expect from any CAD software. Following other threads on this site, we have studiously avoided viewport rotation, and have stripped reference files out of any contributing files to sheet files to avoid circular references. No joy. Solution please asap. PB

Workgroup references throughout our projects are moving around randomly in the viewports of the sheet files they're referenced in to. This is causing serious chaos in our company, and great loss of time and resources. It is also very basic functionality any company relying on drawings would expect from any CAD software. Following other threads on this site, we have studiously avoided viewport rotation, and have stripped reference files out of any contributing files to sheet files to avoid circular references. No joy. Solution please asap. PB

We using PCs. The result is mainly boxes with crosses in them, with the occassional single letter appearing.

We use Myriad Pro font, and issue drawings by pdf. No problem with version 12.5. On 2008 however, all text in the pdf is screwed up. If we use Ariel there is no problem, but we don't want this as it changes all our branding. Any ideas?