Messages

61

[C4D] General Discussion / Re: Some Cosmos assets not team rendering

« on: 2022-06-07, 15:37:10 »

Hi Beanz,
any updates on this?
I checked the chaos help and can’t find out how to configure the cosmos browser installed on the nodes.
How do I make sure on the nodes with just TR client installed that Cosmos is looking in the right network folder for assets? 
MacOs 10.15.7/ S24/ Cor V8

62

[C4D] Feature Requests / Re: Chaos Cosmos browser window naming

« on: 2022-06-06, 20:49:40 »

The COSMOS browser opens in a regular C4D window. I can rename the window and then it shows up, BUT it doesn't survive a restart.
If the window can be named just like the Corona material library, that would be great. Thanks! 

63

[C4D] Feature Requests / Re: Chaos Cosmos browser window naming

« on: 2022-06-06, 15:56:16 »

Instead of moving windows around to find the Cosmos browser, you could bring it to the front by clicking in the window menu, but it doesn't show up. Same in C4D dock icon context menu.
macOs 10.15.7. / C4D S24/ COR V8

64

[C4D] Feature Requests / Re: Materials and node editor

« on: 2022-06-05, 01:58:22 »

I know this thread is “old” but it needs to be revived…
I agree with all of the above, especially this:

"By the way, I think making "base layer" such a long/tall tab, putting together diffuse, glossiness, ior, edge, bump, anisotropy and rotation of the anisotropic highlight was a terrible mistake. It was so much cleaner when they were in separate tabs, there was no need to scroll to look for it (and i also find scrolling in this menus kinda risky, because you can end up scrolling a floating slider or a drop-down menu)." 

Quite right - from a user experience point of view it hides the common settings, but keeps the occasional settings visible. The old way was cleaner and involved less clicks.

"I don't really see the point of having the normal map under the bump channel. To apply a normal map you have to go to base layer, scroll down to bump, enable it, click texture -> plugins -> corona -> normal. Wouldn't it be easier to have it as a category"

Definitely agree.

Yes, yes and yes!
Corona became a huge success, mostly because of it’s ease-of-use approach and of course it’s good looks ;-)
Now it’s starting to add more complexity for NO apparent reason. The goal should be “Less Clicks, Less Scroll = Faster Workflow”

What’s up with the “Enable” checkbox for Bump, disabled by default? Why? Unless you render black holes for a living, every material on planet earth has some kind of “bump”.
In the spirit of “Less Clicks”, can the default be set to “enabled”?
Also, “EDIT” button in the PV/ post process/ tone mapping? I use tone mapping EVERY day, but never used “sharpening”
Shouldn’t tone mapping be there by default and “EDIT” for less used features?

The Corona team has an entire army of unpaid but very active “daily” testers at their disposal.
Getting valuable user input BEFORE spending countless man-hours coding, by maybe showing mockups of planned features/ layouts could be a win/win for all.
I hope you take this into consideration when re-working the VFB - Yes, outdated zoom buttons and scroll bars, I’m looking at you… 

65

[C4D] Resolved Bugs / Re: hdri in Sky object does not show in the viewport

« on: 2022-06-04, 18:06:29 »

@frv
are you on S26?
As a workaround, Stefan-L has a nice xpresso setup here
https://forum.corona-renderer.com/index.php?topic=34597.msg193216#msg193216

@Stefan
since there is still no fix, maybe you can post your sky setup in the "[C4D] Corona Goodies - User Contributions" section,
so it's easier to find?

66

[C4D] General Discussion / Re: Some Cosmos assets not team rendering

« on: 2022-05-30, 00:46:09 »

Hi BigAl3D, same outcome if rendered from mesh. I think the TR issue is related to the immutable shader.
My COSMOS assets get saved to a server that all nodes can access, but maybe they need to live on the main machine to be send to TR.
Are you by any chance already on V9 daily? When you have a minute, can you try to TR the 'Purple Willow 001" or any other asset that uses the mystery immutable shader?
Trying to figure out if this is related to my setup.
Thanks!   

67

[C4D] General Discussion / Re: How to solo node?

« on: 2022-05-30, 00:36:44 »

I mean if you already know what all of your materials look like beforehand, then you probably aren't the target audience for this functionality.

What I was trying to say, I don’t need to review every material I apply to a new model in IR, but I do need to see in the viewport how this material is mapped.
Just trying to point out the workflow difference betw “solo mode” that renders and a “solo mode” that just shows in viewport.
This applies mostly to metal and glass that don’t give you any representation in the viewport. I do it the painful way and copy bump or roughness shader to diffuse. With the legacy mtl I untick all except diff, make mapping adjustment in the viewport and then turn all back on. Of course you need to set preview size to your bump map size to get a useful viewport preview.
I usually leave the bump shader in diffuse (unticked) for later use. This works in legacy but not in physical.

68

[C4D] General Discussion / Re: How to solo node?

« on: 2022-05-27, 20:30:59 »

…you will only see a simple Noise Texture render in LV.

activate solo node, and it will allow me to preview only the noise texture and how it is mapped onto my object live in the IR viewport.

This might be good for a IR workflow but who has time for that? I think the way c4d mtls have the “viewport display” options can be a faster workflow in general.
For example I create my stainless steel with micro scratches in bump, select bump as viewport display and save mtl in asset browser.
Next time I apply this mtl it shows me bump mapping in the viewport, I can quickly adjust mapping and move on. No need to go back into the material and “un-solo” anything for rendering. This would be a huge timesaver!
Not sure how most people work, but when I work in fairly detailed interior/ exterior scenes I never use IR. I know how my materials look in final render, I just need to quickly see that they are mapped correctly.
 

69

[C4D] General Discussion / Re: Some Cosmos assets not team rendering

« on: 2022-05-26, 17:35:42 »

Purple Willow 001
Preview flipped, renders correctly, but maybe bump reversed?
TR shows faint leaves - nodes can't access these "immutable shaders"?
Happens to other assets w/ immutable shaders.

70

[C4D] General Discussion / Re: Some Cosmos assets not team rendering

« on: 2022-05-25, 20:08:18 »

Can we assume your are not missing textures for these assets? I haven't used Cosmos with TR yet, but that was my first though. If the materials are there, what happens if you convert the Proxy to mesh?

I would have said yes, the textures are there, they render on single machine but not in TR
Then I checked to make sure, and now I don't know anymore...
See screenshot attached. …immutable shader what??? No idea what this means.
That "mystery shader" does not show up in asset inspector.

@bnji
In the middle of a project that hopefully finalizes next week. Will try V9 daily then.
In general, is this related to the corona engine or could a cosmos browser update fix issues too? 
It looks like the leaf mapping is flipped 180°?

71

[C4D] General Discussion / Some Cosmos assets not team rendering

« on: 2022-05-21, 15:24:50 »

I’m late to the V8 game, so this is probably a known bug, but some assets render correctly on single machine but not in TR.
That’s a real joy, when you are pressed for time and use Cosmos assets - do a quick low res single machine render and then a full rez TR render overnight.
How fun when the next morning half your garden was rendered with the “nuclear winter pro" preset… There goes your deadline. 
This seems to happen to assets that use the opacity layer.
macOS 10.15.7 / S24/ V8

72

[C4D] Feature Requests / Chaos Cosmos browser window naming

« on: 2022-05-15, 17:01:19 »

Please name the Cosmos browser window.
At least on macOs the browser window does not show up in C4D>Window or the dock icon context menu.

73

[C4D] General Discussion / Re: Mac Studio Experience?

« on: 2022-05-13, 19:41:54 »

Then at reopening the Cosmos browser I get a white window without assets.

Same on Intel mac. Sometimes just blank for 10-30+ mins then suddenly loads.
I always thought the server is overwhelmed. Search still kills C4D completely.
I gave up on the constant updates when opening, because always something funky going on after update.

74

[C4D] Daily Builds / Re: Chaos license server

« on: 2022-05-10, 15:36:28 »

The forum works better than support ;-)
Ticket ID #37805

75

[C4D] Daily Builds / Re: Chaos license server

« on: 2022-05-10, 15:08:36 »

Hmm, contacting support to get a lic server working? Did you maybe make it too complicated?
Anyways, I opened a ticket just to be on file that this should work easier from the start.
We know that's possible since it worked flawlessly pre-Chaos.

How did you guys get to activate TR nodes? Is editing the vrclient.xml file the only way?

What throws me off is:
From Troubleshooting: If you can't find the vrclient.xml file, please reinstall the Chaos License Server as instructed here...
Does the xml file get installed or generated during install?
Essentially this is just a txt file that I could create and paste into .ChaosGroup
Where can I copy the vrclient.xml text and does it live in .ChaosGroup root (on mac)?
Thanks!

EDIT: Ticket ID #37805
What's the usual support response time? I submitted this morning at 7am / 1pm Euro time -
Now it's 9:30am / 3:30pm and you guys are getting ready to hit happy hour...
No response so far...