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 ... 6
Hi Tom,
I totally get your point. It's always hard as a customer to understand how the internal processes work.
We also tend to see and address the software bugs that have existed for years, but no one talks about the really good and useful new features. That must be really frustrating for you. But of course, as a company that makes money from using your product, we are sometimes frustrated when we have to work around technical deficiencies instead of focusing on our actual business.
You probably can't make everyone happy.

I have the most sympathy for the problems and challenges that software development brings with it.
But I also sometimes have the feeling that bugs are endlessly pushed back, no one is interested in them or other political decisions get in the way of fixing them. I am thinking, for example, of:

- 2.5D Displacement is almost not working in animations. (why did you kicked the old, but stable version out?)
- Render Instances are a mess to work with
- Layered Bump
- MotionBlur issues since ever

you know the list is endless and a lot was mentioned in the thread.
Maybe a more transparent prioritization would help?

[C4D] Bug Reporting / Re: Chaos Scatter is slow
« on: 2022-11-25, 20:09:27 »
"No, it's S-L-O-W." 😜

ok,ok, what I mean by"slow" is the viewport performance with a lot of instances. I´m just talking about the laginess...

Some Infos:

- which version of C4D you are using: 2023.1
- on what OS: WIN10
- what is your CPU model?: 2xE5-2680 v4
- how much RAM is installed vs used?: 96GB / ~60
- what exactly do you mean by "slow"? Is it few seconds, 20+ seconds, or maybe minutes?: Lags in the viewport
- do you mean the viewport fps, or maybe it freezes, or something else?: viewport fps
- what exactly do you mean by "many objects"?: 1000000
- what kind of objects?: a Sphere or a simple Grass like "Ray Grass 001"
- maybe you can share a scene? or at least a screenshot?: attached Just scratch the Timeline :)

Display is set to none
automatic update is OFF (On or OFF does not make such a big difference, maybe NO difference)
Max instances: 1

hope this helps and thanks for having a look

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

Hi Bengamin,

I took your answer with a smile.
Obviously, statements like All or Everybody are not representative. How could they, when they come from a single person?
But we have 5 workstations here in the office and we all have the same problem. All Corona 9, C4D 2023.1

I honestly wonder how it would be possible that a crash never happens with you.
I can archive this, in minutes. A running IPR and some settings changed or just moved objects, new Keyframes, or whatever and it freezes.
Does this not happen to you?

I have not heard from anyone who is not affected. Everybody is complaining!

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

[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

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

[C4D] Resolved Bugs / Re: Volume Grid and Render Farms
« on: 2022-08-26, 16:44:56 »
it is R26 and Corona 9 April 21 2022

But this problem exists since the first version of VolumeGrid

[C4D] Resolved Bugs / Volume Grid and Render Farms
« on: 2022-08-25, 20:49:04 »
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

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

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

Pages: [1] 2 3 ... 6