Pat Stanford

Did a restart solve you problem? Or are you still stuck?

Quick off the top of my head response. Zero testing done, so I may be way off base. Plants are PlugIn Objects. Plant Objects contain symbols. Those Symbols may contain other symbols. So if you set you criteria to be Plants, you should get the right count. If you set the criteria to be Plants or Symbols you should get a double count. If you set the criteria to be Symbols and the check the Include objects in PIOs, you "should" get the right count. If you set the criteria to be Symbols and you check both the Include Objects in Symbols and the Include Objects in PIOs buttons you should get at least a double count. HTH

There is no automatic way to do what you want, but you can do it marionettily (I know that is not a word, but you know what I mean.) You will have to create text objects in marionette on the drawing and also store that data into a record.field combination. If you want to be able to have the user enter data in the OIP, you will have to read the data from the record.field combination and then use that data to do the calculations in the marionette object and then store back the results (if you have changed anything) at the end of the marionette network. Take a look that these nested threads for more information. Ask again if you still need more help.

You are very welcome. Ask again when you get stuck.

Have you tried isolating the imported DWG into a separate VWX file and then referencing that file into your working file? Then if you get an update all you have to update is the reference file. Search for Shuttle File in the forum for more information. And more than likely the slowness is not due to 7000 objects, but probably just a few items that look simple but are actually polygons with thousands of vertices.

@Mark Aceto you are only missing two things. The ability to speak Dutch, and living in the Netherlands. ;-) Localized versions of VW often have tools added to meet local requirements. Many of these tools would be nice to bring back to the US version. But often, like with the Stair tool, while they work extremely well in a highly structured environment, but they cause massive frustration for users who just want to get things done and don't care to learn all of the details of a very complex tool.

It probably is my magnetic personality. ;-). Thinks tend to work when I am around.

Check the database header row cell for the Quantity column and make sure the Sum Values check box is checked. It looks like you have multiple rows SUMmarized together. In any column that the data is different for different quantities you get the "---" mark to indicate that there are multiple values. To help explain think about this. The Pr that shows a quantity of 25 could be a single instance with quantity of 25 or it could be three instances with a quantity of 25 each. As long as they are all identical the database will show the identical value. But the value you want to see if (3 x 25)=75. When you turn on Sum Values for a column it will add up all those values instead of showing the identical value or the --- HTH

This is likely due to the fact that the space bar is now used for both the Boomerang mode and also for Smart Options Display (pop up tool bars). If the mouse is completely still, then the Smart Options Display takes priority. If it is slightly moving then you get Boomerang. Try going to Vectorworks Preferences:Smart Options Display pane and unchecking the Show with Space Bar option and see if that helps.

In the Worksheet menu, check the preferences and see what you have the Images DPI set to. It appears to be broken. on my machine 72 DPI looks pretty close to what is on the layer while 300 DPI has all of the lines very thin and washed out.

Wasn't there a thread floating around recently about "everything" being VW's fault? Doesn't Revit export make that even more so? At least with IFC you can point to Solibri being the arbiter of correctness. A Revit export makes Revit (and whatever half [or less] trained operator) the arbiter of correctness. Send them the IFC when they can't work with that, tell them you will help them out and send the Revit file. They will be grateful they didn't have to mess with the IFC and you don't have to tell them where the Revit came from. ;-) All of the above if heresy. I have only exported one Revit file from VW and it took forever for what should have been a simple file. Still have not heard back it is was usable or if they went with the STEP/IGES files that I sent (and which took less than 1/4 the time to export both than the Revit file.)

It might have been on the Beta forum, but I am certain that a senior VW person who I respect talked about extending the objects Materials can be applied to. I don't know if that will be far enough for your needs, but it is (I believe) much farther than they are now.

@willofmaine I am not seeing this on my 16" MacBook Pro on Best Performance. Since this is driving you batty, can you take a few minutes to do a test please? Go to System Preferences:Users & Groups and create a new user. Log into that new user. Launch VW. Create a new blank file and do something that normally would not redraw until you zoom. Does it do so in this user? Open a drawing that normally requires zoom to get it to redraw. Change something and see if the zoom is required. The above tests will help determine if it is a problem with the file or with VW or with your User account. If you have already tried the above. Sorry about that.

As it was explained to me, in the current state, Materials were set first for objects that are likely to be "site built" and that having additional data about the area/volume/weight/etc. could provide value. Since the majority of doors/windows are purchased as complete units rather than as an assembly of pieces to be assembled on site, they were left for later. Materials do not have to be an all or nothing item. Using Materials on the components of a wall for instance might prove to be very useful in calculating the area or volume of each material in estimating. The use of materials in a concrete floor in a "second story" garage for a house on a hillside might prove very useful in calculating the weight the structure below has to support. The fact that they can not also be used to apply textures to a door is secondary. I don't know if trusses are Material Aware, but if they are it would provide an additional way to add the weight of the truss to a lighting position. One of the Beta testers believes that materials should be data only and that the attributes and textures have been added actually detract from their usefullness. That is what Classes are for. If Materials don't help your workflow, don't use them, but also keep an eye open for when they may provide value.

I am not seeing this in VW2021SP2. Try creating a new blank file (not from a template) and placing a scale object there using a super standard font like Arial. Does it still have the spacing problem?

And as always, if you are using a custom workspace, make sure you try one of the defaults. Often workspaces brought forward from previous versions don't have the proper links to the most current version of tools.

Can you check the file in Solibri? If it is correct there, then it is likely an import problem.

By any chance do you have a Viewport Class Override set for the Class the landscape area is in? That would cause it to use the Override settings instead of the Class settings.

Similar setup here and I do not get a crash when exporting EPSF. What happens if you create a very simple file and export that?

I have very bad eyes and a very low requirement for quality, so I think that even your original image looks very good. Yes there is a time difference if you go to higher standards. One possibility is to set the sheet layer resolution to something low to match the resolution you are running your monitor at so you are not calculating extra pixels while you are working. Then once you get it set the so you are ready to do the final, set the layer resolution up. Running at 150 dpi vs 300 dpi should take 1/4 of the time. Running at 100 dpi vs 300 dpi should take 11% of the time. HTH. Good Luck in finding your balance.

What is the render mode you are using? Custom Renderworks? Or something else? Have you tried setting everything to Hoch or Sehr Hoch as a test to see if that help? Otherwise, I am about our of ideas. I will keep thinking about what else it may be.

Hi Tom, thanks for sending the file. Much easier to see what is happening in your file than to try and create a sample. Answering here so it goes into the communal memory. You have your Autohybrid set to Use 2D Attributes of the Contained Object(s). I think this should actually be named Use 2D Attributes of the Sectioning Object(s). See the Fill section in the attached screen shot. Since this is not a Section, I think the lines are getting put into some kind of "virtual class" that is not the class of the objects and therefore not being properly overridden in the Viewport. In VW, Inc. terms, I would bet this is Working as Designed (WAD) rather than being a bug. Certainly worth submitting a Wish on if it bothers you. The work around is to set the Autohybrid to Use Class 2D Attributes. See the Line section in the attached screenshot. This will make the objects in the viewport actually use the class of the Autohybrid and allows the Class Override in the viewport to work. If you don't want to have to change all 29 instances manually, this can be changed in a worksheet relatively easily. Create a Worksheet. Create a Database using Type is AutoHybrid. Set the Column A Formula to Records:AutoHybrid:Below Cutplane Fill. Set the Column B formula to Below Cutplane Pen. Set Column A to SUMmarize. Select the only cell still showing click the Disclosure Triangle and change it to Use Class 2D Attributes. Repeat in Column B.

With the OIP selected if you hit the Background Render Settings button in the OIP, what are the settings for this dialog box?

What version of VW? What Operating System? What hardware? What kind of drawing? More information please.

The next step is to create a new User account in Mac OS and launch VW from there and see if you can dock palettes.