Cinema4D version 2020.1.2 (Obsolete)11.06.2020 Tweet

[aoktar]

Sorry about your criticisms. We should label it STABLE if you/all accept that previous builds are STABLE. Because they were having more CORE bugs and fixed in this CORE. And the plugin is adjusted to provide lighter workflow while working on the content.
Now the latest CORE has a problem with VDB loading. That doesn't mean it's not STABLE, but have a problem. Of course, I'm not happy to see some shadowing on our heavy efforts. I believe you're very kind to accept temporal mistakes and wait until we fix it very soon. And you'll have a better product.

[fatrobotsneedlove]

Sorry about your criticisms. We should label it STABLE if you/all accept that previous builds are STABLE. Because they were having more CORE bugs and fixed in this CORE. And the plugin is adjusted to provide lighter workflow while working on the content.
Now the latest CORE has a problem with VDB loading. That doesn't mean it's not STABLE, but have a problem. Of course, I'm not happy to see some shadowing on our heavy efforts. I believe you're very kind to accept temporal mistakes and wait until we fix it very soon. And you'll have a better product.

I know it wasn't your fault ahmet. I get core vs plugin.

I rolled back to 2020v4 two days ago, and it got killed today. Just got an error that says its not supported anymore.

Very frustrating that I can't use the current version because VDBs are broken, and the last version that worked for me (2020 v4), which I kept on my computer as a backup, does't work either.

[aoktar]

Sorry about your criticisms. We should label it STABLE if you/all accept that previous builds are STABLE. Because they were having more CORE bugs and fixed in this CORE. And the plugin is adjusted to provide lighter workflow while working on the content.
Now the latest CORE has a problem with VDB loading. That doesn't mean it's not STABLE, but have a problem. Of course, I'm not happy to see some shadowing on our heavy efforts. I believe you're very kind to accept temporal mistakes and wait until we fix it very soon. And you'll have a better product.

I know it wasn't your fault ahmet. I get core vs plugin.

I rolled back to 2020v4 two days ago, and it got killed today. Just got an error that says its not supported anymore.

Very frustrating that I can't use the current version because VDBs are broken, and the last version that worked for me (2020 v4), which I kept on my computer as a backup, does't work either.

We're not happy too but there are humans that work on, I believe that you can do mistakes also! Isn't?

You should use this version(R7) until next build, R4 is not fine!
viewtopic.php?f=85&t=74603

[fatrobotsneedlove]

I really wasn't trying to disrespect anyone. I truly apologize if it came across that way.

I will try to phrase things differently in the future.

But please understand that when things break and don't work, WE get yelled at. WE lose clients.

I got yelled at today.

[aoktar]

I really wasn't trying to disrespect anyone. I truly apologize if it came across that way.

I will try to phrase things differently in the future.

But please understand that when things break and don't work, WE get yelled at. WE lose clients.

I got yelled at today.

I totally understand the pressure you have. But why don't you download 2020.1-R7 from the link I sent?
It's very stable one

[Goldorak]

This is on our end, and this is being addressed ASAP in 2020.1.3 hotfix. I’m so sorry this slipped through the Q&A for .2, it’s related to an openVDB library update made in 2020.1.1.