Messages

1

[C4D] Bug Reporting / Animated Material tag is "Unsupported Material"

« on: 2021-12-17, 16:14:28 »

Hello,

I'm working on a simple animation, which has a cube changing material on impact. The material change happens via material tag and keyframing the "material slot". I attached the simplified scene. When rendering frame 0 it works properly. When rendering frame range or any frame in the animation I get the "unsupported material" pattern in the frame buffer.

Can somebody help me with this? Is there a workaround for this to render?

I haven't had the chance to try this with a more recent C4D version or a daily build.

Looking forward to your help!

Full-speed non-debug version
Build timestamp: Aug  3 2021 16:40:22
Version: 7.0
Cinema version: R21.207 Cinema 4D (mutli-license)
Plugin status: Plugin successfully loaded


Cheers,
Ararat

2

[C4D] I need help! / Re: Glass and metal material in viewport

« on: 2021-09-09, 09:33:17 »

It works with the basic material editor as well. Just stick to right half of the snapshot and copy that setup.

3

[C4D] I need help! / Re: Glass and metal material in viewport

« on: 2021-08-31, 10:14:02 »

Hi,

for glass and metal material you could make it visible by adding a color texture in the diffuse channel but keeping the diffuse level at 0%. It will not affect the material, but you will not be able to add anything else in the diffuse channel. Also for glass make sure that reflection/refraction is white/100%.

Just another workaround, would be nice too see this actually taken care of by the corona team. Maybe it is already fixed in the newer cinema versions?


Build timestamp: Aug  3 2021 16:40:22
Version: 7.0
Cinema version: R21.207 Cinema 4D (mutli-license)

Cheers,
Ararat

4

[C4D] I need help! / Re: Issue with glass reflection/refraction and corona light

« on: 2021-01-28, 11:15:42 »

Hi beanz,

thanks for the quick reply. You are right, I attached another snapshot showing something interesting, that might help solve this issue. At 47% the effect gradually kicks in, I guess depending on the viewing angle?

I can go with 40% for now, but would be great to have fixed in the future.

Thanks,
Ararat

5

[C4D] I need help! / Issue with glass reflection/refraction and corona light

« on: 2021-01-28, 10:19:34 »

Hello everybody,

stumbled upon a issue that I couldn't solve on my own or with the forum search.

Corona lights appear black in glass reflection/refraction. With thin glass it works in the refraction, but with thick glass is doesn't work in either. I'll explain my snapshots, I also attached the scene.

• purple is a corona light
• yellow is a reflection of purple
• orange is a corona light behind glass

What I did so far:

• check normals
• check/uncheck different light settings
• cube has a thickness of 2cm
• it works when the corona light type is changed to object
• something weird happens when changed to sector
• light shape doesn't affect issue
• tried the latest daily build (7.0 daily Jan 22 2021)

Anybody has an idea how to fix this? My goal is to have it work with thick glass.

Best,

Ararat

6

[C4D] Feature Requests / Re: Metalic and refractive materials to properly appear in viewport

« on: 2021-01-28, 09:25:48 »

+1

7

[C4D] Bug Reporting / Re: corona bitmap v. bitmap shader in content browser

« on: 2020-11-30, 15:00:18 »

Hello, could be that I understood something wrong, but we do the following when integrating maxtree assets to our server and have had no issues whatsoever:


1. open .c4d provided by maxtree
2. navigate to project info and then textures in attribute manager (see attachment)
3. select a texture and point to absolute texture path on server (folder is enough, no need for specific file-name)
4. say "yes" when asked to replace textures in the whole project
repeat step 3 and 4 for all textures
5. after all textures are relinked, open c4d search with shift + c
6. search for "project asset inspector" (I think it is called differently in versions before R21)
7. select all textures and right-click "globalize filenames"
8. enjoy!


Hope this helps!

Oh and one more tip, that could come in handy at some point. When dragging materials into the content browser holding alt, Cinema 4d will not create a tex folder but point to the original path.

best,
Ararat

8

[C4D] Bug Reporting / Re: Proxy Viewport Bug in Point Cloud mode

« on: 2020-11-25, 12:06:11 »

Of course, I also attached a screengrab.
Full-speed non-debug version
Build timestamp: Nov 18 2020 05:29:31
Version: 7.0 daily Nov 18 2020
Cinema version: R21.207 Cinema 4D (mutli-license)
Plugin status: Plugin successfully loaded

9

[C4D] Bug Reporting / Proxy Viewport Bug in Point Cloud mode

« on: 2020-11-25, 11:09:30 »

Hello,

when Proxy is set to "Point Cloud" but disabled from the object manager (little checkmark) it still appears in the viewport, but it behaves correctly when rendering. I would expect it to be not visible in the viewport. The traffic lights work as expected. I attached a snapshot, easy to reproduce


Best,

Ararat


EDIT: Same behaviour in latest daily build 7.0 daily Nov 18 2020

10

[C4D] Bug Reporting / Re: Images rendering with rectangular irregularities

« on: 2020-11-13, 09:43:36 »

Correct, Corona 6 brought changes to the node editor etc. which means scenes saved in it cannot be opened in Corona 5. It was in the release blog at https://blog.corona-renderer.com/corona-renderer-6-for-cinema-4d-released/

PLEASE NOTE: Because the new node system saves data in a different format, if you save a scene using Corona Renderer 6, you will not be able to load and use it in earlier versions of Corona Renderer.

I'm sure a lot of people may have missed that note - including me. Why don't you add an info to the error message pointing towards the issue of having different corona versions?? I recently spent two hours figuring that one out.

11

[C4D] Bug Reporting / Re: Images rendering with rectangular irregularities

« on: 2020-11-12, 11:58:03 »

Hi there,

just a few things to rule out:

• flipped normals
• phong tag
• try override material
• move camera slightly to see whether the weird rectangles move as well or stay at the same part of the building

Best,
Ararat

12

[C4D] Bug Reporting / Re: An internal error occurred: wxWidgets assertion failure - While rendering in VFB

« on: 2020-10-21, 14:10:43 »

Yes, the interactive render was running at 4000px and it is a medium scene (vegetation and staffage was turned off). But the LightMix was pretty heavy with maybe 10 HDRs and 5 other light selects. (We are creating three images from that scene) And as I said, I was editing the curve when the error ocurred. Then I clicked a few more times and some more messages appeared and then it crashed (while I was searching for this thread :D). The crash interestingly didn't happen before, so that is new to me as well.

13

[C4D] Bug Reporting / Re: An internal error occurred: wxWidgets assertion failure - While rendering in VFB

« on: 2020-10-21, 13:01:53 »

Of course:

Full-speed non-debug version
Build timestamp: Aug 25 2020 09:52:16
Version: 6.0
Cinema version: R21.207 Cinema 4D (mutli-license)
Plugin status: Plugin successfully loaded

Windows 10 Pro Version 2004 (Build 19041.572)
AMD Ryzen 3950X
64 GB Ram
Nvidia RTX2080 Super

Best,
Ararat

14

[C4D] Bug Reporting / Re: An internal error occurred: wxWidgets assertion failure - While rendering in VFB

« on: 2020-10-21, 11:52:59 »

Thanks a lot, because I've been sleeping bad lately :P

Files are attached, hope they help!

15

[C4D] Feature Requests / Re: please use 100% detail as default for inter active viewport !?

« on: 2020-10-21, 11:19:53 »

I actually use it at 50%, because I mainly do it for lighting and then general impression is more than enough and it's a lot faster. Also when creating materials reflection you can navigate quicker. Maybe it could be set up so everyone can save their own preference? Currently the default scene doesn't keep this info.