Sebastiaan

This effect is actually controlled by the renderworks background. The lit fog from the lighting beams is turns on in the renderworks background. When you edit the background it has a checkbox called ‘receive shadows’ this will make sure the lit fog beam stops at a surface that would cause the shadow.

have you made DWG imports in the files that have the shifted user origin? Because a DWG import with default settings can cause this shifted user origin. Something you may not notice if you are unaware of it.

I never used the polar system either. My mind works in XYZ

My main thought was that the two command should become one imho. And yes working plane would give you the onscreen functionality that the move command has. When I explain the move command to new users they always raise a brow when I tell them it works on screen.

Just like the duplicate array uses the rotated horizontal when duplicating.

In that case work from the rotated pln. But still no needs for two commmands

yeah because those views are Perpendicular anyway ☺️ Could be the same command. It’s just moving on x or y. Don’t understand why it needs a different command and why move x 100 woul have to have a a different result. Very counter intuitive

The move command. never understood why I would want to move object relative to screen. And the first thing I do in a new workspace is set the cmd + m shortcut to move 3d

Hi Everyone, Following up on my previous sneak peek: I’ve finally finished setting up the website for my personal toolset at stb-vw.com. The first plugin, Symbol Line, is now available for purchase. It handles the repetitive work of linking symbols along a path using two user-definable points. This creates a "daisy chain" where objects link up perfectly—ideal for temporary event fencing and site layouts. * Placement: Uses two points of the symbol to calculate rotation and placement along the line. * Spacing: Determined manually in the Object Info Palette, or automatically via Loci with the symbol_line_dist record attached inside the symbol definition. * Compatibility: Works with any symbol and any unit (Imperial / Metric). This is the first of several tools I plan to release on the site. More to follow soon! Check it out here: https://stb-vw.com/vectorworks_plugins/symbol-line-vectorworks-plugin I am proud to finally get this online. If you decide to use it, please let me know if the process went well and how you like the tool! #VectorWorks #madewithvectorworks

I have seen similar behavior before. In my case it seems to have to do with nested Symbols in the referenced file. Parts of those symbols would be displaced after the viewport was moved in the work file. Convert to group on those symbols containing nested symbols could resolve it. are there groups or even nested symbols in that referenced document? Is the other document a vwx? Have you moved the viewport in your work file? I just remember another workaround. If I duplicated the design layer containing the viewport. This would make the viewport in the duplicated layer render correctly and I would delete the original design layer. workarounds I know. I filed a bug about it then. It might be related to your experience.

Hi Everyone, I wanted to share a sneak peak of what I have been working on this year. My first own Vectorworks plugin called Symbol Line! This line based tool places symbols with two points along a drawn line creating a daisy chain of symbols on a line, Symbol Line! This tool is especially useful for temporary event fencing, but can be used with any symbol that a user wants to place along line. Why not use Duplicate Along Path? Because that command places only one point of the symbol in the line. Symbol Line places two user definable points of the symbol on the line creating a perfectly linked chain of fences for instance. Works with: any symbol, any unit (imperial / metric). Symbol distances are determined by: Insertion point and manual distance and angle field value in the Object Info Palette, OR Loci with symbol_line_dist record attached placed in the symbol definition. So it does not even matter how the geometry is placed within the symbol. I'm currently working on the last tests before release and creating the sales website that should be online in a matter of weeks. More plugins will follow after this release! Meanwhile I am really curious what you think of the tool and if this could benefit your workflows!

Hi @DomC thank you for your reply. in my case on my Mac the workspace is in the user folder. and I think the desired behavior in both cases would be the same as manually editing the workspace from the workspace editor. The workspace being saved in the default location in the user folder. thank you for pinpointing the possible issue. I will try some thing based on your ideas and might report this as bug too.

@JBenghiat @DomC So I am finally making my plugin ready for release and testing the install script on windows. The install.py below works on Mac, on windows the plugin is installed, but the toolset and tool are not added to the workspace. Various debug dialogs that I tried tell me that the paths are correct but still no toolset in windows. import os import sys import vs tools = [ {"file": "Symbol Line.vso", "universal_name": "Symbol Line", "display_name": "Symbol Line", "tool_mode": 3} ] vw_plugins_path = vs.GetFolderPath(-2) stb_tools_path = os.path.join(vw_plugins_path, "STB-VW Tools") response = vs.AlertQuestion( "Would you like to add the tools to your workspace now?", "This can also be done later manually in the Workspace Editor.", 1, "Yes", "No", "", "" ) if response == 1: palette_display_name = "Tool Sets" palette_universal_name = "Tool_Sets" toolset_universal_name = "STB_Tools" toolset_display_name = "STB Tools" palette_index = -1 palette_count = vs.ws2GetToolsCnt("") for i in range(palette_count): path = vs.ws2GetToolAt("", i) result, name, *_ = vs.ws2GetToolInfo(path) if name == palette_display_name: palette_index = i break if palette_index == -1: created = vs.ws2CreateToolPalette(palette_universal_name, palette_display_name) palette_path = palette_universal_name if created else "" else: palette_path = vs.ws2GetToolAt("", palette_index) if palette_path: toolset_path = f"{palette_path}/{toolset_universal_name}" toolset_count = vs.ws2GetToolsCnt(palette_path) found_toolset = False for i in range(toolset_count): toolset_candidate = vs.ws2GetToolAt(palette_path, i) if toolset_candidate == toolset_universal_name: found_toolset = True break if not found_toolset: icon_path = os.path.join(stb_tools_path, "toolset_icon.svg") vs.ws2CreateToolSet(palette_path, toolset_universal_name, toolset_display_name, icon_path) for tool in tools: found_tool = False tool_count = vs.ws2GetToolsCnt(toolset_path) for i in range(tool_count): existing_tool = vs.ws2GetToolAt(toolset_path, i) if existing_tool == tool["universal_name"]: found_tool = True break if not found_tool: vs.ws2CreateTool(toolset_path, tool["display_name"], tool["tool_mode"]) vs.ws2CommitChanges(False, True) vs.AlrtDialog("Installer finished successfully.")

Also a list of all worksheet functions can be found on the Vectorworks GitHub pages. https://github.com/Vectorworks/developer-worksheets/blob/main/Worksheet Functions/Vectorworks 2026 US.md

It could also vary if your previous export was made from a Top/plan view or a 3D view. As this determines if the export is 2D or 3D. it might be that the second one is 3D and the first one is 2D?