Dealing With Massive Datasets the UI cannot handle: Instalod Command Line without Pipeline

Answered

Comments

4 comments

  • Official comment
    Support
    Hello Simon,
     
    Thank you for posting your suggestion!
     
    Unfortunately, enabling InstaLOD Pipeline to process single files would make it possible to use it in an automated manner.
     
    However, we are currently working on features that will enable Studio XL to load and process larger data sets in the future. You should, therefore, be able to process your data sets, sometime in the future, as long as you have enough system memory available.
     
    Thanks,
    Erhan
    Comment actions Permalink
  • Simon P

    Hi Erhan,

    Thanks for your reply. I had the feeling this might be an issue.

    Maybe you could add a mode where StudioXL would only load every Nth Vertex to display.
    I a colored point cloud so to speak. So you don't have to load the whole thing.

    Or add a surrogate mode. You "load" a placeholder, a symlink. And you can start processing like normal from StudioXL. While you do not "see" your model before it gets processed StudioXL at least does not have to spend hours loading the Mesh into the editor. And you might get a result :)

    Again, Thanks,

    Cheers,

    Simon

    0
    Comment actions Permalink
  • Andreas Strunski

    Hello Simon,

    Thank you for providing us with a detailed report on the issue and uploading a sample file.

    I was able to reproduce the crash that occurs when the mesh is uploaded onto the GPU. Unfortunately, it seems that InstaLOD Studio XL runs out of resources and is not able to load such huge scenes into the viewport.

    We are currently working on improving the viewport in InstaLOD Studio XL and will take the issue into account. One way to deal with scenes over 10 Mio polygons could be to provide an alternative mode where meshes are not fully uploaded on the GPU.

    For the time being, the only workaround for loading such a huge scene into InstaLOD Studio XL is to split it into smaller parts.

    Thanks,

    Andreas

    0
    Comment actions Permalink
  • Simon P

    Hello Andreas,

    Thanks for looking into it.

    Yes, splitting the mesh does indeed work. What it does though is recalculating the tangents for everything in the scene on each additional import. Meaning: Import part 1, calc for part one [...] import part 5, calc tangents for part one through 5. I am not sure if that is intended. 

    I would agree on a solution where the not everything is uploaded to the GPU. For very dense meshes it often is sufficient to display only every nth vertex as a point.Maybe add the possibility to sphere-select certain parts which then are displayed in full glory for Material / topology etc.. verification.

    Also what might be helpful is if InstalodStudio would run import rules before the actual GPU upload happens. That way I could at least let Studio split by materials during import.

    One final suggestion: You already have the "Use Profile with instalod pipeline" button. Maybe you could add a: "Use profile with file" button. This would simply omit the 3D view and directly send the selected file to the (already built in) processor. After processing the file then could immediately be loaded into the editor for verification and (most importantly) saving. That way automated processing of multiple files would be not possible but one could still benefit from the main strength of Instalod.

    Cheers,

    Simon

     

    Edit: Maybe you could have a look at https://github.com/wjakob/instant-meshes and how he very quickly loads and displays huge meshes. It's open source so your engineers can have a peek.

    0
    Comment actions Permalink

Please sign in to leave a comment.