- Fri Jun 08, 2007 9:11 pm
#231970
Hi.
Being made conscious by this thread http://www.maxwellrender.com/forum/view ... hp?t=23523 that there could be s.th. wrong with exporting the c4d-camera I decided to try a few test-renders.
The link above was all about the scale multiplicator, but I believe it's just a part of the problem or one of the results of it... because... during these tests I had to observe:
POV gets lost in a CLEARLY VISIBLE WAY when cam has a distance of less then about 35 cm...!!! The smaller the distance becomes, the less your m~r render matches your c4d-cam...
So.. when you're doing "small to mini"-things, you'll have to forget your c4d cam-navigation and use c4d as an exporter. The rest will have to be done in his "studio-ness".
Two things I would like to know about this issue:
a.) Is it possible for NL or its Testers to not ignore this issue but confirm it?
It would make it easier for me not to think that I do my things in a completely wrong way. So if a.)=yes, then
b.) Will it be possible to patch the plug again? Or would I have to hope for the rewritten plug?
Thx for your attention.
A few examples: (1st is maxwell, 2nd is c4d-outlines, resulting in an overlay-pic in original size. I always used an target-expression!)... (model->http://www.inf.uni-konstanz.de/cgip/leh ... x.shtml.de)
Camera distance to statue: ~100cm
+ =
Camera distance to statue: ~30cm
+ =
Camera distance to statue: ~15cm
+ =
Camera distance to statue: ~4.5cm
+ =
Camera distance to statue: ~1.85cm (notice the flipped m~r render!!)
+ =
Being made conscious by this thread http://www.maxwellrender.com/forum/view ... hp?t=23523 that there could be s.th. wrong with exporting the c4d-camera I decided to try a few test-renders.
The link above was all about the scale multiplicator, but I believe it's just a part of the problem or one of the results of it... because... during these tests I had to observe:
POV gets lost in a CLEARLY VISIBLE WAY when cam has a distance of less then about 35 cm...!!! The smaller the distance becomes, the less your m~r render matches your c4d-cam...
So.. when you're doing "small to mini"-things, you'll have to forget your c4d cam-navigation and use c4d as an exporter. The rest will have to be done in his "studio-ness".
Two things I would like to know about this issue:
a.) Is it possible for NL or its Testers to not ignore this issue but confirm it?
It would make it easier for me not to think that I do my things in a completely wrong way. So if a.)=yes, then
b.) Will it be possible to patch the plug again? Or would I have to hope for the rewritten plug?
Thx for your attention.
A few examples: (1st is maxwell, 2nd is c4d-outlines, resulting in an overlay-pic in original size. I always used an target-expression!)... (model->http://www.inf.uni-konstanz.de/cgip/leh ... x.shtml.de)
Camera distance to statue: ~100cm
+ =
Camera distance to statue: ~30cm
+ =
Camera distance to statue: ~15cm
+ =
Camera distance to statue: ~4.5cm
+ =
Camera distance to statue: ~1.85cm (notice the flipped m~r render!!)
+ =
Last edited by mashium123 on Wed Jun 27, 2007 5:56 pm, edited 3 times in total.
Mesut Capkin
http://www.mesutcapkin.com
http://mesutcapkin.cgsociety.org
i7 4930K@4.2, 32gb, win7prof, 2*980ti-6gb, gtx660-2gb
i7 920@3.6, 12gb, win7 homepremium 64bit, gtx285-1gb
i7 720QM@1.6, 12gb, win7 homepremium 64bit, hd5870-1gb
http://www.mesutcapkin.com
http://mesutcapkin.cgsociety.org
i7 4930K@4.2, 32gb, win7prof, 2*980ti-6gb, gtx660-2gb
i7 920@3.6, 12gb, win7 homepremium 64bit, gtx285-1gb
i7 720QM@1.6, 12gb, win7 homepremium 64bit, hd5870-1gb