I tried saving the ScopeView templates in all the available formats (.svt, .xml, and .mod).
Under normal practice, when saving a file, the file extension is automatically handled by the application, and users typically do not need to specify it manually. However, in the case of Hypersim ScopeView, I observed that the file must be saved with the appropriate extension explicitly included in the filename. Otherwise, the file does not appear in the file selection dialog when attempting to reopen it from the folder.
Hi @Raviteja Thanks for your comment.
Usually, if you don’t specify the extension, it will directly apply the .svt (ScopeView) extension. To save in other formats, like .xml or .mod, you should specify in the File Name the extension format, otherwise it will apply the .svt format automatically
Ideally, that is the expected behavior. However, with Hypersim 2025.2, I am observing something different.
I can see the saved template file in the target folder after saving. However, when I try to open the template from ScopeView, the file is only visible if it has one of the recognized extensions (.svt, .xml, or .mod). If the file is saved without an explicit extension, it does not appear in the Open dialog window.
For example, when saving in the default ScopeView template format, the file is created successfully, but it is not listed in the Open window unless the .svt extension is explicitly included in the filename.
Step2:Open the saved Template. Result is Not able to locate the saved Template, even after multiple times refresh.But able to locate it in file explorer.
As there’s no option to share the recording here, I have shared the recorded video with Opal India Support Team Manager(Hasmath). hypersim#Thais Blasi.
Hi @RAVITEJA
Thanks for sharing your implementation and for the prints.
In this case I would recommend you to contact our OPAL-RT Support team as you already did. Out team of experts will be glad to help you in this case.
Also, you can try the newest versions of Hypersim. I tried to replicate the same behaviors in the 2026.1 version and in this case it works as expected.
I tested this again with the latest Hypersim version (2026.2.3.o32), and the ScopeView template issue still persists.
I have also shared a supporting .mp4 recording with the India Support Team for reference.
The behavior remains the same: the template file is created successfully and is visible in the folder, but when attempting to reopen it from ScopeView, the file is not displayed unless the appropriate extension (.svt, .xml, or .mod) is explicitly included in the filename during the save operation.
Could you please confirm whether this is expected behavior or if there is a known issue related to ScopeView template handling?
