- #Vectorworks student windows software
- #Vectorworks student windows code
- #Vectorworks student windows windows
Given the severity of your symptoms I'm not surprised you say that! Conversely, the fact that they are unique and severe suggests they will be caused by conditions specific to your computer.
#Vectorworks student windows software
Vectorworks Worst software I've ever had,all icons are gone!!! Some DLLs used by these apps are known to be problematic. Apps that use the following DLLs should not be run at the same time as Vectorworks. The file path shown when searching for these DLLs can denote which program files should be avoided, for example “C:\Program Files\NZXT CAM\.\ graphics-hook64.dll”. When Vectorworks operates normally you have found the problematic startup item(s).Ĭlearing these items from Startup Apps should restore normal Vectorworks operation. If Vectorworks is still crashing, re-enable the items you disabled and move further down the list.
#Vectorworks student windows windows
Type “Startup Apps” in the search field of your Windows Taskbar.ĭisable items a few at a time, and restart Vectorworks to see if Vectorworks is operating normally or still crashing. Sometimes these apps automatically start up with the system. Clearing them requires changing the Startup Apps settings as follows:
#Vectorworks student windows code
We have tracked these issues to utility apps being installed which modify the functionality of DirectX 11. These apps sometimes show overlaid graphics on top of normal graphics, or otherwise inject code into the basic graphics handling routines of DirectX 11. Graphics-intensive applications like Vectorworks and others can be negatively impacted by these apps, when normal graphics operations behave incorrectly. We recommend not using such apps at the same time as Vectorworks. Apologies in advance as I'm guessing this is going to turn out to be something pretty basic that i've overlooked.Some Vectorworks 2022 Windows users have reported crashing with basic document window operations such as resizing the application window, tearing off palettes, or switching workspaces. I'd really rather not have to abandon this file and start again, so any thoughts on what the problem might be would be much appreciated. I've tried switching between Architect and Landmark workspaces, varying snap properties, messing around with auto-classing, changing wall and object properties, but no dice with any. Annoyingly I can't seem to isolate what the issue with this particular file is.
The opposite applies if I use objects that I can't grab in this file in others, whereupon the problem disapears. However, when I take objects from these (which I know to work) into the problem file, they too become un-grabbable. This problem doesn't seem to effect other files I've been working with. I can't even get the grab grip to appear on the selection cursor for the object. The only way to move them is by using 'set position' in the OIP.
Basically, after inserting windows and doors, whilst i'm able to select them, i'm then unable to 'grab' them and move them with the cursor, either within the same wall or to move them out or elsewhere.
I'm experiencing an unexpected and seemingly fairly basic problem with objects inserted into walls in a file i've been working on. I'm currently running a student 2017 license. I'm trying to re-learn Vectorworks after a long break.
0 kommentar(er)
