JustinH
-
Posts
95 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Articles
Marionette
Store
Posts posted by JustinH
-
-
can you attach the file, or just part or the file that exhibits the bug here so we can investigate it?
-
- Popular Post
- Popular Post
There was a fix for this flickering issue put in SP2 but a problem was found with it recently so it was reverted. SP3 has a better fix with no issues found yet. Here is video of upcoming SP2 on left (still has flicker bug) and SP3 on right (bug fixed):
- 7
- 2
-
- Popular Post
Shaded render mode in Vectorworks 2022 supports 8 lights only. Shaded render mode in Vectorworks 2023 removes that limitation https://www.vectorworks.net/en-US/public-roadmap <edited for PR>
- 4
- 2
-
When I opened the file I didn't see the glitch -- I didn't find an object far from the origin but I can reproduce your glitch by adding in a sphere at 9999999' away from the origin, like this: So Andy nailed it. This is a numeric precision issue with Shaded (it's a common issue with OpenGL/DirectX/Metal/Vulkan as they use 32-bit floating point numbers for performance instead of 64-bit).
- 1
-
hi, I agree those screenshots look a bit strange. At first I was thinking maybe that was a unified view related problem (Document Preferences -> Legacy 2D -> Turn off unified view) but I wasn't able to reproduce. Then I thought about huge model which can introduce precision issues giving something Shaded render that looks like that. Technically it looks like depth testing is inverted. If you can send me the file, or just part of it, then I can tell you what the problem is. Thanks
-
I logged a jira bug suggesting the Datasmith Direct Link Preferences dialog have an option to specify the origin in VB-188291 Twinmotion numeric precision issues
- 1
-
3 hours ago, rjtiedeman said:
... As of about 1 hour of use the only thing I can report is that VW seams very slow. I have no way to compare it to the previous OS but it just seams slower in shaded mode then before.. ...
We would be interested to do a performance analysis for Shaded mode on your file to see why it seems slow, if that's a possibility.
-
So it sounds like the issue only happens on that particular computer; I didn't see the same glitch on a simple file. You could try turning off VectorworksPreferences->Display->Accelerate graphics as that enables code paths that are heavily dependent on GPU and driver. If you can tell us the machine specs then maybe we can reproduce the issue with one of our machines. The dxdiag utility can write detailed machine specs to a text file that you can upload here, like this:
-
It looks like you might have been in a perspective 3D view with some selected objects and then switched to Plan but the selection graphics didn't go away as they should have.
Is the bug easy to reproduce? If so, can you attach a recording of opening the file and getting to the point in the picture above? Perhaps the issue is something specific to that file. If you can attach the file here, or email it to us jhutchison@vectorworks.net then we can look into that possibility.
-
On 7/2/2021 at 3:17 PM, zoomer said:
Hmmh,
seems I can't even create any light !?
Red Warning in status bar :
"created Light is not visible"
VW 2021 SP4
M1 Mac Mini
macOS 12 Monterey Public Beta
sounds like you have Vectorworks Preferences -> Display -> Display Light Objects option set to Never. Change it to Always as shown here:
- 1
-
I just verified the crash has been fixed testing one build before the fix and one after:
VW2022 SP2 build 614210 -- has crash
VW2022 SP2 build 615870 -- no crashLooks like SP2 becomes publicly available in just over 1 month
- 3
-
QA helped me locate the bug ticket that describes the crash you discovered https://jira.vectorworks.net/browse/VB-181752 Looks like the crash was macOS specific-- that's why I wasn't duplicating it. The bug was fixed last month and has been verified fixed in VW2022 SP2. I'll double check that it's been fixed and report back
- 2
-
hm.. no luck crashing with Lighting Device: must be some other contributing factor.. could be a document/Vectorworks preference maybe. I'll ask around to see if anyone else can crash
-
I can't reproduce the crash. Maybe you can attach a video so I can try following your steps more precisely. This is what I see:
-
send to me jhutchison@vectorworks.net and I can probably tell you the reason it's happening. If it still happening in VW2022 then we can probably put in a fix for SP3
-
appears to be zero height floating pane issue. I don't see this artifact with floating panes in general
-
Can you save and attach that untitled3 file shown in the video so we can investigate?
-
6 hours ago, Nathaniel.C said:
That is unfortunte, I have two files that do it currently and they are extremely large and detailed. with a bunch of the loci imbedded in symbols and some on the same class by the looks of it. which is definately not an easy task.
There must be some way to fix this, as it has happened quite randomly and not when i first started the file.
Also the draw lines arn't infinte.
Hi, can you attach the file (or subset of it) exhibiting the problem here so we can take a look?
-
On 2/8/2021 at 6:03 PM, Sue C. said:
On Vectorworks 2021 and it still bogs. I've deleted all the layers with pdfs on them and it seemed to improve the performance somewhat, but I'm just doing a simple command like copying lines using the offset tool and I'm still getting a beachball. The file is all of 28mb. So no, 2021 still hasn't fixed lagging issues. I'm on a MacBook Pro that's compatible with the requirements for mid-level profile projects per vectorworks requirements, so I should have enough computing power.
Hi, if you can attach a file or subset of the file causing the slowdown along with a screen recording of what you are doing we could investigate more specifically.
-
Thanks for reporting. Bug created for this issue VB-183037 and fix targeting future SP
- 1
-
-
odd. if you could attach the file or a fraction of it that still exhibits the issue and a screen recording if possible we could start an investigation.
-
On 9/15/2021 at 1:48 PM, EAlexander said:
Sadly, any file pre 2020 that I try to open gives instacrash. See y'all in a few service packs.
EDIT: even weirder - I open a file in 2020. I copy all the Geo to the clipboard - move over to 2022 and paste.....I get a 2d line representation of my model (like I ran convert copy to lines and no 3d. ☠️
There was a recent crash bug that might be related to this. In https://jira.vectorworks.net/browse/VB-182592 the fix discovered was to uninstall Dell Command Center and Dell Support Assist. I wonder if there is software running on your PC that, like those 2 Dell applications, somehow causes Vectorworks to crash. -
- Popular Post
- Popular Post
maybe this can help for working in Design Layers:
You can make a saved view called "GL without Edges" and in the saved view dialog turn off everything except "Restore render mode and options".
You can then turn on OpenGL Draw Edges and make a saved view in the same way, calling it "GL with edges"
Now you have an easy to switch between one look and the other by activating the desired saved view.
- 5
Object Selectors for VP Indirect Lighting and Ambient occlusion
in Vectorscript
Posted
i noticed some of the SetObjectVariable calls take a RenderStyleHandle instead of a ViewportHandle. Try this:
BEGIN
viewportHandle := LSActLayer; { Last selected object , Select a viewport }
renderStyleHandle := GetObjectVariableHandle(viewportHandle, 1281); { ovRenderStyle=1281 }
SetObjectVariableLongInt(renderStyleHandle,1269,KIndirectLightIndex);
SetObjectVariableBoolean(viewportHandle,1014,KAmbInfoONOFF);
SetObjectVariableReal(viewportHandle,1015,KAmbInfoBrightNess);
SetObjectVariableBoolean(renderStyleHandle,1302,KAmbOcclusionONOFF );
SetObjectVariableReal(renderStyleHandle,1304,KAmbOcclusionSize);
END