JoarL

Most of my files were started in VW2023 or earlier so I am not sure i can produce a file with the behaviour. Today, when it happened while working on an older file I opened a file created in VW2024 and the behaviour carried over, after closing the files and creating a new one the snapping was back to normal. Could this be memory related?

i5 iMac running Sonoma 14.1.1

I have also experienced the same issue as Skia_D since installing VW2024, never before. I loose the ability to grab objects by the snap handles (cross cursor) and just get the scale cursor (arrow). Sometimes I can use the arrow cursor to grab an object by the midpoint, or close to a corner, and snap that way so it's not like snapping is completely disabled, I just can't grab objects precisely. This happens with objects on the same layer and class. This happens several times each day, sometimes the program start working normally again after a little while, sometimes I have to restart it. Another snap related issue in VW2024: The object snap sometimes disables itself for unknown reasons (grey icon in the toolbar), a colleague has also experienced the same, works normally after re-enabeling.

I have this option on, it only hides the blank window.

IMHO there are some other issues related to how the application window is handled on Mac: With the red close button greyed out there is no way to fully hide the program without clicking cmd+H, and you are always left with the useless blank application window after closing the last document. After clicking back and forth between VW and Finder, with no document open, you are also just left with a stupid empty window. IMHO the way this is done in Photoshop, where the start page comes up after closing the last document makes more sense. Speaking of the start page: Wouldn't it make sense to allow changing VW preferences from this window?

I'm having some problems exporting stairs created with the stair tool from VW2023 Architect SP4 to IFC. Earlier exports from the same file used to work fine in SP3, but in SP4 it's (almost) no go. After some testing I can't get stairs to export to IFC2x3 at all. If I convert the stairs to 3D mesh, and add the IfcStair tag it exports to IFC2x3 like it used to, but this is not a very practical solution. Exporting stairs to IFC4 seems to work, but only if the file has been set up for this before the stair is created. Exporting to IFC4 also seems to exclude all other custom objects created with IFC2x3 tags (typically furniture), so this is even less of a practical solution. Does anybody have any experience with this, or possible workarounds I have missed?

I've looked into this some more and the IFC-data seems to describe which side the opening (handle) is. Around here (Norway) it's common to describe windows/doors as left/right according to which side the hinge is, effectively the opposite of the IFC standard it seems. With that said; defaulting tilt and turn windows to opening outwards, and reversing the front/back view between window creation and graphic legends is still a bit silly.

I have noticed some issues with how tilt and turn (and other) windows describe the opening direction and handedness, getting window/door openings right usually requires some attention so it would be an advantage if this was working 100% out of the box. 1. As far as I can tell tilt and turn windows always open towards the inside IRL, however in the window plug-in settings they are displayed as opening towards the outside. 2. In the window plug-in settings the front view will be from the inside, however in the new graphic legend tool the front view is from the outside. I'm used to drawing window schedules from the outside so the graphic legend is correct IMHO, any way it should be consistent. 3. I'm also used to describe the handedness of the opening as the side with the hinges, when seen from the opening side (the inside for a tilt and turn window). There might be some cultural differences at play here, but to me the IFC-data opening direction is the opposite of what is displayed in the model. This also seems to be the case for all doors and window types I have looked at. Possible workarounds: 1. Ignore the 3D opening, the windows display correctly as long as they are closed. 2. Flip the windows in the plan (to make them open inward), if necessary correct IFC-data manually. Is there something I have missed here, or are these oversights from VW's side?

Unfortunately, what I want to do is not as easy as adding a tag to an object. I need to pull information from multiple Space objects, across multiple floors (layers) of the building, and display the information in a table next to the drawing on a Sheet layer. So far the only method I have found that mostly works is worksheets, do you have a suggestion for how this can be accomplished with Data Tags?

Thank you for your effort, but I already know how to do this. As far as I can tell the Data Tag will not be able to display any more information than the label for the Space object anyway.

I have tested Data Tags some more and spreadsheet functions doesn't work as I had hoped, so I'm back to worksheets.

The Data Tag method I have found adds extra steps, with the possibility for user error, I need hundreds of tags so this is an important concern. The table I want to create also shouldn't be linked to drawing objects like Data Tags are. What I want to accomplish is also a bit more complex than shown in the example. I'm currently working on a housing project with over 100 apartments. For each apartment there will be a separate drawing, along with a table of areas and other information. The table needs to contain gross area, net area, balcony area, internal storage area, extrenal storage area, and some other information stored in the User Defined Info fields. The area part works but not the other information. So far I also haven't been able to get OBJECTDATA (or other functions) to work. I think I read somewhere that spreadsheet commands are now possible in Data Tags. This actually seems like a good option (with the apartment number as the link), but I still need to collect the User Defined Info from the Space object in some way.

Here is my test file. worksheet_testfile_VW2022.vwx

I'm trying to get text from the User Defined Info field (and some other info) for a specific room number into a Worksheet cell. I can accomplish this by generating a report, but I also want to make a small worksheet to display along with a smaller part of the floor plan (an apartment). I'm able to do this with areas but not with this type of text. I'm not sure if this is impossible, if I just haven't found the right worksheet function, or if the syntax is wrong. Any ideas of how to accomplish this?

Is the drawing 2D? There is a "display 2D objects" (or something like that) checkbox in the create layer link dialog, if this isn?t marked only 3D objects will appear. JoarL