MMF2 Ghost code... or something causing corruption

[IXIStreakIXI]

That's all right and fine but the autosave doesn't address the bigger problem. I know you guys work hard on your product and I'm sure you want to make it top notch. I've been having this weird funky problem since the TGF days. Whenever I mess with sound stuff... lots of other code becomes corrupt or starts working funny.

[Novabrain]

Are you using build 248? Found over there --->

Also, for Clickteam to solve a problem, our programmers need to see the file in question. It is difficult to ascertain what the cause is without examining the actual .mfa.

Thanks.

[IXIStreakIXI]

Yes, I was using 248.

I'm sure you guys don't want to go through over 2000 lines of code. I just find the corruption rate in MFA's to be pretty high, is all. It's kind of bad knowing you can't truly work on a huge project when you feel like it's going to corrupt eventually.

[Stephen]

I have maybe encountered 1 or 2 corruptions my entire time of usinf MMF2. I really don't think the "corruption rate" is that much to worry about.

stephen1980

[00J]

Pretty much it's your coding ability.
If you do a lot of Messy coding your bound to break something in MMF or any language.

If you have a Sloppy development routine, then you can't expect to proceed very far without some sort of problem.

-Your computer could be lacking resources, memory, have an internal glitch, anything, you don't want to work on the same project in the same session for hours or days without saving at least every 30 minutes at minimum, your computer is a dynamic machine that is constantly fluctuating and working behind the scenes.

-Do you save over the same file? Instead of Saving different copies of the file incrementally? For instance, Project Build 001, 002, 003, 004. Not Project Build 001, Project Build 001, Project Build 001, and in your file folder you have just 1 100 mb file, that has been written over 1000 times? [laugh]

-Sorry to be so harsh, but before you commit your time and effort to a large game idea or project, you really need to have a clean [as possible] development routine.

Most people that post problems they think concern the actual MMF software usually have terrible coding habits. Just history.

The only reason this conclusion is jumped to, it's frustrating yeah, but there are lots of measures YOU can take and develop to make building a large project fun and non-irritating. Don't punish yourself. [eek]

[Zabooza]

lol, i havent encounter this before.
the only thing close is that sometime mmf2 would delete an entire object

that is why you keep backups. I used to keep 100, but now only 25

[Zenoff64]

I backup my projects religiously. I'll have multiple backups per day, depending on what I did. For instance I might have a file named:

mygame - BACKUP - 5-3-2009 - 12-00PM

And have one for other times of that very day. That way if I go about changing things I won't lose much if something goes haywire.

Ditto. I do the same thing, but I save them all to a raid array, so if one of the drives kicks the bucket, there's a mirror drive still kicking till I get a replacement.

[00J]

CD-R's, Zips, Multi-Gig Hard drives, DVD-Rs, Cloud Based Server side storage... There's no excuse today to not have redundant copies of very important accomplishments... [laugh]

I'd never have created anything if I didn't save as often as I change or test some new idea...