Important Bugs in iOS Export Module!

[Koji_Kabuto]

* Effect Mode: "Set ink effect to Monochrome " does not work properly. In iOS but does apply transparency effect (see flying robot in the iOS and PC screens).

* The touch screen to select different objects ("Follow frame off") in a scrolling game most likely will not work, worsening dramatically if "Multitouch" is highlighted. In my game playing use the weapons on both sides of the screen and move the character with the joystick, it does not use buttons for Fire 1 and Fire 2 for reasons of gameplay. This made ​​me crazy because sometimes it worked and most times not. I thought it was a memory problem, so I gave myself the task of monitoring the Xcode tools and the highest peak was 70 MB, which is not as high and sometimes even the highest peaks Springboard gives my game . So my theory put to test the buttons Fire 1 and Fire 2 and assign them to two weapons that are the same on screen. This works perfectly which verifies my theory.

* The sound system works iOS Runtime different from Windows, if a sample sounds in a specific channel and send another sample to play on the same channel and the first not over, the second not sounds. In Windows if sent immediately to play the second for the first and continues with the new sample we have assigned to the channel. This does not allow such instant weapon switching its specific sound of each. This we have seen in several posts in the forum.

Francois course if you want I can send my MFA and check with the code. It is the same to send you a month ago and you helped me to gain better memory.

If other developers have noticed these bugs, I'd love to share it in this post to help improve the IOS Runtime.

[Koji_Kabuto]

Ready Francois I send my MFA by private message!

[Francois]

I do not understand what is wrong with the touch screen... When you put your finger on the joystick or fire buttons, the touch is NOT registered by the multitouch object.
Can you explain more please?
I'll be away next week..

[Koji_Kabuto]

No Francois, joystick and buttons work perfectly, it's put the buttons to solve the riddle. What does not work well, is the touch of objects under the mouse, notice how the interface is my game. The joystick to operate the main character and seven select objects for the different weapons, if any of these selections with your finger to activate the corresponding weapon. This is what does not work in most of the time and it gets worse if you select the option Multitouch instead of Single Touch (Eye on Multitouch had not set for the interface but for a specific weapon that can handle like a boomerang with your fingers and select different targets).

This all works randomly, but in 90% of cases with the multitouch does not work and 40% does not work with Single Touch, try playing and see what I say. The two buttons on the joystick fire two weapons in the interface, but this always works, does not operate the touch of objects, you can see that with Fire 1 and Fire 2 can keep playing, this of course rules out memory problems.

[Anders]

I think I *might* know what you mean now.

When you press and hold the joystick or action buttons the mouse "clicked" events does not fire anywhere else on the screen.
It doesn't do that because the mouse clicked events only happen for "touch 0" (first finger on the screen). Holding an action button down and then tapping somewhere on the screen does then no trigger any mouse-click event because the tap will be "touch 1" (second finger on the screen).

It might confuse you since the multitouch object does not trigger when you are over the joystick.
If you want to be sure that all touches are detected in your game you should use the Multitouch object to detect if the user clicked/tapped the UI buttons.

Is that what you meant?

[Koji_Kabuto]

More or less is that, and I think this may be the possible error or bug. I will try removing the joystick to see if they work the arms at the touch of active objects corresponding to each weapon.

Andos you had a chance to prove my source code?

Thank you very much!

[Anders]

No you shouldn't need to remove the joystick. Just use the Multiple touch object and use that when testing if the user pressed the UI buttons instead. (also be sure that you set your game to use Multi-touch in the properties)

I'm still looking at your source for your other problem

[Koji_Kabuto]

I'll try and thank you very much for your help!

[Anders]

Did that fix your problem?

[Koji_Kabuto]

Not for long, but tonight I'm with your indications. Indeed, in my game is a video intro MP4, and this bug report here that looks like what I get:

http://community.clickteam.com/showthread.php?t=69911