PDA

View Full Version : huge max problem ?!?


baby
09-29-2002, 08:12 AM
yesterday I was working on a model...

at one point max crashed...and...

it destroy all my .max of this model (it was my third save) and all the autoback except the first one (the oldest).

By destroy I mean I couldn't open or merge them after...

I lost a little bit of work...enough to be angry...


so I decided to save on two HD each time...


at one moment it crashed again...and it destroy my last .max (not all this time....), but strange it destroy it on the two hard drive...and also the autoback...


I'm not sure but I think it's happening in max 4 & max 5...


I'm wondering if it could not come from my graphic card...I don't know...

does anyone had a similar problem ?!? or any idea ?!?

gaggle
09-29-2002, 11:44 AM
Ack :(
Sounds pretty screwed up.

What OS are you using? Many of the "MAX ate my homework" incidents I've come across comes from users running Windows 98 or ME.

I've never lost data due to a corrupted MAX file so my experience here is.. lacking. An advice for the future is "remember to save incrementally". Every so often increment the number, so that no matter how bad it goes (baring a complete harddrive failure :surprised) you can always go back a step.

I've changed my keys so that CTRL-S saves incrementally, and SHIFT-CTRL-S saves normally. This way I can CTRL-SHIFT save whenever I've made some tiny change, and CTRL save whenever I feel I've made sufficient progress to warrant a new snapshot of the project (the reason for the unusual key-layout for the ordinary save is that I have a habbit of saving without realising it, and so I don't want to accidentally overwrite a snapshot I may've wanted to keep)

I realise I haven't helped your immidiate problem.. I.. hope you can move on and eventually scratch this one up to a lesson well taught.. saving often, and in many files, is a trait most MAX users learn at some point...

baby
09-29-2002, 11:52 AM
well I'm someone who saves a lot !!!! because I really don't like to loose stuff !!!
I can have up to 60 files for a character...with autoback ect ect...


but this time it's quite weird...I mean OK it crashes and corrupt my file why not...but how can it corrupt my 3 last/old save !!!!
:thumbsdow :thumbsdow

that's why I really don't know where it can come...

I was thinking it could be my HD....that's why I started to save on 2 HD....

but then it corrupted my files on both of them !!! :surprised


since this morning I didn't have the problem...I open the PC just in case it could be a heating prob...but I don't think so...

now each time I'm saving, I'm doing it on 2 HD, then i try to open the saved file and If it's ok I send it to me by mail...just in case in 2 hours it screw my old files again...

:eek:


Geee I love 3D but I don't like to deal with F*** computers....

derelict
09-29-2002, 03:17 PM
Hi!

there could be 4 areas to look at 1) RAM 2) HDD 3)Software glich 4) CPU heating - Slim chance though

Test your RAM. there is a utility to test the latency and read/write in your RAM.

2) HDD, Lost clusters do happens due to overheating during prolong usage. So get a fan if this is the problem.

3) Software glich - there is a hi potency for max to be cranky. like running a plugin and later nulling it without saving; or holding it as a file later calling it back. Well, that happens when i was using max 4.

4) Add more fan (open up your chasing for a day and see what happens)

I know these are extreme measures. It might help you narrow down the problem.

:)

All the best!

baby
09-29-2002, 03:20 PM
Thx derelict...

how can I test the ram ?!?!?



your cluster/heating idea could be...



hello to your cousin !!! ;)

RealThing
09-29-2002, 03:58 PM
Get this program and run it on your computer http://www.memtest86.com/

Jed
09-29-2002, 05:11 PM
Do you have enough space on your C: drive ? max swaps the file on your boot drive when it opens it, no matter how much swap you defined on other drives. So if your file is , say, 50 megs, you need to have 50 megs on your boot disk, or you'll get a file open failed error. It may be that your file is getting larger as you work along and then gets too big to be opened after a while.
Just an idea, but if you have a small boot partition with just your OS, this could be it.

Good luck

baby
09-29-2002, 05:18 PM
:((

my file was 500Ko

with 700Mo on my C:



perdu, concurrent suivant...

:applause:

Jed
09-29-2002, 05:22 PM
Damn,

what error message do you get when you try to open it ? Also do you work in poly, cause they can be nasty sometimes, especially with meshsmooth on top of them.

... on va bien finir par trouver :curious:

spacefrog
09-29-2002, 06:36 PM
This is a known situation with max, if you are lucky enough the fileheader is ok ( looks like it is, cause max dedects the files as max-files)
Things to do

* make a backupcopy of your autoback folder in the Max dir
* start with a fresh maxsession and try to MERGE the file
* if it crashes on the complete merge, try to merge one object after the other, if it crashes on a specific object i guess you will loose this one but can save the others

had such problems a few times but could always get away with at least an older snapshotfile

;-)

derelict
09-30-2002, 02:02 AM
Helo baby,

http://www.simmtester.com/

It is an ok tester, it will log all the shadow and stresses on it too.
I have another but it test too long but very comprehendsive.

Oh, she will be in france soon! I will keep you posted.

cheers!:)

gundog
09-30-2002, 05:30 AM
the one time i had problems with saving corrupt scenes, even with backing up on other drives, was due to one faulty ram module. i pulled them all out. tested them one at a time and RMA'd the bad one. sometimes, those ram testing programs, for whatever reasons, don't detect the defect.

derelict
09-30-2002, 05:44 AM
Hmm.. it could be a ram test that only check for parity and not the shadowing. Usually parity check is good enough but like you said it, it sometimes just don't detect the defect.

Go to the site i've posted above, it should b good enough 4 most test.

Fozzie
09-30-2002, 02:34 PM
Actually its a known issue that if you are low on space on your drive C: (or whatever your primary swap drive is) and try to save your file, the file will end up corrupted and gone. This is due to a lack of memory available when the file saves and "poof".

700mb of space avialable on your Drive C is not enough, free up some space, or set your swap prefences to a local drive that does have lots of free space available.

Foz

baby
09-30-2002, 05:06 PM
Fozzie at work I've got 60Mo free on my C: sometimes less :eek: :eek:

and no problem at all :annoyed:

CGTalk Moderation
01-13-2006, 05: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.