Announcement

Collapse
No announcement yet.

Exception in CORE: Unhandled exception c0000005 with large file

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Exception in CORE: Unhandled exception c0000005 with large file

    So this is a tricky one that I've been battling with for a few weeks and wanted to bounce some ideas off people here at Chaos. PM me for files and I will package and upload as I can't release these into the wild.


    Code:
    esh file "M:\vrmesh\02 VEHICLES\CARS-TAXI\toyota prius.vrmesh" linked successfully.Mesh file "M:\vrmesh\05 PEOPLE\SITTING\RIGGED_SITTING_ani_CBoy0004_M4_0002 6.vrmesh" linked successfully.Mesh file "M:\vrmesh\05 PEOPLE\SITTING\BMan0201-HD2-O02P02-S var00003.vrmesh" linked successfully.Exception in CORE: Unhandled exception c0000005
    Let me set the stage - these happens on very large files, we are talking 20m edges, 80k components instances, 20k component definitions, 15k groups, etc etc. Huge urban development projects with multiple buildings (from Revit, but thats not the issue - stay tuned), cars as vrmesh proxies, people as vrmesh proxies, and trees as vrmesh proxies. With everything on, I get various forms of the c0000005 error and only part of the model renders (it will be full frame, but entire buildings or ground planes are missing).

    If I delete the vrmesh proxies, everything renders fine.
    If I delete everything BUT the vrmesh proxies, everything renders fine.
    If I make the buildings as vrscene proxies and keep the vrmesh proxies, error.
    Basically, I can have everything in the scene as a proxy, error.

    Usually the error happens after/during the light cache process, so I tried BF/BF or IM/LC, but error.
    On a whim, it seemed like the error happened after it processed vrmesh proxies, so I swapped out all vrmesh proxies with vrscene proxies, purged, and the scene worked fine.
    I also tried an option where I replaced all my vrmesh proxies with Cosmos proxies, purged, and the scene rendered fine.

    So I'm leaning toward these vrmesh proxies being the issue. They were made in early vray next / late vray3 days, on skp 2019 (but BEFORE you could "attach" the materials to the vrmesh). I'm going to try going back to the original purchased meshes and recreate proxies, though it makes me wonder if I should be using vrscene's for more reliable long term use and interoperability with other programs.



    Click image for larger version

Name:	image (8).png
Views:	690
Size:	23.5 KB
ID:	1111013

    Click image for larger version

Name:	image (10).png
Views:	570
Size:	166.8 KB
ID:	1111014



  • #2
    Hi delineator

    Does this happen regardless of the Render engine used? Is it possible to forward us the project in question so we can test in our environment, along with information about the exact V-Ray/SketchUp versions (Extensions > V-Ray > Help > About);

    Additionally, please provide more information regarding your hardware specification - CPU/GPU/GPU Driver version.

    To send us the necessary files, you can get in touch with us through our contact form - just make sure to mention this thread in the email. Thanks!
    Nikoleta Garkova | chaos.com

    Comment


    • #3
      Yeah, I'll package that up and send along. Version was 51003, production bucket (or progressive or RT, but all the same). TR 1950x, 128gb ram, 2080 Ti, studio drivers 461.92 (but i don't believe this is a hardware limitation - this was passed onto me as 2 others were experiencing the same issue with the files in our office).

      Comment


      • #4
        Hi delineator,

        Thanks for the info provided - we'll be expecting the files and I'll let you know as soon as we find something out.
        Nikoleta Garkova | chaos.com

        Comment


        • #5
          yup, all set - I sent it off on friday (it is a VERY large package - 1.5gb). let me know if you need anything else or have any questions

          Comment

          Working...
          X