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 - edub

Pages: [1] 2 3 ... 5
[C4D] Feature Requests / Re: Some ideas for Chaos Scatter
« on: 2022-05-07, 21:32:25 »

- You can set a "frequency" for the clones in "object / instanced children". It would be nice if the setup field worked like a standard C4D input field and we could also easily reset the value to 1.

the way this works currently seems fine...  not sure what's missing, besides resetting to default=1 (doesn't seem that crucial, tbh)... 

[C4D] Feature Requests / Re: Some ideas for Chaos Scatter
« on: 2022-05-07, 21:29:56 »

Here are some suggestion for the Chaos Scatter tool:
- An option to influence which clones are being created where depending on a grayscale map.;topic=36146.0;attach=164192;image

+1000 on this...  it's a must-have

yes, it was 9daily with custom install...  I always use that way.

I've done full un-install if S26 and prefs folder - re-downloaded everything, and clean install, and now it works ;)

[C4D] Daily Builds / Re: C4D S26 supported ?
« on: 2022-04-22, 22:48:04 »
anyone have success with the daily9 update?  I'm getting lots of errors on S26 startup and missing Corona plugins once it's up and running

these are just 4 of the warning/ error dialogues that pop up on start-up...  I didn't screenshot them all....  S26 starts up after, but is still missing several Corona plugins (see last image)

We work collaboratively on files, which means I might need to open a file that someone else created.  We have been experiencing crashes when trying to open certain files.  Stil started after we installed RC2. I have tried rolling back to the daily from 2/2, and had brief success when opening a file that didn't open w/ RC2, but then it caused a crash the next time I tried.  We have experienced this on 3-4 different work stations now. Not entirely sure this is the fault of Corona (if not then it would have to be a C4D problem, which never existed until now).

A separate issue is that the Chaos Licensing system is only working sporadically. 

You need to have both Corona and V-Ray under the same account. If you have them under different accounts, contact us, and we will move your license from one account to the other:

well, this is quite the roadblock for some.  I have several licenses under a company name, and the team that works for me uses them with Corona - but they also personally own Vray license, and have to switch license server each time they change renderer...
I think it's a bad solution to force everyone to use only a single account...  what is the proposed solution in my case?  Surely I'm not the only one in this situation?
You should seriously consider adding the option for multiple accounts

iiiinteresting...   thanks!

there was a notice to update the cosmos browser (Chrome, WIN10) - can't remember exact message...  afterwards I can't see any materials in Cosmos...  is this something with the Corona, or Cosmos, or what?

[C4D] Daily Builds / Re: New Cosmos browser
« on: 2022-02-16, 21:03:32 »
With the latest daily (Feb16) there has been some great improvements, but looks like the 10x scale issue was sadly not resolved (hopefully in next daily?)...
It is great that the proxys are now named uniquely - thanks!
triplnar mapping supposedly works - can you point to an asset where we can confirm this? (I'm unsure about which are using it)
I still see many objects with missing material tag assignments (with the "?" instead) - this is hopefully a priority?  I've tried "fixing" some, but have no idea which material tags are what, as there apparently are not polygon selections associated with them.
I understand the desire from Chaos to keep the Cosmos assets proprietary (i.e. that they won't be usable if they're made editable)...  but can someone please confirm that this is the expected behavior?...  so we won't be able to edit any of the image files (e.g. .tx files) used in any textures either?

[C4D] Daily Builds / Re: New Cosmos browser
« on: 2022-02-15, 01:14:25 »
Any update from the devs on the 10x scale issue in the Cosmos library?...  this is pretty crucial to me, and currently an issue which make it mostly unusable for me at the moment.

[C4D] Daily Builds / Re: New Cosmos browser
« on: 2022-02-10, 02:37:03 »

An observation:
Load a Cosmos object and import it. The proxy is scaled to "10" in X, Y and Z, but this gives it the proper and expected size.
Now "Dupilcate to Mesh". The created mesh is scales to "1" in X, Y and Z, but this also means that humans, for example, are less than 20 cm tall (great if you plan to shoot the next hobbit movie).

Btw, a scale other than 1,1,1 is undesired in C4D in general, at least for objects in their original state.

I had overlooked this thread, and made a new one describing exactly this issue, and the fact that cloners only "see" object scale=1, so when cloning Cosmos proxys, everything is 10x too small
(link to my thread:

A separate issue, which I thought could be a workaround, is when making Cosmos proxys editable they seem to lose the correct material assigments (there are no polygon selections...  is that as expected?

[C4D] Daily Builds / Cosmos assets object scale
« on: 2022-02-10, 00:06:11 »
first of all - thank you for supporting the Chaos Cosmos library - that's exceptional news!
I have noticed that assets are imported with the proxy object axis scale set to 10.  I don't know if this is something that is a work-in-progress (like the glossiness parameters), but this is a huge issue because when you use the proxy in a cloner or scatter, the way it's handled is as if the scale is=1, which means the object is 10x too small.
If I run the "reset scale" on the proxy to make it=1, then it will be too small.
Why are the proxy scales set to 10?  I hope this will be fixed, sooner, rather than later?

edit:  Apologies, but I missed the other thread about the Cosmos browser, and the fact that the problem was already identified by Cinemike, here:

Is there any official update, or statement from Chaos as to why this hasn't been made possible yet for C4D? 


Pages: [1] 2 3 ... 5