Topics

1

[C4D] Bug Reporting / CoronaMappingRandomizer is not so random

« on: 2023-11-17, 19:07:36 »

Hi all,

I´m in the process of rendering flooring tiles. They are cloned using the C4D-cloner. The one tile has a texture tag with the MappingRandomizer.
As you can see in the image there is some sort of randomisation but there is a lot of clustering and very often 2, 3 or 4 times the same tile in a row.
I now manually step through 300 different seed values to find one that is okay for the field of view.
I have 7 different tiles and would expect some sort of evenness in the distribution.

have a great weekend
Andy

2

[C4D] Feature Requests / Volume Grid -> match Pyro orientation

« on: 2023-08-23, 18:00:07 »

while you have a "Flip" Button, maybe a "match Pyro orientation" would be great, too.
Currently I have to rotate(H) by 180° and scale X to -1

3

[C4D] Feature Requests / Volume Grid file handling

« on: 2023-07-03, 12:21:08 »

Hi,
while the new file option in C10 works as expected, there could be an improvement.
Could you add a CheckBox, to change the way the .vdb files are handled when using "save project with assets".

Current functionality is:
all .vdb files are copied to the destination "vdb" folder.
the path in the volume grid object is changed to an absolute path that points to the new location.

New option
don´t copy the .vdb files
leave the "old" absolute path as it is.

This way we don´t have to copy hundreds of gigs of files through the network.

4

[C4D] Bug Reporting / Volume Grid Bug

« on: 2023-07-03, 11:59:01 »

Hi,
In the latest C10, rendering the volume grid creates a visible box in the Indirect channel.
Whether the plane intersects the bounding box or not.

5

[C4D] Bug Reporting / Chaos Scatter is slow

« on: 2022-11-24, 15:39:58 »

in the viewport with many objects to scatter...
And the worst nightmare is to activate "avoid collisions"

Of course the display is set to none.

In my opinion, it should only scatter on render time and not in the viewport.

6

[C4D] Feature Requests / Blackbody material for Pyro

« on: 2022-11-10, 12:05:43 »

With the new C4D Pyro, it would be great to have a blackbody material.
Currently we have to export the "pyro simulation" as a VDB and then import it again with the Corona Volume Grid.

Are there any plans on that?

best regards
Moosi

7

[C4D] Resolved Bugs / Volume Grid and Render Farms

« on: 2022-08-25, 20:49:04 »

Hi,
why is the Volume Grid not working as it should?
One of the main problem is the file path handling. Instead of letting the user choose the file path you create it without the option to change it.
Once the files are loaded  via the "select files" button, there is no way of altering the path and most important, corona is altering the path randomly.
The results are "funny" pathes like (\\Fileserver\project\.\vol\folder). This does not make any sense in no way and will NERVER do.
Either use relative or absolute pathes and/or let the user decide.

I´m really wondering why this is the case since the first version and has not changed in the meantime. There a lot of complaints, but nobody cares...

best regards

8

[C4D] I need help! / Corona 8 on renderfarm not possible?

« on: 2022-04-21, 10:01:15 »

Hi all,

we try to upgrade to Corona8, but there is a problem with the new licensing server. We have a farm with 50 rendernodes running the C4D commandline renderer.
The solution that the CHAOS support tells us is to MANUALLY install Corona and the license server on each and every rendernode, then again manually set every single license server to point to a master license server in the network.
Is this really the official solution for customers with more than a few nodes? How does big farms like rebus handling this?
With Corona7 everything worked just fine. One central license server and one place in the network where the plugin is loaded from.
Or is Corona8 just not intended to be used by larger farms?

thanks for your help!
Andreas

9

[C4D] Bug Reporting / Corona Volume Grid

« on: 2021-09-14, 15:30:06 »

Hi,

I stumbled over a nasty bug when working with vdbs.
the Corona Volume Grid object changes the file path to the .VDB when saving the project using "save with assets".
This way it is almost impossible to render vdbs on a render farm.
It would be better if you did not change the file path in any means. Just leave it and let the user take care of relative or absolute paths.
The second problem is, that the emission, absorbtion, scattering, settings are reset to default, when no vdb is found. Unfortunately this is always the case when opening the saved scene, because of the previous path changes.

It would be great if you could have a look.
thanks
moosi

10

[C4D] Bug Reporting / V5 Render regions

« on: 2019-12-09, 18:36:36 »

Hi,

When I select regions in the Frame Buffer, these are secretly saved in the file.
When sending the scene to the render farm, these regions remain active and only they are rendered.
Sometimes it is not enough to delete them, by clicking the red [X] oder selecting "Remove All"

I would consider this as a major bug, because it secretly saves information in the file completely hidden from the user and it may cost a lot of time and money.

If this is a intentionally desired function, it must be possible to switch it off using a check box.

11

[C4D] Resolved Bugs / Scene conversion from pre-release to Commercial V3

« on: 2019-01-15, 23:05:19 »

when opening "old" scenes  in the final version, the light color is always white, no matter what the original was like.

would be good if you could fix it.

12

[C4D] General Discussion / Helpdesk is responding! :)

« on: 2019-01-15, 18:03:04 »

Hi,
I have a serious issue with your license server. I reported it yesterday evening and hoped to get a reply within this business day.
I´m not able to render on all machines, witch is really an issue, so I have to consider whether I should go back to the beta version with the farm, so that I can at least render.
I have a little time slot for the transition, that´s why I decided to buy the upgrade. I knew there might be problems, but it's not good if the time i have to troubleshoot is wasted by waiting.

So please, I need some response.
regards Andreas

13

[C4D] Bug Reporting / Deformation Motion Blur not working

« on: 2019-01-08, 14:21:00 »

Hi,
deformation blur is not working in the final release.
Is this a bug or is this supposed to never work in C4D.
As corona4C4D has the same pricetag as max, it should offer more or less the same features, right?

14

[C4D] Resolved Bugs / Alembic object motion blur

« on: 2018-10-24, 12:13:24 »

Hi,
alembic files are not rendered with object motion blur.
Would be great if this works in one of the next versions.

A test scene is uploaded.
1540376072_AlembicMotionBlur.zip

15

[C4D] Resolved Bugs / Serious Bug in Version: B1 daily Dec 1 2017 (core 1.7 (hotfix 2))

« on: 2017-12-01, 18:14:06 »

Just a Cube and Sky with LightMat and hdr crashes.

I cleaned old versions before.

Full-speed non-debug version
Build timestamp: Dec  1 2017 16:22:34
Version: B1 daily Dec  1 2017 (core 1.7 (hotfix 2))
Cinema version: CINEMA 4D Studio R19.024 S
Plugin status: initialized successfully