Printable View
Does anybody know of any bugs or reason why I would be getting this? Everytime I run my program it comes up. It is still pretty small and I have made much larger programs with no problems.
Error message: Multimedia Fusion Editor Runtime has encountered a problem and needs to close. We are sorry for the inconvenience.
Any help would be nice.
i have had this happen to me before.
The problem is knowing when to expect it to happen.
First find out why the error appears and what causes it.
Then try your best to avoid doing the same thing again and work your way around it.
I have tried various things and it seemed to work but then broke again. I will keep seeing if there is anything else to do but it kind of sucks with this program not having much too it.
You've not given sufficient details on how to re-create the problem. My best advice is to ensure you have the latest build of MMF2 installed.
I don't really have any more information to give. I am using many counters that are set to gradient bars and that's about it.
It could be one of many things, and the size of the program doesn't matter (sorry if that sounds obvious :) )
What have you added to your program lately?
For instance, I had the same thing happen to me the other day when working on my level editor for my platformer.
I added an extra couple of layers to the editor, and changed the default size of the allowed map, so the binary file went from being 10x10 screens with 3 layers (an array size of 192000) to 20x10 screens with 5 layers (an array size of 640000), and although I adjusted everything else, I didn't adjust the size of the array.
This meant that every time I ran it, the program tried to access parts of the array that was out of bounds, and I got the same crash you're getting, but I knew it had to be something I had changed recently, so it was easy enough to find.
BTW, if you don't already, I would suggest getting into the habit of incrementing your saved backups, and noting down on a piece of paper what it was you chnged for that backup.
i.e.
game1.mfa - blah
game2.mfa - added rotation formulas
game3.mfa - updated scrolling routines to use a momentum camera
game4.mfa - added my new "half life 2" engine extension (wouldn't that be something)
I don't use the auto backup, so I can keep track myself.
Anyway, good luck finding it.
It's probably something simple and obvious....but only once you've found it. :)
Krush
This might not be alot of help but here's a problem I had with this.
I had a small space shooter I was working on, and everytime I died the screen would go crazy when the frame reset. Turns out I was using the Lives object and didn't "set" the number at the start of frame.
My eyes were telling me I had the Lives in the code but when it looped, Bam!
Simple problem, drastic results.
Okay I removed pretty much everything that would do something and it still won't start. I fixed it at one point by changing something but then it happened again and undoing what I did didn't fix the problem. I will check my version but I always update the program.
Okay this is messed up. I went to an earlier revision when it was working and I am running into this issue when I do just about anything. I want to make an object invisible I get the error. I swap to lines of code that are right next to each other I get the error. It looks like I won't be able to recover from this problem.
How about uploading the mfa file and I'll see if it happens on mine.
If it does, then I'll see if I can find the problem.
Well now I have no clue what's going on. One minute it works. I don't change a thing I get an error. All was fine a few days ago and now I can't make this thing.
I have all the updates and still this occurs. There must be some greater power here stopping this from happening.
Could you post your game in the File Archive section?
If the crash happens when the frame starts and your frame has a fade-in transition, then verify that the "Create before frame fade-in transition" property is selected for all the extension objects that are referenced in expressions in Start of frame events. Otherwise the application will crash, as the extension objects are created by default after the fade-in transition.