Posts by Neildo64

Here is an example you can use.
Please login to see this link.

Check this out for a smooth grid snapping engine: Please login to see this link.

If you just need a steady 360º orbit, then you don't need any physics engine. You can just use some trigonometry like this: Please login to see this link.

I can't help you with your current problems, but if you are developing for Android, you need to develop and test on Android during the entire building process since many of the features/functions of F2.5 either haven't been ported properly or react differently on Android. I have had years worth of work that is near useless because of unforeseen, unexplainable "bugs" (which are usually F2.5 programming oversights during porting certain things - not my fault at all). Looking at your game, it appears mostly simple so you should be able to figure how to get most of your things working on Android, but you can't just develop on a PC and then finally export to Android at the end - it is something that needs to happen from the very beginning, always testing on an actual device, not using the windows runtime for debugging.

Are you using .ogg files? If not, I would try that and see if it fixes the problem.

As far as I know, there isn't a reliable way to use ad networks other than the couple that have extensions. If you have any apps on Android markets around the internet (especially Google Play), you will be contacted by dozens of ad networks, phony rating providers, spammy promotion "companies", etc.

Yes, if you are seeing effects, then of course it is effecting your game.

Yes you can do this. The condition you are looking for is in the Special Conditions ---> Compare two General Values. Keep in mind that when comparing general values (vs other methods of comparing values), F2.5 looks at all instances of the object that is being checked, regardless of scope. So if you have 5 objects of the same thing and they all have different values (in alterable value A for example), if any of the objects fit the criteria of the event, they will all be acted upon. So if your event is "if Alterable Value A of object mod 10 = 0, then set Flag 0 on" and only one of the objects Alterable Value A mod 10 = 0, then the flag 0 = on will apply to all of the objects, not just the one like you might first assume.

Green events are executed immediately and should be the first condition of a given event. The other events go in the order they are listed in the event editor, with the exception of loops (which are also executed immediately).

I would suggest not using any of that built-in counter stuff, like the "Lives" counter or the "Timer". They are basically remnants from days past, back in the early days of Clickteam software, when there wasn't as much control over things. I would recommend creating your own counter (or alterable value) to use as a lives counter and just forget that the built-in stuff exists. That way you have complete control over everything and you actually know what is happening.

You need to export your app to an XCode project and then transfer it to a Mac running the newest version of XCode. Then open your exported project into XCode and export it as an iPhone app from there.

When clicking, you could set a counter/alterable value to a random value (for instance random(3) will return 0, 1, or 2) and after clicking, if that counter is equal to 1 --> create your random object and set the counter back to 0. Now your events are ready to accept another click and possibly create another random object. If you wanted your objects to appear in random locations, you could first create the object offscreen and then set its X and Y positions to random numbers within the boundaries that you want the object to appear. Such as Create Object at -50,-50 ---> set object's X position to random(300)+10 ---> set object's Y position to random(100)+10. Now it will look like the object randomly appeared somewhere on the screen between the areas defined by those values.

It can get rather complicated, and no there is no way to do this directly in the Fusion2.5 editors, but yes, auto tiling be done.
Please login to see this link.
Please login to see this link.
At this point, UWC is outdated and there are much more efficient ways to do some of the things it does, but its still fun to play with and use for simpler things.

I don't know why we are on the subject of API 10 or Admob or Google Play Services because none of those have anything to do with the Chartboost extention or Chartboost SDK in the context of this problem.

I have only seen the problem one time. Just once, there was no close button, and the back button acted on the Fusion2.5 frame, not the ad. Almost all ads are fine and there is a good chance this would be overlooked by most developers without extensive debugging.

It does sound like a chartboost SDK error, but since I don't have source codes, I have no idea how any of that stuff is handled. I would guess the SDK takes care of all that and the extension simply gives the app a place to put the Chartboost content inside of. That is why I mentioned a possible safeguard against it, but hopefully if it is a Chartboost error, they will have it fixed soon.

Wolkam, I see your post is talking about a fix for portrait mode so I just wanted to clarify that this happened to me while in Landscape mode, so this isn't isolated to Portrait mode. I'm not sure if that matters, since I don't know how the source code handles that, but I thought I should mention it.

Who did make the Chartboost Extension? I though it was probably you, Fernando.

I have been using the Chartboost extension to show interstitial ads. I have not yet released my project, but occasionally I forget to re-set the ads to test mode (because it changes back after a while) and so I see an ad. I have seen a lot of test ads, and a few real ones, but for the first time, today I saw an interstitial ad that had NO CLOSE BUTTON and NO WAY OUT of the ad. Back button presses and other functions worked normally on the app, which was behind a dark overlay with the interstitial ad on top. The ad remained across all frames while navigating back and only disappeared when I left the app. There is nothing wrong with my code - it is all just very standard stuff and every way that the user could possibly get out of the ad has been covered - this is either a bug in the way it is implemented in Fusion2.5, or this is a bug in the Chartboost SDK itself. Either way, this will get apps banned from Google Play IMMEDIATELY if it gets reported or if it happens while Google is testing it.

I recall seeing someone else post recently about having an app banned because Google said their interstitial ads needed to have a close button, etc. but everything seemed fine in their app. I think I have just reproduced that problem, but I can not get it to happen again. This is a MAJOR FLAW and needs to be addressed immediately, even if it is just some sort of hacked safeguard against this. Unfortunately I haven't narrowed it down at all and it seems to be very sporadic since I have only seen it once, and as far as I know, it has only been reported one other time and only because that person had their app banned from Google Play. Google has a very, very screwed up policy for banning users based on little-to-nothing and 3 strikes of any kind, even all at once, will result in immediate account termination and you will be banned forever from making any new accounts. Will someone please look into this and let me know what is happening here or if there can be some kind of safeguard implemented in case it is the fault of the SDK? I will continue to be testing this, and I will update this with any information. If I find out this is a false alarm and I have overlooked something I will make sure to post that here also. I was building with Android API 15 when this happened, but I am using 19 now, hoping that will fix it.

I just threw this together very quickly without naming or commenting anything, but this should help you. Basically all you need to know about this example is that the hotspots for the parallax objects are in the horizontal center, they are 2x the width of the frame, and the left and right halves of each object are identical.

Please login to see this link.