In the RDM options, under 'Path' then 'Configure Installation Path' I noticed the RoyalTS item is looking for an executable that no longer exists (RTS3App.exe). The executable for that application is now called 'RoyalTS.exe', so even if I point it to the proper path, RDM cannot detect the application.
This also applies to the Hyper-V item (looking for vmconnect.exe but is now vmconnect6.3.exe). Presumably others as well.
Hello,
Thank you for reporting this! An improvement ticket has been assigned to our engineering department in order for them to add the option to "override" the default installation path for these applications. I will contact you as soon as I will have more information on that matter.
Best regards,
James Lafleur
Hello,
This is now fixed internally.
Regards
David Hervieux