HWA Doesn't Help

[Jaffob]

It says 9.0c or something like that.

[Bruto]

If you don't upload the app or a file showing it's slow... will be hard for us to test and try to find what's wrong.

[Stephen]

If you don't upload the app or a file showing it's slow... will be hard for us to test and try to find what's wrong.

What he said.

stephen1980

[Dynasoft]

Press Win+R, enter dxdiag.
Check for "System->System information->Direct X"
If it's below DirectX 8, you're screwed.

That's wrong.
You can have Direct-X 9c installed (and probably do, as it comes with Windows XP and above) on a graphics card that doesn't support it.
The only real way to find out is to go to the display page of dxdiag and run the Direct3D tests. I think the "DDI version" on that page could be your graphics card's hardware Direct-X version support, but I'm not sure. The tests will definitely say.

[Pixelthief]

even so, as pointed out, theres a million possible reasons for slowdown while scrolling aside from lacking directx support.


if your game is something ridiculous like a 100000x100000 area level size, I would expect it to run slowly. We'd need to know more about how it works or what kind of limits it is pushing, like large amounts of backdrops or active objects

[Looki]

Ugh... I knew it. It had to be wrong. Whatever.

[Sphax]

if your game is something ridiculous like a 100000x100000 area level size, I would expect it to run slowly

I don't think the size of the frame impacts the scrolling speed. For example, you can create infinite sized frames and the scrolling will still be smooth (it's how ijiwaru works).

[Looki]

The maximum size is 32767x32767, I think.

[Sphax]

Yes the maximum defined size of a frame is like you said but you can set the Virtual Width and Virtual Height to -1 and you'll have an infinite sized frame.

[Pixelthief]

yes but what I'm saying is if you stretch every ability of MMF2 to its limits, there will be slowdowns. For example, if it has thousands upon thousands of objects, loops, extensions, etc. And things like giant play areas or ridiculous collision mask arrays only serve to exacerbate this; after all, a 32767x32767 area that had obstactle data filled in for every pixel separate would take 500 megabytes, wouldn't it?