Neil Barman

Good idea. Head on over to the Public Roadmap and send it in. It’s great that you’ve tried the feature and have an idea for an improvement.

Interesting idea… I recommend heading to the Public Roadmap (see my first post) and submitting your idea. Ideally, explain how you would use Object Level Visibility inside a symbol so that we can understand how you would put it to use. Thanks!

Great idea to submit via the “submit your idea” button atop the Public Roadmap 😄 (See the link in my first post.)

One way that I am using Object Level Visibility is to hide walls here or there as I work on the interior design of a room... For example, I am currently working on a small project within one room (I can't tell you what it is yet, but you'll see in time). While working on what is inside the room, I often want to quickly switch off one wall or another to get a view into the room from a particular location. Yes, I could use the Clip Cube to accomplish a similar effect, but since this is a small project I'm finding it quicker and easier to just hide the wall that is blocking my view into the room. And when I want to work on just one object inside that room, I select it, then use the "Show selected objects only" command in the view menu to isolate it. (I too have added the Object Level Visibility commands to my right-click or Object Context menu for my custom workspace like @Luis M Ruiz has, but I'm showing the command in its default location for those who haven't used it yet.) Keep the ideas coming!

Bonjour @clemence, notre équipe d'assistance technique a répondu au message que vous lui avez envoyé par courriel. Veuillez consulter votre compte de messagerie électronique pour obtenir de l'aide sur la marche à suivre.

Leading up to the release of v2025 I had the opportunity to work with the new Object Level Visibility feature a lot. I soon discovered that what I thought would be a useful feature had many more applications that I had first imagined and it quickly became one of my favourite new features. Now that Object Level Visibility is available for you to use, I’m wondering how you do use it or how you envision using it as part of your design and documentation workflows. Please share your ideas below to help inform and inspire others. Thanks! (If you have other feedback that you would like to share about the feature, please visit our Public Roadmap and send us your feedback via the “Submit your idea” button.)

For anyone needing to contact Chaos/Enscape technical support, please use this link to reach them: https://enscape3d.com/contact-us/

HI @nahekul, If I may ask, what are you trying to achieve?

@E|FATo see the differences, after watching the AI Visualizer material that we have made, I recommend doing the course "Stable Diffusion: Tips, Tricks, and Techniques" by Ben Long on Linkedin Learning. What that course provided to me are tips and tricks to with our AI Visualizer of course but also a tremendous appreciation for having the AI Visualizer built into Vectorworks and not having to install/manage my own Stable Diffusion server or use a separate third-party service. Also, that course helped considerably to understand where such AI technology is currently at both in terms of its strengths and weaknesses.

Might I be able to suggest that, for the time being, you double-click the Subdivision object when you would like to edit it? That will activate the Edit Subdivision tool. It may even turn out to be quicker than moving your mouse over to the Reshape tool or reaching for that tool’s keyboard shortcut.

@Archistyles Thank you so much for this info and the sample files! They will help quite a bit as the feature takes shape (figuratively and literally).

@hollister design Studio Are you still using Landmark 2023 SP6 as is indicated in your forum signature?

@anniemitch If the Windows mouse pointer settings are not what is causing the pointer size to change for you, I'm not sure what is. Please do know however there is no Vectorworks setting causing it. It's always worth asking the braintrust here, but in this case there's no Vectorworks setting for it. Incidentally, I have checked our system and I see no other mentions of this occurring for anyone else. Something to try, if you wish, would be to fully uninstall Vectorworks using the uninstaller in the application folder, then reinstall Vectorworks and make sure you've fully updated it too. That may help remove the issue in case Windows is somehow having a problem with your current installation of it. Beyond that, you may want to report it to your local Vectorworks technical support in order to log the issue. If they can replicate the issue then it can be investigated by our engineers.

@anniemitch I mentioned to a colleague of mine what you were seeing and he did some digging (He has a Windows computer. I don't.) It appears that Windows has some system-wide "mouse pointer" settings that do what you have shown in your screen recording. See the image below. He also confirmed that the cursor behaviour you are seeing is not related to Vectorworks' own options.

@anniemitch Thank you for the screen recording and photographs of your screen. They do help quite a bit... I see what you mean about the cursor being larger over the drawing area versus its size over the view bar. I am noticing too in the screen recording that your cursor changes colour when it moves between the drawing area and the UI palettes and view bar. Neither of these cursor effects are part of Vectorworks options – I suspect that you have some other installed software or system/accessibility setting affecting the cursor's appearance. I recommend looking into that and observing how your cursor behaves in other applications as well. Also, I noticed that during your screen recording it appears that you are clicking in one location to draw a rectangle but the rectangle is actually being drawing at another location. This may indicate that you have a GPU issue... and looking at the specs of the HP Spectre x360, that machine has limited power in this regard. (It seems to only have an integrated, low power graphics unit as opposed to an actual graphics card. Note that from the Vectorworks system requirements a minimum of 2GB of dedicated VRAM is recommended even for entry level work.) I recommend keeping an eye on that and if you encounter visual oddities, bear in mind that they may be related to the computer's specs.