Omniverse Drive: Overview¶
The NVIDIA Omniverse™ Drive software mounts an Omniverse Nucleus server to the user’s Windows 10 OS as a virtual hard drive, such that one can manipulate server assets as if they were local files. That means the users can copy, read, and write files directly in Windows Explorer. It can also be used to open to and save directly from applications. This is useful for some existing tools that can only export assets to local disks and are not supported by Omniverse Connectors .
Omniverse Drive Usage Video¶
Though Omniverse Drive is typically used to manage files on an Omniverse Nucleus, it is also effective as an intermediary between a Nucleus and Applications. In the video below we demonstrate these capabilities with both Adobe Photoshop and Substance Painter. This same technique can be used with a multitude of apps such as Substance Designer, Gimp, or any other tools that create content that does not need conversion.
You can install Omniverse Drive from the Omniverse Launcher. Simply select Omniverse Drive from the exchange, select “Install” and Omniverse Drive will be installed to your computer. You can then Launch Omniverse Drive from the Library tab in Launcher.
Launch Omniverse Drive¶
Upon launching Drive from the Launcher, the Omniverse server window will appear. Type in the Server Name/Address to connect to a remote server or
localhost to login to your locally hosted nucleus.
Omniverse Drive can only connect to one server at a time.
After clicking the Sign In button, the Omniverse Login will appear in a browser window. Use your Omniverse Nucleus Server credentials to login.
Once complete, You are now connected to the Omniverse Nucleus server with Omniverse Drive. Now it is time to choose a drive letter from the drop down list. Click the OK button to enable it.
The Log File button will redirect the user to the log file for the debugging purpose.
After enabling the Omniverse Drive, a new hard drive shows up in the Windows Explorer. Note that it may take several seconds to populate the file tree to the cache after logging in to the server.
Meanwhile, the Omniverse window is minimized to the system tray icon. Either left or right clicking the icon will bring back the Omniverse window.
Up to this point, the user can manipulate Omniverse assets the same as any other local files in Windows 10.
If you want to un-mount the Omniverse Drive (or switch to another Omniverse server), click the system tray icon and Sign Out. Form here you can Exit completely or Log into a new server.
When transferring a big file in Windows File Explorer, the progress bar may stall a long time at the last 1%
Setting the file properties, e.g. read-only, hidden, from the File Explorer’s property window doesn’t work yet
After logging out, the mounted drive letter may still appear on the left panel of the window file explorer for a while until it is refreshed.
Update some third party libraries including Dokany runtime installer, Config lib, and omni client library
Update omni client library to 1.17.5
Update the omniverse client library
Fix a multi-thread file read/write crash issue
Fix a installer script issue to get rid of the hanging at the end of the installation
Renamed the version format from 2020.x to 100.x
Upgraded the omni client library to 0.18.1297
Upgraded the dokany lib to 1.4.0
Fixed a file time bug
Upgraded the license file
2020.3 Point Release¶
Updated Client Library
2020.2 Point Release¶
New Omniverse Server Login Workflow
No “warm-up” time to launch the mount process
Big files (over 2GB) no longer fail to transfer
Omniverse Drive is no longer unresponsive during large transfers
Omniverse Drive no longer crashes when deleting & uploading files at the same time
Resolved issue where first character of folders were missing in Omniverse Kit’s file explorer
Omniverse Drive now properly reports I/O driver installation errors
Unified logs and temporary data cache paths with other omniverse modules