Mobile ports is not match with runtime . I'm really tired...

Hi,
50 custom animation ? have you make an animation engine ? With so many animations, i suggest you to do so. I did that with active picture, a list with the parameters of each animation (basename|direction|number of images|delay|type of animation(simple, loop, ping pong)).
0) maybe
1)there is a topic on that. little search
2)i make games with more than 1000 events
3)don't understand what you want to do ? levels ? ini or array are good for that. And to populate a level, level editor is the only way.
4) experience ! even with other middleware !
5)...
6)Fusion is for all games.
7)use an engine that you know perfectly.
Fusion 2.5 is already a good choice. Fusion 3 will be more powerfull... no doubt !

Instead of telling that you have many problems, please consider to show one problem by one problem to us. I am sure one of us can helping you.

Yeah i completely get the frustration, sometimes there is a bug on a runtime where it's hard to isolate the cause, and it's easy to blame the development tool.
Here are a couple tricks to prevent these kinds of problems:
- Clean object picks: use loops and for each loops to clearly select which objects are involved, this prevents common problems when multiple things are happening simultaneously.
- Custom movements and animation: Manually set animation frames and exact coordinates using alterable values, alterable values can have floating points, f.ex 4,333 instead of 4, this makes everything smoother and exactly the same on all runtimes.
- Frequent testing: keep running your game on each of the runtimes you need your game to work on while developing, to spot issues before it becomes too complex.

Like i said to you call an image with the active picture or use a part of images of an active object (between im0 et im24, it is stand, im25/im48 walk animation etc...). Very simple.

3) Use an engine to draw only the window for the collision. Call the gfx only for the windows too.
4) you have no choice to test your app in the device ! this is the same with ALL the middleware (and with direct programming too) ! You can not ask the same with a PC than a phone ! And the runtime is different too. So, it is normal that there is some difference.
Build your game for the less platform. Use correct sprite size (power 2). Don't destroy, create many items. Try to make less test of collision (the less overlap test you can ! use collide instead).

+1 with softwarewolf : be careful with loop too.

I don't know much about the mobile exporters but it honestly sounds like the phones you want to try them on can't keep up with what you want to do.
Much like any other port i think you have to dig into your code for each system and optimize it in how it's read and executed. I dont think there ever will be a unified exporter that works for everything from the start.

I have a really simple game on google play(van damnation) that i made ten years ago. Exporting it to Android took some work as i had to rewrite a lot of it even though it worked fine on pc. It's to be expected if you havent built the game for android from the ground up

All engines have their own problems with every runtime they export too. There is no single engine that just works for all platforms, although some might have more features that correspond across different runtimes. it is a little bit of a simplified (and misleading) statement that you can "write once and publish anywhere." In a literal sense, yes you can. But if you want to take advantage of the strengths of each runtime, you have a lot of work to do.

I work on all 3 platforms you mentioned and have done my best to make my main game code work consistently across them all. I have 4000+ event lines as well. The real hassle comes with using services like Game Center or Google Play, and dealing with UI adjustments to meet compliance rules.

Some things to remember:
- Put your code in groups and disable anything you don't need running. Only enable groups of code the moment you run it and disable it immediately after it is no longer needed.
- For Each loops should be used when possible for mobile.
- Always develop for mobile first. if you plan on mobile and PC, PC should be the last platform you add features for. And like everyone said, export to the mobile device often to make sure you didn't introduce something that causes a cpu hit.

Games like Flashback should be simple enough to make for mobile. So I don't see that choice of game style being the problem.

Are your problems performance related? Or simply you get buggy results in your player movement? Without seeing your code it is hard to understand the problems.

As for loops, I have no problems using both fast loop and for each loops in the same project. But you should try using for each loops on operations you do often that are processor intensive ( for example: distance checks between objects). But if performance isn't the problem then you probably are fine without changing your loops or groups.

my suggestion, is find an experienced person you can trust, and show your code to that person who is willing to help track problems or offer suggestions.
* the active picture method, would require an whole game rewrite.~sometimes you may have to rewrite from scratch on a few occasions.

I have actives with nearly 50 animations in them. That shouldn't be a problem. It does mean that every animation frame is loaded into memory when that active is present. But unless you have 10+ enemies with that level of animation complexity running at once, I don't think you will have any problems. but since your problem is not performance related, the animation discussion is not important. If your problem is movement code, then that is a problem most likely related to your coding. Or rather, some coding style that the mobile devices don't like.

I remember that I once coded something for a Windows & Android game and I did some comparing stuff. Sometimes I noticed that >= and > was both possible on Windows to get the exactly same thing, but for Android only >= did the job. I assume this means that you really have to code things differently for Android sometimes. You just have to find the events causing the issues and replace them with Android compatible events.

After looking at the mfa, is your problem that you are trying to use the virtual controls and aren't getting anything to happen? All your movements use inbuilt clickteam movements, so I can't really help you out. I never use inbuilt movements, but it seems to run exactly the same on my Android tablet as it does on Windows. It just seems like the code is not completely written yet to make things work.

I honestly can't make the shooting work on PC either. It just looks like you haven't coded the inventory correctly. This is just badly made code, not a problem with an exporter. Maybe you need to explain what the inventory should be doing and we can help with a fix or an example. Inventories can work a million ways...