¶ ⚠️ Known Bugs and Limitations
Volinga Suite is currently in beta. We are actively working to introduce new features and resolve bugs promptly. The following limitations and known issues exist in the current release:
- Automatic updates are not yet supported. To update to a new version, users must manually uninstall the previous version before installing the latest release.
- Undo and redo actions are not currently implemented within Volinga Suite.
- Asset editing functionality is not yet available. We recommend using external tools, such as Supersplat, for asset modifications until this feature is supported directly within Volinga Suite.
- FQDN-formatted paths (fully qualified domain names) are not supported for asset generation. This limitation affects workflows involving shared network drives (e.g., Samba). We recommend using either local file paths or UNC-formatted network paths.
- When dragging an external NVOL file into the Main Window’s viewport, if an asset with the same name already exists within the project, the existing asset will be loaded instead of importing the new one.
- Occasionally, when initiating the "New Asset" workflow from the Main Window, the Asset Name prompt may appear behind the Main Window, requiring the user to manually bring it forward.
- In certain cases, if a training job is canceled during COLMAP's mapper phase, the associated RAM may not be properly released.
- Due to a known issue with the QT framework, uninstalling Volinga Suite may present some difficulties. To properly uninstall Volinga Suite, you can use the standard uninstallation method through the Programs and Features section in the Windows Control Panel, or alternatively, through the Apps & Features menu in Windows Settings by uninstalling the auxiliary application provided. This auxiliary application addresses the QT framework issue, and removing it will also fully uninstall Volinga Suite.