[mashium123]

Sky don't work.
The exported mxs shows a different time (when I open the scene in studio - just to check), means suns shadow shows a different direction then a cinema rendering.
Neither a "normal" comparison of the both systems leads to a synchronized sky_system, nor the expression that was once provided by forum members that corrected the missing sync between c4d and m~r rendering.


Any experiences?

[seco7]

I also cannot get some of the preset cities to render anything but black. Some seem to work, but others seem not to.

[Kabe]

Sky don't work.
The exported mxs shows a different time (when I open the scene in studio - just to check), means suns shadow shows a different direction then a cinema rendering.
Neither a "normal" comparison of the both systems leads to a synchronized sky_system, nor the expression that was once provided by forum members that corrected the missing sync between c4d and m~r rendering.

Well, I made such an Expression once (don't know if I postetd it here though.

I'll look into that issue, and I'm confident that NL will care to get the
systems working together well. In 1.5 they added features that make it
much easier to get it right from the plugin's perspective.

Kabe

[macray]

until now - I gave it a try with a R10 demo...

the sun never changed whatever hour I set in Cinemaxwell.
Only changes in latitude and longitude change the angle of the sun. Hour settings are ignored.

[Becco_UK]

I agree the time setting in the plugin does not transfer to the mxs file. All renders using the new plugin are at 09.00.

A quick fix is to open the scene in Studio and set the time there. Not ideal but useable while we patiently wait for the plugin to get fixed - soon I hope!

The big problem at my end is the custom material one reported in other posts.

[mashium123]

Sky don't work.
The exported mxs shows a different time (when I open the scene in studio - just to check), means suns shadow shows a different direction then a cinema rendering.
Neither a "normal" comparison of the both systems leads to a synchronized sky_system, nor the expression that was once provided by forum members that corrected the missing sync between c4d and m~r rendering.

Well, I made such an Expression once (don't know if I postetd it here though.

It is this expression I was talking about - whoever did it, it was a very handy thing for workflow:
http://www.maxwellrender.com/forum/view ... hp?t=20348

It seems, that (when you check the exported mxs in studio) it is always 09 a.m., so no matter what time you install in your plug it's always 09 a.m. for the maxwell renderer...

In 1.5 they added features that make it
much easier to get it right from the plugin's perspective.

What is your suggestion for this problem, Kabe?
I seem to be FORCED now to open Studio, to get the right sunposition for my archviz renderings... This was not the case with the prior release together with the expression mentioned above.
Or is it possible, that I'm doing s.th. wrong... maybe it works and I just didnt figure out how... I mean.. after a year of evolution, progess and testing there surely is a way besides being forced into studio... right?

I mean.. hey... it's the position of the sun...

[Tyrone Marshall]

The sky is not broken, there is an issue with values being reported to MXS from the plug in that is being looked into.

You will be the first to know once it is solved.

[Becco_UK]

I agree the Maxwell Sky works fine but in reguards to its use with the Cinema plugin you only get early morning sky

[Tyrone Marshall]

I agree the Maxwell Sky works fine but in reguards to its use with the Cinema plugin you only get early morning sky

Yep!