Distace from Camera to object in drawing.
-
That is a lovely script, but it seems I'm not able to load it..
How can I do that?Thanks a lot Al!
**EDIT: ok, I moved the original utilities rb to another folder and renamed your script "utilitiestools.rb", and it works: now I can get camera distance
Is there a less homemade or brute method?
Thanks again? -
Renaming files is dangerous.
Make a subfolder of Plugins dir, named: !_autoload
"
%(#8000BF)[Plugins/!_autoload]"Then get my !autoload script here, and put it in Plugins folder.
After.. you can put little scripts that you wish to autoload in the "
%(#8000BF)[Plugins/!_autoload]" folder. -
Hi, I got confused about this.
I try using get_camera_distance but the result aren't DOF
am I missing something ?here I attach my screen shot
if too small I also upload here:
http://imageshack.us/f/254/bingungdof2.jpgplease advice, thanks alot.
-
But the distance given by the tool is 703" - not '10' units in the Camera DOF dialog ?
Try using the real equivalent distance [in the correct units for that dialog] to see what happens.
The distance returned by the tool is the distance from the camera 'eye' up to the picked point - in your screenshot it's given in 'inches'... -
Yeah, so what are the expected units of that rendering dialog box? Feet? Meters? cm?
703 inches =
58.58 feet
17.8562 meters
1785.62 cmMy best guess is that it is expecting feet or meters based on the DOF shown in the 2 screenshots. 10 is too close, but 703 is clearly waaaaaaay to far. So its gotta be something in the middle, which would probably be feet or meters.
-
Hi TIG and Chris Fullmer, thanks for your reply.
I think I already put the unit into inch. and I already put 703 (not just 10) in Overide_focal_dist, but the result are all sharp.
I got 703 from get_camera_distance plugin, on the red ball.
here I attach another screenshot with color and setting, I'm going to make the red ball to be sharp and the other ball become blurry.
Do you have simple samples of your blurred .skp ?
and here also my .skp file in google drive:
https://docs.google.com/open?id=0BxjFhe9IY4QWLWUyYVFKdFNWRHM
many thanks for your help guys.
-
It's unclear if you tried what we suggested. I told you to try 58.8 in case V-Ray is expecting the input to be in feet, or put 17.8562 in case it is expecting meters. Do those two numbers then report back.
-
To elaborate again, the SketchUp pop-up is saying 703". But it appears that the V-Ray window is expecting the input to be in something other than inches, otherwise it would have worked. So other common units would be feet or meters. Since we know that object is 703" from the camera, we'll convert that to feet. It is 58.8 feet. Or maybe V-Ray is expecting meters, so convert 703" to meters and you get 17.8562 meters. That is why I'm saying try those two numbers, I'm hoping one will work. Then you will know from that point on, which unit V-Ray is expecting.
-
Have you tried adjusting the F-Stop?
-
Looks like he's got his f-stop set at 2.8. That should give a good DOF blur. And indeed in his first post, the image where he has f-stop at 2.8 and focal distance at 703, there is no visible blur, but when he changed the focal distance to 10, the entire image was blurry, indicating that the DOF is working, he just needs to set the correct distance.
-
I'm already changing my mind. I can see that lowering the f-stop even more might be needed Thom, good call. That should definitely be tried as well.
The further the object is, the harder it is to get a shallow DOF (blur). Lowering the aperture will help create even more blur. But its possible the object could be so far away that there will never be any apparent blur. You could resort to using tilt frame to force a blur. But I'm thinking at that distance, you should be able to get some blur.
-
He used a tool to measure the distance, so it should be correct.
It is possible that the F-Stop in VfS isn't working 100% like a real camera does. -
Well, in thinking about it, he's trying to blur something that is 58 feet or 17+ meters away. I'll get out my camera later today and open it to 2.8 and shoot something at about that distance, see if it produces any blur. At that distance, there is a chance there should be no blur.
-
As I understand it... the bigger the f-stop number the greater the depth of field about the focal-depth.
So a large number uses a 'pinhole' which has almost everything focused about that point, but a small number uses a 'wide-eyed' aperture which focuses on the point, with things nearer or farther away being shown blurred...
In real cameras the smaller the aperture size [i.e. the bigger the number] the less light gets into the 'film' and so this affects the shutter-speed in turn - so then there are three variables to juggle. But in rendering the focal-depth and f-stop interact to control the sharpness of objects that are nearer/farther away... and the 'speed' is therefore somewhat arbitrary...
-
Yup, except I think some (most?) renderers do take into account the shutter speed and use it for brightness/exposure control.
@Thom, he used "a tool" to measure, but is it designed to work seamlessly with the renderer he's using? The tool returns the distance in inches, but do you know what unit V-Ray is expecting? That's why TIG and then I suggested he try some different units.
I'm interested to hear back if its a units thing or not so I can move on from that sticking point.
-
I rendered this image couple of years ago, so in an older version of v-ray, but what I can tell for sure is that, it's a raw v-ray image with f-stop at 0.4. I remember that I had a hard time using physical camera, so I turn it off.
PS: I used a free plugin called "CameraDistance" , and in v-ray, the units are inches.
Good luck.
-
It's working. I added a checker texture on the ground so that the DOF effect is clear.
What you need is a lower f-stop to really see the DOF effect. For this image I used 0,2 and I made the ISO 1 for balancing the exposure.
-
@chris fullmer said:
@Thom, he used "a tool" to measure, but is it designed to work seamlessly with the renderer he's using? The tool returns the distance in inches, but do you know what unit V-Ray is expecting? That's why TIG and then I suggested he try some different units.
VfSU expects inches for everything - because it uses SU's internal units only. But his screenshot indicated the distance was in inches - did it not?
-
@thomthom said:
VfSU expects inches for everything - because it uses SU's internal units only.
Ahh, see I don't know that, not being an VFSU user. The screen shot looked like he used a tool by Al to determine the distance. But the Vfsu screen does not indicate what units it is expecting. So there was no way to know that he had input the measurement in the correct units. But if you say it is expecting inches, then yes, 703 should work.
-
So, as Stefan confirms... IF the f-stop is a very small number [large iris aperture] then most things at or near the 'focal-point' [set in inches] will appear sharp, with blurriness increasing rapidly away from that point. If the f-stop is a very large number [small iris aperture] then most things will appear sharp, irrespective of the 'focal-point' [set in inches] and their relative offset from that.
Advertisement