JMR

Hi all, AFAIK it's not possible to stretch a window or a door to a desired width (this functionality has been wished for previously). How about then if we could measure the desired size from the drawing, as with the scale tool? Quite frequently there is a spot into which the door/window has to fit. Currently the only way to get the exact size is to measure the space available and then input it manually to the window OIP. There could be a button in the window OIP with measuring options a bit like below:

Hi all, AFAIK, when exporting a DWG for engineers, the "adjust flipped text" function doesn't work. The result is that, to the engineer, door tags (and some other PIO tags) look like this: While some texts/tags can be flipped manually, I haven't figured out a way of doing this for doors and windows without affecting their handedness. Is there a way? If not, my wish is for NNA to add a "flip tag" functionality so that we can export DWG's that are properly readable.

Indeed, apparently this "bug" is still there?

Ok, done!

An option for the window (and door) tool: Ability to create extrusion-based window geometry from a detail section. That way the windows would finally be geometrically correct. Often a detail section of a certain kind of window configuration is available from a manufacturer -> easy to set up an extrusion, in principle. While it is currently possible via a custom symbol, due to the time required and difficulty of editing, that is not a desired workflow.

I'd also like an option to create an extrusion-based window geometry from a detail section. That way the windows would finally be geometrically correct. We have triple and even quadruple glazing in different configurations, different types of sills etc etc. This lack of attention to architects' most important tools is amazing. Edit: Often we get a detail section of the window from a manufacturer -> easy to set up an extrusion. While it is possible via custom symbol, due to the time required that is not feasible.

Agreed! And the sample rectangle is way too small.

Hi all, I'm getting this error message at opening a VW 2019 SP 5.3 file. Is there a way to find these "some objects"? Other than finding them manually, by chance.

Here is a quick "workaround" example for old elevation values that won't apply any longer. Create a simple symbol with a horizontal line and a a text object linked to a custom record. This works since the elevation range stays roughly the same, meaning that the elevation text length remains the same. I'm pretty sure it's possible to write a Marionette script that would make the line length follow the text width?

I concur. Strikethrough is essential for council approval documents. Extremely laborous and annoying to manually draw lines over numbers.

Some ideas to try -Check 3D conversion settings in preferences, set to low for diagnosing purposes -Check viewport settings, set detail levels etc. to low -Check model geometry for insanely high number of polys -Check viewport rendering settings, turn off everything except eg. openGL -If still no difference turn off classes in the viewport and start turning them on one by one to find the culprit -Turn off planar information in the viewport -Check that no extra layers are visible in the viewport Hidden line viewports can be notoriusly slow, also room elevations.

After hiring a new employee, after a week or so has passed come the dreaded questions about the screen, screen aligned, 3D and working planes....they notice very quickly, that the boss might not be in complete control of these concepts himself...

Texture mapping controls are not available for subdivision objects, please see attached. In order to properly render a simple subdivision object with correct mapping, the subdivision has to be converted to eg. a set of 3D polygons, thus losing subdivision editability.

I cannot apply the mapping to a subdivision object even manually, that's the problem. Automatic operation would be great, but now I just want access to mapping controls.

Ok thanks. That answer was exactly what I was afraid of... 🙂 As a workaround I can change the subdivision object to eg. a 3D polygon and then map that. However, having to do so doesn't make any sense - what's the point of a subdivision object if it cannot be mapped=rendered properly? ...Or am I missing something obvious? Or is this something that has been completely overlooked?