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

Pages: 1 [2] 3 4 ... 7
16
is there any way to solve this problem on OS X or we have to turn back to some RC older version??
we cannot render on OS X with the latest version.... :-(

17
it happened only when the mac is inactive for me.

I can render 300+ passes without crash if i move the mouse. But if the mac is in sleep mode it crash after some passes ..

no sleep mode... no screensaver active.. no energy safe mode... in some scene the crash happen after 10 or 20 passes.... or when i try to save the CXR file.... i don't understand why....

18
Happened to me very often.

C4D freeze after a couple of passes, like 35 40 ...

the same thing happen to me.... don't matter the count of passes but, in OS X c4d freeze everytime with corona.... 50 - 60 - 100 passes.. once you try to save the CXR files  c4d and corona crashes....
in the WIN version everything seems to work fine....

19
cannot render with corona under OS X yosemite 10.10.5 and cinema 4d studio r19. unfortunately i cannot post the scene... but the same scene, rendered in the PC WIN renders fine.... same scene... same resolution everything it's the same... rendered at 4000 x 2000 in OS X corona crash after some passes.... i have a mac pro late 2013 with 32 G of ram.... the PC it is a simple i7 with 16 G of ram... and if i renders the scene in the PC at 7000 x 3500 everything is fine.... in the mac version corona crash....
i use:
Build timestamp: Feb  5 2018 10:05:29
Version: B1  (core 1.7)
Cinema version: CINEMA 4D Studio R19.053 S

in little words,on OS X , the renders start and seems to work fine.... when i try to save a CXR step, the plugin crash and i have to force the exit in cinema 4d... a cannot understand what's happen. I post a screenshot and the bug report.txt.
thanks a lot
walter

20
@walterfog

Yes, I do have a hard time understanding what your problem is. You're the only one with that problem.
From your last post, I'm not even sure what you mean.

So your botched workflow with normals doesn't work anymore because the normal shader works as it should?
Maybe there were changes, or maybe not? How could we find out?
Maybe one could consult the wise man on the mountain or read the patchlogs! But instead, you meander around on the forum.
Just do it properly from now on and you won't have any problems.

even with other kind of problems I was the only one... and thanks to Nikola I solved them privately .... unfortunately I do not have any more time to waste with your useless speeches ... do not be sad if you do not understand....

 

21
The normal maps work fine. burnin and he previous posters already said everything.
A while ago, in your thread, we have "found out" that Corona uses DX maps(flip Y), but you refused to accept that things are handled differently.

I'm sorry but I made other test, with other normal map and using your method of swapping red or green or both... the result is similar but the corona normal shader don't work well for me, and the results is not equal to the one gives other engine.... the only way to obtain the exact result is using a leveled material as I posted in my scene, and not changing the normal color... OpenGL or direct X I expect that a map, work fine in any engine render...  that's my opinion...

Your expectations of how things ought to be don't matter nor will things change according to them. Just accept it and advance. Do it properly in the future and spare us and yourself the hassle. If you are too lazy to make a small change to your old materials(in case you even need them), then that's your problem.


the case I report now i totally different from the post i've posted ago... in fact in the previous post layered normal or corona normal works fine till alpha A5... now i'm reporting that normal done with alpha A6 don't works fine with the last rc1 version ( r19 and OS X yosemite ) ... this are two different thing... if you don't know what i'm discussing and the problem I'm reporting please shut up... maybe you are to lazy to understand what I'm discussing of....

22
@ Walterfog

IMHO, your example shows "How Normal Maps should NOT be handled".



my example show how normal map work correctly till the last alpha A6 of corona... if  now the way to handle normal is changed, then I have to change all material with normal map....

23
Well I'm sorry if I am repeating myself but if the only thing that is bothering you is the "missing texture" icon then you can safely ignore it. It works.

For the facets, that happens when you have a really rough / strong normal plugged in so if you hit render in your scene you'll probably see the polygons on that sphere. That is "normal" for Corona and you'll need to adjust the strength value to an earthly value :)

this is due at something changed from alpha a6 and the last rc1 beta 1 ? cause in the last alpha a6 it works fine... same object... same project.. same material... same normal setting... probably in the last RC1 beta 1 normal setup is changed....

24

Initially I thought you were experiencing shading errors that offset your texture / create other shading problems. That said, when I opened your file I did notice that your normal map is too strong and it creates a faceted look on the sphere. You'll probably need to tone that down.

i don't know if that normal create problem or not... i only know that till alpha a6 everything works fine... sphere preview and material results with normal... now i don't know if this material works fine, but like you could see in the preview the faceted sphere let me think that there is something wrong... the normal map it is ok.. work fine on the previous version of corona and also works fine with other render engine....

25
Does it happen even if your normal strength is set to something low like 1%?

The missing icon is "OK" because afaik the devs haven't fixed it yet. It works but its showing up like a missing texture right now. Don't worry about that one.

keeping strength like 1% does have no sense... don't you think?? after this  the same project but opened in R17 with the last alpha A6 of corona, works fine and have no problem....

26
strange question mark in bump channel with normal map... look at the picture and the example scene posted... cinema 4d r19 OS X yosemite...

Your normal map appears to be super strong and it is probably creating those shading problems. Try toning it down to see if it helps :)

i try to modify tone .. try to create again normal channel... etc.... the problem still appear... and also I don't know why the question mark appear in the bump channel...

27
strange question mark in bump channel with normal map... look at the picture and the example scene posted... cinema 4d r19 OS X yosemite...

28
Works also on R19(win).
Is it something specific like reflection that you're having problems with?
Also when the scene is complex with multiple lights, the bounced light still hits the excluded object and it might look as if nothing changed.

no complex scene... only 2 light.... 1 with excluded object... but this not work....

29
the include/exclude object option for lights I think don't work at all... cinema 4d r19 studio and OS X yosemite.....

30
just try the bloom and glare under studio r19 OS X Yosemite... during rendering under corona VFB a strange blink appear during setting up the bloom and glare values... and generally VFB don't work well when setting up the value... just take a look at this video I quickly made with phone just to see you what happen...

link to wetransfer:

https://we.tl/RdbR8H2zE4

Pages: 1 [2] 3 4 ... 7