Scene bounding box & Far from Origin ERRORs

V-Ray V-Ray for 3ds Max Issues
1

These are 2 warning messages, which appear in the V-Ray Message Box when the scene has some minor problems.
However they may not influence the final rendering image, but here is some clarification of them.

… Scene too far from Origin …

This warning means that the entire geometry is far away from the Origin
point - XYZ (0,0,0). This usually happens when the model is imported
from some other software like AutoCAD, etc.

Possible solution:

(*) Select all the geometry - Ctrl+A
(*) Group it all and name it - like Group A.
(*) Select the group.
(*) Right-click on the move icon, the floating coordinates will appear.
(*) Under the Absolute:World - you will see the real position of the group.
(*) Put zeros (0) to all the X, Y, Z values. (right click on the spinners)
(*) This will bring the group in the very Origin point.
(*) Ungroup
See after rendering, whether the error appears again.

… Scene bounding box is too large, possible raycast errors …

Thit error usually means one of the following:

Case 1
The scene probably contains some objects which are far from all the others. They however may not be visible, but to present in the scene.
This is often happening with some 2D (AutoCAD, Microstation) drawings, e.g. blocks’ insertion points, buggy objects, which during the import
process haven’t entered correctly or they have, but do not present any real geometry.

Possible solution:

(*) Unhide and unfreeze all, so that every geometry is visible in the scene.
(*) Hit - Ctrl+Shift+Z in Top view
(*) This will Zoom Extend all the scene.
If you are not seeing your scene zoomed extend to fit the whole
viewport, then you have some objects away.
(*) Locate those objects and delete them.
(*) Repeat from step 2, until the scene fits the viewport.

**Case 2** Your geometry may be out of proper scale, e.g. modelling a building in mm. (\*) Rescale it correctly. Check the (Customize -> Units Setup -> Display Unit Scale) Also check - the \< System Unit Setup >

Best regards,
nikki Candelero

2

good info…

i might add:

it’s always good to get rid of the invisible zero-geometry “block” objects when importing DWG files.
they slow things down and even caused some problems with earlier vray versions.

they can be isolated with the selection dialog, by entering “block” into the selection filter.

3

good info guys.
I always move my autocad plans/models etc before I start modelling just to make sure everything is going to be at 0,0,0 or close to it

4

Whats the actual distance involved that brings upon that error? I always clean up my cad drawings as much as possible.

Ive also had it when working from scratch before :lol: Its pretty rare that I dont get it when working on a scene.

Also, - it says it may cause raycast errors, but does it actually make a noticable difference? I cant say ive ever seen anything fuck up, even on a 2km sq site plan.

5

I have those errors with my current project as I have imported a large amount of terrain. I don’t know how the end result will be effected.

6

I have this problem, and it seems to dramatically slow down lightcache and rendering calculations when using the fish-eye lens.

The model is at 0,0,0, and I’ve tried adjusting the system units, but the problem is still there. I’m not keen on scaling my scene(until final render) as it means all the modifiers values will be out of whack.

7

What are the light cache settings? You are not using World scale for the light cache, are you?

Best regards,
Vlado

8

Nope :slight_smile:
Standard adaptive qmc setup. I should also point out, I’m not running v1.5 yet.

I’ve PM’ed you the file with the problem. See if you have the same difference in LC speed with fish-eye on and off.

Don’t worry about fixing it for me… I don’t actually need to use the fish-eye lens on this project… but I thought it would be worth finding out why this was happening and if there was a work around for future projects. ( I wouldn’t want to disturb you from the pressing issue of dongle shipment! :stuck_out_tongue: )

Thanks again Vlado.

9

So what are you supposed to do when you have a large terrain set to scale?

10

dont worry about it juju, we have never had any issues with the error message

11

Never had problems with this message on a 32 bit platform. On a 64 bit platform, it can make a huge difference. Changing the scene on a 64 bit platform in order to get rid of this message makes the file render much faster. Sometimes it doesn’t render when the scene is outside of the limits.

Marc

12

Getting rid of the Blocks does not always work. I often work with Microstation modelled files and sometimes you can delete the Block objects but sometimes you shouldn’t even touch or let alone delete them. Any object that is linked to them will move to some obscure location or be deleted. I’m still trying to work out a good solution since it seems be on the Microstation export side where the problem is and I’m not using Microstation to model (yet)

The only constant seems to be when objects are imported and were instanced when they were modelled…

13

I am wondering, what is the maximum bounding box size ? Is it relative to memory ?

14

who knows?! I’m using mm in both display and system units and I get this error all the time, however it doesn’t seem to be effecting anything…

15

I just ran into this issue. The bounding box hasn’t changed size, there are just now far more objects within that area. The result is most of the small objects simply don’t show up!

16

I think it may actually be the negatively scaled foliage - i’ll be checking it soon.

Further info:
-nothing to do with negative scaling
-occurs with phys cam and standard cam
-camera clipping has no effect
-nothing to do with xref objects, scenes (does the same with a straight merge)
-if i hide all layers EXCEPT the problem layers, the problem remains
-One of the problem layers was fixed - there was a vray fur object and some other geometry object that were god knows where in the scene, i couldnt actually zoom in on them. I deleted them and that layer on now works ok. Moving on!
-Similar problem with second layer, had 1 tree that was apparently at 0,0,0 but I couldn’t actually see it. Deleted it, rendered fine, no message.
-Final layer had no problems with it, I was dreaming. WHATEVA.

So in conclusion, read the original post. Select all you see on the screen, invert selection and see what it is you have selected.

17

I don’t understand this “Your geometry may be out of proper scale, e.g. modelling a building in mm.
(*) Rescale it correctly.
Check the (Customize → Units Setup → Display Unit Scale)
Also check - the < System Unit Setup >”

Why is MM an incorrect scale? - architects in the UK always use this unit. and so since all our DWG’s are made in MM, I Model is MM too, it’s the more accurate form I believe. Does Vray react differently to things using MM?

18

its just that a 1km community would have insanely high measurements if the unit scale is mm. i doubt your going to want to zoom down to something that actually is 1 mm so its overkill to keep it in that units

19

Well actually we blow our images up to a very high resolution and print BIG, and a 50mm shadow gap for instance is a very fine but noticeable detail, we start loosing that and architecture loose’s it’s crispness. MM IS the standard in the UK, so why isn’t it in the software we use? besides the fact that everything in our Viz Lib is scaled accordingly, this would take for ever to re-scale everything and change the proxies etc..

20

you’re missing the point. In lamens terms: The program is giving you a warning merely because you have a 50km area and so if the program does calculations etc it uses few digits. But to calculate that 50km in mm are couple of extra digits. So it’s telling you that chances are higher for a problem in calculating stuff because of the extra digits. Just ignore it. I always get this error and I always work in mm (for architectural stuff).
For very large areas in small measurements, you will have a problem of zooming, because there are just tooooo many digits. I’ve had a situation before that my area was so large (cant remember excact sizes now), that I could’nt zoom extents. It zoomed out only about halfway. Then I had to change to m instead of mm

Also, if you use Hair and Fur modifier, it makes a HUGE difference in your scale and units.