31
[C4D] Feature Requests / Re: Blackbody material for Pyro
« on: 2022-11-10, 16:02:51 »Hi guys, we are well aware of this feature and have it logged ;) +1 from me too :D
(Internal ID=1003640630)
Well, that sounds like very good news!
2025-07-13, 21:35:08
News:
Having trouble verifying your license? If you are seeing a license verification message or are unable to access your Chaos products, please follow these simple steps to fix sign-in issues. If you have already tried this and are still unable to access your Chaos products, please contact Support.
Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Well, that sounds like very good news!
32
[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
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
33
[C4D] Feature Requests / Re: Deformation motion blur
« on: 2022-11-10, 12:01:27 »
This was asked so many times. Chaos/Corona knows we users want it.
But if you ask me, it is a political decision to have a difference between Corona and Vray. So I assume that Corona will never have that.
But if you ask me, it is a political decision to have a difference between Corona and Vray. So I assume that Corona will never have that.
34
[C4D] Resolved Bugs / Re: Volume Grid and Render Farms
« on: 2022-08-26, 16:44:56 »
Hi,
it is R26 and Corona 9 April 21 2022
But this problem exists since the first version of VolumeGrid
it is R26 and Corona 9 April 21 2022
But this problem exists since the first version of VolumeGrid
35
[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
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
36
[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
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
37
[C4D] Bug Reporting / Re: Corona Volume Grid
« on: 2021-12-03, 13:00:03 »Hello,
are you referencing the vdb files relatively or with an absolute path?
Thanks,
Jan
Hi Jan,
the problem is not an relative or absolute path. The problem is that the VDB object messes around with the path while using the "save with assets" option.
In my opinion, the best way to solve the bug would be to absolutely not try to alter the path by any means. Just leave it alone.
38
[C4D] Bug Reporting / Re: Corona Volume Grid
« on: 2021-09-15, 11:08:52 »
Hey,
there is another issue with the Volume Grid and renderfarms.
Logically, a render farm separates all images into individual chunks and let each node render some frames. Node1 is rendering frame 0-5, node2: 6-10 an so on.
The problem is, that the Volume Grid is loading the VDBs in some sort of lazy-loading. That leads to the problem that the node starts rendering, but the VDBs are not loaded. The result is always that the first frame is rendered without VDB. In this example it is frame 0, 6, 11...
The Corona Volume Grid should prevent the node from rendering until all is loaded.
there is another issue with the Volume Grid and renderfarms.
Logically, a render farm separates all images into individual chunks and let each node render some frames. Node1 is rendering frame 0-5, node2: 6-10 an so on.
The problem is, that the Volume Grid is loading the VDBs in some sort of lazy-loading. That leads to the problem that the node starts rendering, but the VDBs are not loaded. The result is always that the first frame is rendered without VDB. In this example it is frame 0, 6, 11...
The Corona Volume Grid should prevent the node from rendering until all is loaded.
39
[C4D] Bug Reporting / Re: Corona Volume Grid
« on: 2021-09-14, 17:03:58 »
oh, that was fast. :-)
thanks a lot
thanks a lot
40
[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
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
41
[C4D] General Discussion / Re: version5 and render farm
« on: 2019-12-19, 12:03:06 »
Rebusfarm says:
We do support all Corona features, these errors shouldn't show up at all, as we have updated our plugin you can solve this by reinstalling it. Please follow these steps to make sure you don't miss anything from the process.
1) Please make sure your 3D application is closed.
2) Open RebusDrop Preferences.
3) Select the 3D software you use and click "Remove" also check and delete it manually from the folder you installed it.
4) Press Save
5) Open Rebusdrop preferences again
6) Click on Find 3d App/Software
7) Press Save
8) After sending a complete job to the Farm please submit a small test job.
We do support all Corona features, these errors shouldn't show up at all, as we have updated our plugin you can solve this by reinstalling it. Please follow these steps to make sure you don't miss anything from the process.
1) Please make sure your 3D application is closed.
2) Open RebusDrop Preferences.
3) Select the 3D software you use and click "Remove" also check and delete it manually from the folder you installed it.
4) Press Save
5) Open Rebusdrop preferences again
6) Click on Find 3d App/Software
7) Press Save
8) After sending a complete job to the Farm please submit a small test job.
43
[C4D] Bug Reporting / Re: V5 Render regions
« on: 2019-12-17, 15:23:58 »
Hi,
thanks for clarification. I find it somehow dangerous, because I use the regions as tool to render previews faster.
But it ok, as long as I can see they are active.
thanks for clarification. I find it somehow dangerous, because I use the regions as tool to render previews faster.
But it ok, as long as I can see they are active.
45
[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.
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.