PDA

View Full Version : Is max just teasing me:S?


backspace
03-03-2003, 07:25 PM
Hello.

I'm having some kinda strange problems working with polys in max:S, HERE (http://www.jodedera.com/comegato/wt.html) are some screens to better ilustrate it. The thing is while I'm modeling anything with polys....really just suddenly the mesh gets all damaged:S edges appear out of nowhere and when I try to remove this...evil edges it just doesnt do anything, I select them, click on remove and nothing happends. This happends ONLY with polys, mesh seems 2 work well(but I hate them)

So I think...hmmm well the max installation got damaged somehow....so I reainstall it (btw this is max5)...the problem continues, so I try to go back to max 4.2.....and in max4.2 the SAME thing happends:surprised , so could it be my windows instalation?, maybe, so I reinstall xp (obviously having to reinstall every app again) and...the same happends:S so at this point I'm desperate and stick another hard drive in and install windowsMe just to try.....install max 4 on it.......and how can it STILL be doing the same weird error?????

So at this point I know its not max's installation, its not a version bug, its not a damaged .max file because this happends with just ANYTHING I try to model even on new files, its not a videocard issue (since in Me I obviously installed different drivers) and its not my windows intalation or version.

So.....is it time to go out and sell my soul to get a new pc cuz its a hardware issue? wich would be kinda strange cuz other from that my machine is running flawlessly ( but if so what piece of hardware?) or this is just some sort of evil curse that some of you might know the spell to brake it?


I'll light a candle for any help from you guys
:p

dogz
03-03-2003, 08:04 PM
hmm never seen that befor...does it only happen with shapes like that?..was that a lofted shape?..any plugins installed?..my only theory would be that max is trying to compensate for polygon tearing..ie if a single polygon is warped and stretched to far.. its creasing angle can only turn an bend so far..but if its none of those things i would say ignore it if it doesnt affect your final result..in meshsmooth..other wise give discreet a call

Rhid1en
03-04-2003, 09:24 PM
hmm... what exactly did you do between shots one and two. Is it and extrude and bevel, or you just simply moving the verts? Maybe if you can explain what you did between the two, I can give it a quick test run to see if I'm getting the same results and hopefully a solution for ya?

backspace
03-05-2003, 04:49 AM
thx guys

Here's (http://www.jodedera.com/comegato/wt2.html)another example so you can see a little better whats going on, as you can see this time it was just a regular sphere with a ffd and then converted to poly, deleted some faces and everything was fine, then just ROTATED THE VIEW :surprised and that edge appeared from out of nowhere....no, actually if you take a closer look its not a new edge, it was the one conecting the vertex to the one next to him, that suddenly broke himself and got connected to a random vertex on the upper side of the sphere.

Now as I said if I try to remove this edge OR even try 2 restore the lost connection with the right vertex nothing happens, but if I select the weird edge and press del on the keyboard it does goes away (along with its entire face) but this.....I dont even know how to call it...error?, just happens then with the next vertex as you can see from the third picture, and I can just keep deleting and deleting faces and the problem just moves but doesnt go away and sometimes it just gets worse, finding like 5 of this "rebel edges"

hmmm I'm sorry I'm trying to explain this as best as I can but as you probably figured out by now this is not my first language

dogz: no, it does it with just anything I try to model with polys, it can be just a simple box and eventually its going to happen. That wasnt a lofted shape, just a poly that started as box, its not a tearing compensation as you can se from the new example and it does affect horribly the final smoothed result

Rhid1en: what I did was probably just change selection type from vertex to edge or something, no real mesh editing was going on, but yes it sometimes happens when just moving a vertex or conecting or doing just about any poly operation....or even moving the view:S. About sending you the file wao I reaally appretiate your help but I'm afraid that woukld be just waisting your time because as you can see its with just EVERY poly, even my older models that always worked fine if I dare to open them now and try to do any modification the error strikes again on them.

Everything seems to point to something damaged on my pc. I just cant figure out exactly what could it be.

A friend of mine guessed it could be my cpu not working right with max's polys mathematical operations......dont know.....its an AMD XP1800+ with just a few months of use working at good temperatures, no overclocking or anything and polys worked right before with this cpu.

It has been really hard finding any clues or help cuz most of max experts are just left blank when they see whats going on and just dont have any idea cuz it doesnt seems to be a 3dsmax bug or anything and technical experts have no idea of what I'm talking about polys and edges and stuff and as I said it's the only thing wrong with my pc.

: (



:hmm:

-=InQ=-
03-05-2003, 10:40 AM
MAX - SUX!!!!
I'm fed up with it completely!!!

I had this problem too. You must convert your object to editable mesh, select the stupid segment and press INVISIBLE button and then convert it back to editable poly. This should help.

Good luck.

TimWoods
03-05-2003, 11:16 AM
i get a problem too when i use the slice modifier on a mesh.
sometimes it blows the mesh apart making some edges visible and some not welded! and it only happens on some meshes. it doesnt effect the slice on edges, but just polys. i have to go back around and weld and hide. very annoying. it happens everytime i use it on this one particular mesh.
im stumped. just getting used to working around it.
backspace your problem sounds very weird too, much more seroius than mine. might have to re install max and see if it keeps happening.
(also a consideration is the max version your using, some warezed copies of max can be dodgy. )
:shrug:

gaggle
03-05-2003, 12:04 PM
I had a similar-sounding problem once where my meshobject would just suddenly start to disintigrate. I could be doing anything really, and bam, a face was lost. Or ten. Or half the model. It wasn't pretty.

It vaguely helped when I collapsed the object.

Anyway, as it turns out it was my operating system, I was using Windows 98 at the time I belive. Not so pretty obviously, those OS' just couldn't handle the ram-requirements of MAX, it ended up making the computer unstable.

Now, you mention you've reinstalled everything, including the OS, and you've used what I assume is one of the NT based products, so it's not that simple in your case. But maybe it could still be a RAM thing? Faulty RAM sort of thing confusing MAX to the point of face-dropping-ness?

If you hit google you can search for free RAM testers that could maybe give a clue if anything interesting could be found in that area...

Just a random thought..

CGTalk Moderation
01-14-2006, 12:00 PM
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.