rb-arch

We do keep the same settings and if we get a corruption we get a back up from the server or time machine from the workstation. Those are rare for us though.

Retrieving data from a backup was never really practical in a real workflow - for us anyway. We now set our autosave to overwrite the original file every 50 operations. This way the shared file is the correct one, and at worst you're out 50 operations. Nothing else worked for us, reliably. I'm not sure what the VW engineers think about this, but that's what we do. As stated above, and to them directly, trying to retrieve work from a back up when you're hoping all over a building is impossible.

I hope everyone here requested the live link on their site.

I was told, directly by VW, that the timeline is out of their hands unlike other live links - it is on Epic Games. I think VW should apply some pressure, but the person I spoke to said the community speaking up wouldn't hurt.

I submitted my request as well.

Apple hasn't helped, that's for sure. Vectorworks was built by Mac users, so it is just a bit frustrating.

Senior staff at VW have told me it is up to TM - VW is not the bottle neck. Either way, Mac users continue to be under served. I'm pretty much used to it at this point.

We've jumped right in. Even with the flaws it is better than anything else we've found for the Mac that isn't too heavy for our needs (like Cinema 4D). We've experimented with Replace Material versus Apply Material to Object. The software itself seems pretty stable to us.

What settings are folks using when exporting C4D and importing C4D into TM? We're finding that an update to the C4D file causes our texture settings to revert back to VW in TM. We export by Texture in VW and include them, then replace them (some not all) in TM with their textures. If we change and update the C4D file it seems to reset back to the original VW textures after the update. Does this make sense? On a side note we've been very pleased with the rendering speed (!) and results.

First one, we don't have C4D - it is way to heavy for what we need. The more we refresh the C4D file, the slower it seems to get. We're trying to confirm that, and a live link is still preferred in our minds to avoid the middle ground software. TM still seems to be a bit limited in texture mapping, but again we're still learning it. We don't really rely on the VW texture and apply our own, or make our own, in TM. It would be nice to see the VW Mac users get some attention for a change with this link.

So I'm due to renew my workstation VSS subscription today. It is only worth it to me if it includes the Twinmotion live link, so it better be available for VW 2021! Above is a rendering we made in TM with no real post production. We used Cinema 4D as the transfer software. It worked okay, but got slower every time we did a .c4d refresh.

This is the problem, I'm due to renew my subscription today and yet we have a current release of software with a broken progress bar and viewport settings that seem to change themselves randomly based on your graphic card setting - and yet we're to re-up for 2021.

Ok, good? What is your work flow from VW to TM? We're using cinema 4d export by texture.

No, why I don't know.

OK, that's encouraging but it also mixes in with some other thoughts that I have about these subscription updates. I'll save those for another thread, but so far TM seems smoother and faster and better. We're early adopters so no $$ yet.