The Twinmotion direct link is for both V6 and V7. I have already downloaded the newest one. In V6 it works as it should (no warning message - and the added Twinmotion drop down in Rhino). Twinmotion is loaded and enabled in V7 also.
I made a comment on the Twinmotion forum, but didn’t get any clear answer - and no answer at all from the developers. Then I tried to make an official bug report directly to the developers, but their bug report software (?) crashed… Haven’t tried again after that (haven’t needed Twinmotion for a while). Still have the same problem though, so I’ll try again, when I have more time.
Perhaps you also could file a bug report to the Twinmotion developers?
Hi guys -
I’m having problems understanding what the issue here actually is.
Does TwinMotion run at all in Rhino 7? Or is the issue only that you are asked to download the latest version? Details, please.
This mirrors my experience with Twinmotion support. The forums are difficult to use to the point of uselessness and answers are rare and rarely helpful. TM feels like software with amazing potential, but it’s definitely got bugs and doesn’t have good support.
It’s weird, because most Unreal Engine software has good support and active user forums.
I’ve been leaning on Enscape, simply because it works reliably… but I want all the hot features of TM… but it crashes almost every time I use it. I’m keeping an eye on TM but not gonna waste any more time until they get their sh*t together support-wise.
It sounds like the TwinMotion plug-in works in both Rhino 6 and Rhino 7, but in Rhino 7 it pops up an update warning. If you click No, everything works as expected. If you click Yes, then you are taken to the update page, where no update is availble.
So the bug is that the Twinmotion plug-in says there’s an update available when there isn’t.
Otherwise, everything works as expected. Is that corect?
Now I noticed that the pop-up warning is perhaps not actually lying - sort of… The V6 version of the plug-in is somehow newer than the one in V7 (2020.2 versus 2020.1). That is really strange, because it’s the same downloaded file…