Jump to content

3ds max 2013 nitrous display problemt


Recommended Posts

Hi guys.. i m having this weired problem with the 3ds max 2013 nitrous display. i have attached a screen shot of a project that i am doin have a look and it ll explain the problem. can someone please give me an explannation.. pls

 

here is my pc spec.

Intel i7 Six Core Enhanced Performance Processor (4.3 Ghz)

12GB DDR3 1333 (6 DIMMS)

NVIDIA Quadro 4000 2GB

250GB 7,200rpm SATA

500GB 7,200rpm SATA

Untitled-1.jpg

Untitled-2.jpg

Link to comment
Share on other sites

I don't believe that this is a Nitrous problem.

 

Try using viewport clipping and/or a clipping plane in your cameras. Is it possible that you really far from the origin? The other possibility is that objects that are scaled up, or at the very least created in a different scale than you are now viewing them, can just display like this. Annoying, yes, but they shouldn't render with any issues from it.

Link to comment
Share on other sites

It's what Corey said, you are super far away from the origin. If you look at the first image, the model is at least 1,063,657 units away from world 0 in the X direction and 918,225 units in the Y. This will ALWAYS cause viewport issues. Move your model to World 0 and it should clear up your viewport.

 

To be honest, I'd like to see Max throw a warning when a model gets too far away.

Link to comment
Share on other sites

It's what Corey said, you are super far away from the origin. If you look at the first image, the model is at least 1,063,657 units away from world 0 in the X direction and 918,225 units in the Y. This will ALWAYS cause viewport issues. Move your model to World 0 and it should clear up your viewport.

 

To be honest, I'd like to see Max throw a warning when a model gets too far away.

 

I remember this warning when importing geometry from AutoCAD, in some previous version of Max.

Link to comment
Share on other sites

I remember this warning when importing geometry from AutoCAD, in some previous version of Max.

 

It still gives you the warning, but the object itself has to have massive bounding edges such as if you import a chunk of terrain or civil data. If you bring in a smaller object like a building, it's bound aren't that large so the warning gets skipped. I think the warning comes from the bounding box of the object rather than the object itself.

Link to comment
Share on other sites

  • 3 weeks later...

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

×
×
  • Create New...