Jump to content

JustinH

Vectorworks, Inc Employee
  • Posts

    95
  • Joined

  • Last visited

Posts posted by JustinH

  1. 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

    • Like 2
  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).

    • Like 1
  3. 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

  4. 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.

  5. 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:

     

     

     

     

  6. 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.

  7. 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:

     

     

     

     

    • Like 1
  8. 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?

  9. 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.

  10. 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.

     

×
×
  • Create New...