Files access for locally hosted WSL drive

Omniverse Core Platform Kit App Template / SDK
1

Kit App template currently cannot access files that are hosted in wsl

image
image1086×449 36.9 KB

a reference application like Paraview (Open Scientific Visualization application) can:

image
image802×145 11.4 KB

this occurred while working with Kit-CAE extension. One of the suggestion was if KIT supports then KIT-CAE would automatically support as well.
reference: Custom File paths in Kit CAE unable to locate OpenFoam files · Issue #20 · NVIDIA-Omniverse/kit-cae · GitHub

2

Yes that sounds expected. It does not work with networked, or non normal drives. It does work with “mapped” drives in windows, meaning a network drive mapped as a “local” drive. You could try that.

3

the drives are mapped now (E:\,F:\) but cannot yet read them ?

image
image1140×322 29.6 KB

4

Omniverse does support networked and mapped drives that are not Omniverse Nucleus servers.

You can access files from:

  • Network shares (SMB/CIFS, NFS)
  • Mapped network drives (Windows drive letters pointing to network locations)
  • UNC paths (e.g., \\server\share\path)
  • Local file systems

Key Points:

  1. File Protocol Support: Omniverse applications support file:// URIs for local and network file access in addition to omniverse:// URIs for Nucleus servers.
  2. Performance Considerations:
    • Network drives may have slower performance compared to Nucleus servers, especially for large USD files with many layers
    • Nucleus is optimized for USD workflows with efficient caching and streaming
  3. Collaboration:
    • Standard network drives work for file access but don’t provide Nucleus features like:
      • Live collaboration and real-time syncing
      • Version control and checkpointing
      • Asset dependency tracking
  4. Configuration: You can open files from network locations through:
    • The File Browser extension (standard OS file dialogs)
    • Direct path entry in content browsers
    • Command-line arguments with file paths

Recommendation: While networked drives work fine for single-user workflows or small teams, consider using Nucleus for production environments where you need collaboration, version control, and optimized USD streaming.

5

i’m not using any custom servers other than locally hosted on same machine ( WSL) and after you informed to map the drives, i did, but it refuses to detect mapped drive (that are not any custom server/Omniverse Nucleus server).

6

This is through WSL, correct? That is Linux running on Windows? I am not familiar with that setup as much. I can tell you, that I am writing this right now on a Windows 11 machine, running kit, that can detected two networked drives that are mapped as local drives. Beyond that, I have not tested it.