3D Subsurface Utilities file crashing

 
OS: Windows 10 Pro x64-based Version 10.0.19041 Build 19041
Software: Power GEOPAK V8i SS4 08.11.09.878
Tool used: SS4 OpenRoads Subsurface Utilities Task Workflow
Element: 580M, 2690 Blocks
Available Memory: 1576M (Virtual)
System Memory: 4096M (Virtual)
Free Limits: 150M (Virtual)
Processor: Intel(R) Core(TM) i7-6700 CPU @ 3.40 GHz
Video: NVIDIA Quadro K2200
Page File Space: 4.86 GB
Noticing more and more crash events with and without Logs for events. Whenever I encounter seemingly broken elements I would create a fresh node, reroute connected conduits to the existing node and connect them to the brand new one, and then delete the old node in it's place or just delete and replace the conduit that seems broken in that case, but sometimes even that crashes it or I'll restart the software and it still crashes, though I can still open the file, and want to salvage as much as I can.
I've also noticed Node Warning elements throughout that I've gone and fixed the issue for the "unable to generate node structure" ones by replacing them, but some of the other ones I haven't found a fix for, but they are on other levels for some reason, and I'm also noticing levels with no visible elements, shared cells, tags, or otherwise to delete and can not find them that is separately occurring.
The File I'm working in is already large, but not that large (132 MB maybe), but I'm trying to find out what is causing some of the crashing issue with this. The crashing consistency is 100% always when either placing, deleting, or connecting Conduits and/or nodes new or existing to each other, and usually the environment just closes out without any notice or it creates a general bug send request dialog box before crashing. Let me know if there's anything I can do, this is a 2D & 3D Multi-modal file with 3D SUE elements throughout a corridor with an imported TIN file. The TIN File seems to be working find and haven't found any issues with that, but I have noticed a lot of issues when adding in the nodes/conduits.
Let me know if there is more information needed to address this or what I can do to breakdown the file to prevent the 32-bit system virtual memory threshold from being reached.  I do use a 64 bit system for Windows.
  • 132 Mb is really large for the SS4 software if I remember correctly. I can't speak to the SUE, but that would be a very large file for anything I've worked with.

    Is there any way to break your project down into smaller regions, to see if the smaller file size made any difference?

    Hopefully one of the SUE folks will be along with more concrete ideas.

    MaryB

    Power GeoPak 08.11.09.918
    Power InRoads 08.11.09.918
    OpenRoads Designer 2021 R2

        

  • I was going to try and merge several copies of the files and then delete everything not associated after a certain "section" of TIN reference and work my way back to something smaller or at least cut the file into a North/South section, but I haven't had any luck successfully merging the file into a blank one yet since it uses both a 2D/3D model view group setup (i'm hoping that this doesn't make it impossible).  I was finally able to upload the project to ProjectWise, but I'm going through Project Explorer and looking to remove possibly profile elements showing up in my plan view that aren't needed anymore (not related to my current utility Model groups) and see if that fixes some of the issues with the memory skyrocketing when rendering.