memory problem when I turn on snap

[artyvisual]

Hi All,

 

Anyone experience with this problem?

3d max shuts down, saying running out of memory, when turning on snap (2,5 or 3d). Okay; it isn't a NASA computer, but it has worked previously on computers with lesser internal memory, so I think it is or a bug in the software, or a problem with my video card/memory banks? Any tips I can try?

(platform is XP)

[Crazy Homeless Guy]

If you open a new file, and create a box to snap to, does it crash? ...also, don't be bashful about posting your computer specs.

[artyvisual]

Interesteing testcase, thanx fot this tip. It works indeed with very simple geometry.

It is running on 1 gb, 2,2 dual core pentium.

I only can't imagine that snapping will increase much of the internal memory bank usage,. I gues I am wrong. I checked the memory and CPU usage when I move over geometry with and without snapping turned on, and the CPU increases tith 30% but I can´t see any change in memory use.

[Crazy Homeless Guy]

Ok, how about turning off 25% of the layers, and snapping around then, does it crash? If not, then turn those layers off, and turn on the next 25% of the layers. ..does it crash? Work through the file. When you find where it crashes, then turn on one of those layers, until you figure out where it crashes. Then if you isolate something on a layer, see what you have there. Chances are you have a corrupt piece of geometry, you simply need to identify it by slowly isolating the probelm.

[danb4026]

The further you are away from Coordinate 0,0,0 the more finicky snaps get and likely to crash max.

[Chris Johnson]

Well that is not surprising.

 

In case you didn't know, computers can NOT store all Real numbers. Even floating point numbers cannot all be represented in a computer with finite memory:

 

Wikipedia says this about floating point numbers:

"The floating-point format needs slightly more storage (to encode the position of the radix point), so when stored in the same space, floating-point numbers achieve their greater range at the expense of slightly less precision."

http://en.wikipedia.org/wiki/Floating_point

 

As for the crash, if you can reliably reproduce it a clean copy of max I would definitely be interested in fixing it.

Remember a reproducible scenario is NOT like this:

 

" make a box and snap something over there and here and it will crash"

 

It needs to be something like this:

 

1. Start 3dsmax

2. create a box near 1000, 1000 (x,y coordinates).

3. turn on 2.5D snaps

4. turn on vertex snaps, turn off ALL others.

5. bla bla bla.

6. click (Left mouse down)

7. drag (bla bla bla - don't release mouse button)

8. release left mouse button over bla bla bla.

 

RESULT:

 

crash with CER.

 

Thanks everyone:

 

Chris Johnson