MMF2 Build #253

Hello all, i just started an old mfa program of mine and noticed this update. i allow it and wait a moment and then i realized hwa version is gone. reinstalled b251hwa and tried again but this time watched background (mmf folder) and deleted again "mmf2hwa.exe"
what can i do for that? anywhere i can find hwa253 version ?
and sorry for my poor english, please use simple sentences that i can understand easy
good night all

HWA is merged into build 253 now, they are the same EXE.

ok then, thank you very much

HWA can be accessed by choosing Direct3D 8 or Direct3D 9 display mode in the application properties.

Just noticed this for the Flash runtime. The "Mouse is within window" condition which was added in b252 beta4 won't work as expected, if I hold down the mouse key and move the mouse out of the window the condition returns true.

That is a limitation of flash that cannot be avoided :\

Heya, I've been having trouble reinstalling MMF2 and updating it since I had to nuke my old laptop. I can install it fine from the CD with one of my two keys, but I can't update it whether from autoupdater or this download- both say that I simply don't have it installed or that its an unknown version. The cd came with V239, but I seem to be stuck with that until I can update it somehow. I looked through the registries, and I couldn't find a clickteam folder under local_machine at all, which seemed odd.

Humm actually disregard that. Oddly, I eventually got it working when I reinstalled using the 2nd of my two cdkeys that you guys had sent- I remember there being some mixup with the boxes. But for some reason, the original key would let me install MMF2 just fine but wouldn't update, whereas this one updated. Ah well, works now

Quote from LB

That is a limitation of flash that cannot be avoided :\

Ah, thanks for letting me know.

is possible to install 251 and 253 at the same time?

Quote from SortaCore

HWA can be accessed by choosing Direct3D 8 or Direct3D 9 display mode in the application properties.

I have a question about exactly this. Previously I was developing my project with the HWA beta and I'm pretty sure I was using DirectX as nothing else really worked. Now, using DirectX I have none of the acceleration and I've noticed a very big drop in framerate in most of my levels.

I'd have no problem switching to Direct3D, except that subapplications don't work with it from the get-go. Apparently, I can create a new sub application once my project is in Direct3D mode and then can check "display as sprite," but I have a good 22 frames each with very complicated rules for the subapplication object, and I can't just go to each frame and check "display as sprite" on my subapp objects because it's greyed out on these.

Basically, I want to keep using hardware acceleration, but now must switch to Direct3D for this, but this means I have to replace all my subapplication objects and rules in all of my frames. Is there an easier way? Or can I somehow roll back to the HWA beta which was working fine for me?

Build number of DLL is old when used /DIB option and displayed in titlebar.

Quote from Yves

One thing was different in the HWA version though, and that could explain your issue. In this version, the collision routines and the collision detection events are better optimized than in the standard version.
...
Possible solutions :

1. You can force the HWA runtime to work in DirectX mode with the /DDRAW command line option. To run your application in DirectX mode from MMF2, just put /DDRAW in the Command Line box in the properties of the application. When you redistribute your application, add /DDRAW to the command line in the properties of the shortcut to your EXE.

Thanks very much for the quick reply, this explains it... Yes, my application is running in full screen mode. I'll try your suggestions.

I tried the /DDRAW command line option, and it slowed everything to a crawl (down to single-digit FPS.) For some reason, DirectX is still the fastest display mode in which everything works.

I tried a few test things to get the subapplication working in Direct3D- I could uncheck the popup window thing, check "display as sprite" and do a few other changes to make it work in this way. I could get it to work, but my application (specifically, my subapplication) makes extensive use of displayed list objects, which do not work in Direct3D. I didn't want to go through the trouble of converting my whole application to work in Direct3D if this part would always be broken.

So, is there any way to make list objects work in Direct3D mode? Alternatively, is there a way to roll back to the HWA version I was using previously? Honestly I would love to have this running in Direct3D 9 for best performance and compatibility, but if that means redoing all of my game I don't think it's worth it.

Quote from Yves

Ah, yes by default /DDRAW is DirectX+VAM. Use /DDRAW /NOVR for DirectX, sorry.
They work in windowed Direct3D mode, they don't work in full screen Direct3D mode. If your app is in full screen, use the tip I gae you above to switch to full screen via a launcher application.

Okay, I tried the windowed launcher method as in the example you posted, and while subapps and lists do work, it now crashes to desktop on the first real level screen. I'm currently looking at four versions of my project:

1. Launcher + Direct3D 9. Works fine until you try to play an actual level, then crashes immediately.

2. No launcher, DirectX. Works, but has a noticeably lower framerate (~10 fps hit, nearly unplayable)

3. No launcher, /DDRAW /NOVR command line. Same framerate issues.

4. An older version that I built with the HWA beta I was using on 12/5- Runs full screen, full fps, no crash to desktop, no complaints

Simply put, I wouldn't have installed this latest MMF version if I'd known that it would have caused this much trouble with my project; I would have finished it up in the legacy version and then fully updated MMF. At least wait until the project was done. Is there any way I can roll back to the older version?

I can provide the .mfa files and exe if you want to look at them, but it's a huge project and the compiled version from 12/5 is 10.5 MB as is. There is a lot going on in the code and picking through it might not be totally instructive.