On running an application I was working on in 1.5 in 2.0 I get a message when I try to open it that it needs:
scrollbar.mfx
dsound.mfx
browser.mfx
browser2.mfx
I expected to see .cox files listed.
Suggestions???
Printable View
On running an application I was working on in 1.5 in 2.0 I get a message when I try to open it that it needs:
scrollbar.mfx
dsound.mfx
browser.mfx
browser2.mfx
I expected to see .cox files listed.
Suggestions???
On running an application I was working on in 1.5 in 2.0 I get a message when I try to open it that it needs:
scrollbar.mfx
dsound.mfx
browser.mfx
browser2.mfx
I expected to see .cox files listed.
Suggestions???
As long as you have those extensions copied into the "mmf1" folder (which is in the extensions folder), just click retry and it'll load fine. At least that's what it did for me.
As long as you have those extensions copied into the "mmf1" folder (which is in the extensions folder), just click retry and it'll load fine. At least that's what it did for me.
MMF2 can't use MMF1.X extensions (unless they're converted_.
because of that, if you put your MMF1.x extensions in the MMF1 folder it will load the old MMF file but won't let you run it until you get rid of all MMF1.X extesions in the game/program
MMF2 can't use MMF1.X extensions (unless they're converted_.
because of that, if you put your MMF1.x extensions in the MMF1 folder it will load the old MMF file but won't let you run it until you get rid of all MMF1.X extesions in the game/program
Well this sucks. My application is dead with MMF2.
Clickteam need to take better control of the COX extensions. I have felt this for a long time.
MMF 2 should be able to load MMF 1.5 extension converted or not. Didn't anyone in the alpha or beta test groups bring up this issue. This causes a real problem.
Well this sucks. My application is dead with MMF2.
Clickteam need to take better control of the COX extensions. I have felt this for a long time.
MMF 2 should be able to load MMF 1.5 extension converted or not. Didn't anyone in the alpha or beta test groups bring up this issue. This causes a real problem.
good point. they should have backward compatibility,
the .gam files still work fine, so why not the .cox?
good point. they should have backward compatibility,
the .gam files still work fine, so why not the .cox?