The current setup for Twinmotion for Revit's "Open in Twnimotion" functionality is not user controllable or definable. With the release of TM4Revit 2023.1 Revit 2023.1 expects for TM4Revit 2022.2.3 or Twinmotion 2023.1 to be installed. The problems is that install locations and order appear to define what version of Twinmotion gets launched, but there is no easy route to get there. There is no user option or configuration file that can be used to define the desired version to open. This makes it difficult to support or train users as we need to support multiple versions of Twinmotion for Revit so as to not cause the "Open in Twinmotion" functionality to error.
The current approach makes managing Twinmotion For Revit difficult as the current approach requires Twinmotion for Revit 2022.2.3 and 2023.1 to both be installed. When you have people working on projects in different versions of Revit it can become problematic on the Visualization side of things. There are ways to minimize the distribution for users, but again makes management very difficult when looking at larger organizations and the underlying changes made in Twinmotion 2023.1 that makes it incompatible with the previous versions. Currently, it also means any user library assets (which we are trying to consolidate in a single network location) must be duplicated in different locations because of the different version requirements.
