- Mon Nov 26, 2007 7:57 pm
#253264
Hi all,
There seems to be a problem with the GMT offset in the Cinemaxwell plug-in under OSX. It has been happening all along (at least to me), and I was hoping that 1.6 would solve things but no.
Under the sky settings I specify lat-lon. 47 -122 (Roughly Seattle, USA) and GMT -800.
Working on a Windows PC this works just fine. Under OSX, not so much. I keep getting black renders, or sun settings way off what I am expecting. So, if I open the resulting MXS in Studio, I can confirm that GMT is set to 1 so for some reason my -800 did not get exported. It is worth noting that I have city set to "Custom" so that is not overriding anything, or should not.
Strangely enough, if I set GMT to 800 it does export as such, but then of course my sun is off by 12 hours.
Could there be a problem with the negative value in -800? Maybe why it is getting exported as 1?
Can anyone on OSX confirm this behavior please?
Thanks a bunch.
There seems to be a problem with the GMT offset in the Cinemaxwell plug-in under OSX. It has been happening all along (at least to me), and I was hoping that 1.6 would solve things but no.
Under the sky settings I specify lat-lon. 47 -122 (Roughly Seattle, USA) and GMT -800.
Working on a Windows PC this works just fine. Under OSX, not so much. I keep getting black renders, or sun settings way off what I am expecting. So, if I open the resulting MXS in Studio, I can confirm that GMT is set to 1 so for some reason my -800 did not get exported. It is worth noting that I have city set to "Custom" so that is not overriding anything, or should not.
Strangely enough, if I set GMT to 800 it does export as such, but then of course my sun is off by 12 hours.
Could there be a problem with the negative value in -800? Maybe why it is getting exported as 1?
Can anyone on OSX confirm this behavior please?
Thanks a bunch.
________________________________________
dyarza - Seattle, USA.
@home: MacbookPro 17" - Cinema4D 13
dyarza - Seattle, USA.
@home: MacbookPro 17" - Cinema4D 13