Why does Move keep wigging out on me??

[secretasianman]

did you make sure that you reference coordinate sys is set to world or view?

[gmask]

what are your system specs?

[halo]

try using view as the basis, rather than local...happens to me as well...local axis just get "stuck" and things wont budge. I also have things moving in the y axis only to start moving 1/2 way through in the z or x randomly...it even does it when i use the transform rollout...or the other fav one of max's is to move something, then the app forgets where u moved it to, and jumps back to the last position when u move it again....max 4...a milestone in programming..:S

[gnarlycranium]

Switching the transform coords (local, world, grid, elephant butt) doesn't change a thing. Neither do the axis constraints.

Turning on Snap can help, if there's nothing around for it to snap TO, it will move like normal... but this only works in certain situations.

My system is dual 1ghz Pentium IIIs... 512 megs of ram, Geforce2 MX video card... though I'm not sure what that could have to do with it.

And yeah, I'm running 4.2. No plugins.

[gmask]

Originally posted by Gnarly Cranium
My system is dual 1ghz Pentium IIIs... 512 megs of ram, Geforce2 MX video card... though I'm not sure what that could have to do with it.


The geforce 2 is pretty old and not supported.. dollars to donuts I bet that is the problem.

[Marcel]

The GeForce is definitely not the problem, until a few months ago I worked with that card without any problems whatsoever.

Maybe a Reset X-form on the object will work?

[gmask]

Originally posted by Marcel
The GeForce is definitely not the problem, until a few months ago I worked with that card without any problems whatsoever.


That may have been the case but I doubt you were using the same exact combination of motherboard , operating system and software version as this guy. .. I could be wrong but with other aps this card is way out of date.

[gnarlycranium]

No doubt, the Geforce2 DOES cause me problems, but I don't think it's the source of the Move issue. Rather, it's the source of my "AAARGGGGH!! WAKE UP AND DO SOMETHING AND QUIT JERKING YOU PIECE OF SHOOOE!" issue, when I'm trying to work with a 300,000 poly scene. :annoyed:

And gmask-- I ain't a guy. :cool:

[Dave Black]

Hey, Gnarly, have you been having these problems in the past, or has it just started?

Also, does it do the funky mouse dance when you have just an empty scene? I'm wondering if perhaps it has to do with the sheer size of the file you are working on...

Video could be a cause...And what better excuse for your boss to buy you a new video card? :D

Hope we can get that worked out...I know it's frustrating when you can't work as quickly as you normally can.

-3DZ

:D

[gmask]

Originally posted by Gnarly Cranium
And gmask-- I ain't a guy. :cool:

Okay that he/she person.. I wouldn't know your gender either way???

[tcomputerchip]

Did you try getting the latest patch for 4.2 (I think there are two for the 4.2, AMD and Intel patch). Otherwise, I would consider getting a better card, I had that same card and I replaced it with a GeForce 4600ti 128meg (awsome performance!).

I have a test for you, try taking a simple few objects (sqare, sphere) make sure you have a small to medium amoun in the scene. About 1000 - 5000 polys.

Then, take and animate all objects; it does not matter where, just make sure they move along a simple path.

Now, just hit the play button with the perspective or camera view selected.

If the animation is choppy in any way, you problem is your modem. Try disableing it, then reboot, then try the same test.

Another solution that I came accross was getting a HD with 8mb cache on board (lowest size 120gig).

[gmask]

Here's antoehr suggestion that often works with other programs.. make new preference files for the program. If this is a problem that has developed recently then in some cases prefs get corrupted and changed in an unfavorable way. Just a thought.

[unrealwarfare]

the same shit happens with me too. Something happens, and moving anything in perspective view screws everything up. i'm not sure what causes it, but what helps me is:

- I right-click on the Perspective label
- Change to any other view
- Change back to Perspective

It fixes the problem until i save or open a new file. (or close and restart max5.1 altogether).

[Maven]

This happens to me when the model is really really far away from 0,0,0.

How far away is it? Move it close to 0,0,0 and see if all is right once agian.

[LORDISH]

Originally posted by unrealwarfare
the same shit happens with me too. Something happens, and moving anything in perspective view screws everything up. i'm not sure what causes it, but what helps me is:

- I right-click on the Perspective label
- Change to any other view
- Change back to Perspective

It fixes the problem until i save or open a new file. (or close and restart max5.1 altogether).

I have exactly the same problem and the same fix for it too heh. Thought it was only me having these ****ed up issues. Nothing too serious though, u can live through it. :)

(Btw running 3D Studio Max 5.1 on an 900mhz athlon, 256 SD-RAM, Geforce2 Mx. As several ppl say the Geforce2 could be the problem. Hopin the issue dissapears when i get my new Radeon 9700 128Mb :scream: )

[gaggle]

:curious:

.. and some say the graphicscard should be the cause of this?

..ihhhdunno.. sounds a little fishy to me.
I can accept that the drivers could be responsible, what version are you running with gnarly? ..Or, well screw that, I don't know about what version does what anyway come to think of it :rolleyes:, but you could install the newest ones and see what happens?

I guess it could maybe be the graphicscard itself.. it just.. seems so unlikely. For what it's worth I had a GF2MX card as my primary card for quite a while, now it's my secondary card, and I don't remember even a hint of the problems you've described.

..format the machine? Begin from scratch, make sure the latest drivers are installed for whatever hardware is in the computer, and see if that helps.. not neccessairly the most fun way to spend a couple of hours though.

[gnarlycranium]

Originally posted by tcomputerchip
I would consider getting a better card, I had that same card and I replaced it with a GeForce 4600ti 128meg (awsome performance!).

That's exactly what I'm hoping to do quite soon! To have to put up with this video card for a year and a half is just criminal. Argh!

Originally posted by tcomputerchip
I have a test for you, try taking a simple few objects (sqare, sphere) make sure you have a small to medium amoun in the scene. About 1000 - 5000 polys.

Then, take and animate all objects; it does not matter where, just make sure they move along a simple path.

Now, just hit the play button with the perspective or camera view selected.

If the animation is choppy in any way, you problem is your modem. Try disableing it, then reboot, then try the same test.

The modem??? What?! :surprised Um... for one thing I have cable... and... what does that have to do with my viewport framerate?



As for the latest drivers/patches.... I doubt it. The comp isn't mine, and my boss doesn't know about that kind of thing. I sometimes tweak stuff myself, but I don't have a lot of leeway to install stuff on it. :annoyed: Which also means reformatting the damn thing and putting on Win2k instead of NT is out, too.


I find it interesting that other people have had this problem too, and with the same video card... maybe it really IS the problem.

I don't think it's the distance from origin, either, I never stray more than a hundred yards or so from that. On the other hand, it definitely does get worse with big files-- I've never had the problem with a low-ish poly scene.

[Maven]

I don't think it's the distance from origin, either, I never stray more than a hundred yards or so from that.

So...try it anyway. Move the model closer to 0,0,0.

Prove me wrong.

[Solesurvivor]

I have a Geforce 4 ti 4600 on a xp1800+ and 1gb of 333mhz ddr ram, and sometimes it happens with me too. it isn't a vid card issue, and it happens randomly.

One thing that helps here from time to time is a zoom extends all and then zoom in again, but there's definately something fishy about this :hmm:

[Dave Black]

I'd say call Discreet.

It's really their problem. Also, check the discreet user forums to see if this problem has already been addressed. If not, report it as a bug and/or call then and complain. It's the only way some things will get fixed.

-3DZ

:D

[gnarlycranium]

Right, right... The next question would be... does anybody have this problem in release 5? If not, then it's already been fixed and I guess I'll just have to shut my mouth. :cool:

[Dave Black]

Gnarly, If you'd like to send me the file, I can open it in R5 and just see if the mouse wigs out.

It's up to you, but it could at least narrow down the problem.

-3DZ

:D

[tcomputerchip]

From what I have been reading, it looks to be a ram issue for some. 3dsmax is prefered to run under windows 2000 with 512 megs of ram or better.

As for the modem issue I brought up, yes, this has happend to several when using OpenGL on some systems. Not just in max, but other OpenGL commands as well.

For some, this has been a life saver.



As for the person with the XP cpu and lots of ram

Solesurvivor I have a Geforce 4 ti 4600 on a xp1800+ and 1gb of 333mhz ddr ram, and sometimes it happens with me too. it isn't a vid card issue, and it happens randomly.

Im not sure what would cause this other than the CPU. I have a 1.6 ghz on my desktop and 2.4 ghz on my laptop (both intel), have not had any problem.

It may also be the Hard Drive or device configuration causing this issue. I know, when I updated my 30 gig 2 meg cache HD to a 120 gig 8 meg cache HD it solved every randering and realtime editing problem I had.

Just a suggestion...

[Alex Morris]

hmmm, this sounds like a combination of video card drivers and max round-off error.

if you cant install driver updates make sure you are running heidi rather than opengl or direct3d.........this is in the prefs on the first tab. This tends to be more stable than the other two.

round off errors are due to the model being so far from the origin that max cant keep its accuracy.........normal symptoms are being unable to zoom extents in the viewports, unable to move objects on screen by one unit intervals (even though you can enter the values in the transform boxes), straight lines drawn in plan show jaggies and move when you pan.

solutions to this are to rescale the model so that it keeps within a reasonable distance of the origin (about 6-7 decimal places as a range usually works OK) and to centre it on the origin by a fixed transform - write it down or script it so that you can reinsert objects created in other packages consistently

[CGTalk Moderation]

This thread has been automatically closed as it remained inactive for 12 months. If you wish to continue the discussion, please create a new thread in the appropriate forum.