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.

Messages - mte

Pages: [1] 2 3 ... 5
[C4D] Bug Reporting / Re: Corona Volume Grid
« on: 2021-12-03, 13:00:03 »

are you referencing the vdb files relatively or with an absolute path?


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.

[C4D] Bug Reporting / Re: Corona Volume Grid
« on: 2021-09-15, 11:08:52 »
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.

[C4D] Bug Reporting / Re: Corona Volume Grid
« on: 2021-09-14, 17:03:58 »
oh, that was fast. :-)
thanks a lot

[C4D] Bug Reporting / Corona Volume Grid
« on: 2021-09-14, 15:30:06 »

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.

[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.

[C4D] General Discussion / Re: version5 and render farm
« on: 2019-12-18, 23:16:44 »
Rebus not supported Multi Shader

Ohh, that's very strange.

[C4D] Bug Reporting / Re: V5 Render regions
« on: 2019-12-17, 15:23:58 »
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.

[C4D] Bug Reporting / Re: V5 Render regions
« on: 2019-12-17, 13:21:05 »
sounds good!

[C4D] Bug Reporting / V5 Render regions
« on: 2019-12-09, 18:36:36 »

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.

[C4D] General Discussion / Re: version5 and render farm
« on: 2019-12-09, 18:16:14 »
Why not using Rebusfarm? They support V5 final!

that sounds promising, very good!

sounds very good!
Is that intentionally fixed?
I did not find any hint in the latest changelog so it might be pure coincidence. ;-)

[C4D] Bug Reporting / Re: Object motion blur
« on: 2019-09-18, 17:27:43 »
The problem are the render instances, for sure.
We have a lot of problems with MB and render instances so we can't use the one or the other.

This all belongs to the huge motion blur problem that corona has.
There are so many stop stones when using motion blur, that it could be considered as useless.

unfortunately no improvements, as far as I know.

Hi corona Team,

is there any progress in this subject?
I have similar problems with the proxies, when scrubbing the playhead in the timeline.
It looks like corona is reloading the proxy on every frame. I´m not using an animation inside the proxy.

Full-speed non-debug version
Build timestamp: Jun 17 2019 18:34:35
Version: 4.0 (core 4)
Cinema version: R20.030 CINEMA 4D Studio

Pages: [1] 2 3 ... 5