MMF2 HWA - Build 251

Hi everyone,

The HWA version of the build #251 of MMF2 HWA is ready :

MMF2 Standard
MMF2 Developer
TGF2

This version replaces the build 250 that has been deprecated. More info about the non HWA fixes in the MMF2 forum.

Let us know if any problem with this build, thanks !

Yves.

Previous version


Bug fixes and new features in this version


- HWA Runtime: crash when switching to/from full screen when an object contains a fade-in transition and the window (and the frame) has been resized with the Resize Frame Window action of the Window Control object (this issue might also happen in other cases).


Bug fixes and new features in previous versions


- Effect editor : double-clicking in effect list now opens or closes folders.

- Data Element Editor : new Effect Files tab.

- Stand-alone apps : graphic filters are automatically included if the application contains actions to load images as effect parameters.

- Runtime : when the Change Resolution Mode option was selected, the size of the window was wrong when you switch to windowed mode.

thank you :)

Just a question, if 250 was still in prerelease, shouldn't this just be 250? Instead of skipping 250?

Well, we had released 2 bugged pre-release versions of the build 250, so to be sure everybody gets updated when the final version is released we have decided to release it as build 251 (I think the automatic update system doesn't support sub-version numbers, I've to check that).

So we really should be at build 252 if you want to be technical since it's not a version number but a build number.

Either way, Click Team is awesome and has busted their back ends and it shows. (not to imply anyone said different)

I want to thank Click Team for all the effort they put in to this product, it has come a looooong way and done so much for me and my companies over the last 16-17 years.

So...

THANKS CLICK TEAM!

K

Hmm... after updating from HWA 249 to HWA 251, the framerates in my projects have gone a bit weird.

Normally, when I have framerate set to 60, the debugger shows my FPS as flickering between 59 and 60. Now it flickers between 58 and 64, or 57 and 63, or any combination of those. The result is that it looks like every 10 or so frames are skipped. Games with scrolling twitch annoyingly. I can't remember this ever happening in older versions. I tried opening several projects and running them, and I get the same weird FPS and twitching.

(EDIT 1)
Framerate 50 seems to flicker between 49 and 53 too, though the twitching is harder to notice. It's still there though.

(EDIT 2)
Err, ok, so I tried using v-sync. Seems to work fine now. However, doesn't that drop FPS straight to 30 if it can't keep up with the full framerate? I wouldn't want that, so... >_<

V-sync forces framerate to be equal to the refresh rate of your screen which differs highly.

Unless it's triple-buffered, but it would be mentioned if this was the case. (MMF3 feature perhaps?)

can you please add a action that allows the size of an active object to be changed?

Quote:

---

Originally Posted by Viewtiful

can you please add a action that allows the size of an active object to be changed?

---

You can do this with Set Scale, or there's an object called Object Resizer which will take dimensions rather than "multiply by x" and resize it properly for you.

Quote:

---

Originally Posted by Fanotherpg

V-sync forces framerate to be equal to the refresh rate of your screen which differs highly.

---

In any case, I don't want to use v-sync, but something changed between HWA build 249 and 251, and it makes the FPS all twitchy unless I use v-sync. I'm just curious if that's a bug or a permanent change. Wouldn't want to continue the project in 251 if I'm forced to revert back to 249. D:

There is no change at all in the handling of the frame rate between the build 249 and the build 251. Maybe it's caused by something else (different hardware, different version of Windows, etc?).

I thought about that too, but I can't remember changing anything crucial lately, at least nothing hardware -related, nor have I patched/switched Windows or anything. I simply patched HWA build from 249 to 251 and instantly started noticing the twitching. At first I thought it was a temporary glitch, but it's been like that for a week or so already.

Any chance some other tweak you've applied, to some other graphics -related issue, could be causing this as a side effect?

Almost 0.0000 chance. I'll check the differences between source codes when I fond 5 minutes free, to confirm it.

k, thanks.

I'll probably revert back to 249 for the time being if nothing's found. That should also verify if it's related to the build version. I just can't think of anything else that could've caused it off the top of my head.

Actually, if installing the 249 patch on top of 251 is enough to revert back to 249, then sorry for the trouble, I just tried that and the same glitch is still there. So... it's something else, at my end. *sigh* Dunno where to even start looking... >_<

Looks like I found a solution. Weird though. Apparently right now I need to have my monitor set to match the framerate set in the MMF2 project, to have the FPS not twitch. My screen's normally set to 72hz, and it's never been a problem before when playing 60-framerate games. I set the screen to 60hz, and things seem to be fine now. Shame though. 60hz tends to give me a bit of a headache sometimes.

Oh well, I'll live. Just dropping this by in case someone else has the problem. Try different refresh rates, heh.

*sigh*

That solution was short-lived. Now even that won't work. It's like the FPS has a mood of it own. Tonight it won't work, next morning it plays nice, then in the evening it goes nuts again.

I'll make a separate topic for this. I've spammed this one more than enough. I already tried a full reinstall of MMF2, which didn't change anything, so it's not an issue with this build version.

Is HWA just the next level of MMF2 or is it separate from "non-HWA" releases? I currently have build 249 installed. Is switching to HWA version 251 considered an update or a different type of MMF2?

It is currently a separate runtime in a different version, but almost exactly the same, just extra HWA-only features. You can 'switch' to it just by installing the HWA runtime and using that to open your files instead of the normal runtime. They can still be opened by normal MMF2, you'll just lose any HWA-only features (ie effects) in non-HWA

Anybody notice that if you have the W,A,S,D movement control type and you are repeating a machine gun firing using say [ctrl] and you press [ s ] a movement direction the sound cuts out?

I have sound repeating every 06 milliseconds repeating by holding ctrl, and when i press [ s ] it kills the sound. Is this just on my end or is [ s ] sound? cutting the sound out? never had this happen before.

It's a strafing movement, and [ctrl] is being held down while [s] is being held down.

hmmm after checking the menu, ctrl+s kills samples... hmmm

-fixed it by removing Ctrl+S from menu to cut sounds.

Would it be possible to have the option to allow loading of external effects via the actual .fx and .xml files or text strings?

So basically if you have no shaders on a active etc you could load both files into the exe from a external folder to apply it without adding a shader to the object in MMF2 HWA first.

This would be useful for things like a shader editor/browser program for example so you could load in effects or code them and see how they look.

I'm experiencing a bug in the latest HWA build (251).
I had previously assumed it was a bug in Werbad's 3D shader, but I've just noticed the same thing happening in Sphax's Crop shader.

Basically, the shaders only work perfectly if I either set the blend coefficient to something other than 0, or set the RGB coefficient to something other than pure white (even 254,255,255 will work).

You can see what I mean here:
http://cid-b1e7ee094271bbda.office.live.com/self.aspx/Public/brokenHWA.mfa
Use arrow keys to move object left/right.
Note how in the broken version, the point at which the object is cropped, moves slightly.

You can also see what I mean, from my GTA example here:
http://www.create-games.com/download.asp?id=8446
See what happens if you change the RGB coefficient of the wall objects...

Request
"Anti-aliasing when resizing" enable / disable by event or command-line.

from my experience it seems that the image parameter of shaders just doesn't work if you try to alter it through the event editor, at least in built stand-alone applications. typing an expression does absolutely nothing and directly loading an image through the file selector in the event editor completely crashes the game when that even triggers in the stand-alone. the functions work fine within multimedia fusion 2 itself but once taken outside, they will not work period. the last update to HWA was almost a year ago so I really hope things like this get fixed soon since this is a major issue.

Quote:

---

the last update to HWA was almost a year ago

---

There is no separated HWA version anymore, the HWA features are now in the normal version (latest build # = 254).

What build of MMF2 do you use? Have you tried to reproduce the problem with the latest build?

Quote:

---

Originally Posted by Yves

There is no separated HWA version anymore, the HWA features are now in the normal version (latest build # = 254).

What build of MMF2 do you use? Have you tried to reproduce the problem with the latest build?

---

was on 253 when it happened, continued to happen even in 254. seems to just be an overbearing issue and I assume it is a glitch since it only happens in built stand-alones and not in mmf2 itself when testing it.