Messages

526

[C4D] Bug Reporting / Re: Adjusting Viewport Preview size past 512x512 makes Cinema4D laggy + IRR crash

« on: 2020-09-03, 11:39:17 »

Hello Yurii,

as mentioned above, I was also unable to recreate the IRR issue. However, I was able to reproduce the lagginess in viewport after changing the preview resolution to values > 512x512. I have forwarded this to the developers. (internal id=559712524).

Thank you for reporting this issue,
Jan

527

[C4D] Bug Reporting / Re: Downward compatibility

« on: 2020-09-03, 09:51:23 »

Hello,

backwards compatibility is not at this point fully supported, especially after the daily build from 30/6/2020, in which some major internals of the node material system were reworked.

Changes in Corona Renderer 6 for Cinema 4D (Daily Build 2020-06-30) (https://drive.google.com/drive/folders/1Pq54oK-EGac_z0VdV05VfsSsG54I1Qkn):

Reworked internals of material node system to improve stability and allow future improvements

• WARNING: the new node system saves data in a different format; if you use the node system in your scene and save with a daily build that's from Jun 30th onward, it will not load correctly in older daily builds from before that date!

Thank you for understanding,
Jan

528

[C4D] Bug Reporting / Re: CORO 6 - Normal map adjusting cause C4D freeze ! R21

« on: 2020-09-02, 15:28:08 »

Hello again and thanks! I have just managed to reproduce it in your scene. I will dive deeper and then report it to developers.

Thank you again for reporting this,
Jan

529

[C4D] I need help! / Re: Round edges doesn't work with corona 6 C4D

« on: 2020-09-01, 09:48:28 »

No problem, glad I could help!

530

[C4D] Bug Reporting / Re: CORO 6 - Normal map adjusting cause C4D freeze ! R21

« on: 2020-08-31, 12:31:36 »

Hello,

is it possible to send a snapshot of your node material editor (or Material Editor window) for further examination (or the problematic scene as a whole)? Simple scene with Bitmap > Normal shader > Corona Material did not result in any issues for me when following your steps. If C4D crashes, sending a minidump or a crash log would also be very helpful.

Thank you and sorry for the inconvenience,
Jan

531

[C4D] I need help! / Re: Round edges doesn't work with corona 6 C4D

« on: 2020-08-31, 12:18:00 »

Hello,

did you try adjusting the Bump % strength to 100%?

Thanks,
Jan

532

[C4D] Bug Reporting / Re: Proxy in Full Mesh disappears when too close to camera

« on: 2020-08-27, 11:18:00 »

Hello and thanks for reporting,

I can confirm that the Proxy does in fact disappear from the viewport (with full mesh setting) once the center of "mass" of the proxy is outside of the view.
I have forwarded this issue to the developers. (internal id=556302158)

Thanks again,
Jan

533

[C4D] Bug Reporting / Re: motion blur

« on: 2020-08-24, 16:02:35 »

I see, thanks!

This seems to be a part of an issue that we are aware of and will hopefully fix sometime in the future. We are to a great extent able to fix sub-issues once we manage to reproduce it in any scene, and therefore providing a scene would be extremely helpful.

In any case, I would kindly ask for patience while we tackle this issue.

Thanks,
Jan

534

[C4D] Bug Reporting / Re: motion blur

« on: 2020-08-24, 13:38:50 »

Hello,

what exactly do you mean by "moves"?
Does it displace the Instanced objects from their course? Do you mean that the instance takes on the tags from the original?
If it was possible, sending a scene over would be very helpful to us in trying to investigate your issue.

Thanks,
Jan

535

[C4D] Bug Reporting / Re: bumb

« on: 2020-08-24, 12:27:11 »

Hello,

thank you for letting us know. We are aware of this issue and have logged it internally (internal id=507183070). We do hope to have this fixed in a future build.

Thanks,
Jan

536

[C4D] Daily Builds / Re: Corona Renderer 6 for Cinema 4D daily build

« on: 2020-08-21, 15:17:27 »

Is it me or is the Round Edges shader not working in RC4? It's not working on new scenes and reloading old ones aren't now showing rounding. Turning off the phong tag makes it work but that's not correct behaviour. It should ignore phong/normal tags and still round the edges...

Hello,

is it possible to send your scene over for investigation? From a quick glance the RoundEdges is working as it used to. Maybe try adjusting the Bump strength in the material settings.

Thanks,
Jan

537

[C4D] Daily Builds / Re: Corona Renderer 6 for Cinema 4D daily build

« on: 2020-08-21, 13:44:49 »

Hi guys,
also, I noticed if you use a normal shader with an additional bump map, bump doesn't work.
Sending screenshot and the simple cube scene file with some textures.

btw. Thanks Jan for a confirmation of a layered mat. mask issue. :)

Best regards
Karel

Hello Karel,

thank you for reporting this!
This issue is actually a bit more complicated than it seems. Going through your scene I will tackle two issues.

1. "fabric_03 - white" material: After thorough investigation, we've noticed that the Projector shader may be the culprit here. I don't know what the desired outcome of this material is for you, but skipping the Projector seems to "fix" the render for us. I've noticed that you're using it to decrease the Length and if that is desired, I've observed that if the input is not a simple file, but a shared Bitmap shader, the bump renders correctly. This is obviously not the correct interaction with the Projector shader and I have passed this to the development team for fixing (internal id=552946286).
I am attaching some of the snapshots of proposed workaround and a comparer for images with and without using the shared shader. Please note that I've changed the Projector Length to 100% on both axes so that the change is visible.
https://corona-renderer.com/comparer/79CR9f

2. "fabric_03 - white - new" material: Once again, it is not necessarily Triplanar > Normal that is acting up, but rather Triplanar > Filter. Changing the structure of the nodes from Bitmap>Triplanar>Filter to Bitmap>Filter>Triplanar did the trick for me. I am not sure if this is really a bug or just the way Triplanar is implemented, I will bring this up for discussion with the developers. I am once again going to attach a snapshot of the editor. Again, please note that I've increased the Triplanar's UVW scale to 200cm for visibility purposes.

Thanks,
Jan

538

[C4D] Daily Builds / Re: Corona Renderer 6 for Cinema 4D daily build

« on: 2020-08-20, 14:26:25 »

Hi guys,
in the latest RC4, in the node editor, the node connection of a mask in layered material doesn't work. Check the attached screen capture video which hopefully clarifies that.

Best regards,
Karel

Hello Karel,
Confirming and passing to the developers. Internal id=552416287

Thanks,
Jan

539

[C4D] Daily Builds / Re: Corona Renderer 6 for Cinema 4D daily build

« on: 2020-08-17, 10:14:19 »

Hi, I just updated to rc 3.

I still get a yellow render in some cases when I rotate Corona Sky object during IR.

Sky settings:
HDRI (Native Bitmap Shader) > Corona Color correct > Corona Sky = yellow
HDRI > Corona Sky = working as expected
HDRI (Corona Bitmap Shader) > Corona Color correct > Corona Sky = working as expected

Thanks!

C4D R20
Windows 10
Corona 6 RC3

Hello llollolo,

I can confirm that this happens if you select the Color correct through Corona Sky Object Properties and then select native Bitmap.
I will pass this to the developers team. If you are more comfortable with using the native bitmap solution, I would recommend trying to use the Corona Node Material Editor with Light Material, in which I was unsuccessful of reproducing this bug, for the time being.

Thank you,
Jan

540

[C4D] Daily Builds / Re: Corona Renderer 6 for Cinema 4D daily build

« on: 2020-08-14, 16:00:29 »

Hello Jan,

there is a snapshot of a node material editor and also the scene file (its om model from FH). It works just fine with corona color correct, but I prefer to use filter shader.

Thanks,
Karel

Hello Karel once again,

I can confirm that Triplanar > Filter > Bump does not work correctly and I will pass it on to developers to fix.
In the meantime, you can use (as you've already pointed out) Corona Color Correct.
For internal purpose: id=549868874

Thanks,
Jan