That link is for MMF2 - not Fusion 2.5
Posts by Techspec
Welcome to our brand new Clickteam Community Hub! We hope you will enjoy using the new features, which we will be further expanding in the coming months.
A few features including Passport are unavailable initially whilst we monitor stability of the new platform, we hope to bring these online very soon. Small issues will crop up following the import from our old system, including some message formatting, translation accuracy and other things.
Thank you for your patience whilst we've worked on this and we look forward to more exciting community developments soon!
Clickteam.
A few features including Passport are unavailable initially whilst we monitor stability of the new platform, we hope to bring these online very soon. Small issues will crop up following the import from our old system, including some message formatting, translation accuracy and other things.
Thank you for your patience whilst we've worked on this and we look forward to more exciting community developments soon!
Clickteam.
-
-
If I upgrade my MMF Developer 2 to 2.5 will my Android Export Module still work or do I have to pay for an upgrade for that too?
-
If you still need this, you can get a program free to do this from Please login to see this link..
-
Anyone know why the touch joystick wont detect "up" ???
When the joystick is touched, the joystick pulls itself downwards making the character crouch.
-
Using the player 1 control you have to define the joystick movement with the button pressed. I only want to define the button press...
Ah, yes I see - didn't realise that you could remove the joystick selection!
-
Can someone point me in the right direction on this one?
Using the touch joystick, the jump button works fine as you can define it for button 1 or button 2 in the properties.
But, how do you define button 2 for punching or firing? -
You need to locate where keytool.exe is installed
(It is usually (c:\program files\java\jdk~\bin\) or (c:\program files(x86)\java\jdk~\bin))
Other words - its in the 'bin' folder of your jdk1.6.0_43 directory. -
Techspec - This thread is over 3 years old...?
Mmmmm, yeh, must have missed the date on that one!
Maybe there should be an archive for old posts like this one...? -
You need MMF2 Developer to do this!
-
I have installed the version 257.17, and the display modes does not work.
If i use a frame 800x600 for my app, with "stretch to Fill" or "Adjust to window size" the screen is cropped on a Samsung Galxy tab 1024x600 and was working properly with version 257.12Try setting the android display to "Stretch to fill" and tick "maximized on boot up", "keep screen ratio" and "resize display to fit window size"
The 640x480 works fine also, so why use a larger display size? -
So, remove the event.
-
Now that I'm home, I'm working on a little bit better version of this. Can someone tell me why I can't make my button transparent so the arm doesnt block out the body of the slot machine?
Try active image instead of bitmap push button. Use transparent background for the arm.
-
Thanks Jahkri, I checked out the example folder and found one that I was looking for.
My copy of MMF2 came downloaded from Clickteam website and when you try to view the examples from the Help it gives an error msg stating "please insert CD 2 in the disk drive".
Manually locating the example folder I was able to actually find these examples. Maybe Clickteam can correct this issue in an update???
Thanks again Jahkri. -
Some visual examples of the problem with Quizzical. It is very awkward.
(Before and after first touch)Try setting the android display to "Stretch to fill" and tick "maximized on boot up", "keep screen ratio" and "resize display to fit window size". Untick "Display status bar".
The nav bar should now be below your app display instead of on top of it.
This works perfectly for me. -
I'd drop the idea. You're only going to end up in trouble for copyright infringement, and besides, you are human, and you are capable of original ideas. Use it. I always thought the Ironman idea had been milked to death already, and basically I don't think we need to see Ironman 3 1/2 or something because I figure the official spinoff videogame is uninspired enough. It's just a disgrace to the conscious thought that people are capable of if they insist on just ripping off what they perceive as a guaranteed winner. Game designing should be an art form or a form of expression, not a means to a quick buck.
I am not trying to copy the Ironman game! My game is totally different and it's not even an Ironman game. I am only interested in the actual mechanics of the background.
-
My Approach would be somthing like this (as MMF2 isn' t a real 3D-Engine, the 3D must be "faked").
1. Have the Background as a Videofile (3D-Rendering of Flight through Level, without any "Gameplay"-Objects
2. Upon pressing "Forward", play the Videofile "forward" from (actual) Position
3. Upon pressing "Backward", play the Videofile "backwords" from (actual) Position
4. You could even simulate different speeds by adjusting the Video-Playback-Speed
5. You can even have some Kind of "Collision-Detection" with the Background by dynamicaly Position and Resize invisible Box-Objects that match the Background
6. All Gameplay would take place in Front of the VideofileCheck out the very old Game "Novastorm" that uses this exact Technique (except you can not "fly back" in the Levels)
Please login to see this link.
With Kind Regards, Jahkri
Cool idea, but I just want to simulate this in 2D???
-
I am trying to make a game with the background moving like in Ironman 3 (Android Game), Please login to see this link. only I need to have the background moving away.
Anyone help with this?
Thanks -
Different versions of Android treat some specific actions differently. One way I have used in Java to get around a similar problem is to start the app with a blank activity (Frame in this case) that sets the status bar to hidden and then goes straight to the next activity. Just something to keep in mind when experiencing weird issues with settings that are set per activity.
Sounds good mate. I will keep this in mind next time I build an app for a device with virtual nav bar.
-
Most phones have a hardware nav bar - so it would only be the models with a virtual nav bar like on the Galaxy Tab 2.7 that could be disabled - meaning not compatible with all devices. And I agree, why would you disable the nav bar anyway...
-
I can accomplish this. PM me if you are still wanting this done. Thanks.