|
Posted By
|
Message
|
Strife
Administrator
Der Dairy Crick
Registered
21/11/2002
Points
2305
     
|
23rd December, 2009 at 21:42:47 -
D'oh geez, my second issue with MMF2 in a day.  So anyway, I loaded one of my MMF 1.5 projects into MMF2, and one of the extensions I was using was DMC2. I completely removed this extension from the game and replaced all of the appropriate events, and it loads and runs fine in the standard version of MMF2. However, when I try to open the game in MMF2 HWA, it still thinks the DMC2 object is there even though it's not. o_o What gives?
I've tried placing CNCS232.dll and bass.dll in the "mmf1" folder, but HWA still gives me an error message. And yes, i'm absolutely sure that all DMC2 objects and events are gone - otherwise the standard version of MMF2 wouldn't have worked either. Any ideas about what could be done?
|
Strife
Administrator
Der Dairy Crick
Registered
21/11/2002
Points
2305
|
24th December, 2009 at 01:19:57 -
After playing around with it a little more, it seems that the data for the DMC2 object is still floating around in the application even though it's not there anymore. I look in the Data Elements editor, and sure enough, DMC2 is listed as one of the extensions. Even if I go back to MMF 1.5 and completely remove the object from there before loading it into MMF2, it still shows up.
Is there any way to forcefully delete an unwanted extension from your MMF2 game, or will I have to remain "infected" with it?
|
Strife
Administrator
Der Dairy Crick
Registered
21/11/2002
Points
2305
|
29th December, 2009 at 14:46:23 -
Sorry for the triple-post, but I discovered a plausible solution to this problem that would benefit anyone who runs into a similar issue - not just with DMC2 but with any extension.
It seems that if I make a new application and then drag all of my frames and global events into it, dmc2.mfx no longer appears in the Data Elements. So if anyone else has this issue, I would suggest doing the same, but drag your frames into the new application one at a time and check the Data Elements of the new application each time to see if the offending extension appears. That way, you'll know if it still exists in a specific frame.
|
|
|
|
Advertisement
Post Reply