Bug reports

[MattEsch]

Just a few bugs I have come across. I am not sure if they are known of or not but thought I would post it here anyway.

1) 64bit processor problem

It seems that some 64bit processors run the applications developed in MMF2 twice as fast. This happens with or without machine independent speed checked as an option. With 64bit processors on the way in I think it's important to support those machines.

2) sounds cause lag

If you are playing wav, ogg or mp3 sounds, it can create a terrible lag in the speed of the game, but can be solved by playing a midi first and stopping it before playing the sound. I should imagine this one has already been brought to your attention.

3) object creation

If you are creating objects at runtime and your original object is too far from the playfield, it is not created at runtime, or it is created, but is inactive off-screen and is therefore not moved to the correct position.

4) direct x graphic mode

in direct x graphic mode (with or without vram), the left most part of my screen is cut off in low res (320 x 240), but appears to be solved when the window is not centralised.

[00J]

1. You could be the first with that problem. You'll have to test your program and you'd set the game speed your self. Since MMF 2.0 is essentially a C++ program, it should run fine. You've got a frame rate controller setting in MMF editor, and during runtime.

2. I've never had that problem. It could be your sound card.

3. Object Creation; Again you can control every aspect of your application. [confused]

-You can load all objects on call, and set the memory and object properties.

-You can *Destroy objects if too far from frame *Inactivate objects on 3 separate levels [for your issue I would set your objects like this -Turn off Destroy objects if too far from screen --Set Inactivate if too far from screen to -NO- ---Set Load on call to -ON- ----And make your objects Global.

4. Another hardware issue, check your settings. It's your graphics card more than likely.

IMHO.

[MattEsch]

On some 64bit processors (reportedly only 2 so far) the code executes faster. The actual frame rate only makes it slower, but in proportion the events appear to execute twice as many times. This results in things like jumps that are twice the height and moving twice as much in the same relative amount of time.

[Maverick]

I'm running an AMD TL-50 Dual Core 64 Bit CPU and I haven't run into this problem... tested on my Pentium 4 2.4 Ghz Compaq Evo Desktop as well and seems to run the same speed and events appear to executed simultaneously (Had my wife test game on her PC while I tested mine side by side). Though that could possibly just be my engine.

[Yves]

1. Could you post an example of application that would be affected by this problem? I don't see at all why a 64-bit processor would cause this issue...

2. You can't play MP3 sounds with the internal sound filters of MMF2. Are you playing those sound files with a specific object?

[Dynasoft]

On some 64bit processors (reportedly only 2 so far) the code executes faster. The actual frame rate only makes it slower, but in proportion the events appear to execute twice as many times. This results in things like jumps that are twice the height and moving twice as much in the same relative amount of time.

Are these AMD Athlon 64 X2 cpus? Because unless the MS patch (or AMD cpu driver, which includes the patch) is installed, a lot of things get confused and run at twice the speed they're supposed to.

EDIT: The problem isn't 64-bit cpus, it's windows getting confused by having two cpu cores AND dynamic frequency scaling (aka AMD Cool & Quiet).

[Villy]

I have no problems with mmf2 on 64bit.. using windows xp pro x64.
Since the mmf2 apps runs in 32bit mode.

Processor is a Intel Core2duo.