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

Pages: [1] 2
1
Quote
20 minutes seems a bit off since an m1 renders it in 12.

But a M1 Ultra (two M1) not a M2 Max (one M2), so this should be what is to be expected i think.
M2 Ultra should be 10:10min then...
Correct me if i am wrong.

edit: (test from asimo)
Quote
I rendered it on both my Mac Studio M2 Ultra...
Quote
Mac Studio: 10:19

2
Hello

Both testrenders from another M2 user:
C4D  R25.117
Corona 11 (Build 29.11.23)



3
I just tried that, but that doesn't work. If emit light is on, the reflection of the plane is not visible.
It cast's no shadow though.

4
@Stefan-L:

Sorry, not a workaround really, i had to change the angle of the sun and moved the foregroundplane not to cast shadow on the building.


5
As i wrote, i used this setup for an architectural vizualisation of a building where i wanted the foreground landscape reflected in the windows.
I had to use planes in front and back of the scene for fore- and backgroundimages instead of environment overrides because i wanted to use global volume (fog)

The frames of the windows are rough metal so i noticed the shadow of the foregroundplane on parts of the metalframes making them too dark.
I solved the problem, just wanted to show you the problem.

Attaches previewrenders: (without plane for background) the frames on the right side are near black because of the shadow of the foreground plane and even shadow on the terrain (without scattered grass)



6
Simple testscene:
Lightmaterial (no emitting light) with a picture on a plane in front of a plane, sun from behind.

-If the plane is nonmetal all is as expected, no shadow from the lightplane.
-If the plane is metal and the roughness is increased, the lightplane casts a shadow on the metalplane.

i think this should not happen? Even with a corona compositing tag and "cast shadow" unticked it casts a shadow on the plane.

I noticed this in an archviz with a lightplane in front of the scene for the foregroundreflections on the glass/windows with metalframes.

(corona-10-c4d-daily-2023-01-23-mac)



7
This setting seems not to be the problem, because this was already set to "C4D picture viewer" in my corona settings.
Thank you anyway

8
Ok, thank you John.
I have this problem only since the last daily build 2023-01-23 (C4D R25). But i will try your workaround.

9
Hello

"render marked takes to pictureviewer" renders always the same take (the actually marked take) instead of switching trough all marked takes.
 

(Daily Build 2023-01-23)

10
[C4D] Daily Builds / Render takes to pictureviewer problem
« on: 2022-12-21, 13:26:52 »
Problem:
some takes with different cameras, each camera has different tonemapping settings.
"Render marked takes to pictureviewer" uses the tonemapping settings of the first camera for all other takes, it ignores the tonemappingsettings for all other cameras/takes.
If i use the renerqueue, it works as it should and updates the tonemapping for each camera/take.


11
[C4D] Bug Reporting / Re: Cosmos Keeps Refreshing - On MAC
« on: 2022-12-21, 13:13:09 »
Same Problem here with restarting cosmos browser.
iMac 2019 MacOS Big Sur.
Latest Corona10daily 2022-12-20

12
[C4D] Daily Builds / Re: Problem with corona normal maps
« on: 2022-04-14, 15:43:15 »
I just repeated my simple test with a cube and a corona normalmap and it works as it should so far now. Thank you!
Test with official V8

13
[C4D] Daily Builds / Re: Problem with corona normal maps
« on: 2022-04-11, 12:08:27 »
There has nothing changed in RC4, still the same problem wiith corona normalmap.
As soon as i apply a normalmap, even the previewpicture in the materialeditor looks distorted and the render looks wrong.

edit:
Found out that if i first choose corona bitmap under corona normalmap and then put in a normalmap (jpg) it works ok.
Do i always have to choose corona bitmap for any map i want to use?  That was not the case in earlier versions.

edit2:
all assets in my projects that use corona normalmap are rendered wrong now and have strange distorted preview in the materialmanager

14
Addition to my previous post

Test with Object from cosmosbrowser:
See example sreenshots. If bumpmap is disabled, the render is ok.

15
[C4D] Daily Builds / Problem with corona normal maps
« on: 2022-04-01, 13:57:00 »
Hello

There seems to be something wrong with corona normal map shader in new versions of corona render.

My simple Test:
If I apply a normalmap to a corona standard physical material (bumpchannel->corona normal)  the edges of a rounded cube are visible. The Materialpreview is also distorted.
See screenshot 100%

The same happens with a Material from the Cosmosbrowser. See attached screenshots.(Cosmos_Material01+02)

This did not happen in earlier versions where i set the value to 100%.
The color profile of the normalmap is set to linear.

Can you please test this?

iMac2019 / OSX 11.6.5 BigSur / C4D R25.117

Pages: [1] 2