I took a look at your site, and did some (admittedly light) testing with my own: I added
2019, 2020 as the value of the
version field on my Maya software entity. For me, it worked fine – I just had launchers for
maya_2020 listed when I ran
So… I think what’s actually at play here is that you are using the
Group field. My guess is that it’s using that long colon-separated launcher name in order to avoid ambiguity – it’s basically namespacing.
You have 2020 listed for both 3ds Max and 3ds Max Pre, and they are both using the same engine. My hope would be that it generates the string that
tank uses from the
Software Name field, but maybe it looks like it’s coming from the engine. Even when I change my
Software Name from
Georgia (why not ), the tank command still lists
So… with that in mind, I guess there’s a feature request in there to respect the
Software Name field, but I’d expect the request to be rejected because it will break existing workflows. I can still run this by the team and see if they have any ideas, but I’d love to hear your thoughts first.