MMF2 Build 256.34

[danjo]

you shouldnt use global events. or code properly (i bet that one zinged more)

[Kazuya]

Olivier, as the build 256 is closed I won't change anything except for bugs that are specific to the build 256.

Alonso, I think it's a known issue, the effects actions should be disabled for this object.

Hi Yves (I can't believe I remembered my password! I havent used this forum in a long time)

After upgrading to 256.34 the enemy characters fall through the ground briefly then vanish. Not all enemies, however which is strange as they have the same code.

The collectable items seem to be behaving oddly also; they have a gravity and react to backgrounds.

I can upload an exe if you need to see.

Thanks

UPDATE: switched graphic mode to Direct3D9 (HWA mode?) and the problems fixed, however now the pause screen does not work: as it uses SubApps, which are now displaying at default screen size (in a tiny window, within the screen)

[Yves]

Hi Yves (I can't believe I remembered my password! I havent used this forum in a long time)

After upgrading to 256.34 the enemy characters fall through the ground briefly then vanish. Not all enemies, however which is strange as they have the same code.

The collectable items seem to be behaving oddly also; they have a gravity and react to backgrounds.

I can upload an exe if you need to see.

Thanks

UPDATE: switched graphic mode to Direct3D9 (HWA mode?) and the problems fixed, however now the pause screen does not work: as it uses SubApps, which are now displaying at default screen size (in a tiny window, within the screen)

Could you send me an example MFA (not EXE) as simple as possible so that I can compare what's different between the build 255 and the build 256? Thanks!

[Olivier]

I get an ntdll crash whenever I try to add the Game Center Achievements (with an s) extension to a new or existing application. This happens only in the Unicode version of MMF.

[Kazuya]

Thanks for the fast reply Yves

I've done some more tests and found the issue HWA has with my game is collisions: "fine detection" (was turned OFF) for those enemies that fell through floor.
Once I turned fine detection ON, they stopped vanishing.

However, I still have the dilema of having to revert back to build 255 as HWA does not support the subApp object?
As stated before - the pause screen now appears in a tiny 320x200 window regardless of the rest of the game screen size

And I tried putting the graphic mode back to standard (the SubApp works) but now the enemies disappearing issue returns.. regardless of "fine detection"

[Yves]

Thanks Olivier, that will be fixed in the next update.

Kazuya, I still need a MFA (as simple as possible) to see what issues you are talking about.

The SubApp object doesn't work in windowed mode in full screen Direct3D apps, as any windowed object (buttons, edit boxes, etc). In full screen Direct3D apps the SubApp object works only if you select its "Display as sprite" option (which is not compatible with the Modal mode).

[Nifflas]

I can't understand how this is not a new problem, because I never touched the "create at start" box and always used the destroy object at start of frame and it has never failed me up until now.

Yet, I've been aware of it for years. Trust me, it has been there forever, but it depends on the events whether it'll cause a problem or not. You should always disable "check at start" instead of creating a Destroy event at start of frame, unless you have a very specific reason not to. It's more resource efficient to not create the objects in the first place than having MMF2 create them first and then removing them. Even if the difference isn't noticeable, it's good practice.

Of course I want this to be changed, but it'll break our games to make this change in MMF2. This is a fix for MMF3.

[Kazuya]

Sorry Yves, I was trying to hold-out as long as possible re sending the open-source (although I trust you 100% of course, as you helped with my previous work: "Robotopia") but it's difficult to make a "simplified" version of this project as it's so complex and dependant on other frames/ini's etc..

Anyway, I have since fixed the issue here- I created a new active object (after saving in latest build) and pasted animations of the faulty enemy character into the new object, then "replaced object" in the code. So far, so good. No problems. The "fine detection" no longer seems to affect the outcome either, now... (strange!)

And I turned off 3D9/HWA mode, so that my pause system (subApp) works again.

Thank you!

ps I agree with Nifflas, please don't change the "check at start" dynamics; it would break our games!

[Aloan]

Honestly, in my opinion MMF2/TGF2 is as a prayer answer to all gamers who once dreamed to make video games. And I want to thank you dearly, for keeping the 2D love alive.
Sincerely, 2D is beautiful. It brings pixel art to life. And it is a pleasure for all of us fans of the 80's, 90's Arcade Experience! with it, you can create games that reflect the past, until the magic of current 2D games which are as science fiction, for they would have never seen the light of day, if it weren't for you.
Through your program, we can relive and recreate those same unforgettable experiences.
Your programs are the world's best in my opinion and also the easiest to learn.
All I ask is: keep making the hard stuff easy for us as you have done in the beginning, Making ordinary people's dreams become a reality! and please don't abandon 2D. If you ever go 3D, always have 2D even if it means a separate buy.
I hope many more come to find out how wonderful MMF2/TgF2 is.
My love for your programs, since I bought my first TGF in the early 2000's has never faded.
Best wishes!
Aloan

[Yves]

Thank you!