Messages

1

[C4D] Bug Reporting / Re: Bug with Physical Materials and the Asset Browser

« on: 2024-03-04, 11:22:18 »

hello we have updated cienma 4d to 2024.3.1 today in the hope that the problem will no longer occur (it could have been that the problem is caused by cinema 4d) unfortunately the error still exists and we can no longer place assets in the library as the materials seem to be reset. (The bad thing is that you think it's fine, because the previews of the materials are displayed correctly, only after you put the objects from the asset browser back into a scene and look at the material properly, or render it, you see that it is basically just a simple physical standard material). The problem only exists with materials that are placed on objects, materials that are saved directly to the library - without geometry are recognized correctly)

We urgently need help with this problem!

win 11, last Corona version, c4d 2024.3.1

The data is on a network drive, everything else has already been explained a few times above

Same problem here. It's an absolutely annoying thing…
Asset Browser Database is on a Synology Drive.

MacOS Sonoma 14.3.1 / Mac Studio / C4D 2024.3.1 / Corona 11

2

[C4D] Bug Reporting / Re: White Stripes - DR

« on: 2023-04-21, 17:37:12 »

* short update
After 2 days of intensive testing, it seems that either materials containing the bitmap shader or / and shared textures (especially SIGER materials stored in the asset browser) are causing the problems.

I will do some more tests.

3

[C4D] Bug Reporting / Re: Invalid Bitmap File

« on: 2023-04-21, 17:19:44 »

I have a similar problem.
If materials containing a bitmap shader are saved in the Asset Browser, the image path gets lost.
Furthermore, the "save project with assets" function no longer works when bitmap shaders are used in materials.
(For example most SIGER materials won't work with the function "save project with assets")

Is this a C4D or Corona bug?
This is extremely anyoing.

4

[C4D] Bug Reporting / Re: White Stripes - DR

« on: 2023-04-20, 14:27:08 »

It MIGHT show up instantly - the strip is very narrow (when you remove the expansion from Bloom and Glare :) ) so it could be that this machine is the slowest and not contributing much, and it could be that in earlier renders other machines "did its work for it" because they finished their work faster, but in a later frame the scene took longer for all machines and this one did send in a contribution. So it's still somewhat possible missing assets could be the issue, worth a check anyway!

Could it also have to do with the fact that not all nodes are equipped with 10Gbit?

5

[C4D] Bug Reporting / Re: White Stripes - DR

« on: 2023-04-20, 14:19:04 »

Hi Tom, your approach sounds interesting. We were just thinking about that as well. Many assets are stored using the built-in C4D Asset Browser (Asset Browser is stored on a Synology NAS with 10Gbit connection)
Possibly it could be related to the lack of indexing of the database.
But it is strange that the error occurred only after approx. 35min. or render time (with a total of 40min render time). The error should show up instantely, right?

We will try to update the index of the C4D Asset Browser.

Regarding the same version, everything is double checked, i.e. the Corona and C4D versions are all exactly the same. So it can't be because of that.
As far as I know, there should be enough licenses available.

6

[C4D] Bug Reporting / Re: White Stripes - DR

« on: 2023-04-20, 12:47:08 »

I do not know if I have understood your question correctly, but we us the TeamRender Function in C4D.

7

[C4D] Bug Reporting / White Stripes - DR

« on: 2023-04-20, 11:47:00 »

When rendering with DR enabled, white stripes appear in the image. The problem cannot be reproduced.

Attachment 1 shows Bloom and Glare enabled
Attachment 2 shows Bloom and Glare disabled

Render nodes: PC (i9 / AMD Threadripper)
Scene on Mac Studio, sent to nodes
Corona 9 (Hotfix 9)
Cinema R2023.1.3