Jump to content

AndyjBard

Member
  • Posts

    16
  • Joined

  • Last visited

Posts posted by AndyjBard

  1. Hi Pete. Just a fui, that didnt work, thankfully I had a full VW24 sp2 install which i reinstalled and then updated back to 3.1 which is working fine. I'll just wait until I see news of sp4 being fixed or sp 5 coming out.

    Cheers

    • Like 1
  2. Thanks Matt, This is what I got.

    Helpfull?

     

    Cheers

     

    Description
    Faulting Application Path:    C:\Program Files\Vectorworks 2023\Vectorworks2023.exe

    Problem signature
    Problem Event Name:    APPCRASH
    Application Name:    Vectorworks2023.exe
    Application Version:    28.0.4.0
    Application Timestamp:    6409adb5
    Fault Module Name:    ArchitecturalObjects.vlb
    Fault Module Version:    0.0.0.0
    Fault Module Timestamp:    6409a852
    Exception Code:    c0000005
    Exception Offset:    00000000001e7fe9
    OS Version:    10.0.22621.2.0.0.768.101
    Locale ID:    5129
    Additional Information 1:    2113
    Additional Information 2:    2113603821582a3d660df2f49063ea50
    Additional Information 3:    c7dd
    Additional Information 4:    c7dd841dd5e5aed8da245911d275277d

    Extra information about the problem
    Bucket ID:    701edfab5170c9c771efa863db91165f (1292436764917569119)
     

  3. HI Matt.

    Goto the window tool, Not the WINDOOR one, but the specific window one. Mines in the Building Shell tool sets and is grouped with windoor, draw windoor objects, door, window

    Select General tab on the side - Configuration setting (at the bottom) - select custom in drop down menu - click Custom Configuration Options.. button that apperas below.

     

    That causes my vectorworks to crash regardless if its a new file or an existing project

    Cheers

  4. This is also happening to me as well, but I dont get a warning window, VW just stops and then closes. The custom window option has always been a bit buggy in my experience but this is a new one to me. Anybody out there that can help?

    Im using Vectorworks 2023 SP4

    Cheers

  5. Good Day all.

    Has anyone had much experience exporting a 3D model so a client can view it through their browser? I think Im following the basic guides correctly but finish up with a mostly white 3D model with only a few of the textures showing, and all the image props are just solid crosses?

    Any ideas or directions to a good tutorial to look at would be much appreciated.

    Cheers

  6. Hi Ben.

    Mine was a very simple fix as I had plugged one monitor into the graphics card and the other into the motherboard, and it was the mother board one that was causing this issue. Plugged both into the graphics card and it fixed it.

    However, I have since been contacted by the local distributor tech office, saying that since a Jan / Feb windows update other users had been experiencing the same issue, which wasn't caused by where the the monitors are plugged in.

    Unfortunately, if both your monitors are plugged into the graphics card, I dont have an answer for you. All I can say is that the powers that be are aware of the issue and are hopefully trying to sort it out as it is a bit of a game breaking bug.

    As a side note I think I have had more issues with VW19 than any other version of VW which is saying something. Im still using VW18 for some projects as Im reluctant to advance any on VW19 for fear of finding something else.

     

    If Im contacted again I'll add to this post, with any news.

    I hope you get it sorted.

    Cheers

  7. Im just reasking this question as I havent seen that many people with the problem therefore any solutions. Im not sure if its an issue with my computer but it makes VW 19 unusable, so its a major issue for me.

    It happens every-time i use the fly over tool.

    Cheers

     

    Edit. A bit more info. It appears to happen only when i use the flyover tool in a rendered mode. If i use the flyover tool in wireframe, its fine. 

    vw 19 glitch.JPG

  8. Ive just made an account to vent my growing frustration that this is still might be an issue in vw2019 version. The 3D visualization aspect of VW is half the program in my eyes and having to restart the program every second render attempt is beyond frustrating. I can remember this happening as far back as VW 2016 but it just seems to be getting worse. With all the updates and revamps that they have made, the fact that this fundamental flaw still remains is just madness. If I had an alternative to turn to I would be gone.

     

    I agree Line-weight, if its not fixed why do they deserve a break?

     

    Please, please, for the sake of all our sanity, hear our cries and sort this out.

     

    • Like 2
×
×
  • Create New...